Hallo,
Yes, I'm aware of that. So I always wait first untill David releases the new update of VDMX with new bundled vuo version. Than I do the tests. But it always gave erros/glitches. Right now I'm on the vdmx b8.7.2.3.dmg( the link you have send) since it came out. This specific version was giving me more problems, not even letting the vdmx to open.It crashes straight away. ( I reported the bug here on 25th of april: https://vuo.org/node/2499)
I think that was still on vuo 2.0.2 and the 2.0.3 update came few weeks later, so Im waiting for the new vdmx update to see if it will be fixed ( at this moment I cannot open vdmx, it crashes at the start)
Im not sure about vdmx not working properly...I have been using more than 10 years and it was always stable and never gave problems (some minor ones): Both on laptop and desktop runs smooth so I think it's something vuo related as it is giving problems since I started to use vuo comps.
I didnt try yet trashing vdmx folder.....would that delete my inner vdmx project settings?
Hallo,
I always test it after each update and on all of them it's still the same. I seems like it's getting worse. With vuo 2.0.3 installed vdmx goes crazy as soon as I open it. Before it allowed me at least to play simple compositions and it only gave glitches and errors when i tried to play compositions containing 3d nodes but now as sonn as i open vdmx, it doesnt even let me click on anything, the whole screen goes glitching.
Ok, thanks. As you mention Vuo going from OpenGL to Metal, is there any aprox. timeline on this?
I still cannot run Vuo on my laptop due to this submitted bug two years ago:
https://vuo.org/node/2209
( I have to create stuff on my desktop and than pre-record the compositions for my vj session turning them into QT, so Im loosing all the real time interactivity)
So I'm still waiting for the solution for this. I have been told that would be probably solved by moving to Metal. Would that be any update soon?
●●●○ — It prevents me from completing a specific task with Vuo.
Steps causing the bug to occur:
Hi,
Has the behaviour of the 3d nodes changed in vuo2? For example 'Spike 3d object' in vuo1 reads the texture correctly and when the effect is applied it spikes the object with the texture applied.
But in vuo2 the same composition doesn't 'recognize' the texture the same way and even with the value 0 in 'Spike effect' it doesnt load it. When I take the effect out, it's fine. Is this the way it's meant to work? Or has something been changed?
First 2 photos are from vuo1 composition and second 2 from the same composition but ran in vuo2.
