ARM505

Flying against the AI is the least convincing dogfight ever. All my years of playing IL2 etc online, I've NEVER seen a human play anywhere near as consistently brilliantly as the AI in terms of deflection shooting, engine and energy management. Sure, humans have their moments - some guys can pull off awesome stuff, but not 100% of the time, and nobody I've ever encountered online is ever as consistently smooth with the aircraft for so long. So - for killing you/putting up an awesome fight, the AI is great. For realism? Not a chance, IMHO.

+1000 internet points to you, that it's. Funnily enough, I deleted the 'autoupdate.cache' file thats in the same folder, but didn't try that one. Anyway, that was fast and sorted the problem out, thanks a lot.

This is the autoupdate.log 00000.000 INFO : === MiniLog opened UTC 2012-11-20 18:46:19 00001.009 ERROR : Caught an exception: Another updater instance is running. 00002.094 INFO : === MiniLog closed. ie basically useless.

During an update by the autoupdater, my UPS decided to die, and the PC powered down. Now, whenever I try to start DCS World, I get the message Error: Another updater instance is running. There isn't any other DCS or related process I can find that is running. The repair option just gives the same error. Multiplayer loads ok. Anything else gives the error. Is this just not a very robust program or am I missing some obvious solution? I've tried deleting autoupdater logs etc, no joy, same error every time.

More expensive, slower, not optimised for gaming at all - I take it you HAVE to use one and don't have a choice? Because if you have a choice, it's an obvious one. My brother had one I think, there's no point for gaming.

GPU normally sounds like a diesel engine running in your right ear. In game, we have a stealth GPU, so thats nice. The new APU sounds pretty much have that shrieking turbine APU sound nailed if you ask me. They can be really painful. Luckily the ones I use are miles away from me in the tail so I don't even hear them at all.

I must say, in that edited image the actual aircraft looks excellent, you really get the impression of an aircraft flying in sunlight. The terrain is a bit washed out though. I guess we can just assume that our virtual pilot has his sunglasses on all the time in game? :)

Total flashback to the IL2 days of deadly AI head passes. One day, maybe 5000 years from now, somebody will code AI that is a bit more human. For now it seems we must make do with 'Harder AI=just more accurate (to superhuman levels)'.

Yup, same here: http://forums.eagle.ru/showthread.php?t=95825 Also using Win8 and Nvidia (GTX580)

Logs attached if that helps. To replicate: Start Mission Editor Add aircraft (used KC135) Go to 'Triggered Actions', select 'Add' Basically any selection from here on in the actions pane will trigger a CTD, ie 'Perform enroute task' etc I've also included a Windows crash file that was generated: \Local\Temp\WERC2CA.tmp.appcompat.txt There is an associated large file as well (32MB+) which I obviously won't attach. I'm using Windows 8 - as far as I've experienced this always causes the CTD when exiting mission, but I have no idea if the above issue is also Win8 related. WERC2CA.tmp.appcompat.txt Logs.zip

Ok, this is actually becoming a bit of a pain in the ass - any progress on fixing this? Anybody? :)

Core i7, Nvidia GTX580. All recent Win8 Nvidia drivers have worked fine, no problems in game, just that post game CTD when going to debriefing.

One day, the makers of Steel Beasts, ARMA, and DCS are going to get drunk and have..........children - we hope :) Actually, a version of ARMA (VBS) can already play with Steel Beasts. So technically at least, its becoming closer and closer to reality. Who knows what DCS holds....

You probably don't want to hear 'it works fine on mine' but....it works on my (and other) installs of Win8. Once you do get it working of course, you'll discover the 'crash on exiting mission' that IS definitely a Win8 issue :)

Depends....if all I have to do is carry it, I'll take the LSW :) Shooting something on the other hand...

The thing is, this used to work, the overhead hatch used to pop open - should be a simple fix.

On ejecting, an AI Ka50 will show the door open in the external model, not the overhead ejection hatch. Sorry if this has been noted already.

Yes! See my post above. It really should be on an axis. :) What you say just makes the argument for this stronger!

OK - last comment for me (I hope) because I've found a workaround that's gone 10 for 10 so far. Just do a couple of alt-tabs back and forth while the the post mission loading bar is showing loading is in progress. While alt-tabbing, DCS keeps trying to maximise, just alt-tab again, eventually you end up at the debrief screen. Worked every time for me so far out of ten or so tries. Could be total statistical chance of course, but anyway.... Edit: FFS, there it goes again. crashing! Dammit.... Sorry :) And yet again: Hmmmm, still having a lot of success with this method.

While we're talking about this, I have a request: PLEASE, please allow mixture to be assigned to a joystick axis. At the moment, we have to crank, maybe prime, switch on the mags once we count six blades, then push the mixture to run. Too much for one mouse! Sure, I could assign the buttons for my stick. But the real thing is a little lever dammit! :)

Well, I just played again and it's back - so for some reason it only worked that one time - weird! And yet another edit: Sometimes it does manage to work, but it's very rare - so far only twice in total.

UNCHECKING the 'disable Aero interface' on my Win8 machine solved the CTD on exiting missions. Logical I guess, since Win8 doesn't use the aero interface. Only had time to test it once, but went from 100% crashing, to working.

Same here, everytime I exit the mission. Edit to add: Also Win8 Pro here. Is this a Win8 thing? Edit edit: Solved my problem, unchecked 'disable aero interface' as per post below. DCS-20121004-074423.zip

Everything is fine....except when I exit the 3D world after playing, DCS.exe crashes with no explanation other than 'DCS.exe has crashed, windows will notify you when a solution becomes available' (as if) or some message along those lines. Not really seeing the fps drop that everybody seems to be mentioning, but it's not like I had some kind of benchmark or anything. Core i7 950 @ 3.08 GHz 6 GB RAM GTY 580

This was actually the most painless OS upgrade I've ever done. I actually set up to reload a whole bunch of 9mmP during the install, and I didn't even get as far as priming 100 rounds! TrackiR works after disabling forced driver signing, HOTAS works fine and all software worked fine first go. Can't actually complain I suppose.