neux on 21/3/2015 at 23:10
Hello!
I've been following this tutorial:
(
http://dromed.whoopdedo.org/dromed/texture_imports)
I've done it once as it's said here and tested it (it worked) but didn't save gamesys at that time.
The problem at the moment is that whenever I load a new texture or family of textures they don't appear under textures in Object hierarchy. I've tried some silly stuff but nothing worked.
Lady Rowena on 22/3/2015 at 00:47
They are probably in "Missing", at the very end of the Object hierarchy. To delete them from that list you have to do "Purge lost obis" from the Edit menu. Then reload your mission to see if they are still there. Sometimes (almost all the times for me), doing that has no effect and you have to repeat it. When they are deleted they will reappear under the Textures hierarchy.
I recommend to save your gamesys under a different name or number every time you make changes.
neux on 22/3/2015 at 00:55
Thanks Lady Rowena!
Love your work! Ohh, the tower.
darthsLair on 22/3/2015 at 02:44
Quote Posted by neux
Hello!
I've been following this tutorial:
(
http://dromed.whoopdedo.org/dromed/texture_imports)
I've done it once as it's said here and tested it (it worked) but didn't save gamesys at that time.
The problem at the moment is that whenever I load a new texture or family of textures they don't appear under textures in Object hierarchy. I've tried some silly stuff but nothing worked.
When you add a new family, your texture names will appear under object hierarchy>Textures.
You hilight the texture with a click of your mouse, then slide it into the material category you want to assign it to. Metal, Wood, ect.
You must save your gamesys.name, set your gamesys.name, and save the mission, or they will always be floating in your Texture hierarchy.
For the textures in your texture palett window that you don't use, type this into your command window:compress_family_all Then save the mission.
For the textures you do not use, and don't want in the Texture Hierarchy, hilight them and click on delete. Save the gamesys.name, and so on as described above.
neux on 22/3/2015 at 03:30
Cheers, Darth!
Yandros on 22/3/2015 at 04:17
For what it's worth, I never save .mis and .gam separately unless I'm packaging up a mission for testing. Saving them together as a .cow is much simpler when you're just doing iterative saving during development.
LarryG on 22/3/2015 at 05:04
Me too. Simpler and safer. You never have to worry about forgetting to save the gam. Cow all the way up to beta test.
