9
by WillyP
SG Commando
D3 finds objects and textures thusly: Say your mission has object "abc" which uses texture "xyz". When you attempt to load that mission, D3 will say I need object abc.oof, and texture xyz.ogf. D3 will first look in the Descent3 main directory. If found there, it stops looking for that textur or object. If not then it will look in the mission mn3, then in the default hog, which is "D3.hog". The first object or texture found with a matching name will be used. So, if there is a abc.oof in all three locations it will use the one that is in your main directory. This is fine to place customs there for you own use, but not a good thing to do if you plan to distribute your work. Reason is that if you do it this way, it will override a custom that is of the same name that someone may have put into a mission. It is also not a good idea to alter the D3.hog, as it will override stock objects and textures used in all missions. Also anyone who wants to play your mission would have to download your D3.hog, replace theirs with it, and reinstall the original when done. So the correct way is to include them in your mission mn3, then you have control over how they are used.