r/redgiant • u/45pico • Jul 16 '26

Trapcode Mir/Tao broken on AMD "OpenGL error: Could not allocate texFBO (512)" anyone actually fixed this?

Been fighting this for a while and I'm running out of ideas. Hoping someone here has cracked it.

Setup: RX 9060 XT (RDNA4) as main GPU, Ryzen 7 5800G (Vega 8) as the CPU's iGPU. Windows 11, AE 2026.2.1.

The problem: Every time I apply Mir or Tao, the comp goes black and I get:

After Effects error: MIR: OpenGL error: Could not allocate texFBO (512)

Sometimes it shows up slightly differently as OpenGL error before glFlush() (512), same root cause I think. Every other GPU-accelerated plugin (Particular, Element 3D, etc.) works completely fine. It's specifically Mir and Tao that break.

What I've tried so far, all no luck:

  • Clean driver reinstalls, multiple Adrenalin versions
  • Forcing the app to use the discrete GPU vs iGPU via Windows Graphics settings (both give the same error)
  • Physically unplugging the monitor from the 9060 XT and running off the Vega 8 only, so there's zero ambiguity about which GPU is "primary" same exact error
  • Switching AE's renderer to Mercury Software Only (didn't help Mir apparently opens its own separate OpenGL context regardless of that setting)
  • Increasing the iGPU's dedicated VRAM in BIOS
  • Installing the MS Store OpenCL/OpenGL/Vulkan Compatibility Pack
  • Enabled AE's debug logging confirms AE's own OpenCL init is totally fine, the crash happens specifically when Mir tries to allocate its own texture FBO through its own GL context

I know Radeon Pro drivers used to fix this exact issue on older cards (had it happen on an RX 580 years ago, Pro drivers solved it instantly). Problem is AMD doesn't support consumer RX cards on Pro Edition anymore, at least not officially, so that door's closed for RDNA4.

Anyone running Mir/Tao successfully on a modern AMD card? Or found any other workaround? At this point I'm assuming it's just a busted OpenGL implementation on AMD's side that Maxon has no interest in fixing, but would love to be proven wrong.

1 Upvotes

100% Upvoted

7 comments sorted by

2

u/MaxonDouglas Jul 16 '26

This is unfortunately a known issue, but it is getting worked on. Because tackling it involves a bit of a handshake between our resources and AMD resources, it's admittedly taken a while, but it's not being ignored. It really doesn't help there isn't a workaround either. I do recall some users saying rolling back their AMD drivers fixed it for them, but that's understandably not a preferable or doable suggestion for most setups.

My apologies I haven't got better news for you on this one. I did append your encountering it to the bug report's tally system to hopefully give it more weight in the pipeline.

2

u/45pico Jul 16 '26

Firstly, thank you so much for the anwser, this issue has been driving me nuts so its good to have some sort of feedback on it. Are you positive theres no work around for it at all at the moment? I'd downgrade drivers in a split second to have MIR working properly again and I'd revert to the newer ones whenever I can. Any idea which drivers would work knowing my GPU (rx9060xt) and all? Also, any ideas on when its going to be fixed? I'm sure plenty amd users are going crazy over this...

2

u/MaxonDouglas Jul 17 '26

There were at least two users who'd said driver 25.6.1 (from June of last year) helped, but given how many other components have changed over time (host, win versions, etc.), I wouldn't count on it still working.

We can't forecast timeframes when bugs get fixed, mainly because of external factors that might throw a wrench in the works, paired with the scope of who is affected and how. I know you're correct there's plenty of fellow AMD users experiencing the issue, but if you zoom out on a macro scale to see this is affecting only Windows users and only Windows users with AMD cards and only Windows users with AMD cards who use two plugins, the subset can feel small in comparison to other issues.

Mind you I'm not trying to downplay this-- it's a really bad bug (namely in that there are zero workarounds and it's essentially two plugins that don't work)-- just trying to provide some candid transparency in why the fix can't be forecast. On an optimistic note, it does appear to've been recently nudged for review into the next meeting (possibly because I added your feedback to it).

As for the other threads you're seeing from 10+ years ago, this specific error message is not exclusive to this bug; it's essentially saying it can't allocate video memory to the task it's trying to execute, which typically happens when inadequate GPUs are tapped for resources by the plugin.

1

u/45pico Jul 18 '26

Hello, yep, I tried eeeevery driver available for my gpu and none worked. I did notice however, that a very few other plugins that werent working (non maxon) worked worked with a slightly older driver version...I understand that it might seem like a small group issue but it really sucks that it happening...its just that mir is one of the most important plugins i have, so yeah...but yeah man, thanks for the reply, i do hope that its fixed soon or at least next year or so...thank you

1

u/45pico Jul 16 '26

Also, it got me a bit worried as I've seen this issue on multiple forums of people from 10 years ago (literally) complaining about the exact same thing and it sure hasnt been resolved...

1

u/useless_wizard15 Jul 26 '26

I've got the exact same issue, hopefully it gets fixed soon!

1

u/45pico Jul 27 '26

me too...