[fv]

Is it possible to add a menu for editing the mxs reference.
Now I have to navigate to were my mxs files are and edit from there.
But in a file full of mxs references it would help a lot if I can just control click a reference and Studio opens with the appropriate file, safe and update the reference.

The way we work now in Sketchup is to build files with as much mxs references as possible. The workflow since the mxs references is so much faster now. I am modeling an office interior with all sorts of detailled furniture that was impossible to model in Sketchup before. Just great.


Francois

[JDHill]

Sure, no problem, I'll add that.

[fv]

perfect.

A tip;
you can just type in a name in de mxm component that shows up in your model. Easy to identify the referencetype.

Second tip;
I make mxs files with several models in them of the same type of furniture, for instance for different sizes or colorschemes. I hide the ones I don't want to see in my renders.
Like that I can just edit the mxs file to see a larger chair and update to see how things look. That's why I would love to just double click the reference and edit the mxs file in studio.

[fv]

Would it be possible to hide and unhide named groups in a mxs reference in Sketchup. That way I can quickly change colorschemes of a reference without even going into Studio.

well, maybe I shouldn't overask...

[JDHill]

It would not be impossible, since nothing stops the plugin from opening/changing/overwriting the file, but I don't think it would be appropriate; for instance, a different SKP may also reference the same MXS. It would also partially defeat the purpose of having MXS references at all, since it would mean opening the MXS during export, when memory usage is already high.

[fv]

ok, I see.
Well, it would already be great if I can just control click a reference to see it open in Studio.
tx for adding this.

Are you any closer for OSX users to have the plugin work without Sliverlight ?

Francois

[JDHill]

I didn't catch the CTRL+click part of your original post; it won't be that, but rather an item in the context menu. On the SL question, as ever, the answer is: of course, I am working on that. There will not be much to tell about it until one day an update is posted where the whole UI has been replaced.