Ok, so this whole CTD scenario started to bug me - and ultimately motivated me to run some testing. So, based on the error I was getting above from the latest nightly builds, I decided to find out where this error crept in for me - what build started this startup crash I posted above. Starting with the first build of March I downloaded every Windows x86 nightly up until April 30th and began testing each one (each had a freshly copied folder that had my basic GOG install with the bare minimum FSOpen files added so the following versions would work:
3.8.0 with MVPs 2014
18.104.22.168259 with MVPs 3.8.2
Nightly with MVPs 3.8.2
All versions had to startup successfully and load a mission - which I would consider a "win". So after many copies, startups and loads - I finally found the culprit. the April 30th Windows x86 nightly. Everything up to April 23rd loads and runs fine. April 30th crashes at startup with the OP error. In fact, none of the nightly versions after April 30th work for me anymore - they all crash at startup with the same error. Maybe something sinister snuck into the Windows x86 build that was compiled April 30th?
Anyway, in the interest of making FSO better for the community, is there anything I can do to assist? Since I already uploaded a LOG file, is there any other information I can supply or adjustment I can try to to help flesh out this error? I am the only one getting this startup error from the April 30th+ builds?
Please let me know if I can help in some way.
Windows 7 x64 (latest updates)
Intel Core i5 3350P 3.1Ghz
4GB DDR3 RAM (7-8-8-24-1T)
EVGA GeForce 1050Ti 4GB RAM (latest nVidia drivers)