changing map type = crash

[siliconbauhaus]

I'm not sure if this is a max problem or a vray problem.

If I have a material set to a bitmap as diffuse and then decide to later change it to tiles max crashes. If I click on the map slot this happens. If I drag a none slot into it and then click tiles it doesnt.

Anyone else had this ?

[vlado]

Which V-Ray/3dsmax version?

Best regards,
Vlado

[insleight]

I had this a lot. I did not have Vray installed on the machine whatsoever though.

I would forget to drag a none slot into the channel and crash max after not having saved so many times...

[Stain777]

Re: changing map type = crash

I'm not sure if this is a max problem or a vray problem.

If I have a material set to a bitmap as diffuse and then decide to later change it to tiles max crashes. If I click on the map slot this happens. If I drag a none slot into it and then click tiles it doesnt.

Anyone else had this ?

Yeah, I've had this many times. It seems to only happen with certain map types for me though. For example with composite maps and with the Vray Arch Materials (they're particularly bad). So it ends up that I have to work around certain set materials or I get an instant crash. Dragging over them with a None type doesn't work as I get the same result.

[timmatron]

I think what you might want to try is disabling the map in the viewport before changing map types.

That was my problem, and now it seems to work fine.

[Stain777]

I think what you might want to try is disabling the map in the viewport before changing map types.

That was my problem, and now it seems to work fine.

Oddly enough, it was when I hit the disable button that it crashed. As though putting that material into the library was a bad thing. I'd like to figure it out so I can get full use of the crappy 24 slots that Max provides.

[werticus]

i've had that problem

the problem just went away with the next scene. so you might want to try reimporting everything into a new scene.

but i think valdo had found the cause to be a call to render a null value in the viewport if im not mistaken.

[MoonDoggie]

The problem is max related and if it's the same problem I was having make sure to disable your showInViewport button unchecked for EVERY bitmap in the heirarchy you are deleting. Here is some (quick) code for doing these things:


Make this a button and select a group of objects you want to turn off their showInViewport buttons and click it, this code will not catch nested bitmapTextures (like in a noise/mix/etc map)

currentlySelected = getCurrentSelection()
for obj in currentlySelected do
(
		try ( showTextureMap obj.material obj.material.diffuseMap off ) catch ()
		try ( showTextureMap obj.material obj.material.opacityMap off ) catch ()
		try ( showTextureMap obj.material obj.material.reflectionMap off ) catch ()
		try ( showTextureMap obj.material obj.material.selfIllumMap off ) catch ()
		try ( showTextureMap obj.material obj.material.specularMap off ) catch ()
)

Make this a button to turn them back on:

currentlySelected = getCurrentSelection()
for obj in currentlySelected do (	
		try ( showTextureMap obj.material obj.material.diffuseMap on ) 
		catch ( 
			try ( 
				showTextureMap obj.material obj.material.opacityMap on ) 
				catch()
		)
)

If this is not your problem then good luck, it was the bane of my existence for a while.

-Colin

[Stain777]

This is very cool. Many thanks Moondoggie!