Haggart Posted November 20, 2010 Posted November 20, 2010 (edited) Hellas, I'm encountering a misbehaving simulator.exe. OS: Win 7 x64, Admin, UAC is off. System Specifications > Signature. BS fresh install (was previously installed on the system, but cleaned up a few weeks ago). Launcher running fine, initiating a mission -> no mission loading screen, instead instantly a windows-crash-report; after choosing "close program", I'm getting the debriefing-screen. Patched to 1.0.2: Same result and behavior. In the temp-folder, there isn't any error- or crash.log created at any time. DirectX is on actual level, did a reinstall with the june-2010-redistributable. Reinstall BS after uninstalling and cleaning the system: same behavior. GPU-Driver on 257.21, so it's on nearly actual level. System is patched regularly and up-to-date. Simoultanously installed is FC2. Installation is on C:\Spiele\Ka-50\. TrackIR and Thrustmaster Cougar installed (recently tried the TARGET-Software of Thrustmaster, but cleaned it up soon - awful...) Anyone any idea of analysing the behavior? Don't want do an OS-reinstall, I'm totally shirty of that idea at the moment... Thanks in advance.DxDiag.txt Edited November 20, 2010 by Haggart attached dxdiag There's no "Overkill". There's only "open fire!" and "time to reload". Specs: i7-980@4,2Ghz, 12GB RAM, 2x GTX480, 1x 8800GTS, X-Fi HD, Cougar, Warthog, dcs-F16-pedals
Panzertard Posted November 20, 2010 Posted November 20, 2010 You've done most of the things I would have suggested for you. All I can do is to toss a few more ideas for you: - Two or three graphics adapters? - not sure how well DCS manages the situation. Perhaps try with one only? - Got any Errors from the crash in the Event Viewer? See post #4 for tips: http://forums.eagle.ru/showpost.php?p=738777&postcount=4 - Tried without any devices connected? (And profiler software). Disconnect everything. - Tried shutting down your antivirus? - I remember when ArmA had issues regarding 12gb computers - not sure how this is with DCS 1.0.2. Last resort, perhaps take out a couple of the mem-sticks and try with 6gb? - FC2 is working? If so, very strange - basicly the same game-engine in both, shouldn't behave differently. - And not modified any of the files in DCS:BS at all? Not even the controller-config? It's a desperate measure - but at least test with a *super*-clean install, to elimiate any problems with file-changes. The mind is like a parachute. It only works when it's open | The important thing is not to stop questioning
Haggart Posted November 21, 2010 Author Posted November 21, 2010 SLI-System, 2x GTX480. DCS would manage, it had done it before, as it has with the 12Gig... (taking out a couple isn't an option, as it's all integrated in the cooling circuit and atm I can't drain the circuit) Tested it with a super-clean install and without anything but my mouse coonected also allready. Same for av completly down. FC2 is working fine. Eventviewer is totally empty - no crash reported, nothing... thats the misterious thing - it seem's like the sim-exe has just the opinion "I don't wanna fly" and leaves the base directly at the gates allready. SOLVED (appending this because I was in writing the post while testing around xD): I'd gone through my analogue system log I'm writing by hand, where bigger changes are noted. My eye felt on WindowBlinds... That's an uhm... a Make-Up-programm for Windows I'd tested a few days before. By setting the "Deactivate Desktopstyles" and "deactivate visual designs" on the compatibility tab off the simulator.exe, I got it running, even without having to kick WindowBlinds away. So - Problem solved - if anyone encounters strange behavior, try setting this modes! Big thanks for help anyway, Panzertard. 1 There's no "Overkill". There's only "open fire!" and "time to reload". Specs: i7-980@4,2Ghz, 12GB RAM, 2x GTX480, 1x 8800GTS, X-Fi HD, Cougar, Warthog, dcs-F16-pedals
Panzertard Posted November 21, 2010 Posted November 21, 2010 My eye felt on WindowBlinds... That's an uhm... a Make-Up-programm for Windows I'd tested a few days before. By setting the "Deactivate Desktopstyles" and "deactivate visual designs" on the compatibility tab off the simulator.exe, I got it running, even without having to kick WindowBlinds away. So - Problem solved - if anyone encounters strange behavior, try setting this modes! Big thanks for help anyway, Panzertard. :thumbup: You just solved another case with similar issues - WindowsBlinds is the mega-culprit. Thank you for updating us! :) The mind is like a parachute. It only works when it's open | The important thing is not to stop questioning
Recommended Posts