Ricebug on 6/8/2014 at 20:15
Since installing 1.22, my custom gamesys no longer saves. Go to File/Save Gamesys and save. Now, it won't even open up the Save dialog. Went and checked the Date Last Modified on the gamesys. It was dated the day BEFORE I installed 1.22. (No, it's not Read Only, you taffers.)
So all this time, I've been thinking the thing has been saving. But I kept noticing the same custom textures ending up in the Missing tree.
AntiMatter_16 on 6/8/2014 at 20:59
Did you previously have DromEd Basic installed? Are you using the menus that came with Newdark 1.22? They're based on the old DromEd toolkit by NV, which requires all the Cmd files in the root directory. With the DromEd Basic toolkit, all the CMDs have been moved to .\Cmds to clean up the root directory. Reinstalling DromEd basic (or better yet, try the new beta, and give me some feedback =P ) should fix the problem.
Ricebug on 6/8/2014 at 23:44
Well, I'm pretty sure I installed the whole package. And, I was able to save my missions. Suddenly, no save capability, after 2 week's work.
So I unzipped your beta package and now everything is working perfectly. Thanks, AM16.
gamophyte on 11/8/2014 at 08:02
Quote Posted by Ricebug
And, I was able to save my missions. Suddenly, no save capability, after 2 week's work.
I'm relearning after abandoning a missing in 2002... I'm confused, I wanna make sure I got it right; don't you edit and save your fm in ext .cow as you develop it? So you don't need a gamesys until shipment?
fibanocci on 11/8/2014 at 08:12
cow is the preferred format as you develop the mission. Lesser confusion, lesser hassle.
