After Effects error: Ray-trace 3D ( 5070 :: 0 )

[adam@blueapplestudio]

I am trying to create extruded vector shapes in AE CS6 and get the below error after clicking on the enable 3D toggle for the layer.

After Effects error: Ray-trace 3D: Out of paged mapped memory for ray tracer.

( 5070 :: 0 )

Any thoughts on how to solve this?

[Tavis_Dunn]

Uninstalled CUDA, rebooted, tried to install driver you linked to, said a newer driver was already installed. Installed latest CUDA.........and no error! Weird thing though, with ray trace on, i can only see my extruded object in Fast draft mode. Every other mode including Off (final quality) renders the object black, or i guess more accurately, it doesn't render the object at all. I go back to fast draft and it works again.

So not really a fix yet, but a heck of a lot better than yesterday....

[walkhumblyfilms]

UPDATE:  I tried the fast draft method and I can get it to work BUT when I go to render out the comp, it gives the same "Out of page mapped memory...5070 :: 0" error. 

The comp was a simple text layer with extruded text, a light and some animation on both.

Fast Draft:	Available
Texture Memory:	512.00 MB
Ray-tracing:	CPU

(GPU not available - incompatible device or CUDA driver)

OpenGL

Vendor:	ATI Technologies Inc.
Device:	ATI Radeon HD 5770 OpenGL Engine
Version:	2.1 ATI-7.18.18
Total Memory:	1.00 GB
Shader Model:	-

CUDA

Driver Version:	-
Devices:	-
Current Usable Memory:	-
Maximum Usable Memory:	-

[PStJTT]

FWIW, the update fixed the problem for me -- I can link back and forth from Permiere to After Effects with no problems now.

Thanks,

Patrick

[nathantryan]

On my iMac, I held down '6' and '4' to boot into 64-bit kernel mode, and it seems to be working so far!

[Guest]

It didn't fix my system.   which is a gtx 285 and a gt 120

Mac 2008 os 10.7.4

cuda 4.2.9 GPU Driver Version: 7.18.18 270.05.25f01

[nielheesakkers-3E0oUt]

Here the same.

Still unable to use the raytraced engine ... I start to regred my purchase ...

[Tavis_Dunn]

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.

[Matt Maxwell]

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.

[@ryna]

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.

[marq5_1]

@@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!

[Tavis_Dunn]

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.

[Guest]

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.

[walkhumblyfilms]

Has anyone been able to get the raytracer to work with an ATI 5770 graphics card?  I still can't get it to work normally, nor can I render out a comp.

[blaset10855379]

Same error. Tried every method listed so far.

System info:

• OSX 10.7.4
• MacPro 5,1
• Nvidia GTX580 (with modded "raytracer_supported_cards.txt" to include card.)
• Nvidia driver: Retail_270.00.00f06 (latest)
• Cuda: 4.2.10 (didn't work with previous version either.)
• Ram 9gb. (3x2gb + 3x1gb sticks - in triple channel mode)
• also installed on this system: AE 5, 5.5.

Things I tried:

• update AE to latest (v11.01)
• update/uninstall/reinstall cuda driver
• reinstall latest nvidia driver
• delete AE preferences (~/library/Pref/Adobe/AE/11)
• delete nvidia caches

[Guest]

well you have a modded card they aren't going to support a card that not even supported by apple.   update fixed my problems just fine. 

[Bigredfirecracker2]

9 GB of ram? does sound a little like a hackintosh, and 9 gig to run after efects is pretty light.

Make sure you are running in 64bit mode that seems to be a factor.

[blaset10855379]

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.

[Bigredfirecracker2]

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?

[zikade]

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.

[SquidBean]

I still have this problem! I have installed the update for AE cs6

I am running Mountain Lion OSX 10.8 Developer Preview 4

Fast Draft:	Available
Texture Memory:	409.00 MB
Ray-tracing:	CPU

(GPU not available - incompatible device or CUDA driver)

OpenGL

Vendor:	NVIDIA Corporation
Device:	NVIDIA GeForce GT 650M OpenGL Engine
Version:	2.1 NVIDIA-8.0.46
Total Memory:	1.00 GB
Shader Model:	-

CUDA

Driver Version:	-
Devices:	-
Current Usable Memory:	-
Maximum Usable Memory:	-

not sure how you guys get the big info box?

[Guest]

Are you a developer?   Does Adobe support 10.8 at all?   did you boot into the 64bit kernel?  Does nvidia support 10.8 yet?  Why would you expect cs6 to even work at all with a developer preview?

[SquidBean]

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.

[Guest]

So what you are telling us is that you are running a pirated version of the OS since you aren't  developer and that is the only way to LEGALLY have it installed. 

[nesha_le]

Yeah, and he is the first one doing that....C'mon man...

[Guest]

He's the only one dumb enough to say he's doing it on a public forum and then expect that the other SOFTWARE company that probably isn't going to be hot to help a pirate with his problems.  😕