I got the cfs3_vista_win7_corrections files to make my Brit Vosper Drivable MTB's work OK with new Win-7 Premium Gaming machine. In fact, I was successful in making several missions in ETO, and a PT-109 mission set in PTO_Solomons with all of the new O-1 Driver's stuff. Even his new ETO effects.xml file works OK (and a bit better, IMHO) in PTO. Not yet done much with PTO_R-S.
From the readme's, seems he "adjusted" the .cfg file somewhere. But I can't find any major differences in either the .cfg or the .air files. So, here is my question...
I plan to make a PTO_Solomons Iron Bottom Sound re-enactment mission set. I plan to use the older versions of a long-past friend, "Mr. P-M", who built some of the most fantastic drivable vehicles, mobile weapons, flame thrower weapons, and drivable ships for CFS3 that I have ever used. For this Iron Bottom Sound set, I plan to use his drivable Clemson DD Destroyer, and his ELCO Drivable PT Boat. Lots of hacking to make them work in ETO and PTO_Solomons, but... There is possibly the chance that they will do the same nose-over dive when the game is run.
Does anyone know exactly what the "edits" were that O-1 Driver did to the Vosper MTB .cfg and/or .air files to keep this from happening when using Drivable Ships on a Win-7 Premium machine? I would like to do this in advance of builing a very complicated Multi-Battleship and Destroyer mission set, only to find out that the Drivable Destroyer won't work in PTO on a Win-7 machine.
BTW, once I have them fully test flown and refined, I plan to Upload my last 7 ETO & PTO_Solomons mission sets for all your enjoyment and comments.
Glad to be back hacking CFS3, even if not as much as i would like to.