Maxwell Render | Official public forum

Here they are..

- When loading a big MXS file into Studio which contains a large number of objects which all share the same material there should be a option to load either one material for all those objects which share that same material or to load one material for each object (the way it works at the moment).

- A large number of materials in a scene in Studio will slow it down when selecting them, same problem with objects in a scene. Materialgrouping would be useful to make it all easier to control and navigate around in.

- If you select a object in a scene in Studio and you have 999 more objects all sharing the very same material (but loaded as single materials in Studio) you don't wanna sit and select them all one by one, instead if we could by clicking one of those objects in the editor/view then it would automatically via a rightclick menu function enable you to select all those materials which are duplicates of the object you just picked. This probably sounds very very confusing but ask and i'll try to explain better what i mean.

- Objectgroups or any other type of groups must be preserved in the MXS file which you create from your host 3d program, this been requested many times before and i'm gonna request it again as it's pretty critical to the workflow for all of us who use Maxwell.

- Exporting MXS files with textures for sharing them between eachother or for network rendering if sharing the texture director on the network ain't working properly or if it's not necessary. Then this would help. This could be a option in Studio and/or the plugins when you're about to render out your MXS file so the user can decide themselves if they wanna do that. Ofcourse the MXS filesize will increase alot with textures in it but it could be a selectable/deselectable option.

- Extended hdr support for more types of hdr maps and projections including EXR support (been partially requested before).

- When in the materialeditor in Studio and opening up a new material from the File menu then it adds that material to the list instead of replacing the current one open, this is a small quirk only but it could be adjusted aswell. Logically it tells me that the material currently open would be replaced by the one you load from the File menu, at the moment it ain't doing that.

- I'm not sure if it's possible right now in Studio but the ability for the users to make their own object libraries with preserved materials and settings and access them via a thumbnailed preview like folder in some sorta objectlist could come in handy for those users as architects who reuse alot of objects in their scenes all the time. That would probably speed up their work alot more if they like this type of thing. So it would be pretty much drag'n'drop for them

That's all for now hehe maybe more will come later..

Cheers!

/ Max

Maximus3D wrote:Here they are..

- When loading a big MXS file into Studio which contains a large number of objects which all share the same material there should be a option to load either one material for all those objects which share that same material or to load one material for each object (the way it works at the moment).

I don't understand, you can already have one material applied to several objects. If that's the case, the next time you open that scene, it will still be : one material applied to several objects. If you already have lots of duplicated materials, just delete them and then select all objects you want to have a material and rightclick in object list->Apply material

- If you select a object in a scene in Studio and you have 999 more objects all sharing the very same material (but loaded as single materials in Studio) you don't wanna sit and select them all one by one, instead if we could by clicking one of those objects in the editor/view then it would automatically via a rightclick menu function enable you to select all those materials which are duplicates of the object you just picked. This probably sounds very very confusing but ask and i'll try to explain better what i mean.

This adds unecessary rightclick options and things can quickly get confusing. See above answer, if you have that many duplicate materials, just delete them.

- I'm not sure if it's possible right now in Studio but the ability for the users to make their own object libraries with preserved materials and settings and access them via a thumbnailed preview like folder in some sorta objectlist could come in handy for those users as architects who reuse alot of objects in their scenes all the time. That would probably speed up their work alot more if they like this type of thing. So it would be pretty much drag'n'drop for them

Already available Did you check File>Load Environment and File>Load object from library?

To add your own objects or environment simply save them as scenes to the objects library, or environments folder in your Maxwell install folder.

Mihai, the thing with the first request you quoted me at is that let's say i create a ring with say 50 diamonds in it in C4D, i give all those diamonds the same mxm material, then i generate the MXS file, take that into Studio and kaboom my ring model suddenly has 50 mxm diamond materials in it when i need only 1 to diamond material to control all those diamonds, i don't wanna sit and check which materials in my scene are diamonds and which are other materials and them like that, i wanna do it automatically to save time and to make the job easier. Removing them manually is very timeconsuming and tiresome.

Second quote you made (sorry i'm not a quoter on forums) about the rightclick option, that i don't think adds unnecessary options or clutter to the interface. Necessary functions will make life easier.

And lastly about the object library request, i noticed that now too but ok will that preserve materials and all that jazz needed for drag'n'drop of objects into a scene ? i'm not quite sure yet how much it exactly covers as there's no info on it.

/ Max

Best to try it out then, the objects do retain their materials.

The first issues are really an mxs scene translation bug, it should import one material if applied at a top level of a hierarchy.