Overall, I am enjoying the new ViaualARQ however, I have a similar experience with VisualARQ crashing Rhino 6. I do not have, nor have had V-Ray installed. I do have Brazil and Bongo plugins as well as several grasshopper plugins. When starting Rhino, a list of grasshopper errors will appear (see attached txt file), several of which name the Clipper Components plugin as having some issue. The Clipper Components plugin will not properly load despite several uninstall/reinstall attempts.
Running Rhino 6 with VisualARQ does feel slightly more sluggish than running Rhino without the plugin. Rhino also appears slower in updating the graphics of ViaualARQ components and misses some objects while in shaded mode. Technical mode appears to work fine.
Hi! I dont know, if this is relevant comment here, but I have just noticed a display error in rendered (and others) display views using skylight and shadows. There are some shadow fragments when using clipping plane. This happens only with VisualARQ loaded to Rhino 6. See picture bellow.
I have downloaded and tried the WIP version, and it works pretty fine. No errors appeared when loading VisualARQ nor Grasshopper. And it appears to be slightly faster in Rhino 6 than the 21.0 version.
As @petumatr mentioned above, I don’t have the shadow fragments when using clipping plane, but I do noticed that VisualARQ objects appears to have some issues when using clipping plane in some display modes:
-Raytraced display mode: Clipping Plane ignores all VisualARQ objects.
These display issues on rendered display modes when a Rhino clipping plane is enabled are fixed. Raytraces display mode still has some problem with VisualARQ. We’ll try to fix them for the next update.
Let me know if any of you have problems with this new release.
I’ve tried to exend a wall until it reach another wall resulting in a T connection without a crash. Can you send me a sample model and the steps to reproduce the crash?
I tried also to create 4 walls and a space in a hidden viewport, and I can select the space without problems. Can you send me also a model where your’re seeing this issue?
Again, I tried to save the model with the 4 walls and the space in Rhino 6 using a Rhino 5 format, and I have been able to open it in Rhino 5 with VisualARQ 2.1. Are you using VisualARQ 2.1 in Rhino 5? VisualARQ 2.0 cannot open files from VisualARQ 2.1.
I’m unable to reproduce this issue. Can you send me an screenshot?
Which PDF printer are you using? We’ve been using here the “Microsoft to PDF” and “CutePDF” without problems. Using the “Rhino PDF” we’ve just discovered that some objects are not visible (specially texts) and we’re currently investigating why.
Is the crash happening all the times? Or only when trying to print some specific models?
The v2.1.1 update to VA appears to have fixed several of the earlier crashes I was experiencing, thank you! Now I have a new bug to report which is a more consistent crash. A specific model (or any VA file with the slightest complexity) causes Rhino to crash either when opening or within moments of opening. The file can be opened and worked on when VA is not enabled; all views are set to wireframe; and tried deleting the last few VA objects added to the file but a crash is inevitable.
I have sent a plethora of crash reports to McNeel (under my user name) over the past two days that are related to this crash.
Hi guys, I have the latest release, I don’t seem to be getting any fills shown on my sectioned geometry in 3d (whether VA or Rhino) in any display mode, Geometry seems to be empty even if Show Fills is ticked in display options and geometry section attributes are correct, any ideas?Line types etc don’t show either. They all do show when creating a section view though. Same exact geometry and settings appears as “solid” in R5. Thanks!
Note: Cuts seem to work fine on plan (Level View active) and they even work in section when both section and level are activated, but not when only section is active. Current workaround is to have a level above all geometry and keep it active in 3d view.