[sandykoufax]

.... Why are you using the Max gamma settings with Maxwell? They are misleading, since Maxwell does its own gamma calculations based on the settings found in the global render options panel. Also, that window allows you to set the input gamma for textures, but those settings are not passed to Maxwell, so it's not ok to rely on them.

Gamma setting is for other renderer. It need gamma enabled.
I've used it when I use maxwell because Maxwell render doesn't affected.
If Activeshade render is affected by it, I can disable it.
But somewhat inconvenient.

[itsallgoode9]

does the new Fire update affect the final render time of an image or is it only beneficial in the realtime preview window? I feel like you guys once mentioned it's more of an adjusting of when/how things are rendered in the beginning of the render process and not necessarily a speed increase, but I could be wrong. I forgot to do a "before" render test using V2 before upgrading to 2.5 :-\

[brodie_geers]

Has anyone noticed either of the following?

1. viewport issues in Studio when using Fire? (viewport locks up while navigating)

2. .mxm's aren't showing up as thumbnails in Win7 explorer. Some still do, but the vast majority aren't.

-Brodie

[Gary Bidwell]

Just testing in Maya. Works great tweaking materials or moving the camera on a high poly scene, but if I move the light, even 1mm it takes about 45 seconds to a minute to complete voxelization and continue rendering. This is far to slow to light a product intuitively and interactively.

Just tested the same scene in mentalray using maya ipr and this updates instantly with no delay.

Hope this is just a bug that will be fixed.

[m-Que]

Has anyone noticed either of the following?

1. viewport issues in Studio when using Fire? (viewport locks up while navigating)

Can you explain this a bit? Is it reacting slowly? (Lagging). Even with very basic scenes?

2. .mxm's aren't showing up as thumbnails in Win7 explorer. Some still do, but the vast majority aren't.

Yes. I think it's the same in here - for example, in Arroway_v2 I only see "bricks-20.mxm". The reset of materials do not have a thumbnails.

[brodie_geers]

Has anyone noticed either of the following?

1. viewport issues in Studio when using Fire? (viewport locks up while navigating)

Can you explain this a bit? Is it reacting slowly? (Lagging). Even with very basic scenes?

I haven't used Studio enough in the last day to see how common it is but I've noticed it on a couple different scenes so far. Both were mid-poly architecture scenes (~40k triangles). The Fire window worked fine but most of the normal viewport window would completely stick, except for a small square, maybe 1/8th of the whole window which would act normally. It was happening most often after doing a Right-Click -> Focus To operation, just after that zooming in/out would cause the bug.

-Brodie

[Mihnea Balta]

Just testing in Maya. Works great tweaking materials or moving the camera on a high poly scene, but if I move the light, even 1mm it takes about 45 seconds to a minute to complete voxelization and continue rendering. This is far to slow to light a product intuitively and interactively.

I'm afraid this is not easy to fix. Since lights in Maxwell are geometry, when you move one (or any other piece of geometry) it has to re-build its scene tree, which is an expensive process. We tried to limit the cases when a full re-export of the scene is needed (other renderers re-export everything when anything is moved, which becomes prohibitively slow really quick), but there's no simple way to eliminate the voxelization too.

[numerobis]

2. .mxm's aren't showing up as thumbnails in Win7 explorer. Some still do, but the vast majority aren't.

yes, for me too.
the old untouched 2.1 mxm's still have their preview and the new ones didn't store or show it anymore

[brodie_geers]

2. .mxm's aren't showing up as thumbnails in Win7 explorer. Some still do, but the vast majority aren't.

yes, for me too.
the old untouched 2.1 mxm's still have their preview and the new ones didn't store or show it anymore

It's hard to tell, but I think that's the case for me too. Anything created in 1.7 or 2.5 shows up as an icon now, but the materials I have that were made in 2.1 still show up. Very weird.

-Brodie

[JDHill]

Firstly, have you rebooted the machine since installing Maxwell 2.5? In theory, a copy of the old thumbnail reader could still be in memory. If you have rebooted, and the issue persists, you may try these steps (this assumes you're using 64-bit Maxwell; if 32-bit, the name of the thumbnail plugin will be maxwell.shell_x86.dll):

1. Start > Search > type cmd.exe
2. right-click cmd.exe and Run as Administrator
3. navigate to your Maxwell directory
4. type regsvr32 maxwell.shell_x64.dll and hit Enter
5. a dialog should indicate that registration was successful

Here, I did not need to do any of this; I used the Maxwell 2.5 patch installer, and it successfully registered the MXM thumbnail plugin.

[numerobis]

works! great! thanks JD!


btw. i had installed 2.5 (patch) yesterday so it had been rebooted/turned off at least one time

[Half Life]

Yep that worked for me too, although I'm running 32 bit so I had to use that dll.

Best,
Jason.

[brodie_geers]

Do I need to restart after running through that info JD?

Does this look right?


I ran it, got the confirmation but nothing has changed in terms of the previews yet. I'm running some renderings so I can't restart just yet.

I did restart this morning though, as I thought that may be this issue.

-Brodie

P.S. these files are on an external NAS. I wonder if that has anything to do with it. I'll probably need to reboot.

[numerobis]

yes, this looks right.
did you try to open a mxm after this? i had to reassign mxm editor one time. after that all previews got updated

[JDHill]

Well, I don't restart here, I just kill explorer.exe and restart it. But I am not recommending that you do that. If you registered the dll, and Windows told you it succeeded, then it is registered.

At that point, you would want to double check that the file is actually new -- if you look at the properties for maxwell.shell_x64.dll in Explorer, it should be versioned as 2.5.0.0. In other words, it is possible that the installer failed to overwrite your old one. Deleting the file, re-running the Maxwell installer, and rebooting would ensure that was not the case.