Hi, > That still doesn't change the possibility of texpage muckups. If i > create a mod you like, and you want to add my mod as a dependency > -- adding models that use my texpages -- then it's all well and > good until i get into warzone studio and add another image for the > software to push into the texpage -- when i do this, the texpage > may get rebuilt in a different way, and although my models will > have their own texpage filenames and coordinates mangled correctly > to match the new texpage, anyone who depends on my mod won't have > that same benefit, and they'll have to ask me for my studio file or > will have to retexture their model (though they'll probably be > lucky enough to only need to translate each mesh as a whole to a > new location). Nonetheless, I believe that any kind of "automagic" > behavior, especially with this kind of individual images -> > composite texpage transparency leave the possibility of problems if > not added on the engine level. I understand that it's unmanagable > to do anything along these lines in the engine unless caching is > involved. i'll be thinking about a way implement a cache with > reasonably well performing cache-invalidations.
Why would the model depend on texpage co-ordinates? Currently all .img files have names, for example: 0,0,36,148,11,0,0,"IMAGE PBAR REQUIRED" A mod/model should know its textures not by their position on a specific texpage but more by their name. Thus, one has freedom to change and reorder texpages as they wish. Regards, Freddie. _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
