![]() ![]() I am optimistic that this config may work on a Mac (albeit running Windows) – and save the cost of purchasing a dedicated Windows machine with a suitable GPU or the horrifically expensive Quadro FX4800 (which will do quad-buffered stereo for specialist applications, but from what I can determine is not compatible with the NVIDIA 3D vision kit.)Īny thoughts on this welcome – I am interested in running the Unity game engine in stereo (realtime graphics) as well as full HD stereoscopic video (1080p) (prerendered material) The links are to the Australia stores as that’s where I’m located. I’m interested in getting stereoscopic 3d running on my Mac Pro (early 2008 3,1 config) if possible and wondered if anyone has had a go with the following configuration:Ģ] Using a EVGA GeForce GTX 285 card (this is available from the Apple Store and also compatible with the NVIDIA 3D Vision Kit under Windows)ģ] Using the Alienware OptX AW2310 23″ monitor. My initial post to the NVIDIA 3D forum elicited no response:Īpple Mac Pro+ Bootcamp (Windows 7) + Geforce 3D Vision + Alienware OptX AW2310 23″, Getting stereo to work on a mac ![]() ![]() One should probably check for parity errors in the system log when using noname RAM, even if the system runs at stock speed.YES, it does work – but it’s a bit tricky – see below: A user reported RAM errors at 2,86 GHz using noname modules. Some noname RAM showed up errors at 2,83 GHz. Using Kingston or Transcend RAM the same results could be achived at 3,24 GHz. With pre-installed Apple RAM we were able to run a 2,8 GHz Mac Pro at 3,17 GHz 24 hours under full CPU and memory load without a single parity error, that had to be corrected. If you shutdown your computer and turn it on again later it will always run at stock speed. Also, the kext is not loaded, because it is needed only to change the bus clock. In this case the system time runs at the correct speed and benchmarks report better results, because Mac OS adjusts the system time speed at boot time, but at no time afterwards. If you reboot without turning the system off (shutdown), the Mac Pro keeps the speed you set with ZDNet Clock. After a reboot the kext will never be loaded, until you run ZDNet Clock again. It is dynamically loaded, when you start ZDNet Clock. ZDNet Clock doesn't load a kext at boot time. The current version of the tool works by loading a kernel extension into Mac OS X on boot that forces the clock speeds upwards immediately after the system starts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |