[JDHill]

This thread is intended for any general discussion of plugin update 3.0.1.

[numerobis]

i just noticed that the autosave function of sketchup writes a temporary bak file into the MXM directory instead of the directory of the sketchup file.
I don't know what is happening here, but the autosave file is later located in the sketchup file directory, which is the correct location.
I don't know if this could be influenced in any way by the plugin - i suppose so since it is the MXM folder - but the problem is, that the MXM dir is on a network drive
and i have intentionally placed the skp on a local SSD to speed up the saving for big files...
So it would be great, if this could be corrected if possible.

I'm now remembering that i found skp bak file from time to time in the MXM folder wondering how they have been saved there. So i think it's a very old problem.

Win7 x64; SU 8

[JDHill]

I don't recall having noticed this, but will try to reproduce it. Could you please be more specific about what you mean by MXM directory? The assumption here would be that SU saves the bak file to the current directory; I don't believe I'm setting current directory explicitly anywhere in the plugin's code, so to help with this, I would need to know exactly what action is causing it (e.g. the use of a file dialog can change the process current directory, or it could be done by MXED when browsing for an MXM -- things of this nature), and then to see if it would be appropriate to force the current directory back to the SKP file's directory whenever that action has been executed.

[numerobis]

I have two search paths specified in the plugin options, one for mxm and one for textures, both on the same network drive. All referenced MXMs are located in this directory.
I never edit an MXM from the scene manager dialog to change it but only directly from the folder.
I'm currently using the custom file browser.

Very strange that first a temporary bak file is written to the network drive and then moved to the original directory as autosave file...

[JDHill]

Well, by rights, an application should never assume anything about the current directory, writing files by saying the equivalent of save("somefile.bak"), and should rather always use an absolute path, simply because there is only one current directory, which may be changed by anyone, at any time. Your description of the situation might suggest that the bak file is being written using a relative path, and the autosave file using an absolute path.

What I was referring to with dialogs & MXED would not specifically have to do with editing an MXM (though that could also apply), but simply with browsing to find one, either using a file browser (custom or not), or the Browse for MXM and Browse MXM Gallery functions, which pop up MXED in browser mode.

I guess it could take some time to reproduce this, and then to figure out what is triggering it.

[numerobis]

ok, thanks!

[fv]

Exporting to Studio does not work well with hdr.
When set the hdr at same as background and exporting to Studio the settings are changed to HDR instead of same as background. I then have to manually change the setting again in Studio to be the same as background. Apart from the fact that the rotation is off as mentioned before. There seems to be a bug in the hdr settings in Studio. Might even be unrelated to the SU plugin.
I haven't been able to test if things work well when exporting directly to Maxwell.
Francois
OSX

[JDHill]

Sorry, but there is no way for the plugin to communicate "same as background" in the MXS -- I imagine that may seem strange since the concept exists in both places, but it is nevertheless the case. Regarding the degrees vs. radians input for Offset in the plugin's IBL, I simply forgot to fix that, prior to building 3.0.1.

[fv]

ok, so that means that in Studio if you want to have the settings behave as set in SU you have to manually set the hdr's to bakground in Studio.
Anyhow, I hope you fix the hdr rotation bug.
Tx for all the other bugfixes. I do experience less crashes now. Although I no longer use Fire in SU. Studio is a little faster as well to see what the potential of a model is. So exporting to Studio is major to me.
Francois

[messire]

hi,
Can't seem to find link for the 3.01..in the portal its not showing..thnx

as for HDR, still got questions on how to set the right rotation so the sun in the HDR matches the north of my models...is there any method you guy use?
thnx
Nils

[JDHill]

3.0.1 is available from the betas area. As far as setting an HDR to match a certain scene, since there is no "north" in a random image, you can only line it up visually. Please note that there is currently a glitch in the HDRI offset values in the plugin, where they are accepting values in radians, rather than degrees, so if you want to work in degrees, you need to multiply by pi/180.