Just a little question concerning backbuffer; using renderer(EX9) I could easily set the backbuffer height and width with the input pins. In renderer(DX11) I can’t seem to find the trick. Viewport size doesn’t seem to be the answer either, or maybe I’m not using it correctly ?
Any suggestion on how to set the height & width of a dx11 renderer would be welcome !
Ive got a similar problem, a renderer that is full screen on a 1920x1080 desktop, that i’m sending to a capture card that is also registering a 1080 signal, yet the actual backbuffer width & height as reported by the renderer itself is only 1280x720.
How can the renderer be only 720 when it’s full screen on what windows says is a 1080 desktop? Is the renderer just mis-reporting it’s backbuffer?
Is there a way to force it to be 1920x1080?
I’m having a similar problem as @fatalex - I have a 4k (3840x2160) monitor, which windows recognizes correctly as such, yet when I have the DX11 renderer go fullscreen, it reports it is only 1920x1080, and it looks it. The monitor reports itself as running at 3840x2160. So I’m pretty confident the display is really at 4K and the DX11 renderer is not sensing it properly.
Windoze “set resolution” shows it as 3840x2160 - this is on Win8 x64, 34.2_x86, latest DX11, and a GTX770 with latest drivers. I get the same on my Win7 laptop, with Intel HD4000.
When using a DX9 renderer, if it is set in Herr Inspektor for fullscreen “AsDesktop”, it only goes to 1920x1080 for fullscreen. But 3840x2160 is in the list, and when that is selected, it will correctly go to 4K fullscreen.
So apparently the DX9 renderer is also sensing the current res incorrectly.
Starting to sound like a vvvv bug in how it gets current monitor resolution.
One other datapoint: With the DX9 renderer, when I set it to AsDesktop in Herr Inspektor, I get a message on the console “AsDesktop: 1920 x 1080” instead of the correct current res of 3840x2160.
Thnaks for the tip antokhio, but I won’t be near the 4K monitor for a few days. But I tried screwing with that setting on a regular HD monitor (150% was the highest option), and it has no effect on what AsDesktop means with the DX9 renderer or what res the DX11 renderer reports when it goes fullscreen - both still do 1920x1080. But I’ll check it out, thanks!
Surely I’m not the first person to try DX11 at 4K, so I must be missing something!
is the monitor connected via HDMI? we had such a 4k-Monitor once, having only HDMI (which is not supporting real 4K atm.) and it forced the graphics card to 30fps INTERLACED! So setting the Fullscreen-Framerate to 60 might result in 1080p, 60fps. I didn’t test vvvv with this monitor.
Does not have to do anything with vvvv, just in case someone has similar problems…
HDMI 1.4 does just support 4K 30p (and 8-bit color), but HDMI 2.0 supports 4K 60p and 10-bit color, and that’s what both windows and the monitor itself report it running at. So yes be sure to check what your monitor has. (DisplayPort also supports 4K 60p).
The monitor I’m having the problem with is in a University lab, so I just ordered one of these for my own testing; 24" 4K(UHD) 60p for $290 - cheap!
OK, big surprise, what I am seeing is a Windoze 8 problem. (I HATE THE 8!)
@antokhio, Win8 does apparently automatically set the scaling to 200%, which fools vvvv into assuming the wrong resolution. Changing the scaling to 100% (actually just listed as “Small” in the dialog) fixes it.
All works fine with Win7, I suspect I might have had a bad HDMI cable with my first Win7 test. I have not tested Win10, but @keftaparty sounds like they may have fixed it there.
What is odd though is that changing the scaling on Win7 does not cause vvvv to use the wrong fullscreen res - but in Win7 I can only set scaling up to 150%, not the 200% Win8 uses by default with 4K.