- Prefers to be called
- Uses pronoun
- Personal website
- Work website
- Vimeo profile
- Twitter profile
- Facebook profile
- LinkedIn profile
- 2 years 11 months ago
- Last seen
- 17 hours 14 min ago
Hello, a follow up... I think the shader error in the console may have been a red herring (although I have not rolled back my comps to confirm)
However the issue was still happening, where after loading a certain composition, it causes some kind of error with all the other comps where the audio input stops working and overall it breaks all other Vuo comps. It was difficult to debug as I wondered if it had to do with audio error George pointed out.
However I'm almost certain now that there is an issue with the "make image layer" node. I had this node in a couple of comps and removing this has stopped the "breaking" of the other ones (sorry for my incorrect language here, it's really hard to explain and I will take some screen recording to demo this)
If this theory continues to be confirmed as I stress test today (fingers crossed) I will log a proper bug here and with VDMX, after this weekend.
I've been having problems with some compositions in VDMX where they don't render properly, they get "cut off" in the output window and preview windows. It's a bit hard to explain but it's something I've raised before here a while back and thought was fixed. Reading the console logs I was getting the error on this bug report - both in 188.8.131.52 and 184.108.40.206. A lot of my compositions had lit colour and unlit colour shaders so I thought that was the problem, however I have removed all shaders from my comps and and am still getting the error in the console. I also created a brand new Vuo file and pasted in the nodes (that did not include any shaders) in case there was something in the memory that was still being referenced.
After removing the shaders I've not had this rendering issue happen yet - however it will be sometimes ok for hours and the I'll trigger a comp randomly and then it "breaks" a bunch of other comps. I was trying to find the post I did a year or so back regarding this but can't find it.
Do you know why it would be throwing this error if those nodes are not in use? I have removed any custom nodes, FFGL plugs and any Image Filter Protocol that I was using as effects.
It's worth mentioning that there are no issues if I have "run Vuo files in separate processes" checked ON - however this is not a solution for my show this weekend, as there is a momentary pause each time I load in a new composition, even if it has been loaded in before. I did a 4 hour show with all the same the files I was troubleshooting today containing shader nodes on the weekend past without problems, with "run Vuo files in separate processes" checked ON.
I must have completely misread your last comment then somehow. 🙄 The language that you are using to communicate your thoughts is coming across somewhat negative and hostile.
Ps. I wasn't advanced enough to do OpenCL particle systems. I'm a noob with GLSL too. I'm a designer who learned a bit about code. Sitting here making snide comments is quite frankly unhelpful. This is meant to be a positive space to discuss Vuo. I'm out.
I hear what you are saying George but things like colour coding, node naming, being able to search with names mapped to QC, the notes and details added to each node that was missing in QC etc. contributes to an overall improved user experience. This is not just "styling". The UX of Vuo is way better than QC and it's finding that balance. Origami improved a lot of things in QC but this was not native and ran super slow if you exposed the values on the nodes for example. There is also not much use having something purely functional that is not intuitive to use, I feel Vuo has done a lot of good work in this area, a huge amount of effort has gone into the documentation too.
I like to add coloured coded notes with my colour coded nodes so I understand what they are when I open up a comp at a later stage. Anyway we are talking about this ad nauseam but I don't think it should be all about function over form. Yes we have different ways of working - as a product designer I've appreciated the care and attention taken to the details even if I don't have a native particle node yet for example because even QC particle node was crap and we used external plugins.
Magneson I actually don't visit the node gallery too often! I should do!