CompuServe Messages

I seem to recall a similar problem I ran into a while back. I was using project files since I tend to work on several jobs at once. Because of this, I keep separate map paths for each project. I can do this easily *without* changing my 3DS.SET file. Before I start a new project I create a set of directories to hold all my maps for that project. Then, I jump into 3DS and select Configure. From there I type in the map paths for the project. Next, I save the project file. The result is that 3DS will always use the map paths stored in the .prj file as opposed to what is in the 3DS.SET file. I recall the problem because I changed the map paths in the 3DS.SET and when I restarted 3DS and loaded a project file the new map paths settings had no effect. When I checked the Configure box I found that the map paths associated with that project had not changed to match what was in my 3DS.SET. Instead, they were right where I left them when I changed them by hand. However, upon starting a new project, the map paths in Configure are preset to match the 3DS.SET until manually changed. Actually, I think this is a really great feature. It helps me maintain organization between projects. I can backup and restore entire projects without worring about path problems. I'm not sure if this same phenomenon will occur with simple .3ds files. By the way, I prefer .ifl files too.