danni.coy Posted May 8, 2013 Share Posted May 8, 2013 One of the problems we having with material files is that high level systems like tracker alter parameters on some textures, which means that we get a lot of changes for our versioning system that don't do anything useful and can potentially over write explicit edits. I would like to see a state somewhere between editable="0" and editable="1" where manual texture edits are possible using the material editor but the file isn't saved on quit. alternatively someway to detect a unique name for the machine unigine is running on and make it editable on some machines but not others. Link to comment
frustum Posted June 23, 2013 Share Posted June 23, 2013 The possible solution is to exclude material file from the list of preloaded world material libraries and load this material library manually before the world loading (in system script for example). In that case material library will never be saved automatically. Link to comment
Recommended Posts