Since the 3.0 preview and the move to Stride, I can’t use Skia nodes: the Stride SkiaRenderer is not working. Even through its input preview is showing what is expected, its output is blank. Observed this with any kind of Skia Layer type node as input. Stopping and Running the patch again does not help.
OS: Windows 10
Graphics card: Radeon RX 560X (latest drivers)
vvvv version used: vvvv gamma 2020.3.0-0042-g1a9a5c158d preview
We had a similiar issue on a machine with two graphic cards. The SkiaRenderer chose a different one and the internal resource sharing didn’t work. So if you have two graphic cards in your machine, try to disable one and see if that solves it.
Interesting - you still have that machine? Indeed we need to create a GL context with a dummy window and then later make the dx11 device available to that context using before mentioned wgl interop extension. Maybe if for some reason that context is on a different device than the directx context things don’t work.
When trying to patch along to the Reactive Patching workshop from Node I discovered SkiaRenderer (trying to render the ISS data text output in Stride renderer) doesn’t seem to work for me either on a super modern Surface Pro 2 with intel graphics.
Rendering other geometry in the Stride renderer works and if I connect the Text Layer to a Skia renderer the text renders fine.
(edit: running vvvv gamma 2020.3.0-0042-g1a9a5c158d preview seems like there are more recent versions I could try)
@eps@mburk I assume you both were on desktop machines?
@beyon The GL version looks dated to me - compare it to my screenshot further up. Is there a driver update available maybe? Intel HD 4400 is from around 2012, while the HD 530 is from ~2015 - these three years could make quite the difference I fear :/