Heron GDAL error 'OSGeo.GDAL.GdalPINVOKE' threw an exception

[Soporte3 (Soporte)]

Any ideas about what is going wrong and how to fix it? I installed Heron from the PackageManager in Rhino 8. Thanks in advance.

1. Solution exception:The type initializer for ‘OSGeo.GDAL.GdalPINVOKE’ threw an exception.
   
   

[Brian_Washburn]

Hi @Soporte3 ,
Can you try loading Heron from disk as described here:

Import Vector error

Hi @Dongyeop_Lee , I have seen this happen when installing Heron through the package manager, which is the preferred method (related Heron Github issue). Basically, Heron is looking for GDAL libraries and can’t find them when they are installed in the packages folder. The work-around for this issue has been the following: in Grasshopper Settings>Solver>Plug-in Loading, scroll down to Heron and click the little puzzle piece icon so that you see the disk. [image] I have found a possible fix …

-Brian

[Soporte3 (Soporte)]

Thanx Brian… loading Heron from disk worked fine just once, then I installed Human via PackageManager and threw this new error:

1. 8840f75be1e66b9f12d2493f2455b7a2
2. Solution exception:The type initializer for ‘OSGeo.OSR.OsrPINVOKE’ threw an exception.
   
   

[Roberto_Cognoli]

HI!
do you solved?

same issue
tried to load from disk, work once, than nothing.

[Brian_Washburn]

I updated Heron to v0.4.3 a couple weeks ago and tried a new approach to resolving the issue of finding the GDAL libraries. Are you using v0.4.3?

-Brian

[Roberto_Cognoli]

I’m using v.0.4.4

[SimonM]

Same here, though on Mac (Apple Silicon) and using 0.4.2.1
No luck with disk loading enabled.

Anything I can do to help debug?

[Adam_Lagner]

I usually activate Grasshopper plugins by moving them into the Components folder. That’s what I did in this case as well, which resulted in the issue described above. What solved my problem was deleting the plugin from that folder and then installing it through the pop-up window in Rhino that asks about the missing component and offers to install the plugin. The plugin then ends up in a different location, and the libraries work correctly.