Macha Posted June 18, 2010 Share Posted June 18, 2010 There are some nodes in compositing that work with z depth information, such as lighting and fog. Over the months I have periodically tried them on 4, perhaps even 5, different machines and they only ever worked on one of them. I usually get mixed up garbled images consisting of funny colored squares or lines. The one thing all these machines had in common is windows and nvidia cards. Do other people experience that problem or is there a trick to this? A typical example looks like the one below. Quote Link to comment Share on other sites More sharing options...
3__ Posted June 18, 2010 Share Posted June 18, 2010 I had a similar display problem, but with the scale COP. Turning off 'Use GPU to Assist Compositing' and 'Use Collapsible Pixel Operators' in preferences solved it. Quote Link to comment Share on other sites More sharing options...
Macha Posted June 18, 2010 Author Share Posted June 18, 2010 Thanks. "Collapsible Pixel Operators" surely never crossed my mind. It seems better but some nodes still don't work. (Expand COP for example). It's all very mysterious. I need to test it a bit more... Quote Link to comment Share on other sites More sharing options...
Macha Posted June 18, 2010 Author Share Posted June 18, 2010 Wow, look at this craziness. I almost like it! Quote Link to comment Share on other sites More sharing options...
Jason Posted June 18, 2010 Share Posted June 18, 2010 Nice;) You can't do that on purpose! Quote Link to comment Share on other sites More sharing options...
LFX Posted June 18, 2010 Share Posted June 18, 2010 These effects were my first experience I made with the compositor, and I thought that's why they tell it's useless for compositing. Quote Link to comment Share on other sites More sharing options...
old school Posted June 18, 2010 Share Posted June 18, 2010 Surely this can be submitted in to Support as a bug. Hardware acceleration on or off, doesn't matter. Quote Link to comment Share on other sites More sharing options...
abvfx Posted July 8, 2010 Share Posted July 8, 2010 Yeah i get it too, cool but not very useful Quote Link to comment Share on other sites More sharing options...
Macha Posted March 22, 2011 Author Share Posted March 22, 2011 Old thread, same problem. Some versions of H work and then it's all messed up again. What's going there? Recently I can't use any of the fog, lighting, and color correction nodes. I either get crashes or those funny windows popping up and crazy graphics. Quote Link to comment Share on other sites More sharing options...
Macha Posted March 22, 2011 Author Share Posted March 22, 2011 (edited) And here is what I get when I blur a shape... Don't know why cops have deteriorated so much lately... Edited March 22, 2011 by Macha Quote Link to comment Share on other sites More sharing options...
malexander Posted March 22, 2011 Share Posted March 22, 2011 I would suggest turning off "Use GPU Acceleration" if you've turned it on. This option uses GLSL to process images for certain COPs. Unfortunately, unlike the rest of Houdini, GLSL code is compiled at runtime by the compiler in whatever driver version you're using. Updating our gcc or MSDev version for a new build often causes compiler errors, but we resolve all of these before the software can be shipped out, and the compiler version is completely under our control. Not so with GLSL - the compiler version is out of our hands, and unfortunately code that compiled before sometimes stops working as driver developers optimize and add features to it. Ideally this wouldn't happen, and GLSL code that was written 2 years ago would work on any current AMD or Nvidia driver. However, this just does not seem to be the case and it requires constant maintenance (the same goes for viewport shaders). Unfortunately, this same issue will also apply to OpenCL. Doing a quick search through the bug database for COPs bugs, I do not see any of the above issues submitted. As no active development is currently being done in COPs and none of the regression tests are currently failing for it, unless we receive a bug report, we won't know to fix it. Please don't assume Side Effects knows about an issue, regardless of how glaring it may seem. Quote Link to comment Share on other sites More sharing options...
Macha Posted March 22, 2011 Author Share Posted March 22, 2011 (edited) Please don't assume Side Effects knows about an issue, regardless of how glaring it may seem. OK, I'll submit it. The problem with these kind of bugs is that I usually get a reply along the lines of "we can't replicate the problem", and I can't really say much more than "I plugged an image into the blur node" It seems that at least some people experience these problems and perhaps one of the people seeing this found a solution. So, using an old driver might solve it then? Edited March 22, 2011 by Macha Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.