[paxreid]

'deleted'...rivoli should comment

[rivoli]

never mind, loading a bitmap instantly crashes maxwell studio.

[vinys]

as long as i can tell only bitmaps are supported. by bitmaps i mean .bmp

someone wrote that .png works best

[rivoli]

true, PNGs seem to work much better.

[Mihai]

Trying to change the weightmap setting in the materials stalls Studio. I'm trying to render just a coating, no bsdf layer.

[Frances]

I drank 3 cups of coffe this morning and uninstalled/reinstalled Maxwell to a folder called NextLimit. I added the mxcl directory to the Path variable. I copied the license.dat file to the Maxwell root and mxcl folders. I rebooted.

I can now use the render button from the Studio.

I can render from Max also. Here is what I've noted about the emitter presets: They are messed up - all of them. The only way to get an emitter material to work properly is to set it to Custom and then the values you need are totally whacky. GI doesn't seem to work either.

[Mihai]

I think that's because the default scale value in Studio is 1, so in your modeling software you need to set it to the same value before exporting the mxs. It works well for me, but shame we can't use any textures yet. And material editor is buggy.

[Thomas An.]

Mihai,

Right click My computer, properties, advanced, Environment variables.

The MAXWELL_ROOT entry, should point to:
C:\Program Files\Next Limit\Maxwell\

The Path entry should point to:
C:\Program Files\Next Limit\Maxwell\mxcl\

You are refering to the user variables, not the system variables ? Right ?

[Mihai]

Right, that's where I added them. There is however also a MAXWELL_ROOT and a Path variable in system variables as well. But i only added these to the user variables and mxcl opens.

[Frances]

I think that's because the default scale value in Studio is 1, so in your modeling software you need to set it to the same value before exporting the mxs. It works well for me, but shame we can't use any textures yet. And material editor is buggy.

This was rendered out of Max. The scale is correct. GI doesn't work. All layers are enabled.

[etbarchitects]

as far as being to click on a file in explorer, and getting studio/render to launch it

it is needs to be set through windows explorer.

go to tools->file types->find the mxs file type, or new if it is not there

click advanced

and hight open, click edit

put "C:\Program Files\Next Limit\Maxwell\mxcl\mxcl.exe" -mxs:"%1" -d (this will open up render like the beta did)


now i have not tested this, cause i decided not to install RC1 but it should work....

i am guessing from a lack of this, a lack of the manager for net renders, the nonset env variables, and the missing popup that everyone is right and wehn the posted/complied this install, it was not the RC that meant to put out there

[etbarchitects]

The MAXWELL_ROOT entry, should point to:
C:\Program Files\Next Limit\Maxwell\

The Path entry should point to:
C:\Program Files\Next Limit\Maxwell\mxcl\


i wrote a setup script that will do this for you guys....

but just to remove any lialbity from me.... i am not resonpsile for anything that happens to ur puter... create a system restore point before using if u are worried

http://ezmatch.org/mrrc1fix.exe

if anyone has any problems with this fix, let me know ASAP at email clinton.collins@gmail.com or pmsg here, or aol im: EMberOfEden

[iandavis]

so.. let me get this straight.. after several hundred combined hours were spent by many people who potentially could be doing something else more constructive..

the end result is that this RC does LESS then available to us in the beta?

But hey, it's got some really DEEP shader controls... just no way of actually producing finished results.

Umm... RC... does that stand for Release Candidate?

shouldn't something almost ready to be called VERSION1 be capable of performing most of it's originally intended operations? I mean, being a bit buggy is to be expected... but to not work AT ALL. That means its still in Beta. The installer isnt even near complete.. 90% of people's current RC woes could easily be avoided had they spent A COUPLE MORE DAYS on the installer. That doesn't help selling this as an RC... now does it?

So techically, once again, we have been given something labelled much more then it actually is. Call a spade a spade NL and stop assuming we all have hours and hours to waste on stuff we REALLY shouldn't be seeing at all!

[iandavis]

OH THIS IS RICH...

Now we have USERS writing scripts to correct a crappy installer!

Oh, how I've seen EVERYTHING!

NL, you should be ashamed... calling this an RC.

[daros]

if i change a color of a material in the material editor with the color picker MW crashes.
I have installed MW now on 8 different machines and almost every one has different bugs.