Odd normals issues

Generic forum to discuss Octane Render, post ideas and suggest improvements.
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Post Reply
gvnwst
Licensed Customer
Posts: 12
Joined: Tue Oct 19, 2010 5:56 pm

Hey all, not sure if this has been asked (Couldn't find anything) but I'm having some really weird issues with object normals in my latest project.
As you can see, the background quite odd...Max reported no export errors, and I am only using about 450 MB of my VRAM (out of 900 total in my GTX 260). I assume there is some trouble with the normals on the object. (the material isn't causing it, from what I can tell, either)

Any ideas/another thread this problem has been solved on?

Thanks,

Gavin

Oh and I'm running 2.43, which I understand to be the latest release...
Attachments
Test3.png
Last edited by gvnwst on Tue Mar 01, 2011 9:33 pm, edited 1 time in total.
GTX560Ti 2GB | i5 2.66 Quad | Win7 x64 | 12GB DDR3
User avatar
kubo
Posts: 1377
Joined: Wed Apr 21, 2010 4:11 am
Location: Madrizzzz

yeap, it's not a normals problem, rather is an issue with the scale, check to see if max scale is in meters (there is TWO configs to change, under customize "units setup" AND "system unit setup", change both to meters) and scale properly your scene, you'll get rid of those artifacts.
windows 7 x64 | 2xGTX570 (warming up the planet 1ºC at a time) | i7 920 | 12GB
gvnwst
Licensed Customer
Posts: 12
Joined: Tue Oct 19, 2010 5:56 pm

Kubo -- thanks for the idea...but that still didn't fix it. (my two unit setups in Max _were_ different, but making them both meters didn't do a thing)
GTX560Ti 2GB | i5 2.66 Quad | Win7 x64 | 12GB DDR3
User avatar
kubo
Posts: 1377
Joined: Wed Apr 21, 2010 4:11 am
Location: Madrizzzz

well, there is another rare bug max related. Move your whole scene to the 0,0 point for example place your guitar base there. Re-export, if your scale is right this is the only other thing that could be producing that result. It's a max limitation concernig distance from origin.
Cheers
windows 7 x64 | 2xGTX570 (warming up the planet 1ºC at a time) | i7 920 | 12GB
User avatar
ttaberna
Licensed Customer
Posts: 320
Joined: Sun Apr 04, 2010 8:02 pm
Location: BCN

Maybe the scale in octane import parameters is set different than meters.
Check it out in account prefs in the octane file menu and match them between max and octane.
Then you have to check the scale value in the OBJ exporter in max. to be set to 1, sometimes it is set to 0.01.
and of course, ALWAYS set your scene near to origin (0,0,0) as master kubo said.
Cheers
Rampage IV Extreme+i7 3920k+2x GTX580 3GB+2x GTX470
User avatar
Skeletor
Licensed Customer
Posts: 83
Joined: Fri Aug 06, 2010 7:43 pm
Contact:

Try to turn up the ray epsilon a bit and see if it helps
Win 7 64bit, GF 460 2GB, Intel quad, 4GB memory
User avatar
suhail_spa
Licensed Customer
Posts: 229
Joined: Tue Nov 16, 2010 9:51 am

lastly...
also check if you dont have another instance of background copied over itself..

nice guitar model btw... :)
DELL Precision M4500 Laptop (win7 -64bit, Intel core i5 M520 2.4Ghz, 4Gb, Quadro FX880 1Gb, PCI express slot)
with GTX 460 -2GB (running on home-made GPU-expander)
gvnwst
Licensed Customer
Posts: 12
Joined: Tue Oct 19, 2010 5:56 pm

Thanks for all the help, guys. My scene was, somehow, like 20 meters above origin, that helped a lot (there were still one or two oddities), then I found that my ray episilon setting was at 0...changing that fixed the rest.
Now I just need to get those steel materials looking better. xD

suhail_spa wrote:nice guitar model btw... :)
Thanks!
Attachments
Test4.jpg
GTX560Ti 2GB | i5 2.66 Quad | Win7 x64 | 12GB DDR3
Post Reply

Return to “General Discussion”