Render to Texture Error in 3DS Max

Luke003

Hi all, I did a search for anyone having a similar problem and haven't found anything to help with this particular issue. Assistance would be greatly appreciated.

Problem:

When I hit "0" to open the Render to Texture dialogue on my model, I get this error (pictured below): " -- Unable to convert: "!>>?false" to type: BooleanClass"



Why I'm confused:

• Using the exact same file on my laptop, everything works fine.
• Opening a fresh file and creating a simple shape, then running RTT, works fine.

This is really aggravating because I stopped lugging my laptop to work, mainly because my workstation is more powerful. But now I can't bake what I'm working on, so I'm kinda stuck waiting until I get back home to my personal computers.

Any insight would be helpful. Thanks in advance.

Eric Chadwick

Hard to see the error clearly, but are there funky characters in the error? Looks like an upside-down ? next to the "false".

Maybe your OS is set to display in a different language? Or set to a different Unicode?

Regretful123

I've seen this error before from a friend of mine's workstation. Try this; export the file into fbx, reopen it in a different scene, and collapse the modifier stack. Once you do that, try to open the render to texture.

Luke003

@Eric Chadwick - Yeah, I'm sorry, I should have just cropped out the error window. Those are strange characters in the error. Upside down ? and a !. It could be a language issue, there are international students using my machine from time to time, but I don't get why it would work and then not work in the same session.

@Regretful123 - I'll try exporting an FBX when I get to my workstation tomorrow. But I went home and baked my textures on my laptop for the time being.

Thanks guys for the responses.

Illusive

just started getting this error.. going to open in another max and see what happens

The Flying Monk

I had this error today.
Exported the mesh to an FBX and made a fresh scene and everthing was fine.

So what I think was happening was that the scene was set up with a renderer or a material plugin that I didn't have installed.

The renderer was setup as Max scanline and there was just a standard mat on the mesh. But I think just having the missing plugin referenced in the scene was causing the problem.