maybe it might be a possibility for our older GPU's
ok, in what language would it be written in, and is there like a template for it?
maybe it might be a possibility for our older GPU's
That I really don't know I am not an expert in this areaok, in what language would it be written in, and is there like a template for it?
It’s not sidecar per se but the underlying support for these new features built into a multitude of Catalina frameworks + apple actually dropping support for our machines. Up until Catalina Apple deprecated a lot, but remnants were actually left hanging around allowing us to play. It’s just much harder now.yikes, ok, is there anyway i can get my hands on the framework for the SkyLight and CoreDisplag framework?
[doublepost=1560021710][/doublepost]
do we really need sidecars though, can’t we just take that code out?
http://www.macvidcards.com/drivers.html that is some info on the Nvidia web drivers for the macOS versions so far I go Cuda 7.0.29 to work on my iMac 9,1oh ok, doesn’t nVidia supply webDrivers for their video cards?
so wouldn’t that help with the Metal Capability?
Yup they are still linked for a reason.Unfortunately not for Nvidia Tesla series, but Metal is a different framework from OpenGL, uses different Acceleration drivers (but OpenCL is still there) even if I guess OpenGL is not totally abandoned by apple in Catalina, I mean they still need it.
As far as I can tell, the only reason the OpenGL/CL FWs are still in Catalina at this point is to provide compatibility for older Mac apps and games that utilize OpenGL instead of Metal.Yup they are still linked for a reason.
Alright, so for those who were wondering, myself and @parrotgeek1 have been working on this acceleration issue on our own, and have come to the conclusion that it is not going to be possible to achieve graphics acceleration on non-Metal video cards in Catalina. This is for various reasons, but the main one is the SkyLight and CoreDisplay dependencies. In Catalina, SkyLight and CoreDisplay have been changed greatly, and are interdependent on each other. Meaning, if you replace one from an older version of macOS, you must replace the other, otherwise you'll be left with a ton of unresolved symbols. The problem with doing this, though, Catalina's AppKit relies on all the new functions present in the Catalina CoreDisplay framework. You cannot use a copy of AppKit from an older macOS version, without causing a ton more unresolved symbols.
TLDR, based on this analysis, non-Metal GPU acceleration is not, and will not be possible on 10.15 Catalina. With that said, I will not be releasing the "usual" patcher for 10.15. I do not believe the general public should be using a copy of macOS without full graphics acceleration (I sure as heck know I wouldn't want to), and I'm not going to release a patch that results in extremely poor system performance for the end user (not to mention I would get thousands of complaints per day about it if I did).
I will, however, more than likely make somewhat of a "cut down" patch, designed for use only on Mac Pro systems and some iMacs that have had their video cards upgraded.
I'm as disappointed as you all are about this discovery, and deeply apologize I won't be able to provide a patcher because of it.
usually C/C++That I really don't know I am not an expert in this area
Just following up on my (failed) attempts at hand crafting a Catalina boot partition. Seems like the CCC and SuperDuper! guys are also hard at work supporting Catalina. So not just me, the new file system layout and "hidden" volumes are providing challenges for even the experts. But they will crack this within a weeks/months - definitely before Catalina release.I’m using dd to create a block level clone of my Catalina install. It involves having both disks unmounted with
diskutil unmountDisk /dev/disk#
So to do this I used the Terminal in a USB Installer.
Use:
diskutil list to find the right disks
Double check. Then patiently run:
dd if=/dev/disk# of=/dev/disk# bs=1m
if is in, of is out. Do not get the in file and out file mixed up or you will completely erase your install.
You can backup and restore to disk image as well. And you should be able to restore from disk utility’s GUI. Jury still out on this one.
I may write a GUI front end for this and it could be added to a patch tool. Showing progress would be the only challenge.
I'm running a iMac 11,1 late 2009 with ATI Radeon HD 4850 512 MB. Thinking it won't work?https://www.idownloadblog.com/2019/04/22/macos-10-15-api-device-drivers/ maybe someone might find this article interesting
http://www.macvidcards.com/drivers.html that is some info on the Nvidia web drivers for the macOS versions so far I go Cuda 7.0.29 to work on my iMac 9,1
As far as I can tell, the only reason the OpenGL/CL FWs are still in Catalina at this point is to provide compatibility for older Mac apps and games that utilize OpenGL instead of Metal.
I think a 3rd of WWDC was talking about the newer games coming soon very little time about macOS the most part was hyping iPhones and iOS 13Yes, during WWDC they showed a demo of Asphalt 8 (or 9) that was first game full Metal based, so they surely kept also for those reasons, more compatibility.
Just following up on my (failed) attempts at hand crafting a Catalina boot partition. Seems like the CCC and SuperDuper! guys are also hard at work supporting Catalina. So not just me, the new file system layout and "hidden" volumes are providing challenges for even the experts. But they will crack this within a weeks/months - definitely before Catalina release.
The separate Data volume is especially tricky - I just added the volume and rsynch'ed the data - but someone posits that you can't just add the Data volume to a system boot partition (like I did). It's the other way around. Doesn't make sense to me but read here: https://mjtsai.com/blog/2019/06/06/backing-up-macos-10-15-beta/#comments
Yeah gave up on DU a while ago also. Used to be able to manually set up an APFS boot on Mojave with ease. Cat seems a little more complex... I have Cat on external for the moment. Would like to clone that to my internal disk... otherwise experimenting and exploring is slow and time consuming...AFAIK not even DiskUtility has always properly worked to clone an APFS container, I often got failed in "Inverting Target Volume", on a supported machine, but somehow I managed to fix it manually.
Yup. Haven’t had a chance to inspect Skylight and other frameworks yet, but have they stripped out some of the old embedded OpenGL shader code that was still hanging around?As far as I can tell, the only reason the OpenGL/CL FWs are still in Catalina at this point is to provide compatibility for older Mac apps and games that utilize OpenGL instead of Metal.
That’s cool. Wondering if the software update hack will still work in Cat - so you can avoid the supported Mac dance when an update comes out (next week?)macOS Catalina runs great and very smooth on MacPro5,1. No need to patch or upgrade.
You just need to do these 3 simple steps for the MacPro5,1 to run macOS Catalina:
(1) install macOS Catalina on a drive on a supported Mac
(2) boot your MacPro5,1 to recovery, and then in terminal, type
sudo nvram boot-args="-no_compat_check"
(3) transfer the drive with macOS Catalina installed to the MacPro5,1 and and boot. The MacPro5,1 will now boot up macOS Catalina.
Alright, so for those who were wondering, myself and @parrotgeek1 have been working on this acceleration issue on our own, and have come to the conclusion that it is not going to be possible to achieve graphics acceleration on non-Metal video cards in Catalina. This is for various reasons, but the main one is the SkyLight and CoreDisplay dependencies. In Catalina, SkyLight and CoreDisplay have been changed greatly, and are interdependent on each other. Meaning, if you replace one from an older version of macOS, you must replace the other, otherwise you'll be left with a ton of unresolved symbols. The problem with doing this, though, Catalina's AppKit relies on all the new functions present in the Catalina CoreDisplay framework. You cannot use a copy of AppKit from an older macOS version, without causing a ton more unresolved symbols.
TLDR, based on this analysis, non-Metal GPU acceleration is not, and will not be possible on 10.15 Catalina. With that said, I will not be releasing the "usual" patcher for 10.15. I do not believe the general public should be using a copy of macOS without full graphics acceleration (I sure as heck know I wouldn't want to), and I'm not going to release a patch that results in extremely poor system performance for the end user (not to mention I would get thousands of complaints per day about it if I did).
I will, however, more than likely make somewhat of a "cut down" patch, designed for use only on Mac Pro systems and some iMacs that have had their video cards upgraded.
I'm as disappointed as you all are about this discovery, and deeply apologize I won't be able to provide a patcher because of it.