I am going to create tools for handling project folder, my tools contain switch project, create project, and edit template project
and I need your advice, should I create custom project with absolute path or modify max project folder so it has benefit of relative path?
and could you also give me what pros and cons of both?
I already create the one with modify max project, in max 2009 it has no problem but in max 2013 PU6 sometimes our max inifile reseted like when max first install, project folder path, unit setup, ui setting reseted even .mxp file overwriten to default. is it bug in max 2013?
It is probably best to do it all through the pathconfig structure interface. I believe I have posted a test script I created using the pathconfig interface for creating a project folder directory here at one point, but the search function for me keeps timing out.
-Eric
I already created it with pathconfig structure interface, eric. some folder put it in local, the other put in network etc
but in max 2013, sometimes when we switch between project our max inifile reseted to default and mxp file overwriten. this problem never happen in max 2009
and I also want to know if anyone here not using pathconfig structure interface, whats their reason and what pros cons of it?
I had built a project manager without using pathconfig because it was pre-2008 (maybe 2010? I don’t remember) versions of max and they did not embedded the project oriented maxscript functions. Also, I was new to maxscript and didn’t know pathconfig :).
Since that time, I have discovered pathconfig struct which make thing more easy to handle… but it has some downsides:
[ol]
[li]the projects created with pathconfig have all the big folder hierarchy of a 3dsmax project even if you need only 4 of them (you can filter when you load a project but not when you create one, if I remember well)
[/li][li]the loading of a mxp file using a lot of bitmap paths was buggy. Only a few paths were added. I had to split the loaded mxp into several smaller mxp files before the loading, then load them individually.
[/li][li]if artists create new folder in the images folder, the mxp will not import this path. I recursively search the folder hierarchy from a base images folder each time I load a project.
[/li][/ol]
At the end, I went with a mix of both: custom project creation to have only the needed folder and pathconfig with on-the-fly creation of mxp file when loading/switching projects. the mxp is created from a xml database of the projects where I store only the base path of images folder, then parse the folder hierarchy to be sure that the Asset Tracking will find all the textures).
Hope it helps