Filetexture and 2 renderers

vvvv beta general
#1

I was patching some kind off foto slideshow, for wich I ‘pingpong’ between 2 filetextures.

For testing purposes I created 2 renderers, 1 with the 2 textures, so I know what I am suposed to see, and on the other my ‘cool’ slideshow module.

I have 2 monitors at my computer, currently set in ‘extend desktop to next screen’ (not in spanmode, because I like a short taskbar).

Well, when I put 1 renderer on 1 screen, and the other on the other screen, the ‘up and running’ pin from the filetexture just keeps blinking on and off. (I was using this pin to toggle back and forth).

Took me a whle to figure out is was a screen problem, so I wondered if it is a bug, or a lack in hardware (GF7600).

Going to test in spanmode now, let you know.

#2

I deleted my small preview, and all seems to go well, so I got another question, about ‘post processing’.

If I use a renderer - DX9Texture combo (renderer closed), to group some 3D and 2D layers, do I have to specify on what screen I am goin to use it? So all textures remain in memory for that screen, or doesn’t it work like that?

Feel like a noOb, but I need more performance!!

#3

of course you know the “device”-pin of the renderer?!?

btw.: i prefer my taskbar vertical on the left side…

taskbar.png (67.5 kB)

#4
  • If I use a renderer - DX9Texture combo (renderer closed), to group some 3D and 2D layers, do I have to specify on what screen I am goin to use it? So all textures remain in memory for that screen, or doesn’t it work like that?

no need to specify anything. the dx9texture is rendered only on the device it is also visible). therefore if you have 2 renderer connected to a dx9texture, one on monitor 1 and the other on monitor 2 it will be rendered twice. if you hide the renderer on one monitor it will only be rendered once.

better you know nothing about the “device” pin…

#5

hmmm, that’s odd. when i want to use a dx9texture on 2 separate monitors/adapters, i have to use 2 separate dx9texture-nodes - otherwise the second adapter only displays buffer noise. but now that joreg claims otherwise, i’ll have to investigate further…

#6

@diki: you sure? what you describe is the known problem with videotextures, but dx9textures should just do fine.

#7

positive; i just reproduced the problem on two machines. when using a single DX9Texture, the texture on the renderer that was created second freezes when one of the two renderers is moved to a different monitor. it continues operation when both are on the same monitor again.

#8

@diki
damn. right. thanks.
fixed.