[tenz148]

Hi!

I am on Windows 2016 sp2.

Things I have found dont work on my computer.
I tried cleaning up preferences and reinstaling the plugin but all the glitches keeps on happening.
Dont know if having two graphic cards (nvidia gtx non sli) has something to do with it..

FIRE

When I assign a Material Assistant to an object, it updates only the first time. The rest of the changes I make (color,Roughness..) I need to click on Full Restart option to see the update. If I convert the material to Layered it will work as expected.(This has happened on previous versions aswell)

The same updating problem happens with Grass Generator and Scatter Modifier. If I dont make a full restart it wont update any change.

SCATTER MODIFIER.

The option Remove Overlapping does not seem to have any effect.

Some Sliders (like density) which defaults to 100, as soon as I click on it to change the value it goes up to 80 million or something, so I have to input the values with the keyboard.It also happens with Scale but not with Scale Variation which seems ok.

The slider glitch also happens with the grass modifier.


MAYA Viewport WINDOW

When I switch from 2.0 to Maxwell it goes to black.No image is shown.
...

I also tried to open a maya file with the AssetReference in Maxwell Studio beta but no success(both ma. and mb.) . Objs were fine though.


Regards!!

[Mihnea Balta]

FIRE

When I assign a Material Assistant to an object, it updates only the first time. The rest of the changes I make (color,Roughness..) I need to click on Full Restart option to see the update. If I convert the material to Layered it will work as expected.(This has happened on previous versions aswell)

The same updating problem happens with Grass Generator and Scatter Modifier. If I dont make a full restart it wont update any change.

This is probably a bug in the FIRE engine, I will look into it.

SCATTER MODIFIER.

The option Remove Overlapping does not seem to have any effect.

Seems like a bug in the extension, since the value is exported correctly from the plugin. I will talk to the developer in charge.

Some Sliders (like density) which defaults to 100, as soon as I click on it to change the value it goes up to 80 million or something, so I have to input the values with the keyboard.It also happens with Scale but not with Scale Variation which seems ok.

That's because those attributes have huge upper limits. I will add soft limits where appropriate. The variation parameters don't suffer from this because they are percentages, so the range is small (0-100).

MAYA Viewport WINDOW

When I switch from 2.0 to Maxwell it goes to black.No image is shown.

You're not supposed to manually switch to the Maxwell viewport override, that's something we use internally in the plug-in code to implement FIRE. Please see my last post here for a more detailed explanation: http://www.maxwellrender.com/forum/view ... 64#p387164.

I also tried to open a maya file with the AssetReference in Maxwell Studio beta but no success(both ma. and mb.) . Objs were fine though.

The AssetReference extension will not import Maya files - that would basically mean Studio has to include Maya. I don't know the full list of supported formats, but I know it can read FBX, OBJ and DAE files. I'll ask the developer which other formats can be used and get back to you.

[tenz148]

Thank you very much for the reply.

I noticed the Fire refresh from maybe a couple of versions back but there was no post about it so I thought it would be my computer.At work I use MentalRay so this is what I have been learning at home and didnt have much time to clean up-reinstall until recently.I missed the "press render-no surprise result" of Maxwell

The slider values was more of a way to avoid a possible crash. if you have one tree with default density of 100 and just clicking on the slider goes to 1 million with Fire open, maybe would choke.I noticed the density goes from 0 to ..1000millions...this makes for a good a forest ..could be cells or something..

The Maya viewport topic...should have check better the forums...

About the AssetsReference I was very surprised Studio could read maya files, but listening at the Novedge Webinar 164, Essential Maxwell Render Tips, from 00:37:20 to 00:39:50, I thought it was like a PacknGo in turbo mode, so with Maya open could read the file on the fly and update it. I think it is a great idea, although I prefer a good plugin within Maya.With robust Fire and good procedural/utility nodes for some flexibility, would be great!

Saludos