2 x Quad-Core Intel Xeon 2.66 Ghz
NVIDIA Quadro 4000 ROM-Version 3581
CUDA Driver Version: 4.2.7, GPU Driver Version: 22.214.171.124 (256.02.25f01) - CUDA Prefs say there is no newer version available
After Effects 6 Version 126.96.36.199
Ray-traced 3D: Initial shader compile failed. (5070 :: 0) error at program launch is still happening.
I have a macpro 3,1 with a GTX 560 Ti
It seems the card makers have finally come to the party with mac compatibility and you can run pretty much any of the recently released card without too much hacking. My other macpro has a HD6870 replacing the 8800 GT that died. No boot screen but everything else is perfect.
I did come across this error and none of the answers fix it on their own but a compination did.
When I got the error I was running 10.7.3 and as it happened in 32bit mode. nvida drivers 4.2.7
I updated to 10.7.4 which broke the card drivers loaded from here http://www.nvidia.com/object/macosx-270.00.00f01-driver.html
so do this
Open the driver dmg and copy to desktop the installer, right-click the installer and click show package contents, navigate to Packages folder and fire up the installer there. Restart the Mac and you are ready to go. (from you tube video http://www.youtube.com/watch?v=xYa39Y5nR6A)
restart in 64 bit using the app mentioned early in this thread, then hack AE by going "show packet contents" and adding your graphics card to the file raytracer_supported_cards.txt
Working just perfectly now. (I think the adobe guy's probably not going to like the 'hack AE bit but they need to add more support for cards on the mac now.)
Same as well. Have also run into some serious ram preview issues. Clearly this is not suitable for a production environment. We've gone back to vs 5.5 and I've been very vocal to our peers to hold off on upgrading until adobe is able to address. Photoshop is lovely though. Premiere is a nice upgrade, which makes it all the more frustrating.
After a few nightmarish 5070 days, I have finally had some success. If the dreaded error shows up I restart my machine and I get a solid error-free days work out of it before I see the error again. I was having absolutely no luck quitting AE. Every time you return to the file it gets crashier and crashier. You need to restart. Also, if you let your Mac sleep during a render it 5070's every time. I am now getting great error-free performance and rendering some pretty complex ray tracing scenes. Dont throw in the towel yet. This ray tracing is amazing and worth it! I have a Mac Pro with 64Gb and two Quadro 4000 cards (but it also worked with 32gb and one Gpu). A few days of solid success now with very little trouble. Knock on wood...
Having said all this though, Adobe had no business releasing this in its current state. They should have called the Raytracer and disk caching "beta" so people would have the correct expectations.
Fundamentally, the biggest problem here is that (in my case) four parties are now involved: Apple, Adobe, PNY, and nVidia. In the previous version there were only apple and adobe. This complicates everything technically. There will be errors lingering forever on this because the actions of any one of the parties can break things.
I would like some cheese to go with all this whine. I'm sure this will get resolved people and for the most part, seems to be an isolated issue to a few of us. Risking sounding like a fan boi, Adobe does listen to their customers. As previous issues/bugs in their products have been fixed, I'm certain this one will too. If 3D extruded text and bending solids is your major reason for upgrading to CS6, perhaps investing in a copy of Zaxwerks Animator Pro would be worthwhile.
@@ryna et all,
I personally don't want to come across as a complainer. This forum should be used to collectively get to the bottom of whatever issues may be at hand.
I'm not really sure that the error is effecting me because I'm not using extrusions or 3D text. But my feeling is that the error may be indicating a failure in some part of the CUDA processes. The error disappears in my Ae when I switch the "Ray-tracing" option to "CPU" in the "GPU Information…" button next to the "Adaptive Resolution Limit:" option in "Previews"; After Effects Preferences. So that may mean that the error is only effecting the "Fast Preview" in my case. I'm not sure that it is a real problem at all … but also not sure it isn't.
I'm amazed at the amount of first person response from Adobe on this forum (in general) and especially concerning this problem. I've never experienced a software that worked perfectly on all machines in every instance. That is the main reason one should not update in the middle of a project.
In order to make a product "perfect", the users and the developers will always have to work together. And that, constantly.
Keep up the good work Adobe!
Begging your pardon, but i work in a broadcast television production environment. During my freelance days i may have considered this a non-issue as i wouldn't have upgraded till whatever long-term project i was working on was done. But in my environment, everyday is a new graphic, everyday is a new deadline. We produce 2 (22min) daily tv shows that air all over Canada, the US, and Australia, year round. There is no downtime and text is a heavy component of the graphics, this feature would be a major major time saver.
Zaxwerks is fine, i want text that truly integrates with the whole environment. Again, the AE ray-tracer would be a major time saver as opposed to trying mimic it with Zaxwerks. From what i can tell in the fast draft render (it crashes in the other render modes), that this is something that i have been waiting for, for sometime. So yeah, it is a big deal.
I understand that this doesn't affect everyone, though the law of forum users says that the percentage of people who actually come to a forum and complain about something to those who are too lazy to go thru that hassle is much higher. I understand that it seems to be a hard error to replicate (although for a number of us, it's replicated ever dang time we open the program). And your right, it probably will be eventually fixed, but i'll keep the applause and kudos til when the problem is actually solved. I sure as heck don't get a pat on the back till i finish my work. This is business after all.
Or those of us who will get files from people using CS6 for whom it works but we can't open their files that are using the ray tracer and the job is now screwed because we have to find a way to use the files from the vendors.
I get the 5070 Error on start up, so Ray Trace isn't even an option once I'm in the app.
I've tried updating AE un-installing, re-installing, as well as the same with NVIDIA software
Mac Pro 3.1
- What operating system are you using? Mac OS 10.7.4
- Did you upgrade your operating system from a previous version? If so, which one? No, installed CS6 straight onto Lion
- What is the model of your CPU? 2x 2.8 GHZ Quad Core
- What is the model of your GPU? NVIDIA Quadro 4000
- What is the version number of your graphics driver? 270.00.00f06
- If you have an Nvidia card, what is the version of your CUDA driver? 4.2.7
|Texture Memory:||204.00 MB|
|Device:||NVIDIA GeForce 8800 GT OpenGL Engine|
|Total Memory:||512.00 MB|
|Devices:||1 (Quadro 4000)|
|Current Usable Memory:||1.93 GB (at application launch)|
|Maximum Usable Memory:||2.00 GB|
FYI, i had some time today to completely re-install my OS (10.7.4), CS6 and Cuda/Nividia drivers.
Ray-traced renderer still doesn't work, a nice waste of an afternoon. Very frustrating that it's been a month now guys.
Going thru this list it seems a majority of us are using a Mac Pro 3,1 (2008 model). If Adobe can't replicate the error, can you confirm that a Mac Pro 3,1 model was tested?
|Texture Memory:||1152.00 MB|
|Device:||NVIDIA Quadro FX 4800 OpenGL Engine|
|Total Memory:||1.50 GB|
|Devices:||1 (Quadro FX 4800)|
|Current Usable Memory:||1.24 GB (at application launch)|
|Maximum Usable Memory:||1.50 GB|
As an update to my problem...
Stripped the Mac Pro to just the single Quadro 4000 card (removing the GeForce GT8800) but I'm still plagued by the 5070 error on start up.
Is anyone else experiencing this?
I had previous re-installed the OS, but left the apps alone. This time i completley wiped the drive. In addition to that i installed the latest CUDA drivers in the nvidia developer zone. They were updated a few days ago to 4.2.10
Now, was it the new CUDA drivers or the totally wiping of my drive that did the trick? I have no idea, but what i do know that the ray-tracer works beautifully for me now. No errors, even on renders.
Before you go thru the hassle of completley wiping your drive though, i'd try the latest CUDA drivers first!
Same error. Tried every method listed so far.
Things I tried:
Thanks Bigred, I am, but regret that I didn't put it in my summary sheet. Too late to edit unfortunately.
Not a hackintosh, (I have 2, but they're not stable enough for a work environment.) Its the standard 2011 Mac Pro. Came from the apple store with 6gb, swapped out the 1Gb_x3 for 2Gb_x3 to keep it triple channel as recommended.
Cooincidentally I tested AE6 on a backup hackintosh with 6Gb and a gtx285, and it works great. The Global Caching is amazing, but that's the other thing that doesn't seem to work on the MacPro. I'm suspecting the issues are related.
I have 2 as well, made then as render node originally. Sometimes I think they could be reliable enough, but I wouldn't want to rely on them solely, but if apple don't release a new macpro soon I might consider it. They are a great time waster when it comes to updating system software.
Have you tried flashing you graphics card with a mac rom?
Desperation led me to do the same thing and start afresh on a new drive with a fresh install of Lion and CS6 -and I have got rid of the 5070 error too!
What I'll try doing when I get some downtime is using Carbon Copy to clone my old drive but without any Adobe or NVIDIA software and re-installing CS6 again to see if that'll help.
Well, having the same problem
- What operating system are you using? Win 7 64
- Did you upgrade your operating system from a previous version? If so, which one? No
- What is the model of your CPU?i7 2600K
- What is the model of your GPU? NVIDIA GeForce GTX 570
- What is the version number of your graphics driver? 301.42
- If you have an Nvidia card, what is the version of your CUDA driver? 4.2.1
One observation I made: I do have another GPU, a 550 Ti, which is, of course, not supported. AE still uses it while rendering. Upon discovering this, and receiving aforementioned error too often for my comfort, I disabled it using the CUDA_VISIBLE_DEVICES environment variable. Having done this, it gets much farther rendering into the comp. I discovered, however, that AE fills the GPU's VRAM to its limit (happens to be 1280 MB) and stops afterwards with the dreaded 5070::0 error. As soon as I restart AE, the GPU's VRAM gets flushed and reloaded and I can render the rest of my comp.
I still have this problem! I have installed the update for AE cs6
I am running Mountain Lion OSX 10.8 Developer Preview 4
|Texture Memory:||409.00 MB|
(GPU not available - incompatible device or CUDA driver)
|Device:||NVIDIA GeForce GT 650M OpenGL Engine|
|Total Memory:||1.00 GB|
|Current Usable Memory:||-|
|Maximum Usable Memory:||-|
not sure how you guys get the big info box?
Why does it matter if im a developer or not? No im not, just like 99% of everyone else running Mountain Lion because it generally runs way better than Lion. That said, yes I am running 64bit kernel and there is inbuilt Nvidia drivers for 10.8 as seen in my info box "NVIDIA-8.0.46". Also everything else that is gpu related runs just fine, games, premiere and so on.
CS6 runs totally fine on a Dev preview, I dont know what it is people are so ignorant about when it comes to macs and pre release software.. if people would read through this thread they will see it has NOTHING to do with whether people are running Windows 7, Snow leopard, Lion or ML DP4...
So thanks for a completely useless response. Now is there any solutions rather than the random lucky I deleted everything I have and reinstalled it all and somehow "for now" I don't get the problem "solution" ?
I have noticed that this issue happens regardless of what I am trying to render with the raytrace engine. As soon as the raytrace engine is turned on and any layer is switched to "3D" the error happens regardsless of what the layer holds.
Haha what ever floats your boat mate.... people are not idiots.. you don't have to play hero and hide all your own pirated software by trying to call out me, find a fix AE or go somewhere else to waste our time.
Legitimacy of software aside (believe it or not, some of us buy ALL of our software), you can't really expect to get tech support while using a dev preview OS. It's a OS that is in a preview state and might not reflect the final shipping product, it makes zero sense for a business to support it.
Of course, but haven't we already established that this error happens across the board? the exact same error! this is not about what version of osx or windows you are running, because the error can be replicated in all scenarios with even both AMD or Nvidia.. there is something else fundamentially going wrong here. It's a lot more likely that it is a Nvidia/Cuda/CS6 error than anything apple or microsoft does.
Hmm that is interesting though, so maybe some of the problems comes from the fact that (im guessing here) most people with the problem is using a machine with preinstalled software? Like I got my macbook pro 1 week ago, so of course I haven't done a full partition wipe and reinstalled everything from scratch yet, how ever it does seem like it has to be done (once Mountain Lion is released in Final) to fix this?
What I don't like about it is that no one has yet to pin point why the full reinstall works, for some... Is there a way to uninstall the Nvidia drivers in OSX? and let the auto update find them again to reinstall? cheers
Originally I did not have the 5070 problem. But out of curiosity I installed the developer CUDA driver from Nvidia. This did not enable CUDA support, Ray-trace was still on CPU. But I now had the 5070 memory problem on CPU. Uninstalling CUDA didn't help. 11.0.1 update didn't help.
Facing a reinstall I did a systemwide search for CUDA (With system files included.)
I then removed anything related to CUDA. Mostly .plist and .kext files. Problem solved.
Ray-tracing works perfectly fine (using CPU) again.
I was never able to switch from CPU to GPU. I guess something related to the CUDA driver
is still affecting AE's behavior on CPU.
That is really interesting! And yes I never expected the raytracing to actually run on the gpu with cuda, it's not built for standard gpu's. How ever it should crash as it does since it does have cpu support. mind helping me out with how to search and find all the cuda stuff? Im new to the whole OSX thing.
EDIT: DUDE!!!! you are a legend !!!!!!!
I did exactly what you said, I figured out how to search for system and hidden files, searched for "cuda" and deleted everything, just one big "all to trash". Restarted and BAM! AE doesn't crash anymore!
You are how ever correct that since it is run purely on the cpu, it's nearly impossible to use as it is sooo heavy, but it works!
Same problem here. I installed the update but it doesnt fix the problem.
I run windows 7 64bits with I7 920, 18go of ram. I dont have nvidia card like many of you but an ati firepro. By the way, too bad the card is not supported for gpu...
|Texture Memory:||368.00 MB|
(GPU not available - incompatible device or display driver)
|Vendor:||ATI Technologies Inc.|
|Device:||ATI FirePro V5800 (FireGL)|
|Version:||3.0.11296 Compatibility Profile Context FireGL|
|Total Memory:||920.00 MB|
|Shader Model:||4.0 or later|
|Current Usable Memory:||-|
|Maximum Usable Memory:||-|