Getting .numpyArray from TOP broken within Engine 2025.33070

Bugs
1

Hello,
I am not sure whether this could be related to my older GPU (Quadro M5000M), but I feel like the latest build (actually this could have happened couple builds earlier but I have noticed just now) broke usage of .numpyArray on TOPs within Engine COMP. When I use attached example in 2025.32280, it works without any problem. But when I open it in 2025.33070, I am getting just black pixels.

engine_top_numpy.zip (7.1 KB)

Thanks :slight_smile:

2

Hi - there was a workaround for a driver issue introduced in 2025.33070 which may have affected this. Your example works here on a newer GPU.

I suspect that if you can do something to cause the texture to be modified inside TouchEngine before you use .numpyArray then it might work - something like In → Transform TOP → Script TOP (with the Transform TOP on default parameters so it’s effectively doing a copy).

We’ll take a look here to see if we can find a way to restore the previous working behaviour.

3

Hi Tom, thanks for reply and for looking into this. I am actually using Flip TOP before going into Null TOP (from which I read image using .numpyArray), so I guess the copy is made, but it doesn’t make it work.

Thanks, in case there might be some way of making this work it would be great.

Nevertheless I feel like I should start looking at some new laptop as I have seen quite a few problems related to DirectX texture sharing over last couple of years (all caused by my old GPU). :slight_smile:

4

Yep a flip will be making a copy - sounds like that must be failing too. Having had a bit of a look I suspect this may be a device or driver issue you won’t be able to avoid.

In the longer term we hope to be able to reverse the workaround and restore the 32280 behaviour, but I couldn’t put a date on that. Sounds like you might have a new laptop by then…

5

Thanks for info. I guess for the time being I will do custom C++ operator to bypass this issue (converting custom python-based component into an optimized cpp code - so that no Engine is needed for this use case) and later I will check out new laptops to get rid of such old gpu problems. Thanks again for help :slight_smile: