-
Posts
1016 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Everything posted by ARM505
-
Tired of damage and don't want to restart CDU/TAD/etc.. here!
ARM505 replied to WildBillKelsoe's topic in DCS: A-10C Warthog
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)'.
-
Repeatable Mission Editor crash adding waypoint actions to SU25T and KA50
ARM505 replied to jib's topic in Game Crash
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.
-
Is this a damage model argument, a 'the AI is ludicrously accurate with moveable cannons/MG's', or both? Just trying to classify it into a standard sim argument box.... :) Seriously though, the AI is stupendously accurate with cannon fire (try vs the Hind, or anything that has a cannon/MG that can pivot), locks you up instantly, and always sees you if you're within sight. This has been brought up before.... Sure, you *can* kill them if you're religious about employing the precisely correct tactics, but the point is that the AI will always outperform a human who is tasked to do this particular thing, ie slew the camera around, lock up an air target, which we all know is terribly hit or miss and time consuming, and move the helo into weapon constraints. The hit rate on you from the helo will be incredibly good (beyond what would actually be achievable with a real world system IMHO), and you are fired upon the instant it is physically possible to be fired upon in almost all circumstances. This affects the above discussion IMHO.
-
Frankly, there is zero reason for a sim player to change to Win 8, the only reason I did was because I get it free. All the nuts and bolts that we like to tweak are still in the usual places, except they've made things harder (IMHO) to get to with the newer UI. I could see no real improvement, nor were there any slowdowns though in terms of performance in sims, although one game I play (Company of Heroes) was a but more stuttery when panning around larger maps. Bear in mind I didn't benchmark anything, that's just subjective impressions. On another pc, the Heaven benchmark improved by one (1) point, ie nothing! Both pc's are relatively ok, (Core i7, GTX 580 on main pc, SSD OS drive) but not brand new. Win 8 boots faster, but that is spoiled by going straight to the 'metro' desktop, which is mostly a waste of time. To sum up: I wouldn't murder myself if I had to get a new pc with Win8 pre-installed, but there is absolutely no reason to change at the moment. Win 7 is definitely the new XP IMHO, it should do well for a quite a while I reckon.
-
Most won't worry, but just in case you do, I did an upgrade (if an OS change can be called that) to Win 8 from 7 (ie NOT a fresh install) and DCS World + all the addons ran with no problems. No reactivation needed. Track IR on the other hand.....
-
It's channeling the spirit of the original Steel Beasts? (Famous for having stationary road wheels/tracks) Homage to the greats and all you know...
-
To add to what I already wrote, the playing around I was doing before hand was checking system dependencies for start up (actually I was trying to melt the engines, but anyway). The first thing I did was try a start with the inverter off (APU gen on) with the obvious result. I then tried cranking both engines at once (inverter still off). I then motored both engines individually. Then I wanted to actually get going, so I did my last experiment, and cranked #1 but only turned the inverter to standby when the engine was at max motoring RPM (trying for some kind of hot start). The engine lit normally. So, the status is: APU running, gen on. Inverter to SBY. Engine #1 running, but gen off the bus. Fuel boost pumps on. I then tried to start # 2, no joy (cranked, but no light up). Tiny daughter then demanded attention (she who cannot be denied!) and I had to stop. Wish I'd thought to record the track. Still don't know if I did something stupid. No random failures.
