Version 0.11.2 does not work on macOS with case-sensitive filesystem

[afh]

When opening the version 0.11.2 on macOS 15.0 (24A335) the application briefly shows a unity splash screen and then an empty screen. The app does not ask for microphone of virtual camera permission, and the regular keyboard shortcut ⌘ , for the preferences does not work.

Splash Screen	App Screen

When building and running the VCamUIPreview from source the app showing with a large square (see below). When trying to install the virtual camera from the settings it fails with the following error message:

Screenshot of locally built VCamUIPreview

Is the VCam incompatible with macOS 15?
What is needed to get the app working again?

[tattn]

In my environment, VCam is working without any issues on macOS 15.

Are you using VCam on macOS 14, and after updating to macOS 15, the app no longer works properly?

If so, it is likely that some saved data is interfering with the app’s startup. Please try the following steps:

1. Open ~/Library/Application Support/com.github.tattn.VCam
2. Make a backup of that folder by zipping it.
3. Delete ~/Library/Application Support/com.github.tattn.VCam/prev/model.vrm
4. Launch the VCam.app

This change will reset your avatar model, so please reload your avatar as needed after launching the app.

If the issue persists, please try deleting the entire ~/Library/Application Support/com.github.tattn.VCam folder and then relaunch the VCam app.
Please make sure to back up the data first, as this will reset everything.

[afh]

Thank you for your response, @tattn. To answer your question: No, this is a first time installation of VCam directly on macOS 15. FWIW the ~/Library/Application Support/com.github.tattn.VCam folder exists, but does not contain any files, not even hidden dotfiles.

What else can I do to find the underlying issue?

[tattn]

@afh Thank you for the information!

If possible, could you please open ~/Library/Preferences/com.github.tattn.VCam.plist and let me know the values of the keys that start with vc_?

Additionally, if there is no key named vc_prev_version, could you please try the following steps:

1. Close VCam app
2. Back up the plist file.
3. Add a key named vc_prev_version and set its value to 0.11.2 (as a String).
4. Open VCam app

[afh]

@tattn vc_prev_version did not exist in the ~/Library/Preferences/com.github.tattn.VCam.plist and after I added it and played around with VCam some more my system froze when changing Camera access to VCam in the System Settings. So unfortunately the previous comment I wrote that included the vc_ prefixed strings from the plist is lost and the plist now contains several more entires than before…
This is the third time I had to hard reboot my system when changing Camera or Virtual Camera settings related to VCam. What could be the cause of this?

Fortunately after a reboot I can start VCam properly and do see an avatar, yay! But only when I run it from the mounted dmg 🤔

Three things that might be unexpected and that could cause issues:

1. I usually install apps in ~/Applications instead of /Applications and install apps in the latter if they absolutely need it. Which may be the case for VCam, as trying to install the Virtual Camera results in the following alert

2. My main user is not part of the admin group and therefore has its access to certain paths in the filesystem.

3. I use macOS on a case-sensitive APFS. The fact that VCam works when run from the mounted dmg, but not when copied onto my filesystem leads me to believe that some app resources might like libraries or nibs might not be found because of that.

Another thing I haven't found out yet: Once I've loaded a custom VRM model, how can I unload it / go back to the default model?
And which websites would you recommend to download decent quality free VRM models?

[tattn]

@afh
You seem to be quite knowledgeable about the technologies, so I explain in more detail.

VCam uses Core Media I/O’s new Camera extensions, which have been available since macOS 12.3. This technology is more secure than the previous virtual camera technology, but since it is embedded in the system, it sometimes requires system reboots, which is a limitation on Apple’s side.

However, having to reboot three times is unusual, so there might be an issue on VCam's side where proper handling isn't happening.

/Applications

The reason installation to /Applications is required is due to the way Apple’s Camera extension works, and it’s not something that can be changed in the current macOS.

case-sensitive APFS

I haven't tested in that environment, so there could be a bug on VCam’s side. Unfortunately, I’m unable to prepare that development environment immediately, so it may take some time to resolve the issue.

Once I've loaded a custom VRM model, how can I unload it / go back to the default model?

There’s no built-in feature to revert to the default, so you’ll need to load a model again.
The default model is a free model available here:
https://3d.nicovideo.jp/works/td32797

If downloading from a Japanese website is difficult, you can also download it from here:
https://github.com/tattn/VRMKit/blob/main/Tests/VRMKitTests/Assets/AliciaSolid.vrm

Which websites would you recommend to download decent quality free VRM models?

VRoidHub is a great website where licenses are clearly displayed for each model.
https://hub.vroid.com/en
https://vroid.com/en

[afh]

Thanks for the quick and helpful response, @tattn, much appreciated.

While I'm not thrilled about reboots I understand that they can be necessary, what I' a bit worried about is that my system froze and I had to hard-reboot…

I'd like to recommend VirtualBuddy, which virtualizes macOS 12 and later on Apple Silicon. I've found it quick and convenient to use.

Thanks for pointing me to the default model, that's helpful.
Would you consider adding a built-in feature to revert to the default?

[afh]

Oh and much more if not most important: I don't see a virtual camera device from vcam in Chrome, OBS, or QuickTime Player, which I'd expect in order to be able to use the avatar for video conferencing or screencasts.

[tattn]

@afh

Although macOS 15 is now officially released, I think there are still quite a few bugs with niche features such as the camera extension, so further troubleshooting may be necessary. I plan to improve this in future versions.

Thank you for recommending a virtualization app 😄

Would you consider adding a built-in feature to revert to the default?

I'll consider it, but since many VCam users prefer using custom avatars rather than the default one, the feature may have a lower priority.

I don't see a virtual camera device from VCam in Chrome, OBS, or QuickTime Player

It's likely that the virtual camera installation was not completed properly.
You can reinstall the virtual camera from the settings, but due to potential issues with the file system, app installation location, or user permissions, VCam may not work as expected in the current version.
I'm sorry for the inconvenience.