Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[SAS~Skylla]

Hi Gents,

I fear I ran into some trouble with IL-2 Great Battles.
Whenever I try to start the sim, I will see the loading screen, then the programm locks up and I get to see the following error message:



Probably this has to do something with the new Graphics Card I just installed (Asus GTX 660).
The latest drivers for said card have been installed already.

Any ideas how to get it going again?

[sniperton]

"I find that if I have 3D Vision disabled in NV CP (NVidia Control Panel) when the game loads, then there is no problem, but if I have it activated in NV CP, and I let it to turn on (normally when game launches) it crashes in the load screen (see sshot). If, as soon as the game launches and the screen becomes black, I disable 3D Vision with hotkey (Ctrl+T) then the game loads but as soon as I hit Ctrl+T to activate it, the game crashes in the same way."
Hope it helps.

https://forum.il2sturmovik.com/topic/42660-3d-activated-crash-on-load/

[SAS~Storebror]

Yeah, probably a driver installation issue.
Personally I always untick all driver parts but the raw graphics driver itself, and the physics extension.
Anything else I untick so it won't even install.

If you accidentally installed the 3D part, you can uninstall it using Windows' remove programs tool.


Mike

[SAS~Skylla]

Thanks for your help Gents.

Yeah, probably a driver installation issue.
Personally I always untick all driver parts but the raw graphics driver itself, and the physics extension.

Well, seems like I made the mistake to let the system look for updates itself. 

I deinstalled the 3D drivers meanwhile, but the issue still remains the same unfortunately.

[sniperton]

Try this:

https://www.sas1946.com/main/index.php/topic,57602.msg640100.html#msg640100

[Blaubaer]

I think I had the same problem:
https://www.sas1946.com/main/index.php/topic,57602.msg636265.html#msg636265

Well, I think I've found the solution to my graphic problems: I have to set "Distant Landscape Details" (BoX graphic setting) to x2 at most (because my graphics card has just 2.0 GByte GDDR5-VRAM). So I can enjoy 60 FPS in every (?) situation.

Maybe you should try this.

[SAS~Skylla]

Try this:

https://www.sas1946.com/main/index.php/topic,57602.msg640100.html#msg640100

success!
The fresh reinstall of the latest NVIDIA driver (without the 3D stuff) finally allowed me to see the log on screen.
Just deinstalling the unwanted 3D Vision driver was not enough.

I think I had the same problem:
https://www.sas1946.com/main/index.php/topic,57602.msg636265.html#msg636265

Well, I think I've found the solution to my graphic problems: I have to set "Distant Landscape Details" (BoX graphic setting) to x2 at most (because my graphics card has just 2.0 GByte GDDR5-VRAM). So I can enjoy 60 FPS in every (?) situation.

Maybe you should try this.

Not exactly, my problem didn't even allow me to enter the game.
But thank you anyway, I will keep your solution in mind and will stay <= x2 when it comes to distant landscape details.
That's even an improvement, with the old GTX 750 I couldn't set distant landscape details to anything above "normal".

Again, thank you very much to all of you

[sniperton]

 

[JollyJack]

  ..... Personally I always untick all driver parts but the raw graphics driver itself, and the physics extension. Anything else I untick so it won't even install. ....
If you accidentally installed the 3D part, you can uninstall it using Windows' remove programs tool.
  Mike

I used to do that too, but found out last week that for my outdated ASUS AMD Radeon R7 360 OC some settings in the Settings control panel makes it able to run 60fps in 1920x1080 without stutters. (In Cliffs grass off)

PS if you have unexpected crashes in Windows 10, it might be wise to edit the registry disabling atirecord. It's a logger that coflicts with certain Windows 10 versions. For NVDIA there is probably a similar edit ... J

[SAS~Storebror]

Mind you that this was a particular Nvidia issue and it has been solved half a year ago.
What you're talking about are AMD quirks and no, there's no similar thing on Nvidia


Mike