*Showstopper* Shader properties not saved/copied

Rak'kar

26-01-2007 23:33:15

I'm setting up oFusion materials for the artists and saving them to a material library. In the Vertex and pixel shader edit boxes, I click the checkbox and set up the shader constants, such as, worldViewProj with WORLDVIEWPROJ_MATRIX.

The problem is that these properties are not saved or copied between materials, or to the material library:

1. If I drag the material to make a copy, the new material doesn't have these settings set.
2. If I click 'Put to Library", and load the material from the library, these settings are not set.

The only time the settings are preserved is within the .max file itself.

This is a showstopper bug because
1. I cannot provide artists with usable materials from a library.
2. Even if I could, the shader settings would not get copied with the material, and the material wouldn't work.

Please fix ASAP. With this bug in place my art team is unable to progress past the texturing stage.

I'm using the paid professional edition with Max 9.0.

Thanks.

Lioric

26-01-2007 23:44:24

This is a known issue with some max configurations, i will put this at the top of the list so it will be reviewed first

Lioric

29-01-2007 23:45:52

The issue with the shader in materials copied or added to the library has been fixed

Do you need this, immediately in a hotfix, or do you prefer a single hotfix with all of your other reported issues fixed?

Rak'kar

30-01-2007 00:10:05

Thanks for asking! If you can get all these fixes in within a week, I'd like to just wait. If it will take longer than that I'd like to get them as a hotfix.

cybereality

30-01-2007 20:11:16

I am in need of this fix too I think. I am trying to set up a pipeline for the artists I'm working with and oFusion seems like a great solution. But I need to be able to provide the artists with materials (including shaders, like for normal mapping) that they can easily edit with their own textures, etc. I haven't got as far as Rakkar, so I didnt notice this issue until he brought it up. Is there a workaround for this you do we need to wait for an update? Thanks.

Lioric

30-01-2007 21:43:49

This fix will be included in the next CE update (with max9 support) as well