hobbes57

Usually, after ~20 minutes of crackling, sound going on/off DCS crashes. I'm attaching the files from the DCS\Logs folder. There seem to be some sound-related entries but I'm not sure if they are helpful. me.log.txt DCS-20120829-182624.crash.txt dcs.log.txt

Thanks for your suggestions here, RedX. Unfortunately, I have a pretty standard (ASUS + i7 processor) system and never did any overclocking / tuning that I'm aware of. I'll hunt around and look for memory clocking options, see if that helps any. The maddening thing is that this occurs not reliably. About 80% of the time when I play, but sometimes not at all. No direct relation to hot/cool CPU temperatures either, as far as I'm able to observe. Will struggle on.

I'm experiencing the exact same problem here, only with DCS:World 1.2.0, flying the Ka-50. After a while, the sound crackles, cracks, turns completely off and comes back on again to more cackling. This continues even after DCS was shut down. Interestingly, I've noticed the same when playing another graphically demanding game (Empire :Total War). No overclocking of my ASUS board, though. Running on windows 7 64bit. RedX, did you even find a cause/solution for this issue?

Thanks for all your input guys! I guess it all boils down to "how to avoid MANPADs in close quarters", something I'll definitely have to practise. I did dump flares continuously in that mission, but usually the first Stinger launch nailed me - so my flares probably weren't that effective. Does anyone know how "badly" flares spoil a Stinger launch/lock? In real,life I mean, is it more of a 5% or 50% chance? How does altitude factor into this? Woul 10m RALT be safer for me that my current ~150m? Also, should I be moving? To or from the launch area? Does the orientation of my enginer exhausts affect anything? If everything fails, I might just have to use my wingman as Stinger absorber until I can swat the launcher.

Hi guys, I've tried that mission now for the fifth time, having reasonable flying skills and slowly edging my way into combat. Even knowing where the ambush will take place, I alsways get shot down by a Stinger, it seems there's no way to avoid it. Usually, I just hover 2 km out from the village and pour rockets into the bushes when the rebels start firing.... then the Stinger hits me. If I move around, the convoy gets shot to pieces... and thew wingman isn't too helpful either. Any tips for that particular scenario? - Hobbes

Now this is something I'd like to hear in the Officers Club, after returning from a mission: http://www.myspace.com/laminor I just saw these guys play last night and was quite impressed. From St. Petersburg, too. Now, if we could only instruct the ground crew to mount speakers on the outer pylons :)

Problem solved - in fact, it did not even exist. I was editing the controls for the "Mig-29G" while the test mission I flew used a "MiG-29A". After setting the controls on the correct page, everything worked fine. This is probably an argument for having an "all aircraft" controls page though. Nevertheless, thanks for your input here! Hobbes57

Hi all, I have - Windows 7 64bit - a clean install of Flaming Cliffs 2.0 - a Saitek X52 (NOT Pro!) - the Saitek Profile Editor 6.6.6.9 and a problem: I cannot assign anything to the big horizontal rotary, the small vertixal rotary and the small slider on the throttle :( With a new, frewsh and clean Saitek profile, I go to the FC2.0 Options -> Axis page and try to assign the rotaries to slewing the radar cone left/right or up/down. Also, I'd like to map the small slider to Zoom. Once in the game, the don't do anything. Note that the X,YandZ axis of the stick work, as does the throttle. Why doesn't FC recognize the other axis here? Thanks for any help! Hobbes57