Beta9.10 doesnA,A't render at all

i downgraded to beta 9.2 again, which works amazing on my ancient laptop, because 9.10 doesn’t render anything.

sorry, didn’t have the time to analyze this more exactly.

I’ve some problems with renderer.

Ex9 Renderer Node seems to be very bugged. I can’t put it fullscreen more than one time. Renderer being grey when put in fullscreen. When windowed the border disappear (it is an old bug of renderer node). Sometime, changing some renderer pins values make the renderer bug.

waiting for the next beta :)

ai bois.

can we have some more info on that? we haven’t encountered any similiar problems here. so if you could provide us with some more info. kalle i know you cant, but thiv what about latest graka drivers?

does the tty renderer tell us anything?

I’ll give you more details soon.

what is graka drivers?

with “graka drivers” joreg surely wants to say graphic card drivers.

EX9 Renderer of vvvv9.10 seems to be more sensible than the previous. Some bad values make it bug easily.
I’ve solve my gray renderer problem. Coming from videotexture " wait for frame" pin value. I’ve set it to 0 for better renderer framerate but this value introduce some instable behaviours.

I think that some of my renderer bug coming from bad values

tty renderer write some “zero division error”

@+

hmm… anybody with some more info? kalle?

ok…update

on my old lappetoppe beta10 also doesn´t render at all.
TTYrenderer tells when creating a Renderer (EX9):

00:09:40 * : This device does not support the queried multisample type.

seems that this is not from interest:

still the same thing with beta 11.1
00:01:18 * : This device does not support the queried multisample type.

renderer (ex) stays grey.

at work i am with 11.1
on my laptop i stick to 9.2

aaaa.

sorry kalle for being late on this. i just had a look into our code and didn’t see anything that could go wrong there. so…hard to say. there is a tool out there which comes with the directx sdk called “Caps Viewer”. if you had this and could click: file>print whole tree to file i could have a look at your cards capabilities and maybe understand what your card does not like.

meanwhile you could also try to select a different swap effect than “discard” in the renderer. any other should prohibit multisampling and maybe trick your card to behave.

meanwhile you could also try to select a different swap effect than “discard” in the renderer. any other should prohibit multisampling and maybe trick your card to behave.

tried this once again:
doesn’t have any effect but the same error message.

now i am going to find that “caps viewer”

see youreg later…

if you had this and could click: file>print whole tree to file i could have a look at your cards capabilities and maybe understand what your card does not like.

downloading and installing that 390 MB-Monster took a while.
but where the FAQ does it “print whole tree to file”?
didn’t find it.
but i used PDFcreator with “Print to printer”.
hope this helps you…

DirectX Graphics Adapters.pdf (232.5 kB)

humm. according to the document the card understands the settings we are using for “no multisampling”.

really strange… and again hard to debug…without the machine in hands.

ahm…one last guess: create a Device (EX9 Auto) node and set the vertexprocessing type to software…hm…

setting the vertexprocessing type to software doesn’t help.
but setting Device Type to D3DDEVTYPE_REF helps.