Bullant Geomgym tab missing in Rhino 8

I have just upgraded to Rhino 8 and my 2 favourite grasshopper functions in bullant are gone. ggsweepprofile and ggcatalogueprofile no longer exist. Am I missing something? are they moved and I cannot find them. Is there an update or plugin to fix the issue?

Hi David,

Glad you find the plugin helpful. I’ve just rebuilt the plugin, see if updating it fixes the missing components. They are there for me still.

Thanks,

Jon

Hello Jon,

We have noticed that the most recent builds of bullant are not showing Geogym in grasshopper. We have been running an older version. 24.8.14.8 still works but the angle profiles in geo gym are having a weird glitch on only the 1/4" thicknesses.

Is there any warnings or errors shown on the rhino command bar as grasshopper starts? Is this running dotnet core or framework?

Can you please share a script demonstrating a profile that isn’t accurate? Thanks.

Here is the history of the command line.
Command: _Grasshopper
Command: _Polyline
Command: _Polyline
Exception
at System.Xml.XmlDocument.CheckName(String name)
at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI)
at System.Xml.XmlDocument.CreateElement(String name)
at GeometryGym.ggSettings.convertToXML()

The ‘’ character, hexadecimal value 0xE000, cannot be included in a name.

Exception
at System.Xml.XmlDocument.CheckName(String name)
at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI)
at System.Xml.XmlDocument.CreateElement(String name)
at GeometryGym.ggSettings.convertToXML()

The ‘’ character, hexadecimal value 0xE001, cannot be included in a name.

Exception
at System.Xml.XmlDocument.CheckName(String name)
at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI)
at System.Xml.XmlDocument.CreateElement(String name)
at GeometryGym.ggSettings.convertToXML()

The ‘’ character, hexadecimal value 0xE002, cannot be included in a name.

Exception
at System.Xml.XmlDocument.CheckName(String name)
at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI)
at System.Xml.XmlDocument.CreateElement(String name)
at GeometryGym.ggSettings.convertToXML()

The ‘’ character, hexadecimal value 0xE003, cannot be included in a name.

Exception
at System.Xml.XmlDocument.CheckName(String name)
at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI)
at System.Xml.XmlDocument.CreateElement(String name)
at GeometryGym.ggSettings.convertToXML()

The ‘’ character, hexadecimal value 0xE004, cannot be included in a name.

Exception
at System.Xml.XmlDocument.CheckName(String name)
at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI)
at System.Xml.XmlDocument.CreateElement(String name)
at GeometryGym.ggSettings.convertToXML()

The ‘’ character, hexadecimal value 0xE005, cannot be included in a name.

Exception
at System.Xml.XmlDocument.CheckName(String name)
at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI)
at System.Xml.XmlDocument.CreateElement(String name)
at GeometryGym.ggSettings.convertToXML()

The ‘’ character, hexadecimal value 0xE006, cannot be included in a name.

Exception
at System.Xml.XmlDocument.CheckName(String name)
at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI)
at System.Xml.XmlDocument.CreateElement(String name)
at GeometryGym.ggSettings.convertToXML()

The ‘’ character, hexadecimal value 0xE007, cannot be included in a name.

Exception
at System.Xml.XmlDocument.CheckName(String name)
at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI)
at System.Xml.XmlDocument.CreateElement(String name)
at GeometryGym.ggSettings.convertToXML()

The ‘’ character, hexadecimal value 0xE008, cannot be included in a name.

Exception
at System.Xml.XmlDocument.CheckName(String name)
at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI)
at System.Xml.XmlDocument.CreateElement(String name)
at GeometryGym.ggSettings.convertToXML()

The ‘’ character, hexadecimal value 0xE009, cannot be included in a name.

Not sure what dotnet core or framework means. I’m not a programmer though I am tech savvy, tell me what that means an I can figure it out.

I have screen shots to send you because I don’t use scripts just the UI
Untitled 2.pdf (675.3 KB)
Untitled.pdf (450.0 KB)

I encounter the same issue. Reinstalling Bullant fixed the problem for me. Cheers

Thanks, there was a bug in an older build. Recent builds should resolve it. Glad it is now working.

I fully uninstalled bullant 24.8.14.8 restarted rhino and reinstalled the latest version of bullant and the issues seem to be resolved now. Thank you

The angle profiles of all L#x#x1/4" thick and under still don’t work correctly.

Can you please share a simple gh script that demonstrates the problem? I don’t see it here yet.
Which units do you use in rhino? Feet or inches? Out of the box template including tolerance?

Thanks,

Jon

I just did a test based on your question to see if this issue persisted in any drawing template. It does not. I tried a drawing with the small objects inches template and the angle profiles were fine. I used a L4x4x1/4 in this example. I then tried it in a large objects feet template and the same profile failed. Also large objects inches feet template failed, but the small object - inches, Feet and inches template worked. It seems that the angle profiles don’t work on large object templates but are fine in any small object template. These are "out of the box templates, just open the file and draw a single straight curve and apply the profile to it with GH.

I’ve pushed an update to the plugin. Can you please update from rhino package manager, and see if that works better? Here is the gh script I test with.

241210 sweep.gh (4.2 KB)

The update made an improvement to the angle profiles. Now it shows the vertical and horizontal flanges, but they appear as wedges. I used the script you provided in a large objects template to get this result.