[polynurb]

when i create a mxs reference, and i select the created instance, i don't see any options in the properties box, just the subdivision controls.

i had this before, but back in v2. it was working ok for a while, but i can't remember when the controls where still ok.
haven't used the function inside rhino much lately.

what could be the reason/solution?

some .net stuff?

thnx,
D.

[JDHill]

Sorry, but it works fine here. Does the referenced MXS still show up in the export/render? Have you run any tools that would remake, or otherwise affect user data attached to block definitions? The properties page decides whether to show the regular UI, or the MXS Ref one, based on whether it finds some specific user data attached to the definition. There was a problem in older V5 SRs, where the definition was not storing its data properly, but I just checked here with SR7 and SR8, and it is working fine.

[polynurb]

did you apply some remote fix?
it is working again right now, i can see the box and change settings fine!

could it be somehow related to using a "no template" file for setting up the references scene initially?and that reopen made it go away?

in that file i also had a problem with fire not being linked to a camera (only switching view/mat change updated), this problem also fixed itself by reopening.

[JDHill]

I see no way for those two things to be related. The camera does not have any sort of real "direct" connection with what happens with the viewports, so in rare circumstances, it's possible for the camera that's current inside the plugin to become unsynchronized from the view that's active in Rhino. Switching (meaning, selecting) between viewports once or twice should take care of it, if that happens. The MXS Reference thing seems much stranger, though -- if the data's there, it should always be there, and if it's not, then not. I didn't quite grasp your reference to using an empty template, though, so could you please provide a specific sequence of steps I could try?