Game exits when helicpoter crashes/blows up

Many times in single and multiplayer the game crashes whenever the helicopter blows up or I crash. Mostly this happens when I've taken damage as a result of combat.Sometimes this happens if I'm being shot by bullets. If I just ram into the ground on takeoff or over torque and crash the blades together to crash it I can respawn with no problems. Every other aspect of the game is working perfectly. Strange....

The simulation exits and I get a crash message from Windows, the the game reloads back into the menu screen. I can jump right back in and fly again but have to rejoin server/refly mission.

I couldn't find an error log in the game but I pulled this out of the Event Viewer in windows vista. It doesn't appear to be graphics related.

Faulting application DCS.exe, version 1.0.0.0, time stamp 0x48f5b977, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a783, exception code 0xc0000005, fault offset 0x0002f8f4, process id 0x934, application start time 0x01c9543b696b2123.

I got same broblems, saitek x52pro drivers cause that.

Look:http://forums.eagle.ru/showthread.php?t=34155&page=4

Now i really hate saitek .

In the BlackShark folder list at the bottom is a temp folder, in that folder you will find an error log.

Ok. Im now 100% sure that Saitek X52pro causes ctd's :mad:

After re-install i played about 20 missions with my old logitehc joystick. No broblems or crashes.

Then i played mission with my x52pro, when i hit the fly button CTD!! .

I try couple more times, no luck. CTD.

I boot my system and try one more time, now i get to air and when i crash and my chopper blows up...CTD!

I plugged my old logitech back and everything works like dream.

My friend has just same broblem with his x52pro, and again when he uses other joystick X52 (no pro) no broblems at all.

Old or new drives,newinput.dll and so on.... nothing helps It just keeps crashing if x52pro is instaled.

In Short:

Orginal X52 worksor or any other joystick, X-52pro causes random ctd's.. WTF????

Here is my crash.file and Error file.

Many reinstalls -> many deactivations less now. And i still can't play wiht my x52pro hotas.:cry:

-esa

i´ve the same problem with my x52pro and BS. in the moment when i crash or the heli starts to explode -> ctd

my error log:

Error running Config/autoexec.cfg: cannot open Config/autoexec.cfg: No such file or directory

03.12.2008 12:32 V808201900

World::LoadPlugins: Loaded plugin module CockpitBase.dll

FILE NOT FOUND: .\Bazar\Terrain\Map\map_towns_names_en.sup

Dispatcher: initial random seed = 4014688

Dispatcher: apply random seed = 4014688

Cosmos: Mission date assigned - Year:2009, Month:6, Day:1

loaded from mission Scripts/World/GPS_GNSS.lua

Map objects for beacon site Потийский NOT FOUND! Ojbects created.

Map objects for inactive beacon site Мыс Сухумский NOT FOUND! Ojbects created.

Map objects for inactive beacon site Мыс Тарханкутский NOT FOUND! Ojbects created.

Map objects for inactive beacon site Мыс Железный Рог NOT FOUND! Ojbects created.

Map objects for beacon site Мыс Херсонесский NOT FOUND! Ojbects created.

Map objects for inactive beacon site Мыс Анапский NOT FOUND! Ojbects created.

Map objects for inactive beacon site Мыс Айтодорский NOT FOUND! Ojbects created.

Map objects for beacon site Батумский NOT FOUND! Ojbects created.

Map objects for beacon site Мыс Фонарь NOT FOUND! Ojbects created.

Map objects for beacon site Мыс Евпаторийский NOT FOUND! Ojbects created.

Map objects for beacon site Ялта NOT FOUND! Ojbects created.

Map objects for inactive beacon site Мыс Кыз-Аул NOT FOUND! Ojbects created.

Map objects for inactive beacon site Мыс Кодошский NOT FOUND! Ojbects created.

ComplexTask::open_state(). Precached tasks data loading.

ComplexTask::load_task_data(). "Follow_Line" task data loaded.

ComplexTask::load_task_data(). "Follow_Vector" task data loaded.

ComplexTask::load_task_data(). "Follow_Vector_Old" task data loaded.

ComplexTask::load_task_data(). "Approach" task data loaded.

ComplexTask::load_task_data(). "Cannon_Ground_Attack" task data loaded.

ComplexTask::load_task_data(). "Rocket_Attack" task data loaded.

ComplexTask::load_task_data(). "Level_Bombing" task data loaded.

ComplexTask::load_task_data(). "Dive_Bombing" task data loaded.

ComplexTask::load_task_data(). "Missile_Ground_Target_Attack" task data loaded.

ComplexTask::load_task_data(). "Missile_Ground_Target_Level_Attack" task data loaded.

WARNING: multiple connectors "smoke" in model ".\Bazar\Terrain\Structures\High\TEC_A.lom"

WARNING: multiple connectors "RED_BEACON" in model "KA-50"

WARNING: multiple connectors "Gun_point" in model "KA-50"

WARNING: multiple connectors "MAIN_SPOT_PTR" in model "KA-50"

WARNING: multiple connectors "RESERV_SPOT_PTR" in model "KA-50"

WARNING: multiple connectors "WHITE_LIGHT" in model "KA-50"

WARNING: multiple connectors "RED_BEACON" in model "KA-50"

WARNING: multiple connectors "GREEN_LIGHT" in model "KA-50"

WARNING: multiple connectors "RED_LIGHT" in model "KA-50"

WARNING: multiple connectors "Gun_point" in model "KA-50"

WARNING: multiple connectors "MAIN_SPOT_PTR" in model "KA-50"

WARNING: multiple connectors "RESERV_SPOT_PTR" in model "KA-50"

WARNING: multiple connectors "WHITE_LIGHT" in model "KA-50"

WARNING: multiple connectors "RED_BEACON" in model "KA-50"

WARNING: multiple connectors "GREEN_LIGHT" in model "KA-50"

WARNING: multiple connectors "RED_LIGHT" in model "KA-50"

WARNING: multiple connectors "Gun_point" in model "KA-50"

WARNING: multiple connectors "MAIN_SPOT_PTR" in model "KA-50"

WARNING: multiple connectors "RESERV_SPOT_PTR" in model "KA-50"

EagleFM initialize time .. 403.062959

DXDefTexture: failed to load Ka-50 font lamp.tga, D3DXERR_INVALIDDATA.

Chunk is not present: ABRIS/Options.lua

ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Options.lua

Chunk is not present: ABRIS/Database/NAVIGATION.lua

ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Database/NAVIGATION.lua

Chunk is not present: ABRIS/Database/ROUTES.lua

ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Database/ROUTES.lua

Chunk is not present: ABRIS/Database/ADDITIONAL.lua

ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Database/ADDITIONAL.lua

ABRIS load default failed Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Database/ADDITIONAL.lua

Chunk is not present: ABRIS/Loader/NAVIGATION.lua

ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Loader/NAVIGATION.lua

Chunk is not present: ABRIS/Loader/ROUTES.lua

ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Loader/ROUTES.lua

Chunk is not present: ABRIS/Loader/ADDITIONAL.lua

ABRIS load default Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Loader/ADDITIONAL.lua

ABRIS load default failed Scripts/Aircrafts/ka-50/Cockpit/ABRIS/Loader/ADDITIONAL.lua

Cockpit::avDevice::link_all: no such device in hash - 'ARCADE'

Cockpit::avDevice::link_all: no such device in hash - 'MRP'

Cockpit::avDevice::link_all: no such device in hash - 'ARCADE'

Cockpit::avDevice::link_all: no such device in hash - 'PADLOCK'

Cockpit::avDevice::link_all: no such device in hash - 'PADLOCK'

Cockpit::avDevice::link_all: no such device in hash - 'MRP'

Cockpit::avDevice::link_all: no such device in hash - 'MRP'

Cockpit::avDevice::link_all: no such device in hash - 'ARCADE'

loaded from mission Scripts/Aircrafts/ka-50/Cockpit/ARK/ARK.lua

Cockpit: ccClickable.cpp. Custom data unavailable

cockpit initialize time .. 3441.750628

input layers loaded :

Aircraftka-50

Ok heres my crash logs so far. I don't believe they are related to the Saitek but who knows. Most of them are access violations that point to wRadio.dll,World.dll,MSVCR71.dll and ntdll.dll

[ATTACH]22157[/ATTACH]

I don't have another joystick to test this, the dll's seem kind of random.

Maybe someone who knows a bit more than us can take a look at these....

IT IS saitek or saitek drivers.. No crashes or erros with my logitech.

If i install saitek i get CTD and error boxs when i try to quit mission or if i crash.

-esa

Any info,workaround or solution about this bug ???

:helpsmilie::helpsmilie:

-esa

Using the vanilla X52 and never had any issues with beta and release versions of BS. I've heard that the 52pro drivers might be corrupted, I'd suggest you either try older drivers (I'm using the one that come with the CD, 2 years 9 months old) or bring this to Saitek customer support.

I got same broblems, saitek x52pro drivers cause that.

Look:http://forums.eagle.ru/showthread.php?t=34155&page=4

 

Now i really hate saitek .

Same here. I also suspected saitek drivers. Looks like I was right.

Using the vanilla X52 and never had any issues with beta and release versions of BS. I've heard that the 52pro drivers might be corrupted, I'd suggest you either try older drivers (I'm using the one that come with the CD, 2 years 9 months old) or bring this to Saitek customer support.

No help, old drives installed, CTD and error box. wtf..

Well i just have to buy ch producs or thrustmaster :cry:

Or maybe install windows vista ?? :music_whistling:

-esa

No help, old drives installed, CTD and error box. wtf..

 

Well i just have to buy ch producs or thrustmaster :cry:

 

Or maybe install windows vista ?? :music_whistling:

 

-esa

No issues with mine. :smilewink:

No issues with mine. :smilewink:

So you have Vista? and x52pro?

What drivers (version) are you using??

:helpsmilie:

thanks .

-esa

Possible FIX need a dev to look at

I have isolated the problem causing the X52Pro crashes on my system.

I ran a few test flights with different configurations to see if I could figure out what is causing this.

It is because of DirectOutput. The game is using the DirectOutput SDK to send the infamous "RULLEZ !!!! SAITEK" to the MFD on the joystick and turn one of the fire buttons yellow.

If I go into Windows Task Manager under the services and manually stop the service before playing the game (SaiDOutput) this will prevent the MFD from operating BUT NO CRASHES. The profile will still work, just that there will be only the default display on the MFD.

[ATTACH]22234[/ATTACH]

It is easy for me to duplicate, if that service is running, I start a mission, hit eject (via the keyboard)....game crash. Goto SaiDOutput service and stop it, start another rmission eject or get shot down....NO CRASH

I have played many games using this stick without any crash to desktop or exiting etc. But only 1 other game used the Directoutput...FSX

Directoutput is buggy at best DCS shouldn't try to send anything to the stick anyways...that "RULLEZ !!!! SAITEK" does absolutely nothing except be annoying and cause crashes. I hope this gets removed before the English release of this game. The service should be able to run just fine IF the game doesnt tell it to do anything.

If a dev or someone with knowlege of the inner working of the game could kindly tell me which file to delete or which LUA to edit so that I can remove support for the game sending stuff to the stick MFD.

Haukka81 can you also try to disable that service and see if it fixes for you also?

I have isolated the problem causing the X52Pro crashes on my system.

 

I ran a few test flights with different configurations to see if I could figure out what is causing this.

 

It is because of DirectOutput. The game is using the DirectOutput SDK to send the infamous "RULLEZ !!!! SAITEK" to the MFD on the joystick and turn one of the fire buttons yellow.

 

If I go into Windows Task Manager under the services and manually stop the service before playing the game (SaiDOutput) this will prevent the MFD from operating BUT NO CRASHES. The profile will still work, just that there will be only the default display on the MFD.

[ATTACH]22234[/ATTACH]

 

It is easy for me to duplicate, if that service is running, I start a mission, hit eject (via the keyboard)....game crash. Goto SaiDOutput service and stop it, start another rmission eject or get shot down....NO CRASH

 

I have played many games using this stick without any crash to desktop or exiting etc. But only 1 other game used the Directoutput...FSX

 

Directoutput is buggy at best DCS shouldn't try to send anything to the stick anyways...that "RULLEZ !!!! SAITEK" does absolutely nothing except be annoying and cause crashes. I hope this gets removed before the English release of this game. The service should be able to run just fine IF the game doesnt tell it to do anything.

 

If a dev or someone with knowlege of the inner working of the game could kindly tell me which file to delete or which LUA to edit so that I can remove support for the game sending stuff to the stick MFD.

 

Haukka81 can you also try to disable that service and see if it fixes for you also?

Sure! i try it, thanks :thumbup:

-esa

Ok, made two quick tests.

Directoutput killed from task manager. Eject -> no crash

Directoutput not killed from task manager. Eject -> CTD and error box.

I have windows xp.

Great! Now i can use my x52pro :smartass:

-esa

To kill Directoutput permanently it should possible to deactivate the service via the service management in the windows control panel called "Saitek DirectOutput". Not tested yet.

Thanks for the hint. It helps me alot. Had one of these files in suspicion, but no time to test it.

These "Saitek rulez"-message is located in the file x52pro_device.lua. Eventually it's a problem among this file and the X52Pro.lua/X52Pro_num.lua?

So you have Vista? and x52pro?

 

What drivers (version) are you using??

 

:helpsmilie:

 

thanks .

 

 

-esa

No, I have no issues with my CH Products. Control Manager v4.2

To kill Directoutput permanently you also can deactivate the service via the service management in the windows control panel called "Saitek DirectOutput". This helps me alot.

 

Thanks for the hint. Had one of these files in suspicion, but no time to test it.

 

These "Saitel rulez"-message is located in the file x52pro_device.lua. Eventually it's a problem among this file and the X52Pro.lua/X52Pro_num.lua?

I'm going to dig into those files and see what I can come up with. I don't want to permanently disable the display and shouldn't have to. It works fine in every other game and I like to see what the button function is for testing purposes and sometimes forget the lesser used buttons when I program all the modes :P If I can just figure out how to stop the game from sending crap to my stick it should be fixed.

Permanent fix

I went on the saitek site and looked a bit at the DirectOutput SDK forum. To me it appeared that something had to be compiled into a .exe or .dll by a programmer to use this so I did a bit of looking at the files and found this in C:\Program Files (x86)\1C\Eagle Dynamics\Ka-50\bin\stable\lua-direct_output.dll

Only 1 thing I know of even uses DirectOutput...you guessed it...the X52/X52Pro

I removed this file from the directory and tested again. Load mission,eject rinse repeat a few times.

It worked flawlessly with no crashes and I was able to leave the SaiDOutput service running so I can still see the commands and stuff on my MFD. No more dumb message sent to my stick causing crashes.

:thumbup:

Maybe some others can test and verify if this fix corrects the problem on their system and post results?

I don't want to permanently disable the display and shouldn't have to. It works fine in every other game and I like to see what the button function is for testing purposes and sometimes forget the lesser used buttons when I program all the modes :P

Me too ;)

I like the mfd and won't miss it.

But I can verify your hint removing the lua-direct_output.dll. It works great for me. No crashes when big flames appearing/at ejecting and no exception faults, when quitting the game. An the mfd is enabled though! :thumbup:

I went on the saitek site and looked a bit at the DirectOutput SDK forum. To me it appeared that something had to be compiled into a .exe or .dll by a programmer to use this so I did a bit of looking at the files and found this in C:\Program Files (x86)\1C\Eagle Dynamics\Ka-50\bin\stable\lua-direct_output.dll

 

Only 1 thing I know of even uses DirectOutput...you guessed it...the X52/X52Pro

 

I removed this file from the directory and tested again. Load mission,eject rinse repeat a few times.

 

It worked flawlessly with no crashes and I was able to leave the SaiDOutput service running so I can still see the commands and stuff on my MFD. No more dumb message sent to my stick causing crashes.

 

:thumbup:

 

Maybe some others can test and verify if this fix corrects the problem on their system and post results?

I've tested and works fine :thumbup: No Crash so far.Many,Many Thanks to You,Slayer.:smilewink:

Moka(FIN) - Fly friendly skies with Me

Good to hear, I've been able to fly multiplayer now on the 159ths server without crash every time I die. Fun fun!

Slayer, I am brand new to BS. Your investigation has certainly done the trick. I removed the lua-direct_output and not one problem Thank you for your efforts. Rep coming your way. :thumbup:

I enjoy my Saitek, but they must be wishing they never allowed that little trick.

I had the X-45 with no problems. Bought X-52 pro and BS crashed all the time. Thanks to this tip i can play this game. This should be a sticky untill it's fixed.