[JDHill]

I'm having problems with both version 8 and 2013, after about 5 to 10 minutes it just quits and the applications closes, this only happens when the maxwellrender standalone plugging in in the plugin folder.

You are on OSX, correct? If so, then I found what is probably the same problem, just about ten minutes ago. It looks like the Draft engine is leaking memory -- please try using the Production engine instead, and let me know if that takes care of the problem.

[Nicolas Rivera]

I'm having problems with both version 8 and 2013, after about 5 to 10 minutes it just quits and the applications closes, this only happens when the maxwellrender standalone plugging in in the plugin folder.

You are on OSX, correct? If so, then I found what is probably the same problem, just about ten minutes ago. It looks like the Draft engine is leaking memory -- please try using the Production engine instead, and let me know if that takes care of the problem.

Yes, latest OSX. Ok i will try it right now and let you know, thanks man!

[Nicolas Rivera]

Still the same, i repeated what i did last time... while fire was rendering i changed a cars material to car paint and as soon as it was computing the change it crashed sketch up... here is the crash report.

https://www.dropbox.com/s/y2p0pys62je2w ... report.rtf

[JDHill]

That looks like something very different -- it shows a crash in SketchUp itself, apparently having to do with recalculating shadows. The issue I was referring to, you should be able to reproduce by opening a simple cube scene and rendering it with the Draft engine, while watching memory usage in Activity Monitor, then repeating the process (including restarting SketchUp) with the Production engine instead.

[mgordon320]

Wanted to see if anyone else is getting a BSOD issue with the newest version of Maxwell 3 (Render Suite) for SketchUp. So far, it's been only through the FIRE window, when it's set to SL12, and the BSOD happens around SL7-8. Bam, shuts down.

Going to re-install a clean OS and try again, but there's specs on the computer if that helps.

BOXX 4920 Xtreme
Intel Core i7-3960X CPU @ 4.5GHz
RAM: 32GB
GPU: Nvidia Quadro 4000

Thanks,

Matt

[JDHill]

I don't know of any possible way that the plugin could cause a BSOD, except by stressing the system, and therefore potentially triggering an issue with a driver, with memory, with overheating, etc. Before going so far as to reinstall the OS, I would suggest to try running at stock clock, and see if you are still able to reproduce it.

[numerobis]

As JD said, this should be more related to a bad overclock than to a sketchup plugin (even if this should be impossible looking at the BOXX prices)
I would call them to fix this immediately - this is why you pay a triple price, no?

If you want to fix it yourself, you could check the error code of the bluescreen. The most common would be 0x101, which normally means that you need more vcore (sometimes QPI/VTT )
http://www.overclock.net/a/common-bsod- ... erclocking
For a quick fix you could lower the multiplier to 44 or 43. That should fix the problem if the 4,5GHz is to much.

But as i said before, i think you have bought this BOXX to get the support and because you don't want to overclock yourself. So let do them their job...

[fv]

I have a few bugs to report.
System Macpro 2.1 system 10.7.5 8GB ram.

1. Glass in symbols leaves the asigned glass pane inside the symbol invisable. This was hard to find but I noticed that glass was not reflective at all. Further study in Studio made it clear that after editing the glass material opaque nothing happened. I don't know why other materials like the wooden frames were fine in the same symbol. Exploding the model cured the problem.
2. the path is lost to HDR mappings at export to Studio. Although the right filenames are visable in Studio the maps are not imported. Reimporting them in Studio cures the problem. Exporting to render to Maxwell crashes Maxwell. So I have to use Studio.
3. The sun-icon in the model panel in Studio does not move in Studio when changing the settings.
4. MXI switched off in the SU-plugin or Studio results in less crashes.

In general, rendering causes a lot of crashes. Sometimes directly or just before after voxelization has finished.
Placing referenced .mxs symbols also causes a lot of crashes at export.

I am getting work done now by using Studio.
Sorry for my rather unscientific bug report. But I haven't had the time to do tests yet to properly research what exactly happens. It might all be related to my older Macpro 8-core and system 10.7.5. Maybe for users with the same system its still best to keep using 10.6.8 and Maxwell V2. I am not sure though if the bugs are a result of my the less than up to date system and hardware.

Anyone who sees simular problems ?
Francois

[JDHill]

Hi Francois,

• 1. Sorry, but could you please clarify what you mean by saying "symbol"? It sounds like a case where I'll need to see a SKP model.
  2. I'm not able to reproduce this, but wonder, have you checked it with the 3.0.0.1 version on the portal download page?
  3. Yes, it seems so (on both Win & OSX), though not after clicking File > New. It appears to be due to opening MXS files that use the Direction method of sun location, as is always the case coming from SketchUp. I'll work up a report for the Studio developers.
  4. Probably I would check 3.0.0.1 here, too.

In general, I know they fixed various small things in the 3.0.0.1 build, so I'd encourage trying that.

[numerobis]

MXMs are no longer embeded in the exported mxs, is this true? I can't find any switch to enable it again.

I just tested my first bigger v3 (3.0.0.0) render with the skp plugin... it exports and loads into maxwell - and the crashes when voxelation starts. I can load it into studio, but i get the same crash when i press render...
The scene is nothing special, a few old and new materials, only phys sky, no grass, mxs-references etc.

i think i'll go back to v2 to get things done...


one small wish for the plugin (i think i have asked this before, but i'm not sure):
would it be possible to get an option that the skp file name is added at the beginning of the mxs name? Or alternatively the name of the current scene added to the skp file name?

[JDHill]

I have had a couple instances similar to that, now -- able to export, but crashes during or after voxelization -- which were fixed with 3.0.0.1, so I can only encourage trying that. Regarding the wish, please see the table of supported output macros (specifically, %skp and %scene), here, and let me know if they do what you want.

[numerobis]

Regarding the wish, please see the table of supported output macros (specifically, %skp and %scene), here, and let me know if they do what you want.

Oh, this looks VERY useful! Thanks!

Ok, i think i'll try v3.0.0.1 then...

Although i think the better choice would be to go back to v2 because i have to finish some renders for next week... so last try for this month i think.

btw. Maxwell Sea is not working for me in sketchup - fire displays nothing and exported to maxwell the sea object gets scaled down...

[JDHill]

Are you possibly applying Maxwell Sea to a plane? It needs a group with some volume. In the next build, I'll detect that and artificially give it a microscopic amount, though in that case, you'll barely be able to detect any waves on the surface, since it does the simulation based on the bounding box of the geometry. If that's not it, please let me know if you have more info.

[numerobis]

ahh, ok. Yes it was a grouped plane. Sorry! I really should read the manual... Now it works in fire and exported.

Regarding the crash... 3.0.01 fixed it! It now renders as it should. I think i will update my nodes now and give network render another try...

Could you say something about the referenced materials? Is there a way to embed MXMs on export?

[JDHill]

Sorry, I forgot that question. No, there's not currently a way to embed them -- linked MXMs are exported as being linked. Do I guess correctly that you ask because you'd prefer to minimize the number of external dependencies in the MXS file?