Maxwell Render | Official public forum

You can't. You can prevent the plugin using the standard dirs (they should only be used the first time the dialog is shown in any given session -- after that, they should remember the previous folder) by setting Options > User Interface > File Browsers to Default, in which case the plugin will just use the standard file dialogs supplied through the SketchUp Ruby API.

I'll see about adding some kind of configuration for the custom browsers.

brodie_geers wrote:Sorry, I'm sure this has been talked about before but I'm just too darn lazy to look through the posts from awhile back and even then perhaps something has changed. You've implemented the proxies very well. I'm using them for grass now which is coming in really handy. But Richard had come up with an idea some time ago where there would be a sort of super proxy which would reference an outside .mxs file for it's source object rather than an object within the SU scene. Have you put any more thought into this and whether or not it's possible?

-Brodie

JD I've got to bring this up again for what I'm finding as the main reason for this request from this end anyway - at ALL costs to avoid having to ever open a SU export in studio. I'm still finding it so darn buggy. Again I've been battling for two days in an attempt to get a render out of studio which exported from SU without hitch.

Not to say you aren't having problems Richard, but I'm always so mystified when people say Studio gives them a hard time... it's always worked flawlessly for me.

Could it be that something you are trying to get studio to do is not the way it is designed to work? It is a very different design environment from Sketchup... a big part of why I did the videos focusing on Studio so much was I know the high value it has to Sketchup users (not to mention ZBrush and 3DCoat users).

Best,
Jason.

No mate just opening a simple scene that exported direct from SU without hitch, adding trees (MXS) then export.

Finding the same issue that Brodie and Stefan reported, with file not saving or exporting, then a few more issues like half my roof tiles disappearing.

Gotcha -- I definitely need to start experimenting more with manipulation deeply nested components more in Sketchup to see how that plays out in Studio... I suspect my modeling style caters to Studio since I learned it about the same time I was really learning Sketchup.

Sorry to hear you are losing days to headaches like that.

Best,
Jason.

Small request. It doesn't seem to be possible to enter a negative value for the V degrees box (up/down adjustment) when positioning your HDRI. In other words, you can't move the HDRI down a bit from it's default position.

-Brodie

IBL Offset should go from -360° to 360°, for both U and V, where it used only to go from 0° to 360°. It is working fine here, anyway -- do I need to do anything special to reproduce the issue?

Hrm, just to clarify, you can enter a negative value into this slot?


I didn't think it was a bug to be reproduced, just a feature that was mistakenly left out. The slider starts at the far left so you can't slide it to a negative number (unlike ground plane elevation) and when I select the number I can type in 20 and it works fine, but if I type -20 and hit Tab or click elsewhere it goes back to 0.

-Brodie

Also, I just found out that there's a new SU plugin. I didn't see anything about it and it wasn't listed as one of the plugins with the Fire preview (because it doesn't have it) so I assumed 2.5 worked fine with the old plugin. It pretty much does, until you try to link up a SU texture with a material created in 2.5 in which case it just refuses to do so. Took me awhile to even think about going to the gateway to see if there was a new plugin.

-Brodie

Haza! and that solved my HDR positioning issue as well.

-Brodie

Ah, yes that might do it. Also, the 'triangle index' problem you were having previously should not be present anymore; apparently it was due to an obscure issue in the SDK.

brodie_geers wrote:Also, I just found out that there's a new SU plugin.

Maybe Next Limit ought to inform SketchUp users by email, that there is a new plugin available along with the 2.5 upgrade?

"Fire" is AMAZING.
JD, will it be possible to implement this feature in the SketchUp plugin? - and if so, when might we see it?

/Stefan

JDHill wrote:Ah, yes that might do it. Also, the 'triangle index' problem you were having previously should not be present anymore; apparently it was due to an obscure issue in the SDK.

Dam JD that's great news! Ta mate!

Maybe Next Limit ought to inform SketchUp users by email, that there is a new plugin available along with the 2.5 upgrade?

In case that happens in the future, you should assume that whenever there is a new version of Maxwell, that there will also be a new build of the plugin, regardless of plugin-specific developments, because we need to maintain binary compatibility on MXS & MXM files.

JD, will it be possible to implement this feature in the SketchUp plugin? - and if so, when might we see it?

Sure, of course anything is possible -- it is just a matter of time, and I can't give any estimates on this at the moment. It's pretty fun, due to 32-bit limitations; I don't think anyone wants to have both SketchUp and Maxwell scenes in that small memory space at the same time. So it's a little more complicated than one might wish.

Richard wrote:

JDHill wrote:Ah, yes that might do it. Also, the 'triangle index' problem you were having previously should not be present anymore; apparently it was due to an obscure issue in the SDK.

Dam JD that's great news! Ta mate!

AH! someone tell me what the triangle index problem was! I must know what issues I can celebrate being squashed.

-Brodie