I have had limited/inconsistent success using Rhino/Octane with UV mappin
Just when I think I have a method that works, it seems to break, despite using the same method/file basis.
In fact, when I do UV unwrap to position geometry against the texture map, the geometry is sometimes flipped in the wrong direction.
Currently, the attached file/texture refuses to map correctly (it is upside down) despite the rest of the box/object UV mapping correctly.
I have tried flipping normals/directions of surface to no avail.
Any thoughts/assistance would be appreciated.
Thanks,
Rick
g over the years.Mapping issue (texture direction)
Moderator: face_off
Hi. Octane should just use the UV coordinates provided by Rhino. Is the UV mapping showing correctly in the Rhino viewport? If not, then the issue is at the Rhino end. You can also debug UV mapping issues by rendering a UV Coordinates pass in Octane, which will show the raw UV coordinate X/Y values. If you have no luck with this, please send me the Rhino file and I will take a look.
Thanks
Paul
Thanks
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Ok, figured it out Paul...Unwrap seams defined in Rhino were causing issues when creating correct UV.
Redefined them then unwrapped and remapped everything and it seems ok.
Thanks,
Rick
Redefined them then unwrapped and remapped everything and it seems ok.
Thanks,
Rick
Win 7 64 | GTX260 x 2 | Core i7 860 | 4GB & OSX 10.6 | 8600M GT | Core 2 Duo | 4GB
One other persistent bug which cropped up a month ago is incorrect rendering of textures, unless I set the Rhino viewport to Render, then initiate Octane viewport.
Also finding that when I Open a second file from Rhino, after a fresh boot of the app, all viewport are black and won't refresh properly.
Using the latest version of Rhino (seems persistent over the last 4 iterations of Rhino 7) and latest Nvidia drivers.
Thanks again.
-Rick
Also finding that when I Open a second file from Rhino, after a fresh boot of the app, all viewport are black and won't refresh properly.
Using the latest version of Rhino (seems persistent over the last 4 iterations of Rhino 7) and latest Nvidia drivers.
Thanks again.
-Rick
- Attachments
Win 7 64 | GTX260 x 2 | Core i7 860 | 4GB & OSX 10.6 | 8600M GT | Core 2 Duo | 4GB
Yes, this was happening to me too. I even reported it to McNeel -> https://discourse.mcneel.com/t/rhino-vi ... ene/129055. However it stopped happening for me a long time ago. Unsure if it was Nvidia drivers or Rhino7. Perhaps reply in the McNeel forum thread, and they can investigate further.One other persistent bug which cropped up a month ago is incorrect rendering of textures, unless I set the Rhino viewport to Render, then initiate Octane viewport.
Also finding that when I Open a second file from Rhino, after a fresh boot of the app, all viewport are black and won't refresh properly.
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question