Jump to content
AutoDesSys Forums

Managing texture maps across multiple platforms

Recommended Posts

I have recently begun porting my FormZ work from my beloved (if underpowered) Mac to a more robust PC Workstation. In the process of working out bugs, and when I'm on the road, I still do lots of modeling work on my Mac. However, I'm running up against an annoying issue with texture maps losing their link when I move to the PC station.


I keep all my live documents and 3D resources in a DropBox account which keeps all my computers synced and my work available where ever I go. So when I open model "x" it is always from the DropBox location which also contains all the related texture maps. Even MXM textures live in a folder on that remote drive. However, when I try to render my work, I get constant error messages about missing links... The really weird thing is that it's not uniform. Some textures go missing while others are still there. 


To add insult to injury, Maxwell Fire, which I use as a flight check for my final renders, lists missing textures or texture components... one. at. a. time. Meaning I have to cycle through starting Fire, then opening the log to find which texture is causing the render to fail, then relink that texture, then start all over again. Wash, rinse, repeat, repeat, repeat.


So two points; 


a) has anyone come up on this and found a solution to keep texture linked to the model across stations? 


B) would it be conceivable for Maxwell to perform a complete flight check of all dependencies before writing the log?


Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...