Caradavin on 20/8/2013 at 02:52
I have been working all night customizing the basic DEDX01 gamesys that comes with Dromed Deluxe. After getting everything in, I began to realize something was wrong. All of the extras that come with the DEDX01 gamesys were not in the object hierarchy. (i.e. MageX, BugbeastX, and all Xobjects). I used ObjTree and it showed that those items were indeed in the gamesys but when I saved it as a different gamesys, it only kept my changes and the DEDX01 items were gone. Now, all my gamesys files are identical to one another (and none of them have the DEDX01 gamesys original items!!! What could be going on here? Is version 1.21 not compatible with Dromed Deluxe gamesys? I can't figure this one out. :wot:
kdau on 20/8/2013 at 03:53
That's very strange indeed! DEDX should work fine in NewDark. I'm not sure what you could do to fix it, but this might actually be a good thing. Several bugs have cropped up over the years in the DEDX gamesys, and it's not really recommended anymore to use it directly. The preferred option is to copy the specific archetypes, etc. that you need from the DEDX gamesys to your own. If you don't need a lot of things from DEDX, you should now be able to do just that. (If you're ever starting from scratch again, the version of dark.gam in AntiMatter_16's (
http://www.ttlg.com/forums/showthread.php?t=141121) Thief2 Fixed is a better choice of base than even the stock T2 version.) If you need many DEDX archetypes, I hope someone else is able to help you.
Caradavin on 20/8/2013 at 08:09
I was actually beginning to think maybe I should just make individual gamesys and only include the DEDX files I want to use. The gamesys stays as I modify it, it only gets rid of the DEDX objects when I use it so maybe that is the issue. I am going to try this out.
MysteryMan on 20/8/2013 at 13:32
Quote Posted by Caradavin
I was actually beginning to think maybe I should just make individual gamesys and only include the DEDX files I want to use. The gamesys stays as I modify it, it only gets rid of the DEDX objects when I use it so maybe that is the issue. I am going to try this out.
Always remember your default .mis and .gam backups when something goes wrong in saving your .gamesys
backup.mis, and backup.gam is created automatically, so you can always fall back to the original setup.
You can save once as Dedx01.gam, then save .cow for a combination of .mis and .gam Your Dedx01.gam should still be intact. As a habit, I save as Dedx01.gam and the .mis separately.
Caradavin on 20/8/2013 at 14:18
Do you guys use ObjTree? I tried using it the other day and found I could add new objects and then save the gamesys - I was doing that. It does take, right? Then, I can just go in and add the models. I tried doing this and the models were already there (not sure how that is possible...) but like I said, all the DEDX01 objects were long gone. My inserted custom objects, however, were all still there and had their assigned models which I had assigned in a previous gamesys but did not assign in this current one. Is this normal?
MysteryMan on 20/8/2013 at 14:48
Quote Posted by Caradavin
Do you guys use ObjTree? I tried using it the other day and found I could add new objects and then save the gamesys - I was doing that. It does take, right? Then, I can just go in and add the models. I tried doing this and the models were already there (not sure how that is possible...) but like I said, all the DEDX01 objects were long gone. My inserted custom objects, however, were all still there and had their assigned models which I had assigned in a previous gamesys but did not assign in this current one. Is this normal?
I always use the obj tree, yes.
Anything you add to the Hierarchy is saved by saving the gamesys.name The .mis file will show current progress as you add to the Hierarchy. You can change the name of your .gam file anytime you wish. As long as the gamesys is saved, your work will always be preserved in the Hierarchy. Also, you will notice that the .gam file size will gradually increase as you add more custom material to the Hierarchy. Keep an eye on the size of the .gam file, so you will know when a corruption has occured, so you can revert back before the .gam save.
Then, use backup.gam, and backup.mis to continue.
LarryG on 20/8/2013 at 15:03
There are three basic gamesys related commands (there are some others, but they don;t apply here):
* load_gamesys - Load .GAM file - Resets the level
* save_gamesys - Save current gamesys info only to a .GAM file
* set_gamesys - Link .GAM file to your mission
My bet is that you renamed your gamesys when you saved it, but forgot to set the new filename to your mission. Because I would tend to do similarly, I use COW files exclusively during builds and only switch to MIS/GAM during beta test. Less to screw up.
Yandros on 20/8/2013 at 15:06
Wait, you mean the ObjTree utility? I've not used it, but it is probably based on the default dark.gam, so if you added to it and saved it, you may have blown away the DEDX entries in the hierarchy. If ObjTree offers a Load function where you can load dedx.gam and then make your changes and save, that should work.
