Maxwell Render | Official public forum

Hi.I've juste upgraded my licence for maxwell sketchup v3 standalone. And the sea or grass extensions are not working anymore. Either in sketchup 8 or 2013. 2.7.25 is fine, and i can have grass. In v3 grass give me error:
MX: unloading Fire data
MX: unloading Fire data
MX: Exported in 0.064s.
MX: Fire error => [Extension MaxwellGrass] Error creating blade primitives
MX: unloading Fire data
And the sea extension just give a grey surface, without any texture or transparency. It's a simple file with one surface as group.
So! What am i doing wrong?
Cheers moujiik32

Regarding the grass, could you please try opening a new SKP, creating a small group, and assigning grass with a very low blade count, to confirm that it works -- my guess is that in your actual scene, it might be running out of memory, and stopping with the generation, rather than crashing SketchUp. Regarding the sea material, it just uses whatever material is assigned to the group, so please confirm that you've assigned a material there.

Hi. The same. New sketchup file, a simple surface as group, 135 blades/m². "the scene as errors". And sea extension as no material.
Thanks
moujiik32

The machine: i7 2600; nvidia 560ti; 8gb memory.

It works fine here, so to rule out possibly having files from multiple versions of the plugin, please uninstall the plugin using Control Panel > Programs and Features, manually confirm that maxwell.rb and the maxwell folder have been deleted from the SketchUp Plugins folder, and then reinstall the plugin.

I have uninstaled maxwell, reinstall, on sketchup 8, on sketchup 2013. Always the same message in the ruby console!

All I can say at this point, is that it appears something is not right with your particular installation. Please look in the [SketchUp]\Plugins\maxwell\ext folders (of your SketchUp 8 and SketchUp 2013 installations), and let me know which files you find there. They should be these:

• mx.dll
• mxcommon_32.dll
• MaterialModifiers.win32.mxx
• MaxwellGrass.win32.mxx
• MaxwellHair.win32.mxx
• MaxwellProcedurals.win32.mxx
• MaxwellScatter.win32.mxx
• MaxwellSea.win32.mxx
• MaxwellVolumetric.win32.mxx
• MGrassH.win32.mxx
• MGrassP.win32.mxx
• subdivisionmodifier.win32.mxx
• wireframetexture.win32.mxx

All of these files should have a Date Modified value of 2 December, 2013. So please confirm that these files are all present, and that they have the correct date.

Hi. Every files are here, with the right date. I uninstall sketchup, maxwell, reinstall english version of sketchup 8, reinstall maxwell, and always the same.

Could you please email me (jeremy at nextlimit dotcom) a simple SKP file that shows this happening?

Done

Thanks for sending the file, unfortunately, it works fine here. So next, I am going to ask you to please zip the maxwell.rb file and the whole maxwell folder from one of your SketchUp Plugins folders, and send that to me, so I can take a look at the actual files you have on your system. The zip file will probably be too large for email, so please use dropbox, or another file-sharing site.

Thanks, but still no luck -- your files are perfectly identical to mine. So, let's try this:

• 1. Open SketchUp and load the test file that you sent me..
  2. Open the Ruby console.
  3. Type MX.log=true and hit Enter.
  4. Type MX.trace=true and hit Enter.
  5. Try to render in Maxwell Fire.

You should end up with lots of text printed in the Ruby console -- please copy and email it to me.

I appear to be having this, or a very similar problem with Grass....

I've been using maxwell for a while, but I haven't touched it much in the last few months. I just got a new computer, so I loaded up sketchup and downloaded the newest standalone maxwell plugin and I'm just playing/re-familiarizing myself with it.

So, I set up a really simply model. Just one cube and a bit of sandbox terrain (really small) I tried to apply grass to the terrain group every time I open fire it gives a brief error and then renders the scene w/o any grass

I'm stumped- please help

Windows7
8 G DDR3 RAM
i-7 4700MQ

Please try using the 3.0.1 update mentioned in this post, and let me know if it helps.

worked like a charm