Mainloop dotimer error when using multiple vvvv instances

vvvv beta question
1

Is triggered in tty when opening a renderer ex9 in secondary instance

any ideas?

2

[MainLoop.TMMainLoop.DoTimer: error occured in RendererNodes.TMRendererNode.RenderCB](MainLoop.TMMainLoop.DoTimer: error occured in RendererNodes.TMRendererNode.RenderCB): Access violation at address 0067B458

more specifically.

Doesn’t do it with empty vvvv. Patches are now quite built up so it’s tricky to troubleshoot. One of the three instances I’m using is just for the memofluids plugin. Getting weird behaviour from this also

3

Ok, reproducible -

2x vvvv.exe, one /allowmultiple

Make one renderer(ex9) in first vvvv.

Make one renderer(tty) in second vvvv. Drag this patch to 2nd screen.

Make first vvvv renderer fullscreen.

Make one renderer(ex9) in second vvvv.

Errors

4

just a quick thought, shouldn’t both instances should be /allowmultiple?

I can imagine the one without it would complain

5

is this the same as: https://discourse.vvvv.org/t/8223 ?

6

Hi Joreg. I’m Only going fullscreen in one instance

7

And I’m also getting serious problems with another patch even without the 2nd instance having a visible renderer

8

hei boni, please try daily/core/vvvv_45alpha28-dx9ex-6159a6933625642c4a318940fa66767b2d1388d9.zip to see if this problem is gone. note: this is a build with dx9ex/sharedmem-stuff.

9

To confirm - this is fixed in current alpha