Jump to content

Philljc

Member
  • Content Count

    26
  • Joined

  • Last visited

  • Medals

Community Reputation

0 Neutral

About Philljc

  • Rank
    Private First Class
  1. Works fine. Like I said its the EXACT same error that people used to get with 4GB, so I don't think it should be classified as some other problem, and like I said it goes away with 4096MB now. Maybe its a brand thing with different RAM? Its Kingston Hyper X if that matters, 4 x 2GB.
  2. Well, in the real KA-50, they weren't made with very good Night Fighting equipment. Basically they hand you a pair of NVG's and say. Here you go. So it could be that, not sure if ACE did anything to edit the Kamov but yeah. lol so in real life, they just send up pilots that regularly crash? Something seems fundamentally wrong with that.
  3. Also, I don't know if its the mod or not but the AI tends to crash helicopters an aweful lot. This happened on the 2nd mission where the helicopter takes off to find you in the night, the one where you have to snipe the officer, and the night mission where you have to blow up tanks. If I hear a helicopter coming, I generally just wait. I know it'll crash and then I'm safe, which isn't what I should be doing but its what happens. They usually just fly straight into things, or in the night mission straight into the ground. I'd say if I tried to watch them do it, it would happen 70% of the time fairly quickly, but eventually it happens no matter what.
  4. The game works fine'ish now with my 4870X2 after a lot of fiddling, but the 8GB of RAM still has to be changed to 3072. So something is definately wrong there. If in 1.14 patch it gave me a black screen with a loading icon when I used 8GB, and it does the exact same thing in 1.15b then it can't be anything else but the same error. Especially since it goes away when I change it to 3072. Thanks a lot for your testing. As this is what I consider one of the most important issues currently seen in ArmA, I will revisit the fix again and retest it with a broader testing HW. Meanwhile, could you please post (either here, or via PM) if: - can you still see the issue with OS RAM limit set to 4096? - what is the amount of VRAM in your 4870X2? 4096 works ( hooray! ) but reverting back to the maximum amount of memory still gives a black screen + loading cursor. The 4870X2 is 2GB.
  5. What missions are we talking about? Stock missions in ArmA, or custom ones? Due to for example the wound system missions will have to be designed with another approach than before, since the whole dead/alive bit isn't black and white anymore, but a shade of grey. Changing triggers from 'No BLUFOR/REDFOR' to other variants, possibly with small scripts connected to them, and more extensive use of radio messages, multiple mission outcomes and such would probably be required to make 'ACE-proof' missions. In the end I really do urge people to get and learn to use the BattleCenter. It might take some getting used to, but it is a very, very powerful tool in mission making, *and* it helps the AI perform better on a large scale by having groups trying to surround the enemy and stuff like that. For traditionalists what I wrote further up still remains true though. One will have to alter the way one designs missions a bit to adapt to the mechanics of ACE, and when that bump is overcome I sure hope it'll be more enjoyable than stock ArmA Stock missions. The one that it last happened on (cant remember the name) but you and 2 others have to go up to a village and kill everyone. The radio comes over with something like 'We have to go in and kill them all, nobody leaves" or something. You are armed with M4's / Supressors. I tried dragging his body to the right spot too, but it did nothing.
  6. The healing system breaks missions sometimes. Twice, when my whole team had to take a position or be somewhere, one of my men wasn't dead (it said he would die in minutes, he never did though) and the only way I could proceed was to kill him myself. Also, I don't know if its the mod or not, but NO MATTER WHAT at night enemies that don't have nightvision in pitch black will ALWAYS see me. I'll be crouching, killing nobody and I'm always at a distance. This is the most unrealistic thing I have come across. Sometimes from even 200 metres away in the dark I will be spotted. You can change it to an easier difficulty but it remains the same. I don't ever remember it being like this when the game first came out, but now I skip night missions because of it.
  7. Philljc

    Advanced Combat Environment

    Thanks. Also, the healing system breaks missions sometimes. Twice, when my whole team had to take a position or be somewhere, one of my men wasn't dead (it said he would die in minutes, he never did though) and the only way I could proceed was to kill him myself. Also, I don't know if its the mod or not, but NO MATTER WHAT at night enemies that don't have nightvision in pitch black will ALWAYS see me. I'll be crouching, killing nobody and I'm always at a distance. This is the most unrealistic thing I have come across. Sometimes from even 200 metres away in the dark I will be spotted. You can change it to an easier difficulty but it remains the same. I don't ever remember it being like this when the game first came out, but now I skip night missions because of it.
  8. Philljc

    Advanced Combat Environment

    How do you select missiles in the helicopters that lock onto targets? The weapon switching button doesn't work like it used to and I'm stuck.
  9. The game works fine'ish now with my 4870X2 after a lot of fiddling, but the 8GB of RAM still has to be changed to 3072. So something is definately wrong there. If in 1.14 patch it gave me a black screen with a loading icon when I used 8GB, and it does the exact same thing in 1.15b then it can't be anything else but the same error. Especially since it goes away when I change it to 3072.
  10. I notice you all keep saying the RAM issue is gone. For the people that saying it is gone, how much RAM are you using? Because with 8GB mine still gives me a black screen. Maybe 4GB is the new limit, or perhaps 6? Either way 8 doesn't work.
  11. Apon formatting I updated EVERYTHING.
  12. Reinstalling the OS to find that the game suddenly runs, even though you are using same drivers and setup as before is a clear sign that something was wrong with your system. Maybe something is still wrong. It could be a hardware problem, for example overheating, CPU or RAM problems. Have you tried running Memtest86+ and Prime95? The patch clearly states what its trying to fix with the 4870, and it hasn't done a good job. I hope the final is a lot better, because I'm sick of waiting for patch after patch, getting a little excited each time for nothing.
  13. Pressing Shift + numpad minus and typing savegame used to work. Now when I do it, it says savegame activated, but in noway can I load that save. Any ideas? Running ACE if that helps.
  14. I have ARMA installed on a seperate HDD (a game one) to the Windows HDD. Would that cause a problem? Should I be changing the page file of one of them or both? Also, unlike older games again, Armed assault doesn't recognise its in a x64 bit environment. Usually games that are meant for 32bit install to program files (x86) - Armed assault doesn't. And at the end of each install I get an error that there isn't enough space to install the game (apparently 960GB isn't enough) but it installs anyway.
  15. Actually Operation Flashpoint GOTY runs flawlessly with everything maxed. As well as Deus ex and a tonne of older games. ARMA a decade old lol? It's like 3 years or so. I tried maxmem, I tried every code I could find. Nothing helps those pop ins, you can see in the vid nothing is lagging you can just stare at an object for up to 8 seconds sometimes until its all fully loaded. I doubt 2GB (or even 1GB) of VRAM is not enough to run everything at high even on 1024 x 768 without pop ins.
×