D3D Error in BOS

[brrmatteo]

Hello, when i launch this game (steam edition) i get D3D Error:"Can not create direct3d device d3derr_invalid call".

I tried to check and reinstall directx9. Can you help me?

[NobbyNobbs]

Hi. You can try to use minimal graphics settings.

For that you should find game data directory (for Steam version it will something like ..\Steam\SteamApps\common\IL-2 Sturmovik Battle of Stalingrad\data)

open file startup.cfg with notepad.exe and manually set graphics settings like this:

[KEY = graphics]

adapter = 0

desktop_center = 1

fps_limit = 60

full_height = 768

full_width = 1280

fullscreen = 0

gamma = 1.00000

mgpu_compatible = 0

multisampling = 0

or_enable = 0

or_ipd = 1.00000

or_lens_offs = 1.00000

preset = 0

vsync = 0

win_height = 768

win_width = 1024

[END]

Edited April 14, 2015 by NobbyNobbs

[BradMick]

I'm in the same boat. Tried the config trick, no change. Tried un-installing/re-installing...No change. Reloaded DirectX...no change. The game worked fine and then bam, every time I go to actually fly in game D3DErr...

[Jarhead1]

I updated my Nvidia drivers to 350.xx and got the same D3D error.

Apparently there is a conflict with this game and Nvidia Geforce Experience. The Geforce Experience program loads with the Nvidia driver package.

I deleted (uninstalled) Geforce Experience via the Control Panel and all is well.

[Urra]

Is this true only for steam?

[Jarhead1]

The  Nvidia driver package has nothing to do with Steam (if that's your question).

[Urra]

The Nvidia driver package has nothing to do with Steam (if that's your question).

Thanks,

I have most updated driver and everything works for me...so curious.

[CAN_Yeager]

I got same problem and I have the non steam version. I will uninstall Geforce Experience and report back.

[TG-55Panthercules]

IIRC, there was some other issue a few months ago (can't remember whether it was about TIR or maybe SweetFX or something else not working) where the culprit turned out to be the GeForce Experience software and uninstalling it seemed to do the trick.  Whatever it was, apparently the problem got resolved at some point because I've been back to running the Experience software again for a while now and everything seems to be working OK, and I can't remember the details.

Edited April 22, 2015 by TG-55Panthercules

[BradMick]

I'm still having this issue. The game just updated with an almost 1GB patch and I still get:

 

D3D_ERROR

 

DrawIndexedPrimitive FAILED:

D3DERR_INVALIDCALL

 

I can get through the menu, select a quick mission, load the quick mission but as soon as I jump into the cockpit, I get the above message. Fresh install, reinstalled DirectX...fully updated Nvidia drivers, tried the resetting the config trick...Deleted the GeForce Experience...no change in status whatsoever. 

[71st_AH_Mastiff]

did you make changes in your graphics terrain ini file? if so, change the LOD load to under 9 I changed mine back to 7 and works.

 

My game runs great with the new drvrs and GeForce experience.

 

under your data\graphics\terrain.ini

 

PixelSize=50 //meters

 

 

LodCount=7

 

 

texlod=8192,8

 

texlod=4096,8

 

texlod=4096,8

 

texlod=4096,8

 

texlod=8192,8

Edited April 22, 2015 by 71st_Mastiff

[BradMick]

Yup. No change. Based on the error, DirectX is having issues finding an object, this isn't a texture issue as far as I understand this error. So changing resolutions or anything like that isn't going to fix the problem. 

 

A little MSDN: https://msdn.microsoft.com/en-us/library/windows/desktop/bb174369%28v=vs.85%29.aspx

 

So, the issue could be that it's not at the right index point, it could be that it's not loading the necessary geometry...anything under the heading of that article is a likely culprit. I know from a programming standpoint I've gotten the error if I've mislabeled something or flubbed a number. Why this would just randomly start giving me this error makes no sense to me.

[CAN_Yeager]

I had to replace d3dx9_42.dll and d3dcompiler_43.DLL in my windows/system32 folder andin my syswow64 folder. I used DLL fixer software to save time. I usually don't purchase this kind of software but it was 30 dollars and it fixed a bunch of other stuff and made replacing the DLL files super easy.

[71st_AH_Mastiff]

I had to replace d3dx9_42.dll and d3dcompiler_43.DLL in my windows/system32 folder andin my syswow64 folder. I used DLL fixer software to save time. I usually don't purchase this kind of software but it was 30 dollars and it fixed a bunch of other stuff and made replacing the DLL files super easy.

wow and you probably only needed to reinstall the distribution pack from inside the game, could of saved ya some money there.

 

*:\SteamLibrary\SteamApps\common\IL-2 Sturmovik Battle of Stalingrad\_commonRedist

 

inside this folder are common DX and dotnet VC reinstallation programs that run C++

and such for common graphic games. Most gaming companies now include this in there file structure.

Edited April 23, 2015 by 71st_Mastiff

[Zappatime]

I had this same D3D error after trying to start the game following the big update today; I went into my data/startup.cfg file and set the resolution settings to my native res (1920 x 1200) - I had been using a DSR resolution of 3840 x 2400 and that was the culprit, as to why , I've no idea , but setting to native res sorted the problem ;-)

[Zappatime]

Seems DSR was turned off after new driver install, so the DSR res set in my sartup.cfg was too high to work with 'available' resolutions hence  CTD

[BradMick]

I have an update to this issue. It only seems to occur in the 109F, I was able to load a Lagg-3 with no issues...anytime I load up a 109F, with the headrest removed and white paint scheme (my usual config) I get the DrawIndexedPrimitive FAILED: D3DERR_INVALIDCALL

 

This is now a fresh install Steam version since I migrated my stand alone to Steam today.

 

V/R

 

Brad