Rhino Inside (headless) displays popup about missing fonts

Hi,

I’m creating an application that uses Rhino.Inside to import .3dm files…

Am I right to assume that this popup should never be shown to me after I call RhinoDoc.OpenHeadless from within a new RhinoCore([], WindowStyle.NoWindow) context?

This is a bit annoying as I was hoping that using Rhino Inside with NoWindow and creating headless docs would never require UI interaction…

I’m going to check the “Don’t show this message again” and hope I never encounter a popup like this again :sweat_smile:


Using Rhino 8 SR23 (8.23.25243.17001, 2025-08-20) with Rhino.Inside 8.0.7-beta

Popup keeps appearing, even after checking the “Don’t show this message again”…
This could be a major blocker for us… @dale

Also reproducible with Rhino 8.20.25157.13001

Here’s a file with a font that’s not normally installed with windows
Firacode.3dm (27.4 KB)

And here’s some code to reproduce the issue. It’s a modified version of the Rhino.Inside sample project, modified to use OpenHeadless and WindowStyle.NoWindow.

OpenHeadlessFontsWarning.zip (2.5 KB)

To reproduce, simply build and run the code, then point it towards the Firecode.3dm path…

Interestingly, I cannot reproduce this issue with Rhino.Inside 7.0.0…

This issue does appear to be specific to OpenHeadless;

The popup does not appear when using CreateHeadless(file) nor CreateHeadless(null) + Import(file)

Hi @Jedd_Morgan,

I am looking into this.

https://mcneel.myjetbrains.com/youtrack/issue/RH-89162

Thanks,

– Dale

1 Like

RH-89162 is fixed in Rhino 8 Service Release 24

1 Like

Thanks Brian,
Just gave the RC a quick spin, looking good so far!

1 Like

Just a heads up @brian @dale,

I think we’re encouraging a similar issue with some files that show this popup:

Opening the file normally via Rhino8 shows this popup. Dismissing it with “No” is not a problem, the file opens pretty quickly.

But from Rhino.Inside (windowless, headless doc), the rhino process just gets stuck at 0% cpu indefinitely (I let it sit for 20mins to see what it would do, and nothing…)

I have very little visibility on what’s going on, but I highly suspect that some part of Rhino is waiting for a response from this popup.
Unlike with the font popup that we encountered previously, this one doesn’t actually display a window at all, so not 100% certain

Either way, the file cannot be opened with Rhino.Inside…


I’ll try and get a minimal reproducible file created for you guys to take a look at, but I’m not so familiar with this acoustic plugin, so it may take me a while to get something simple…

@Jedd_Morgan - a file and some sample code would be helpful.

Thanks,

– Dale

Appears to be resolved now.

Thanks Dale