Help!

[Hal Newman]

Hi,
I've been having a pretty dire problem with my game since the new update.
If I open an image from my image library and then close it I get the error log showing up and I get a grey ghost box in the same size as the Image I just shut, resulting in having to restart Fantasy Grounds. It seems to be caused when I have a story pin in the Image. I tried a few Images without pins or tokens and they seem to close fine.
I've Included some images.
1. Here's an image of a map I have in my current game. As you can see there are a few pins on the image.
2. If I close out the image I get this error box....
3. once this greyed out box comes up, everything else I open, opens below it.

Is this problem a result of the upgrade, and if so can I go back to the earlier version of Fantasy Grounds? (I did backup my FG folder when I upgraded to V4.6.0)
I am running macOS Sequoia Version 15.1.1 (which is fairly new) and my version of Fantasy Grounds is V4.6.0 Ultimate (2024-11-21)
I've restarted my computer a couple of times..
any help would be appreciated as I have a big game session coming up

[RosenMcStern]

Same problem here, but I get a stacktrace that might be of use.

[21/11/2024 21:27:41] [WARNING] Object (CONTROL_GENERIC) deleted without cleaning up attached Lua object.
[21/11/2024 21:27:41] [WARNING] Object (CONTROL_GENERIC) deleted without cleaning up attached Lua object.
[21/11/2024 21:27:41] [WARNING] Object (CONTROL_CONTAINER) deleted without cleaning up attached Lua object.
[21/11/2024 21:27:41] [WARNING] Object (CONTROL_CONTAINER) deleted without cleaning up attached Lua object.
[21/11/2024 21:27:41] [WARNING] Object (CONTROL_CONTAINER) deleted without cleaning up attached Lua object.
[21/11/2024 21:27:41] [WARNING] Object (WINDOW) deleted without cleaning up attached Lua object.
[11/21/2024 9:27:46 PM] Campaign saved. (0s)
[11/21/2024 9:30:49 PM] [ERROR] API: System.NullReferenceException: Object reference not set to an instance of an object
at FG.CompositeImage.RemoveObject (AABGGCCNJPM DMCHMAMPCAA) [0x00006] in <a405798b6f8940e7b61a8876cc40c958>:0
at AABGGCCNJPM.ELGDPNMMIGL () [0x00024] in <a405798b6f8940e7b61a8876cc40c958>:0
at IFEMBGIBBMG.ELGDPNMMIGL () [0x00000] in <a405798b6f8940e7b61a8876cc40c958>:0
at GFJMMMMFDFP.ELGDPNMMIGL () [0x00018] in <a405798b6f8940e7b61a8876cc40c958>:0
at FG.CompositeImage.Cleanup () [0x0010b] in <a405798b6f8940e7b61a8876cc40c958>:0
at FG.RTTManager.RemoveCompImage (FG.CompositeImage PIIGCFODIFJ) [0x0000a] in <a405798b6f8940e7b61a8876cc40c958>:0
at FG.ImageControlUI.RemoveCompImage () [0x0001a] in <a405798b6f8940e7b61a8876cc40c958>:0
at HDACBIMOOAJ.ELGDPNMMIGL () [0x0004d] in <a405798b6f8940e7b61a8876cc40c958>:0
at GKGMBMKEHAJ.CLOOIAHJDIJ () [0x00000] in <a405798b6f8940e7b61a8876cc40c958>:0
at GKGMBMKEHAJ.KCFLDHIKIKM () [0x00083] in <a405798b6f8940e7b61a8876cc40c958>:0
at OHMAFMOJLCC.CLOOIAHJDIJ () [0x0001a] in <a405798b6f8940e7b61a8876cc40c958>:0
at PJFFFCNHHML.INCCFNFOPKO (OHMAFMOJLCC KFIAIMODOCG) [0x0000b] in <a405798b6f8940e7b61a8876cc40c958>:0
at OHMAFMOJLCC.BHJHHMBHGKK () [0x000b4] in <a405798b6f8940e7b61a8876cc40c958>:0
at OHMAFMOJLCC.GIGMIDKDKPF (System.Boolean FDMAIFANOJD) [0x00067] in <a405798b6f8940e7b61a8876cc40c958>:0
at OHMAFMOJLCC.LHOEGMNMLAG (System.IntPtr FAMBEIDCDAM) [0x0000e] in <a405798b6f8940e7b61a8876cc40c958>:0

[Zacchaeus]

Yes, you can roll back to the previous version. go into settings and then advanced and in the dropdown select Prev and then update. Note all of your players will also have to do this.

The error you are reporting is being investigated; it has been reported on Discord.

[Galadrim]

Rollback did not help. Still get same error now even in previous version.

It also leaves a black screen after you close an image that has no close button so it makes the client not usable.

[Galadrim]

I rolled back and updated again. Now it looks like it's not happening.

[Moon Wizard]

A hot fix was pushed for this issue about 4 hours ago; so you can grab the latest update by running a new Check for Updates.

Regards,
JPG

[RosenMcStern]

From someone who has managed the release of hotfixes for Really Big Software Systems: congratulations to Team SmiteWorks for their reactivity!