Updated - Can't Launch on Mac (Mojave)

[fieldson]

Update - Solved
Solution from Moon Wizard and Jaharmi in March 2022. See their posts for more details, but the short version is there is a plist setting that is incorrect for screen width that caused the crash, and the solution was deleting the com.smiteworks and unity.smiteworks plist files and restarting.

---

I just ran the updater and FG crashes when I try to launch. Not sure where to dig for versions inside the app contents, but the jist of the crash log is:

Process: Fantasy Grounds [630]
Path: /Applications/SmiteWorks/*/FantasyGrounds.app/Contents/MacOS/Fantasy Grounds
Identifier: unity.SmiteWorks.Fantasy Grounds
Version: 1.0 (0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Fantasy Grounds [630]
User ID: 501

OS Version: Mac OS X 10.14.6 (18G8022)
Report Version: 12
Time Awake Since Boot: 80 seconds
Crashed Thread: 0 tid_307 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
validateTextureDimensions:1081: failed assertion `MTLTextureDescriptor has width (30720) greater than the maximum allowed size of 16384.'

I expect that I will wipe and re-install a clean copy this evening, unless something obvious pops up

[Moon Wizard]

The Fantasy Grounds main application was not updated in the update yesterday; only the data files and the updater application.

Please check any antivirus software you have installed; and make sure it is not blocking or quarantining the FantasyGrounds or FantasyGroundsUpdater applications.

Regards,
JPG

[fieldson]

Thanks for the feedback. No issues on antivirus.

I tried a clean install, and still no success.

I notice the permissions on my MacBook (where the launch is crashing) are different from my iMac (haven't updated):

[ls -l@ for app on MacBook - doesn't work]
drwxr-xr-x 3 gregory admin 96 Feb 17 17:42 FantasyGrounds.app

[ls -l@ for app on iMac - works]
drwxrwxrwx@ 3 gregory admin 96 Dec 8 2019 FantasyGrounds.app
com.apple.FinderInfo 32
com.apple.metadata:_kMDItemUserTags 52

I am curious what the permissions should be, and if the updater may have changed, since I see permissions update in the logs.

[Moon Wizard]

I've forwarded to our developer who handles the Mac/Linux install/update; but he's in Texas where they are having power issues. Hopefully, he might have some ideas to try.

Regards,
JPG

[smelton]

Last time I saw an issue like this it was ACLs ... you can check to see if you have ACLs on the FGU directories using ls -le
.. and remove them recursively with chmod -RN

[Nemesismmx]

This is happening to me regularly. So far, the only cure is to delete an application and open an updater that will download the application again. You only need to delete the executable FantasyGrounds.app from the SW folder.
I thought that this is something specific for my case (macOS 11 and M1 chip) but apparently is a widespread issue.

[fieldson]

I've had a moment to try a few things:
1.FantasyGrounds.app didn't have ACLs, but FGUpdated did, so I cleared those - no change
2. I deleted the FantasyGrounds.app and reinstalled from the downloaded installer - no change
3. I deleted the whole app folder (but not my data folder) and re-downloaded and run the install - no change
4. I deleted the whole app folder re-installed, with a changed (empty) Data Directory, and chose ForceAppUpdate in the settings - no change

the failure remains the same:
validateTextureDimensions:1081: failed assertion `MTLTextureDescriptor has width (30720) greater than the maximum allowed size of 16384.'

any thoughts on what to try next?

[smelton]

Can you provide some details about your hardware?

[fieldson]

Thanks for your assistance. Please let me know if there's anything else I might try. At the moment, it occurs to me I could also run the uninstall script and delete any preferences..

Here's the info from About This Mac. I haven't made any hardware modifications to this since new.

MacOS Mojave 10.14.6
MacBook Pro (Retina, Mid 2012)
2.6 GHz Intel Core i7
16 GB 1500 MHz DDR3

NVIDIA GeForce GT 650M 1GB
Intel HD Graphics 4000 1536 MB
(graphics is on auto-switching, but I run the notebook on power supply, so am almost always using the NVIDIA chips)

[Ulric]

I've had a moment to try a few things:
1.FantasyGrounds.app didn't have ACLs, but FGUpdated did, so I cleared those - no change
2. I deleted the FantasyGrounds.app and reinstalled from the downloaded installer - no change
3. I deleted the whole app folder (but not my data folder) and re-downloaded and run the install - no change
4. I deleted the whole app folder re-installed, with a changed (empty) Data Directory, and chose ForceAppUpdate in the settings - no change

the failure remains the same:
validateTextureDimensions:1081: failed assertion `MTLTextureDescriptor has width (30720) greater than the maximum allowed size of 16384.'

any thoughts on what to try next?
Are you rebooting your Mac after the deletions? I have multiple Macs that I use with FGs and I've done several reinstalls of FGU. I have found it's best to restart your Mac before doing the reinstall.

[smelton]

Was FGU running before the last update?

[fieldson]

smelton,
Yes, it was running before the last update, and I think after the last app update, too - this hit me when I ran the updater the day I've started the thread.

I've been trying different things, and I think this is a local permissions issue, and not an FG app issue - I just haven't figured out the full resolution.

What I discovered is:

1. a different user logged in under different FG account (i.e. 2nd demo account that I use as a client when I'm running a game on my main iMac) could launch FGU and everything behaved as normal, even after all of the various updates I ran (including forced updates).

2. I built a new user (non-admin) but had some odd problems - FGU would launch, but the FantasyGroundsUpdater.app wouldn't (no window appeared). FGUpdaterEngine.app launched, but I couldn't finish setting up a user, because I couldn't change permissions needed with this user.

3. I converted the user to an admin user, and had the same issues, with the message "Fantasy Grounds Updated does not have write acces to either the Application or Data directory."

4. I ran FGUpdaterEngine.app via sudo and was able to enter my regular user and Ultimate license info. At this point I can launch FantasyGrounds.app, or FGUpdaterEngine.app (but get the error in #3 but can continue to the Updater), but FantasyGroundsUpdater.app still won't launch.


At this point, I am wondering if installing under my regular admin user has mangled permissions, but I am not sure why, since I didn't do anything nonstandard with the install. As this isn't a critical computer (primarily 2nd user and testing) I would like to wipe everything fantasy grounds and then am thinking of re-installing from a freshly created admin user that has no history.

My new question is, other than the App and Data folder, plus Library/Preferences/Smiteworks folders, is there any other location I need to delete?

Alternatively, is there anything in this narrative that suggests something specific that I should fix, or any logs you might be interested in seeing?

Thanks
G

[fieldson]

UPDATE
I deleted the Smiteworks folder in Applications, the Smitework user folders, and the Smiteworks preferences folder, then installed from a newly created admin-level account.

After the install, the new admin user, and other (non-primary) users can launch FGU.
My primary user (also admin-level) still won't launch FantasyGrounds.app (crash before screens appear), but if I launch FantasyGrounds.app via sudo (and the extended path inside the package), FGU will launch as expected.

This definitely is a permissions issue. I have no idea where, unfortunately. Initially, when I ran the FantasyGroundsUpdater, I had a "permissions" error window in the updater, for which the fix options wouldn't work, but when I ran this as admin (via SUDO), that stopped happening.

-G

[Moon Wizard]

Thanks for letting us know. I've forwarded to @smelton, so that he can see what you've done.

Regards,
JPG

[smelton]

UPDATE
I deleted the Smiteworks folder in Applications, the Smitework user folders, and the Smiteworks preferences folder, then installed from a newly created admin-level account.

After the install, the new admin user, and other (non-primary) users can launch FGU.
My primary user (also admin-level) still won't launch FantasyGrounds.app (crash before screens appear), but if I launch FantasyGrounds.app via sudo (and the extended path inside the package), FGU will launch as expected.

This definitely is a permissions issue. I have no idea where, unfortunately. Initially, when I ran the FantasyGroundsUpdater, I had a "permissions" error window in the updater, for which the fix options wouldn't work, but when I ran this as admin (via SUDO), that stopped happening.

-G

Ping me on Discord (smelton#0068) and I'll help you troubleshoot

[Chilipig]

I was wondering if you have been able to find a fix for this as I seem to be experiencing a similar permission issue. I'm running version is v4.1.2 on macOS Big Sur. I'm able to launch the updater without issue, but Fantasy Grounds.app fails to load. I have tried multiple reinstalls but with no success. Running the app via terminal with sudo works but I'm hoping for a solution that doesn't require this work around.

[fieldson]

I haven't solved the problem - I have been focused on other parts of life since February and haven't followed up with @smelton.
This isn't my primary computer so I put up with it.

[smelton]

I was wondering if you have been able to find a fix for this as I seem to be experiencing a similar permission issue. I'm running version is v4.1.2 on macOS Big Sur. I'm able to launch the updater without issue, but Fantasy Grounds.app fails to load. I have tried multiple reinstalls but with no success. Running the app via terminal with sudo works but I'm hoping for a solution that doesn't require this work around.

I'm running Big Sur as well and haven't been able to replicate this issue so my initial thought is it is something specific to your setup. If you want to ping me on Discord I can try to help you troubleshoot the issue further.

[wardrake]

I get this problem reliably since around february on Big Sur on an M1 mac Mini so its a Rosetta issue. When the OS updates the problem disappeared. Then a few days later its back again. I have reinstalled it and now it works again (didn't bother uninstalling first). I am expecting it to fail again in a few days - let's see.

[J0e S.]

I'm consistently getting this on an M1 Macbook Air with Big Sur. Just did an uninstall and reinstall, no luck. It did run without issue previously. I'm exploring whether Malwarebytes is blocking it, but I've had that installed since day one so I doubt it.


Process: Fantasy Grounds [19536]
Path: /Applications/SmiteWorks/*/FantasyGrounds.app/Contents/MacOS/Fantasy Grounds
Identifier: unity.SmiteWorks.Fantasy Grounds
Version: ???
Code Type: X86-64 (Translated)
Parent Process: ??? [1]
Responsible: Fantasy Grounds [19536]
User ID: 501

Date/Time: 2021-07-28 10:17:06.890 -0400
OS Version: macOS 11.4 (20F71)
Report Version: 12
Anonymous UUID: 2C8AF6FF-DF70-87F3-BF98-3B007AA0CBE1

Sleep/Wake UUID: 2930705D-68D4-4710-B257-7085EDDA8360

Time Awake Since Boot: 70000 seconds
Time Since Wake: 4100 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: EXC_ARM_BREAKPOINT at 0x00007ffdffed8370 (brk 1)
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Trace/BPT trap: 5
Termination Reason: Namespace SIGNAL, Code 0x5
Terminating Process: exc handler [19536]

Application Specific Information:
rosetta error: /var/db/oah/c642c66595f5050af26db8f86497ea83caff7cea5a9bcb2361 ffa81d0e090b58/923c6b322f5f707c20d8e959f0edaeac4ee71fdc0812dd8006 327f4bb62a3daf/Fantasy Grounds.aot: attachment of code signature supplement failed: 3


Thread 0 Crashed:
0 runtime 0x00007ffdffed8370 0x7ffdffe85000 + 340848
1 runtime 0x00007ffdffed83bc 0x7ffdffe85000 + 340924
2 runtime 0x00007ffdffe92fe4 0x7ffdffe85000 + 57316
3 runtime 0x00007ffdffe9452c 0x7ffdffe85000 + 62764
4 runtime 0x00007ffdffe94024 0x7ffdffe85000 + 61476
5 runtime 0x00007ffdffe86280 0x7ffdffe85000 + 4736
6 ??? 0x0000000000000003 0 + 3

Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000003 x2: 0x000000000000003c x3: 0x000000000000002c
x4: 0x0000000000000303 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x000000000000236b
x8: 0x00007ffdfff05000 x9: 0x0000000000000000 x10: 0x00007ffdffefbc5d x11: 0x0000000000000000
x12: 0x00007ffdffeef6a0 x13: 0x00007ffdffeef690 x14: 0x00007ffdffeeaa30 x15: 0x0000000000000020
x16: 0xffffffffffffffe1 x17: 0x00007ffdffedc7f4 x18: 0x0000000305fdca43 x19: 0x00007ffdffefbb78
x20: 0x0000000305fdd0f8 x21: 0x0000000100dab000 x22: 0x0000000000000103 x23: 0x0000000100dab000
x24: 0x0000000000000003 x25: 0x0000000000000001 x26: 0x0000000305fdc550 x27: 0x00007ffdffe85000
x28: 0x0000000000000001 fp: 0x0000000305fdb2f0 lr: 0x2b13fffdffed8368
sp: 0x0000000305fdb2d0 pc: 0x00007ffdffed8370 cpsr: 0x60000000
far: 0x00007ffdfff06000 esr: 0xf2000001


Binary Images:
0x20112a000 - 0x2011c5fff dyld (852) <1AC76561-4F9A-34B1-BA7C-4516CACEAED7> /usr/lib/dyld
0x7ffdffe85000 - 0x7ffdffef8fff +runtime (203.46) <C447D2A9-BB07-30A8-97AB-399362D14FC8> /Library/Apple/*/runtime

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 0
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=1324K resident=0K(0%) swapped_out_or_unallocated=1324K(100%)
Writable regions: Total=18.8M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=18.8M(100%)

VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
STACK GUARD 56.0M 1
Stack 8176K 1
VM_ALLOCATE 10.5M 1
VM_ALLOCATE (reserved) 32K 1 reserved VM address space (unallocated)
__DATA 288K 4
__DATA_CONST 32K 1
__LINKEDIT 272K 4
__TEXT 1088K 2
mapped file 4.7G 9
=========== ======= =======
TOTAL 4.8G 24
TOTAL, minus reserved VM space 4.8G 24

Model: MacBookAir10,1, BootROM 6723.120.36, proc 8:4:4 processors, 8 GB, SMC
Graphics: kHW_AppleM1Item, Apple M1, spdisplays_builtin
Memory Module: LPDDR4
AirPort: spairport_wireless_card_type_airport_extreme, wl0: Apr 28 2021 19:53:33 version 18.50.40.7.7.8.119 FWID 01-e6894c69
Bluetooth: Version 8.0.5d7, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.1 Bus
USB Device: USB 3.1 Bus
Thunderbolt Bus: MacBook Air, Apple Inc.
Thunderbolt Bus: MacBook Air, Apple Inc.

[Moon Wizard]

In the previous reports of this specific issue, the users reported that updating to the latest OS updates fixed the issue (including Rosetta updates). This is related to the Rosetta emulation engine in Mac OS not handling Intel-based application signing correctly; and is not something we have any control over.

Regards,
JPG

[J0e S.]

that did it! I had thought I was running the latest version, but that was not the case. I updated the OS and I'm all set now, thank you!

[bosshappy]

I've having the same issue. FG Unity refuses to load and immediately aborts with a Problem Report to Apple, however, FGUpdater will load and run as expected but cannot launch FGUnity.

After scouring this website I discovered this thread and ran with SUDO: it runs as expected. Everything loads.

I have an i9 Intel Mac, so it's not a Rosetta issue. Also, I have verified I have the latest updates to the OS. Currently, I'm on Monterey 12.2.1.
This is what the FantasyGrounds_Player.log shows when it aborts:

Mono path[0] = '/Applications/SmiteWorks/Fantasy Grounds/FantasyGrounds.app/Contents/Resources/Data/Managed'
Mono config path = '/Applications/SmiteWorks/Fantasy Grounds/FantasyGrounds.app/Contents/MonoBleedingEdge/etc'
Initialize engine version: 2020.3.11f1 (99c7afb366b3)
[Subsystems] Discovering subsystems at path /Applications/SmiteWorks/Fantasy Grounds/FantasyGrounds.app/Contents/Resources/Data/UnitySubsystems
GfxDevice: creating device client; threaded=1
2022-02-14 21:43:35.204 Fantasy Grounds[48791:188018] LG ULTRAWIDE preferred device: AMD Radeon Pro 560X (high power)
2022-02-14 21:43:35.204 Fantasy Grounds[48791:188018] Metal devices available: 2
2022-02-14 21:43:35.204 Fantasy Grounds[48791:188018] 0: AMD Radeon Pro 560X (high power)
2022-02-14 21:43:35.204 Fantasy Grounds[48791:188018] 1: Intel(R) UHD Graphics 630 (low power)
2022-02-14 21:43:35.204 Fantasy Grounds[48791:188018] Using device AMD Radeon Pro 560X (high power)
Initializing Metal device caps: AMD Radeon Pro 560X
Begin MonoManager ReloadAssembly
- Completed reload, in 0.079 seconds
2022-02-14 21:43:35.415 Fantasy Grounds[48791:188018] CAMetalLayer ignoring invalid setDrawableSize width=26880.000000 height=1862.000000
2022-02-14 21:43:35.416 Fantasy Grounds[48791:188018] CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000
-[MTLTextureDescriptorInternal validateWithDevice:]:1325: failed assertion `Texture Descriptor Validation
MTLTextureDescriptor has width of zero.
MTLTextureDescriptor has height of zero.
'

Update: I created a new user and was able to run FGUnity with it. During my testing, I did experience some issues like fieldson did, however, I believe those issues were the result of installing/re-installing the app. After running chmod those issues disappeared.

As far as I can tell, the issue seems to be with MTLTextureDescriptor and/or an object that is tied to the user account. FG will bomb if the size is too large or too small. I don't know how to clear it out. I've removed all SmiteWorks folders, like fieldson, and re-installed the app, but the issue persists.

[Moon Wizard]

It looks like it is trying to set the drawable width size to 26880; which is many multiple monitors wide and probably causing an issue with the Unity engine. Are you using some sort of virtual desktop or stretching across multiple monitors?

You also might be able to reset by making sure FG is completely closed and deleting:
~/Library/Preferences/com.SmiteWorks.FantasyGrounds.plist

This is something within the Unity game engine itself; so not something we have any control over from the application level.

Regards,
JPG

[bosshappy]

It looks like it is trying to set the drawable width size to 26880; which is many multiple monitors wide and probably causing an issue with the Unity engine. Are you using some sort of virtual desktop or stretching across multiple monitors?

You also might be able to reset by making sure FG is completely closed and deleting:
~/Library/Preferences/com.SmiteWorks.FantasyGrounds.plist

This is something within the Unity game engine itself; so not something we have any control over from the application level.

Regards,
JPG

To answer your question. I have a 15" MacBook Pro and a 35" monitor. When I'm running FG for my on-line game, I use the monitor. There's another game, in which, we meet in person. In those cases I use just the MacBook. When I switch between the big monitor and the laptop monitor I have to adjust the scale of the game or it's very difficult to read. This issue occurred when I started FG for my on-line game and adjusted the UI setting for my big monitor.

After a bit more fiddling I got it working again. This is for all the Mac owners out there. I'm writing this from memory so I'm hoping I captured everything correctly. Here are the steps:

Make a backup of your campaign, module, extensions, portraits and tokens

Open Terminal and type the following from your home directory
mkdir FGBACKUP (or whatever you want to name your backup directory)
cp -R ~/Library/Preferences/SmiteWorks/campaigns ~/FGBACKUP/
cp -R ~/Library/Preferences/SmiteWorks/extensions ~/FGBACKUP/
cp -R ~/Library/Preferences/SmiteWorks/modules ~/FGBACKUP/
cp -R ~/Library/Preferences/SmiteWorks/portraits ~/FGBACKUP/
cp -R ~/Library/Preferences/SmiteWorks/tokens ~/FGBACKUP/

Delete the following (I'm assuming you're going to need SUDO for some of the commands)

rm -f ~/Smiteworks
rm -f ~/Library/Preferences/unity.SmiteWorks.Fantasy Grounds.plist
rm -f ~/Library/Preferences/unity.SmiteWorks.Fantasy Grounds Updater.plist
sudo rm -f /Applications/SmiteWorks
sudo rm -f /Library/Preferences/SmiteWorks
sudo rm -f /Applications/SmiteWorks
Open Finder. Go to the "Applications" and delete the "Fantasy Grounds" link.

REBOOT -- DO NOT SKIP THIS STEP
Download and reinstall Fantasy Grounds
Restore your FG library

cp -R ~/FGBACKUP/* ~/Library/Preferences/SmiteWorks/



NOTE: In hindsight, I think the issue is the plist files are being held in the user account memory, therefore, the fix is possibly as simple as: shutdown FG, remove the plist files, then reboot.

Thank you Moon Wizard!

[jaharmi]

I can’t speak to specifics about how Fantasy Grounds and/or Unity work, but the plist files in ~/Library/Preferences are generally on-disk representations of memory-based preferences. If the app is using the macOS preferences framework (CFPreferences) then you should be able to remove settings immediately via:


defaults delete ~/Library/Preferences/unity.SmiteWorks.Fantasy Grounds.plist
defaults delete ~/Library/Preferences/unity.SmiteWorks.Fantasy Grounds Updater.plist

Deleting those particular files with the Finder or a command like “rm” will generally not take effect immediately. A log out or reboot (which includes a log out) would fix this because afterwards, the preferences would be read from the files again — so if the files are gone, the preferences can’t be loaded into memory.

It seems strange to me that the window size would cause this kind of crash. I don’t normally switch between a laptop and external screen; I use FGU on a desktop system with multiple monitors attached. I’ve found that FGU starts up fine on my multiple screens. I use the app Divvy to manage windows and move them between monitors. I’m on Intel, but I haven’t to my knowledge seen this condition crash FGU.

Is there a way that FGU could detect this resolution condition and set something more appropriate for the current display(s), rather than crashing? This would go along with my problem / request for supporting macOS more fully by using the user’s current home directory (https://www.fantasygrounds.com/forums/showthread.php?71838-%93Fantasy-Grounds%94-folder-and-home-directory-path-on-macOS&p=632582#post632582). It might also be helpful for the other platforms FGU runs on.

[Moon Wizard]

As I mentioned, this is part of the built-in Unity game engine preferences. I have not seen anything in the Unity documentation that allows disabling of those window placement preferences; though I haven't looked recently.

Regards,
JPG

[fieldson]

SOLVED

Thank you Moon Wizard and jaharmi. Moon Wizard's post sent me in the right direction, but I had never scrolled down through my gazillion prefs to discover additional pref files with the unity.smiteworks prefix. I deleted and restarted and for the first time in over a year, I can launch and run SmiteWorks from my default user.