Rhino 8 Crashes after installing VA 3 Beta

Hi,

I just installed VA 3 Beta and Rhino crashes at opening. I followed the install instructions and remove previous versions of VA 2. Rhino 8 is running SR 3 and uses Core.NET.

Opening Rhino 8 via the VA desktop shortcut, Rhino just crushes after the first use plugin window appears. I still can open files that contain VA objects via the use of Rhino 8 (standard shortcut). But the VA desktop shortcut just makes Rhino to crash.

Any help would be much appreciated

Thanks

Hi Biz,

Do you have your Rhino 8 set to use the .NET Core Runtime? VisualARQ still requires the legacy .NET Framework. We have received some reports from a crash when .NET core is selected.

I’m currently working on a quick fix that will be released later today. The following VisualARQ features will require to change Rhino to use .NET Framework:

  • Grasshopper Components
  • Grasshopper Styles
  • Script API

We will add support for .NET Core before the final release.

In order to change the .NET Runtime, just run the command SetDotNetRuntime and select “.NET Framework”. You may need to run Rhino 8 in Safe Mode.

Regards,

Enric

1 Like

Hello!
First, congratulations on the (beta) release! The day has finally come… =)

I had this crash, too (the moment GH fired up). After doing what you suggested (SetDotNetRuntime), it worked.
Checking it out…

1 Like

Is there any side effects by doing the runtime trick?

I’m tempted to take it for a spin. I have time but also don’t have time…

Hi @keithscadservices,

There are no known downsides, unless you have specific plugins that require different runtimes, then, it is not possible to have all plugins working in the same instance.

We will add support for .NET Core soon, before VisualARQ 3 ships.

In the last VisualARQ 3 beta, VisualARQ will load correctly even when Rhino 8 uses .NET Core, but a warning message will be shown, and some features will be disabled:

  • Grasshopper Component
  • Grasshopper Styles
  • VisualARQ Script API

You can change Rhino 8 runtime as many times as you want. This doesn’t affect 3DM files.

Enric

1 Like

I still have the same crash problem, I already ran the command SetDotNetRuntime and select “.NET Framework” , you have other solutions?

Hi Miguel, does it crash when doing any specific operation? do you get a crashdump file on your desktop when you experience that crash? if you do, please rename that file before closing the Rhino Crash message. Then zip it and send it to us (visualarq@asuni.com).

Hi, I made the change to the NET Framework and it worked fine, but I installed the new LANDS DESIGN and it doesn’t work anymore, even after I canceled the installation. what do we do with it? I can’t work with VISUALARQ at all now, it just crashes

Hi @11170 As per Lands design support team , they are still working on compatibility between LD 6 and VA3. You just uninstalll both and reinstall VA3 fo now. It worked for me. It will take a week for them to solve it.

1 Like

Hi @asisintel,

We have discovered an incompatibility between the currently published VisualARQ 3 Beta and Lands Design Pre-Release. We’re going to publish updated versions of both plugins tomorrow.

You no longer need to change .NET Runtime to “.NET Framework” in order to run VisualARQ 3 or Lands 6, as this crash was fixed some weeks ago. “.NET Core” is fully supported now.

Enric

1 Like

Thats great news. @enric Thank you for the update!

greate thanks

Hi @enric . Are the plugins with updates releasing today? I am waiting as I want to use LA6 with VA3 for project asap!

Hi @asisintel,

Yes. I’ve just updated both installers. I have to make the public announcement with the changelog, but I’ll do it tomorrow.

You can download the new versions now (using the same links).

Enric

1 Like

where can I find the links? Is it the one I got in the Email when I got visualarq3?

Hi @11170,

Yes, the link hasn’t changed. You can fill in the download form again too.

Enric