Hi, i m experiencing very strange behaviour on a project requiring a full screen renderer on laptop screen for tracking, and using 2nd output screen as projection.
The tracking is done with mouse/sytlet
Either in DX9 or D11, moving the mouse out of limits of the renderer doesnt give a data > to - 1 or 1, but rebounce the mouse position to 1/3 position of the screen !
I tried to put conditions with limits / borders in my patch to avoid this, but it seems to be windows dependant !
How can i avoid this and continue to have the old behaviour i m used to ( coordonates -1,3 for example) ?
Yup I have come across this many times as well. If you use the mouse for rotation for example by say right-click and dragging, you want it to continue rotating even if you hit the edge of the renderer. The mouse cursor jumps back and can continue to move. Since all mouse moves are usually relative, it doesn’t matter, since it only looks at the directional change in one frame.
I never quite figured it out either, but it seems to be hardcoded behavior in the vvvv renderer.
Maybe this can help you. Just middle-click inside the renderer to set the window handle.
do you know where i can get the mp.essential pack in non vpm format ( vpm doenst work on my computer) to accessto HandleFromCursor node ? The github source doesnt show up this ressource. 27797592_1992663527415230_6914104044486730847_o|800x613
in the vvvv folder open vvvv.exe.config (hidden file by default) and look for:
<probing privatePath="lib\core" />
replace it with
<probing privatePath="lib\core;packs\md.core" />
and that’s why I wrote vpm so people don’t have to download multiple things and edit xml config files themselves and I can keep reusable components separately maintained.
