NZgunner

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?

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?

Hi everyone, I'm just rediscovering SF: P1 after a long break and I have just been amazed at the amount of modding and mission building that has gone on in the last couple of years!!!! When I was last playing, the Burning Sands campaign was still broken !! Anyway I've downloaded the Middle East Wars pack and all the associated files (aircraft, terrain, etc) but I'm getting random CTDs in about half the missions I fly, regardless of the campaign (ie just as likely to crash in the 6 Day War as I am in Yom Kippur). The last CTD coincided with jettisoning the drop tanks on an Israeli Phantom, but I'm sure I've dropped tanks before. I've downloaded the most recent updates for each file and everything was added to a clean install patched up to the last service pack and subsequent patch. I was wondering if anyone else has installed the pack recently and if they found that they had to do something extra not mentioned in any of the install instructions or readmes to get it running smoothly? Any help would be most appreciated. (NB I've also downlaoded the DRV terrain for missions in 'Nam but the only associated campaign (Rolling Thunder) doesn't work properly - any tips here would also be cool)

I thought it might have something to do with updates to *.ini files where the requirements have changed - eg no longer need to update groundobjectdata.ini but need to make sure each new ground object has a new line in its default ini file. It is also sometimes a bit unclear as to where files end up extracting to and I've had to clean up a few that have gone to a default directory rather than into a new custom folder for the object/aircraft. The campaigns aren't unplayable but ithe crashes are annoying.