[JDHill]

Interesting -- the smoothing issue occurs on OSX, but not on Windows. Suffice to say, it's not the plugin doing this; it is simply exporting whatever data SketchUp gives it, and it would appear that this data is different depending on the current context.

The second issue is also reproducible (irrespective of OS) here, and appears to point to a problem with instances. Can you confirm that (a) it happens both in Fire and Maxwell Render, and (b) that it does not occur when instances are disabled?

[stefan_kaplan]

Can you confirm that (a) it happens both in Fire and Maxwell Render, and (b) that it does not occur when instances are disabled?

a. and b.: Confirmed.

[JDHill]

Here's another thing to confirm, regarding the smoothing issue: does it still appear when you export to MXS via File > Export 3D, then open or render the resulting MXS file in Maxwell Render or Studio?

[numerobis]

The second issue is also reproducible (irrespective of OS) here, and appears to point to a problem with instances. Can you confirm that (a) it happens both in Fire and Maxwell Render, and (b) that it does not occur when instances are disabled?

The "missing faces" problem has already been there since the last build. It appears with nested components. I had already prepared a scene to send it to you, but i forgot about it...



The windows of the right building are nested components. All other parts have been exploded.
I have included the left facade, because it seem to have an effect on the missing faces. If you delete all of them, more faces will be rendered.

[stefan_kaplan]

Here's another thing to confirm, regarding the smoothing issue: does it still appear when you export to MXS via File > Export 3D, then open or render the resulting MXS file in Maxwell Render or Studio?

Nice one: No, all smoothing works just fine when exported via File>Export 3D

[stefan_kaplan]

Richard recently posted a comment about the Undo history in SketchUp, that is being filled up with actions when a render is started.

When Re-Exporting the Scene to Fire, after eg. push-pulling a face, it takes 21 undos of so-called "Proporties" before you can undo the push-pull...
I guess you would often want undo something after seeing the result in Fire, and it would be great if the Undo history in SketchUp was not affected by Maxwell.

/Stefan

[JDHill]

Thanks for confirming regarding the smoothing issue. The only difference when exporting via File > Export 3D instead of the toolbar commands is that the latter call the export via Ruby. I also notice a time lag when using Export 3D, so it might seem that SketchUp is doing some extra bookkeeping when you export that way.

Regarding these dark faces, I don't yet have any kind of theory about it. The only difference when using instances is that an instance is written instead of geometry -- everything else is the same, meaning mainly, the object's transformation.

Regarding the undo stack, as far as I know, there is no way around it -- I have to store data on the model if we mean to use it, and SketchUp considers this as being an interesting change. Perhaps I can find a way to make it ignore those changes, I'll let you know.

[Richard]

JD in regards to the UNDO state, is there an action that could be introduced at the "end of export" that performs an undo/s automatically to that prior to export by default? Thereby the next undo enacted by the user is actually undoing that action preformed directly prior to export.

Some issues do occur here though with SU native undo memory which means that the number of undos required to get to the "before export" state limits the number of user undo's. For a workaround I have since been careful to manage file saves / versions to allow reloading should I wish to get to an earlier version.

[JDHill]

Well, it did occur to me after writing the last post that there's a specific way to do this, so I'm testing that now to make sure it doesn't break things elsewhere.

[Richard]

I can imagine with anything thats always the issue mate, though if history so far proves correct it wont just work but add stuff one couldn't even dream of like telapathic communication or something!

[brodie_geers]

It doesn't look like the FIRE preview takes into account your camera trickery using offsets to match the maxwell camera to the SU camera when using 2point perspective mode in SU.

-Brodie

[JDHill]

Correct; the key piece of info for doing that is not exposed via Ruby.

[brodie_geers]

You're talking over my head there, but do you foresee any workarounds beyond exporting to MXS, checking the camera offset settings, and then copying them into SU?

-Brodie

[JDHill]

Sorry, it means that I don't have the information I need to calculate the offset, except during the actual MXS export. You'd probably be better off using the Maxwell shift lens.

[chedda]

Outstanding work JD what a revelation ! My only concern is using a single core in 32 bit mode are these limitations caused by sketchup and it's architecture ? After using fire in studio it is a little sluggish compared. You sir have just confirmed my investment in Maxwell & Sketchup.