groundobject.dll

[NZgunner 0]

Interestingly enough this is for both SF: P1, where I have lots of add-ons so it could be an object I haven't set up properly, but also for a fully patched 'virgin' (ie no addons) install of WoV (happened just as I was about to land after my 1st campaign mission).

 

I've searched the KB and the only suggestion (for a stock install) was dynamic shadows, but I had these turned on for aircraft only so that is unlikely to be the cause - right?

 

Any ideas on what the issue might be?

[gillg 4]

I to have encountered this problem with the Korean campaign and the six day war. I am running WOE, but i found that only a certain sqn from each of these is the prob. So i repeat NZgunners question.

[Wrench 9,851]

Most of the time, it seem to do this when it's looking for something taht isn't there; either a missing GroundObject or something it looking fr in the terrain folder.

 

Unfortunately, you might have to go line by line in the terrain types ini to see what's missing. Most defintely, check for missing bits in a ground object, or one missing altogether.

 

Wrench

kevin stein

[NZgunner 0]

Most of the time, it seem to do this when it's looking for something taht isn't there; either a missing GroundObject or something it looking fr in the terrain folder.

 

Unfortunately, you might have to go line by line in the terrain types ini to see what's missing. Most defintely, check for missing bits in a ground object, or one missing altogether.

 

Wrench

kevin stein

 

Thanks for the reply Wrench, and almost certainly something to look through on my modded version of SF - but I don't think that's the answer to the problem on a 100% stock, fully patched version of WoV.

 

Can a groundobject.dll CTD come about because of basic stuff like graphics settings?