CS3 OpenGl problem

[Graham Proctor]

this is very, very interesting…

Recently I upgraded my main production system from a G5 dual 2.5GHz PPC 6gb RAM to a 2 x3 GHz Quad-Core Intel Xeon with 4gb (Apple) RAM. I also went from using Tiger v10.4.11 to Leopard v10.5.3 .. and switched over to using an NVIDIA board (8800GT).

Just as soon as I got going I straight away noticed that there were issues with OpenGL in AECS3 (v8.0.2).

I”ve also got a MacBook Pro (2.33 GHz core duo, ATi chip set, Tiger 10.4.11) so I made up test file set to use on both systems. On the laptop everything was OK. Back on the new G5, OpenGL in After Effects is all over the place. Even with a completely empty project, just switching from adaptive to OpenGL in Fast previews will instantly bring up a message which says:

After Effects error: AE_OpenGL: Failed to render fragment. (5605 :: 0)

I don’t know much about OpenGL but what I do know suggests to me that something is happening prior to delivery of the rendered fragment into the ‘per-fragment ops’ part of the procedure – i.e at the rasterization stage in the pipeline.

Apple kindly offered to ship me a replacement 8800GT in case the board was defective – but after installing, everything was exactly the same as before.

Adobe tech support has been ‘distant’ on all this. They’re going through the motions but it doesn’t feel like ‘support’. I have pointed out to them in an e-mail that on many on-line forums, contributors were reporting very similar issues. I also followed through on their reasonably extensive fault finding suggetions in:

https://www.adobe.com/go/kb402244

…but all to no effect.

I have reinstalled the AE CS3 software, installed every available update and so on and so forth. I also ran Apple’s hardware test , Xbench and Realtech’s VR GLview but saw nothing in any of that to raise an eyebrow.

I’m totally exhausted now and still out in the void between Apple and Adobe.

Any ideas?

What would be great would be some test or some procedure that would nail it down – some method where I could demonstrate that either the OS, the card, the software or a combo of these is behind all this.

thanks

best,

Graham Proctor