TimelineFX doesn’t work on mac OS Sonoma
- This topic has 15 replies, 2 voices, and was last updated 9 months, 3 weeks ago by
.
-
Posts
-
hello,
we are using TimelineFX in our studio for many years, after upgrading our OS to Sonoma 14.2.1 TimelineFX doesn’t lunch anymore.
I’m assuming that maybe it is needed to be compiled for the Sonoma OS?hello, I wanted to check up and see if there is any progress with resolving of this issue.
It’s pretty urgent for us since our studio is unable to create effects, as most of us already upgraded to Sonoma OS.Well there’s good news and bad news. The bad news is that I’ll probably discontinue the old version of TimelineFX Mac version as a lot of the things that I developed it with are no longer supported so I’m not even sure if I can get it working again.
The good news is that I’ve been working hard on the new version for mac over the last week and it’s is now fully working – I may even be able to release later today, I just need to fix a couple of issues. It is possible to convert old eff files in the new editor although some tweaking will probably be required due to some feature differences.
Whilst the new version has more features then the old it currently only deals with png files but if you let me know any other file formats you use I can add them.
It would be nice to keep the old version going a little longer but it’s hard to justify spending the time on it now and would rather focus completely on the new version which is way more future proof.
I’m assuming you still have intel based macs? I can only compile intel for now but should be able to cross compile for arm as well soon. I’m actually compiling with Monterey as my Mac is from 2015 is apparently too old but I don’t think that should be a problem.
Ok, I guess previous versions of mac os must have emulated intel cpus for older software as I don’t think the old version would have been arm enabled. Either way hopefully I can cross compile I will just need to map some intel intrinsics to the arm equivalents, unfortunately I won’t be able to test it very easily.
I just uploaded a version here for Intel based Macs (after much battling with Apple validation and notoriety service!).
I guess I’ll have to bite the bullet and get an arm based mac to build and test on 🙂
I now have an ARM Mac and already have it compiling and running having remapped the Intel intrinsic stuff. Just need a few niggles ironed out then should be good to go 🙂
Now Available to test on the download page.
This is a universal version that works on ARM and Intel Macs. Check the orientation section on the Help tab (under getting started) to see some of the main differences are between this and the old version.
Last login: Wed Feb 21 11:12:22 on ttys004
/Applications/TFXEditor.app/Contents/MacOS/TFXEditor ; exit;
omere@PSIL-MBP-OMERM1R3 ~ % /Applications/TFXEditor.app/Contents/MacOS/TFXEditor ; exit;
Fatal : VkResult is ” ERROR_INCOMPATIBLE_DRIVER ” in /Users/peterrigby/Documents/GitHub/TimelineFX/TFXEditor/submodules/zest/zest.c at line 1255
Fatal : VkResult is ” ERROR_EXTENSION_NOT_PRESENT ” in /Users/peterrigby/Documents/GitHub/TimelineFX/TFXEditor/submodules/zest/implementations/impl_glfw.cpp at line 34
ERROR: vkEnumeratePhysicalDevices: Invalid instance [VUID-vkEnumeratePhysicalDevices-instance-parameter]
zsh: abort /Applications/TFXEditor.app/Contents/MacOS/TFXEditorOk thanks for the report, will see if I can figure out what’s going on, what Mac do you have? What I’ll probably do is try and get all the validation layer debugging to output to a text file and ask you to run that and then send me it to get more precise details.
It’s probably something stupid I’ve overlooked as I’m still not very familiar with the Mac build and release system, thanks for the help debugging though!
You must be logged in to reply to this topic.