Ginsu

I have now done a complete format and Win 7 reinstall. So far everything seems to be working fine. I'll keep you posted. I had hoped to be able to pinpoint something specific to fix and thus help anyone else who has had this problem, but instead I just used the "nuclear option."

STILL having crashes. I have tried the following: using onboard audio - crash using legacy video drivers - crash updating audio drivers - crash unplugging input device - crash reinstalling DCS - crash updated chipset drivers, flashed BIOS - crash Error log attached to previous post, crash attached to this one. I have seen several other posts with this problem (effects.dll). Does ANYONE have ANY ideas about what I might do? Should I reinstall to a different drive/folder? Can I uninstall the codecs that have previously been mentioned as a problem with Creative sound cards? I'm getting desperate. thanks DCS-20091216-225459.doc

Well, several missions into a campaign and I'm having the exact same problem. I'm on the downed pilot rescue mission first campaign and when the guns in the trees open up, CRASH TO DESKTOP! It's worked without difficulty on every other mission thus far, independent of what effects (guns, explosions, etc.) were present. starting to get a bit disheartened with this! EDIT: Same error now on any mission when effects.dll executes. HELP!! Crash log and error log attached. Could you have a look at it and tell me what it indicates? DCS-20091215-032608.doc Error.txt

Success, my friend! Just not sure why exactly. Uninstalled DCS and my audio drivers this morning. I'll list the exact order in case anyone else has the same issue (since I'm not sure exactly which part fixed it). I also installed the game to a NON-SYSTEM drive under EagleDynamics folder and NOT the program files folder. Reinstalled DCS (run setup as administrator) reboot reinstalled audio drivers reboot Launched the game, no lag, no crashes Updated to 1.0.1b (run as administrator) reboot Launched, no crashes Updated 1.0.1c (run as administrator) reboot Launched, no crashes. issue seems fixed, although I'm not sure exactly why. I'm sure it could happen again, so I'll be sure to post if I have any other problems. Now, a few more refresher hours and I'll be ready to start tackling some multiplayer. thanks for all the help.

Dutifully followed your instructions as before, disabling sound in the OPTIONS menu in the game AND in the device manager tab (per your previous link) before starting the game. After disabling the sound in the device manager, I was prompted for a restart, then tried to run the game and got the error "Launcher.exe has stopped working". Repeat, the game will not launch when I have disabled the sound through the device manager AND the in-game options menu. As soon as I re-enable sound through the device manager, the game will launch, albeit with the crash to desktop as previously mentioned. No overclocking here at all. No mods whatsoever. Clean install of both the game and the update. Tomorrow morning, I may remove the game completely and reinstall to see if that does any good. Thanks for your help so far. I love the game - played well on my old system, but this new system seems to have problems with it.

OK. I disabled the sound (both ingame and in the device manager), rebooted, and...as soon as I clicked the DCS icon, an error message came up telling me the launcher had failed and shut down. I did this of course several times to make sure. I re-enabled the sound device through the device manager and DCS launched without problems. However, once in the instant action, I had repeated crashes to the desktop while approaching the town and settling into a hover, NONE of which, I might add, were associated with explosions (crash log attached, same as before). I'm guessing this could have been a SAM launch or other effect associated with the effect.dll that I didn't initiate. Either way, CRASH. So, game won't load without the sound enabled, but won't play without crashing with the sound enabled. I'm ready to troubleshoot - what's next? 121009.doc

I'll try that tonight. My question of course then becomes, if it is related to the sound, how do I fix that?

Ok, no alchemy active, drivers all up to date. Set the sound settings to lower sample rate. At the first explosion, however, it happened. Thinking back now, it is happening EVERY time an explosion occurs, and I think every time there is enemy fire (SAM launch). Crash log again included, but nothing new there, I think. I'll mess with the video settings to see if this fixes it, but any ideas on which specific settings to change? crashlog (2).doc

Doesn't seem to happen all the time, no. It is intermittent. No codec packs installed that I'm aware of. I'll try disabling the sound tonight to see if this solves the problem. One setting I do know of is that I have my default sound device (SoundBlaster X-Fi Elite Pro) set to the highest (studio quality, high sample rate) - Think that could be the problem? I'll try changing it tonight and see what happens.

No mods, brand new computer, clean installation - 1.0.1 as listed, both english versions. Sound and video drivers are up to date. Does the crash log tell you anything?

System Specs Below and crash log attached. It seems as though once explosions or heavy particle effects start up, there is an immediate crash to desktop. No glitches prior to that, temps running fine (28C). Smooth frame rate with all settings to high at about 90fps+. version 1.0.1 DCS Black Shark Windows 7 Ultimate 64 Intel Extreme i7 3.33GHz EVGA X58 3X SLI Classified HydroCopper MOBO 12GB Corsair DDR3 1600 RAM 2 X EVGA 295 GTX HydroCopper GPUs in SLI 2 X Intel X-25M G2 160GB SSDs Koolance Exos Water Cooling DirectX 11 X52 FCS + Saitek Rudder DxDiag.txt crashlog.doc

Well, after playing around with it, I have found that I was holding the cyclic/rudder inputs in just a millisecond too long after trimming and that was causing the helicopter to have a case of the 'yips'. Now I just have to pretend that the trim button simultaneously electrifies the controls and try to let go instantly. If I'm quick enough, though, I don't notice any wobble, so that seems to be the problem - THANKS for the help. Just glad to know I wasn't the only one.

EDIT to original POST 'when SETTING the trim' Not resetting (ctl T) but actually trimming it out. sorry for the confusion

So I've got about 20 hours logged in now (just getting comfortable) and I've had the sudden "I'm now a brick" moment quite a few times due to intersection of the blades - at least a few times it's happened when I've been yanking around on the controls at high airspeeds with severe bank angles or inputting too much rudder. However, I've noticed that I have had consistent problems with blades intersecting when *setting* the trim. I have the X52 so after I trim I center the controls. When I do, there's a second or two of exaggerated yaw (or pitch, depending on the trim configuration) and that's when, if the conditions are right, I 'cross the streams' as it were and begin my rapid descent to oblivion. Has anyone else noticed this or had a problem with it? My main concern is that I'm scared to trim now for fear that the sudden yaw will render my bird a lawn dart. *sigh* Perhaps I just need a few hundred more hours in the pit. Ginsu Intel QuadCore 2 Extreme @ 2.93 Asus Striker Extreme nForce 680i SLI 4 GB Corsair XMS2 Xtreme Memory 2 X NVIDIA 8800 Ultra 768MB 300 GB WD Raptor @ 10,000RPM

Off topic but figured one of y'all can help me. How do I program the right "shift" key into a macro. Whenever I try to program it, it doesn't show up on the command list.