I am trying to UV Pelt an object and having a problem. I did the pelt but when I try to save out the UV Texture to Image it give the error “Invalid usage for display command” I have done it many times in v.8 but it does not want to work at all in v.9.1.124. Any ideas what I'm doing wrong?
No problem here Jerry, but I'm on 9.1.193. Mind you I've never had a problem saving the uv image. Worldcmt, are you on the same version? Any chance you can upgrade?
“gravity is not a force, it is a boundary layer” “everything is coincident” “Love; the state of suspended anticipation.”
Yes I'm using Houdini v.9.1.124 , I really don't know what is going on, I did try with UVProject and with the UV Pelt and the same problem. What I am doing now is saving my geometry as an OBJ and then import the model to cinema, then save my images with Bodypaint. It is frustrating because I want to do it all in Houdini but it just gives me the same “Invalid usage for display command” error.
There is/was a bug where this would fail for a path/filename containing spaces. I'm not sure whether this was fixed in 9.1, but avoid spaces and it may work.
I am using Houdini v.9.1.124 as well so I will try Houdini 9.1.179 today and see if that helps. I have it on 3 different computers and they all do the same thing.
9.1.179 and still the same problem, I did uninstall the software, reinstall it, etc. and nothing. What this error means ? “Invalid usage for display command”, it has something to do with the video card ? OGL ? Thank you all
I never use spaces anywhere in Houdini. I can have the name a.pic and it still does it. It also does not matter if I type in the path or use the browser.
I just wanted to make sure. Note that it would still be a problem if the space was in the path to the file, not just the file name. On windows it is not that uncommon to run into spaces in paths.
This feature uses wren to render the image, and that error message seems to indicate that the wr_detail field in the wren version of an .ifd file is out of place. There is not much variation in the generation of this file, so this sounds odd. I can't reproduce it.
THANK YOU! That was the problem alright. At 512X512 it works perfectly) It would be nice if it went higher though. Not sure why that would need to be limited in Apprentice.
jjstanley THANK YOU! That was the problem alright. At 512X512 it works perfectly It would be nice if it went higher though. Not sure why that would need to be limited in Apprentice.
because you could use the FREE Apprentice to do pro level UV/texture work…