I’m having this intermittent problem in Rhino 8 Va 3 current with most objects (No Va objects are in this file, just Rhino objects and Va Sections.) It’s been coming and going for a bout a month and has been particularly acute this last couple of days.. A clean reinstall of the video driver didn’t fix it, though restarting Rhino seems to make it go away for awhile. Trying it without Va for a bit to see if this makes a difference. If so we may need a fix, and in the meantime if anyone can report a similair problem it may save me some headaches.
Update: It appears that the only way to fix this has been to disable all Visualarq plugin components. I hope for a fix.
I first posted about the problem here, and it’s been intermittent since then: Disappearing Selected Objects
Luckily I’m not relying on parametric objects, just Va sections, in the current project. But I’ve had to create many clippling planes and associated cplanes to do what those now-deactivated Va Sections were doing.
Hi @djhg Without any file to reproduce this problem, I’m going a bit blind on this. I recently reported a similar issue to McNeel, which happens with geometry with a transparent colors inside blocks, and it was unrelated to VisualARQ, if it helps: https://mcneel.myjetbrains.com/youtrack/issue/RH-89896/Block-instance-hides-when-it-is-selected
If you say without VisualARQ doesn’t occur, I’d like to check it on my side.
Thanks Francesc. That link doesn’t work for me.
Most of the objects I’m working with are blocks, so I’m not absolutely sure the problem occurs with non-blocks, but when in my office in about an hour I will experiment to see, and I’ll send you a link to an uploaded project.
Another factor here may be that many of the objects have been imported from sketchup. I don’t recall it happening on projects with objects created within Rhino, but it has happened on blocks both created in Rhino and imported, and blocks created in Rhino containing objects both created in Rhino and in sketchup.
A characteristic of the issue is that when block edit is done on a disappeared selected block, it immediately appears again.
It’s happened at some point on most projects I’ve worked on over the last month or two, almost all of which involve mainly objects imported from Sketchup.
I’ve enquired on the RHino forum about this:
An update: it began happening again at the end of yesterday’s workday. It began immediately after I used a block as a source for a matchproperties command. I don’t know that was the cause, as I have had the problem begin while I was away from the computer making coffee. Also It’s only an issue with blocks. Nonblocks I can still select without them disappearing.
Hi @djhg as I’ve mentioned by PM, we need a file where you are experiencing this problem, and try to reproduce it in our machines. And then, determine if it’s something related to VisualARQ or not. If it’s related, we will fix it. Otherwise, it needs to be reported to McNeel developers.
Thanks Francesc.
I don’t know what PM refers to.
I did send a file to you, saved while the problem was present. It was more recent than the example I posted video of earlier to which you refer above. You weren’t able to reproduce the problem.
Today I worked with Va active for the afternoon for several hours until the problem occurred again, there’s an update on the Rhino forum about this.
I understand that it’s important to report any pattern of steps which reliably eproduce this issue, but I haven’t been able to recognize a pattern.
Hi @djhg, by “PM” I meant the email you sent me with the file.
I’ve been messing a bit with your new file, and I haven’t been able to reproduce that error either.
At this point I’m not sure how to help you. On one hand the error you describe doesn’t seem something caused by VisualARQ (I mean, it doesn’t involve VisualARQ objects, or any VisualARQ features), and no other user has reported a similar problem.
On the other hand, without being able to reproduce this problem, we go blind in guessing the reasons of this problem.
So any clue, pattern, or detail you notice from now on will be a great help in identifying the cause of this error. I hope you can get a better help from your other post at the McNeel Forum.