Jump to content

Bitmap paths - make shorter?


paneli
 Share

Recommended Posts

Hello there :)

I am looking for a method to make bitmap paths shorter (should I call it relative?)

for example:

g:/models/piano/textures/wood.jpg

turns to:

textures/wood.jpg

 

On the other hand, is there a way to make the MAX file to save the textures inside of itself? I mean witout having paths. Like the bitmap supposed loaded no metter on which workstation I open the file and no matter if the copy of the bitmap located on the hard drive.

I think it is like the Strip Paths option but for somereason it doesn't work properly.

 

Any ideas?:confused::confused:

Thank you :)

Link to comment
Share on other sites

As you are talking about multiples stations, I assumed you had a server.

 

-If you send your renderings via Backburner instead of opening it on the other machine, you have the option to include maps, so 3dsMax will package all the maps that the slave computer needs in order to produce the rendering. Also, using Backburner, you do not have to run from machines to machines, you control everything from the main machine.

 

You can also use UNC with computers only, without server.. So instead of mapping G:\... you go \\stationIP\project name\textures\wood.jpg

 

Works the same way as on a server, and allows all of your computers to read the same texture.

 

Hope it helps

Link to comment
Share on other sites

Hello there :)

I am looking for a method to make bitmap paths shorter (should I call it relative?)

for example:

g:/models/piano/textures/wood.jpg

turns to:

textures/wood.jpg

 

On the other hand, is there a way to make the MAX file to save the textures inside of itself? I mean witout having paths. Like the bitmap supposed loaded no metter on which workstation I open the file and no matter if the copy of the bitmap located on the hard drive.

I think it is like the Strip Paths option but for somereason it doesn't work properly.

 

Any ideas?:confused::confused:

Thank you :)

 

You could do this, but it spells recipe for disaster in a professorial production environment.

 

Also, as far as I am concerned, no bitmaps should be used that are stored locally on a machine. You mention your local hard drive. This should not be used for storing items that are shared amongst a team. If you work solo it is probably ok, though I still wouldn't do it. It is a no no. All render assets should be networked via UNC or DFS pathing.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...