UE4 & Spout problems (black textures, memory share, texture share, OpenGL / DirectX Interop warnings)

[meetya]

OK, the main problem seems to be ‘Cannot create DirectX/OpenGL interop’. All the others, such as ‘Couldn’t read Shared Memory’ are not really bugs - just warning & notifications.

Unfortunately, I don’t have any out-of-the-box ideas yet, but I’ll try to reproduce the error tomorrow. The only idea I have atm is that UE4 for some reason uses another GPU (integrated graphics perhaps?)
Reminded me of this post:

Realsense Camera Input distorted and lagging

It seems like camera input doesn’t work correctly using integrated graphics, which the application was defaulting to. Upon creating a custom rule to force it to use my good graphics card (To fix Spout issues), I tested the camera again and it seems to be working properly. At the very least it appears to have solved the issue.

Is there any chance you could try on a different computer in the meantime?

Thanks!
Mitja

[robb]

This error looks similar to one of the issues I had in the past (Author of the linked issue post). In my case I was running everything on a laptop, and LightAct had been using integrated graphics while UE4 was using the proper card. I believe spout needs both to be running on the same card since it uses shared memory to communicate.

Ensure that both applications are set to the same graphics card, if there are multiple. (NVidia control panel should have these settings) If that’s not the case, then unfortunately my post will be of little help.

Good luck,
Rob

[meetya]

The conversation with @rolfesam switched to PM for some reason, but after I’ve asked him how did it all turn out, he replied this:

On another topic

From my brother/creative partner:

So, we tried everything obvious, e.g. completely reinstalling the GPU drivers, reinstalling the Spout plugin, restarting. We noticed the Vive running through our Blackmagic into the motherboard, and, since the Blackmagic was a new object, decided to unplug it and test. It worked. Plugged it back in (without the Blackmagic, just in case), and it still worked.

So what was likely the reason was, at some point in working with VR, Lightact and the Blackmagic, Lightact had prioritized the motherboard’s integrated GPU over the NVIDIA, meaning Spout would have a fit every time. Removing the motherboard as a visual unit for a moment seemed to help things self-correct

I’ll add that I don’t think the Blackmagic had as much to do with it as the Vive being plugged into the motherboard.

Thanks for sharing @rolfesam.