Page 1 of 1

Invisible instances... sometimes

Posted: Thu Nov 19, 2009 7:11 pm
by osuire
Hi JD,

I had the case of invisible instances again, with 2.0.1. : A block containing one object was shown properly, and another one containing multiple objects wasn't.
There is no block nesting, and my objects were a collection of surfaces and polysurfaces ; no meshes this time.
Strangely, I just re-opened the file, and it seems to work.

Anyone else seeing this from time to time ?

--
Olivier

Re: Invisible instances... sometimes

Posted: Thu Nov 19, 2009 7:17 pm
by JDHill
It seems, though I have not confirmed it (by definition it would not be repeatable), that from time to time Rhino loses track of things in its instance table...re-starting, or possibly just re-opening the file, seems to get things back in their proper places.

Re: Invisible instances... sometimes

Posted: Thu Nov 19, 2009 7:44 pm
by osuire
Thanks for the fast answer, as always !

What is amazing here is that it happened on two (very) different machines (32 vs 64 ; XP vs Win 7)
Although it was the same base model , the students created the blocks each in their own way, and there was all sorts of little differences between their two files,
but when they both hit "render", they both couldn't see the instances.

I hate it when these funky behaviors happen during a training.
Anyway, I'm not sure exactly what to ask the Rhino guys...

--
Olivier

Re: Invisible instances... sometimes

Posted: Thu Nov 19, 2009 7:54 pm
by JDHill
If you have a .3dm where this is repeatable, I would like to take a look at it...maybe I can trap it while running in the debugger and try to see what's going on. As far as debugging something like this on your end, what you would want to do is to check out the plugin's Log Viewer - that shows you exactly what is getting exported. It will tell you the number of meshes and the number of instances it is exporting; that looks like this:
Code: Select all
* line 279: Render, _notify, generating new MXS meshes, press CTRL+ALT+SHIFT to cancel
* line 280: ExportScene, _info, cacheMXSMeshes=False
* line 281: ExportScene, _info, exportInstances=True
* line 282: ExportScene, _info, exportActiveCameraOnly=False
* line 283: mesh transfer 100.0% completed (1 of 1)
* line 284: Exporting blocks as instances (see Plugin Options)
* line 285: block transfer 08.0% completed (2 of 25)
* line 286: block transfer 16.0% completed (4 of 25)
* line 287: block transfer 24.0% completed (6 of 25)
* line 288: block transfer 32.0% completed (8 of 25)
* line 289: block transfer 40.0% completed (10 of 25)
* line 290: block transfer 48.0% completed (12 of 25)
* line 291: block transfer 56.0% completed (14 of 25)
* line 292: block transfer 64.0% completed (16 of 25)
* line 293: block transfer 72.0% completed (18 of 25)
* line 294: block transfer 80.0% completed (20 of 25)
* line 295: block transfer 88.0% completed (22 of 25)
* line 296: block transfer 96.0% completed (24 of 25)
* line 297: block transfer 100.0% completed (25 of 25)
* line 298: ExportScene, _info, total export time: 00:00:00.1716000
* line 299: OnEndWriteMxs, _notify, ExportScene returned: True
Whereas, the same export with instances disabled looks like this:
Code: Select all
* line 307: Render, _notify, generating new MXS meshes, press CTRL+ALT+SHIFT to cancel
* line 308: ExportScene, _info, cacheMXSMeshes=False
* line 309: ExportScene, _info, exportInstances=False
* line 310: ExportScene, _info, exportActiveCameraOnly=False
* line 311: mesh transfer 11.5% completed (3 of 26)
* line 312: mesh transfer 23.1% completed (6 of 26)
* line 313: mesh transfer 34.6% completed (9 of 26)
* line 314: mesh transfer 46.2% completed (12 of 26)
* line 315: mesh transfer 57.7% completed (15 of 26)
* line 316: mesh transfer 69.2% completed (18 of 26)
* line 317: mesh transfer 80.8% completed (21 of 26)
* line 318: mesh transfer 92.3% completed (24 of 26)
* line 319: mesh transfer 100.0% completed (26 of 26)
* line 320: ExportScene, _info, total export time: 00:00:00.3276000
* line 321: OnEndWriteMxs, _notify, ExportScene returned: True
So, with instances enabled, if the number of blocks indicated is different from session to session using the same document, then it means that in one of the sessions, Rhino is not telling the plugin about some instances. Whether that means that there is some obscure issue about how I'm asking for them, or if it indicates a transient bug in Rhino, at least with a repeatable scenario, we'll have something to work with. Until I can confirm that this wouldn't be related to plugin code, it probably will not do alot of good to ask the McNeel people about it.

Re: Invisible instances... sometimes

Posted: Fri Nov 20, 2009 11:05 am
by osuire
Ok, I get the idea.
If it happens again, I'll save the log.
But I'm not sure if I can get a repeatable case, from a session to another...

Thanks,

--
Olivier