PDA

View Full Version : No text visible in Fantasy Grounds



wolf1066
July 6th, 2025, 01:37
I've been successfully using Fantasy Grounds on Debian Linux for over 2 years - currently on Debian 11.

A couple of days ago I bought the Blood Dice pack and ran the update, since then there has been no text on any of the buttons or windows, including the chat window. The buttons all work - I can pull up windows - and I can roll dice, but no text ensues.

I did a complete manual uninstall of Fantasy Grounds and reinstalled it, cold-started computer. Tested it using the default tutorial campaign and it still does not have any text - see screen capture.

Have attached my compiled logs.

Cheers

superteddy57
July 6th, 2025, 04:02
I'm on Debian 12 and it's working as intended. First have you tried a new fresh campaign with no extensions? That also includes any themes you have enabled.

wolf1066
July 6th, 2025, 04:32
That screen grab is from a brand new install - after manual uninstall of my original setup - using the "test campaign" that comes as standard, not one of my own campaigns. No themes enabled at all.

I wiped my .smiteworks and the folders in .config, reinstalled Fantasy Grounds, cold booted and then started it up, picked "load campaign" and clicked on the tutorial campaign. That's the sum total of actions. Then I typed /console (really hard when you can't see a cursor or what you're typing) chose compile logs - that button at least had text in it - then uploaded the logs here, per the instructions given to me by Joseph after I reached out to Tech Support.

LordEntrails
July 6th, 2025, 04:35
According to the logs you attached, you have the Dark Theme enabled. Try without it.
BUT, the Dark Theme should work...
Can you attach a screen shot of what you are (not) seeing?

wolf1066
July 6th, 2025, 05:09
The "Fantasy Grounds Test.png" file on the original post is a screen grab of what I'm not seeing.

Edited to add:

64747

All themes disabled

pindercarl
July 6th, 2025, 13:49
The "Fantasy Grounds Test.png" file on the original post is a screen grab of what I'm not seeing.

Edited to add:

64747

All themes disabled

It looks like there may be an issue with your plug-ins. In the install directory look in ../FantasyGrounds_Data/Plugins and verify that libfreetype.so is present.

wolf1066
July 6th, 2025, 13:58
Yes, it's there. Freshly installed as at the date/time of the reinstall earlier today.

pindercarl
July 6th, 2025, 14:14
Yes, it's there. Freshly installed as at the date/time of the reinstall earlier today.

Try extracting the .so from the attached ZIP and replace that file. It is possible that the updated .so is not supported on Debian 11.

wolf1066
July 6th, 2025, 20:40
and the prize goes to pindercarl! That worked. Replacing libfreetype.so fixed the problem.

Many many thanks for that.

pindercarl
July 6th, 2025, 20:45
and the prize goes to pindercarl! That worked. Replacing libfreetype.so fixed the problem.

Many many thanks for that.

It will work for now. Once the client is updated, the plug-in will be overwritten. I'll have to look into building freetype for older OS versions, but Linux is not in my wheelhouse. Some new features in progress require a newer version of freetype. The earliest version of Linux we officially support is Ubuntu 22.04 which is a year newer than Debian 11. Have you considered updating to Debian 12?

wolf1066
July 6th, 2025, 20:55
I guessed it was a short-term fix until the next time the client updates. I've not long ago undergone an unplanned "update" (read: complete rebuild) to Debian 11 from 10. I could go to 12, I suppose. Any idea how smooth the transition's likely to be?

pindercarl
July 6th, 2025, 21:03
I guessed it was a short-term fix until the next time the client updates. I've not long ago undergone an unplanned "update" (read: complete rebuild) to Debian 11 from 10. I could go to 12, I suppose. Any idea how smooth the transition's likely to be?

It's unlikely to be very smooth.

wolf1066
July 6th, 2025, 21:18
OK, I'll budget a day or 2 to do it. Thanks

MrGrenadine
July 7th, 2025, 03:28
Hi! I just encountered the same problem today on my Macbook. Will that file work for me, too, or is that only a Linux solution?

pindercarl
July 7th, 2025, 03:59
Hi! I just encountered the same problem today on my Macbook. Will that file work for me, too, or is that only a Linux solution?

The .so file is only for Linux. Which version of Mac OS are you using?

MrGrenadine
July 7th, 2025, 04:41
The .so file is only for Linux. Which version of Mac OS are you using?

Its an older Macbook --- 10.13.6

pindercarl
July 7th, 2025, 12:56
Its an older Macbook --- 10.13.6

Hmm. I tested locally on an old doorstop running 10.14 and the dylib is working normally. The minimum system requirement for FGU is MacOS 11+ so both of these are below spec. There are some upcoming changes that will require the updated library. You can replace the dylib in your installation with the one in the attached zip file and see if it addresses the issue temporarily. To find the library, Control+click on the application, choose "Open package contents," and navigate to the plug-ins directory. The steps will need to be repeated following any updates. As noted, if this works it is only a temporary fix and you will need to update the OS.

MrGrenadine
July 7th, 2025, 17:33
Thanks so much! I'll test it as soon as I can.

MrGrenadine
July 7th, 2025, 22:43
It worked! Thanks so much -- you really are a SmiteWorks Saint

Moon Wizard
July 8th, 2025, 00:15
Just a reminder, the files that @cpinder provided are just supposed to be a temporary short-term band-aid until you can update your computer to a supported version. The FG builds going forward will be using the new libraries as we update to the most recent Unity supported build and adding Apple Silicon native support.

Regards,
JPG

wolf1066
July 18th, 2025, 22:58
Well, tried an upgrade to Debian 12, now FG won't run at all, manually removed FG and tried reinstall, wouldn't install (I enter "Y" for the EULA and nothing happens, terminal closes) downloaded fresh copy of FGUWebInstall.bin still won't install - same result.

And the Kernel errors when updating so I have to manually choose the older kernel at boot in order to start my machine.

Yay! :/