[Richard]

Hmmm! I can't reproduce it JD it would definately have something to do with the namings of the dragged in whole component v the naming of the sub components when exploded weird.

[epix]

I have 16GB of RAM but maybe it is not sufficient?

SketchUp can use an absolute maximum of 4GB (or 2GB, if you are not on SU8 M1/M2), regardless what you have on the machine. So, to know what's going on, you need to open Task Manager and monitor how much memory is being used.[/quote]

I monitored the process and came to this point just before quitting:



Do you think it is a memory issue?
Is there a workaround?

[numerobis]

the memory used by sketchup is not listed in your screenshot...
look for the RAM usage of the sketchup.exe on the "Processes" tab of the task manager (or maybe the next column in your Recource Monitor)

btw... is "use instances" selected in your maxwell export settings?

[epix]

the memory used by sketchup is not listed in your screenshot...
look for the RAM usage of the sketchup.exe on the "Processes" tab of the task manager (or maybe the next column in your Recource Monitor)

btw... is "use instances" selected in your maxwell export settings?

Hi Richard,
Yes, "use instances" is on. Do not misunderstand the first image. I forgot to link up those tree boards showing.
Maybe it is a problem with RAM. I followed the process until it passed 4MB usage, then the export shut down. This is the last screenshot before passing:


Maybe I have to wait for this:
http://www.maxwellrender.com/forum/view ... 07&t=37796

In the meantime; -any workaround?

By the way, -here´s the log:
http://www.epix.no/uploads/Forum/export.log

[numerobis]

so with more than 3GB RAM usage for skp i would say it is definately a RAM issue.
But i don't know why it is getting so high using instances... is it only one "highpoly" tree or a few different tree models?
How much RAM is used by Sketchup after a fresh Sketchup start (and loading your model)?
Can you render only the highres tree(s) without proxys?

There are a few points you can do now:

- remove all unused geometry, use lowres textures (highres only in the linked MXMs) and purge your model.
- sketchup's ram usage tends to stay higher after any mxs-export. It is possible that after a fresh restart of sketchup you will be able to export the mxs and the next time it will fail because it already uses 500MB more RAM at the beginning. Then close and reopen the program...
- split up the export in a few parts and merge them in studio

[Half Life]

The only current workaround would be to break up the scene and re-compile your final scene in Maxwell Studio instead -- but you are correct in that MSX file referencing would definitely be the solution you are looking for within SketchUp in the future (since they are unlikely to support full 64-bit).

Edit (obviously was beat to the point here )

Best,
Jason.

[JDHill]

One thing that has changed, which could come into play, is that the plugin exports more accurately now than it did before. Basically, in the past, if you had two instances of one component definition, where each appeared differently in SketchUp due to their inheriting different textures, the plugin would still export the first as a mesh, and the second as an instance, and the render would end up looking different than the viewport. Now, such a scenario is detected, with the result being that this component is considered as not being a candidate for instancing. You could trigger this scenario by leaving any part of the component definition without material, such that it inherits different textures in different instances of that component.