Page 1 of 1

Old .opt model - O/S issue?

Posted: Sun Dec 29, 2019 7:28 pm
by Bman
Have a weird situation. Working on an existing .opt model. When I save it after editing, and test it in Skirmish mode, the "old model" still shows up. Even if I delete the model in \Flightmodels folder and go back into skirmish mode, the old model still manifests in-game. It's not write/read-only protected. It's almost a like an invisible ghost shadow copy exists of the model, but I can't figure out where/why the game engine is still using it. This also happens sometimes with .tie mission files.

However, if I rename the edited file to Model2.opt and same within the Spacecraft0.lst file, then the newest version shows up just fine as it should. This seems like an O/S issue to me, but I'm not clear. Anyone have any ideas ? Windows10 x64. Thanks.

Re: Old .opt model - O/S issue?

Posted: Sun Dec 29, 2019 8:40 pm
by Darksaber
Are you sure you don't have the old opt in a different slot with a different opt name?
Or
Do you have the opt replaced with the old opt in a mission.txt file, oh hold on you mentioned skirmish!!!
Or
Does the old opt have an exterior model and your just replacing the base model, so in game you see the exterior and not your new base model, then when you rename your new opt to model2.opt because it doesn't have an exterior opt (Model2Exterior.opt) you will then see the new model.

Re: Old .opt model - O/S issue?

Posted: Sun Dec 29, 2019 10:00 pm
by Bman
EDIT: Figured out the problem. It was the old tool OptGL.exe. This program saved a copy of the older .opt model within /Flightmodels folder perhaps as a 32-bit file (?) that Windows Explorer 64-bit doesn't see, nor with any other editing tool. When I did a file, open, dialog box, there it was listed with other current models but file date was older. Deleted it, closed the tool, and now all is well. AlliED sometimes does similiar thing too. I can see files within it's scope but not by the O/S. :?