***BAD BUG (Octane accuracy)...PAY ATTENTION!***

3D Studio Max Plugin (Export Script Plugins developed by [gk] and KilaD; Integrated Plugin developed by Karba)
Forum rules
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
User avatar
gabrielefx
Licensed Customer
Posts: 1701
Joined: Wed Sep 28, 2011 2:00 pm

Hi Refractive team,

hi found a bad bug in the Octane for Max accuracy

Octane for Max doesn't respect the 3ds Max accuracy, check yourself with the accuracy calculator.

The conclusion is that if you have a room distant 50 meters from the origin you have to move every time your scene on the origin because Octane will render triangles with gaps and black areas.

I've posted here some examples and the Max scene.
This scene is drawn in centimeters and if you merge it in a new scene setting the units in meters you will get the same results.
Attachments
vase.zip
(27.55 KiB) Downloaded 285 times
at_0-0-0.jpg
at_5000-5000-0.jpg
at_50000-50000-0.jpg
at_100000-100000-0.jpg
test_cucina02b.jpg
quad Titan Kepler 6GB + quad Titan X Pascal 12GB + quad GTX1080 8GB + dual GTX1080Ti 11GB
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

why did you attach a photo at the bottom? proves that nature has some bugs too?
scnr ;)
you'r renderings amaze me every time. perfect down to the detail, like pieces showing weld lines...
The obvious is that which is never seen until someone expresses it simply

1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
User avatar
pixelrush
Licensed Customer
Posts: 1618
Joined: Mon Jan 11, 2010 7:11 pm
Location: Nelson, New Zealand

You have sharp eyes to notice, I was too busy looking at your nice picture... 8-)
Doesnt seem like it would be too serious until 100m radius, I guess, still that's good to know, a few of my scenes have been 25m away, but they are nothing like your standard, so it wouldnt have mattered anyway. :roll:
Lucky we have you, with your attention to detail, finding these things for us. :)
i7-3820 @4.3Ghz | 24gb | Win7pro-64
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55
User avatar
Karba
OctaneRender Team
Posts: 2300
Joined: Sat Jun 11, 2011 9:05 am

gabrielefx wrote:Hi Refractive team,

hi found a bad bug in the Octane for Max accuracy

Octane for Max doesn't respect the 3ds Max accuracy, check yourself with the accuracy calculator.

The conclusion is that if you have a room distant 50 meters from the origin you have to move every time your scene on the origin because Octane will render triangles with gaps and black areas.

I've posted here some examples and the Max scene.
This scene is drawn in centimeters and if you merge it in a new scene setting the units in meters you will get the same results.
Can you try to increase rayepsilon?
User avatar
gabrielefx
Licensed Customer
Posts: 1701
Joined: Wed Sep 28, 2011 2:00 pm

Karba wrote:
gabrielefx wrote:Hi Refractive team,

hi found a bad bug in the Octane for Max accuracy

Octane for Max doesn't respect the 3ds Max accuracy, check yourself with the accuracy calculator.

The conclusion is that if you have a room distant 50 meters from the origin you have to move every time your scene on the origin because Octane will render triangles with gaps and black areas.

I've posted here some examples and the Max scene.
This scene is drawn in centimeters and if you merge it in a new scene setting the units in meters you will get the same results.
Can you try to increase rayepsilon?
obviously yes, it doesn't help.
quad Titan Kepler 6GB + quad Titan X Pascal 12GB + quad GTX1080 8GB + dual GTX1080Ti 11GB
User avatar
mbetke
Licensed Customer
Posts: 1293
Joined: Fri Jun 04, 2010 9:12 am
Location: Germany
Contact:

Almo Nature - very good cat food. :)
PURE3D Visualisierungen
Sys: Intel Core i9-12900K, 128GB RAM, 2x 4090 RTX, Windows 11 Pro x64, 3ds Max 2024.2
hadouken
Licensed Customer
Posts: 103
Joined: Thu Jul 01, 2010 10:56 pm
Contact:

This isn't so much an octane thing as much as the nature of 3d apps. The farther you work from the point of origin, the less accurate the system will run. The same thing happens in max. This is why choosing the correct unit scale for your scene is really important. You might want to change to inches, although doing this mid-workflow is never a good idea.
Intel Core i5-2500
6GB DDR3
GTX470
Windows7 Home Premium 64-bit

http://zaixxiaz.com/
User avatar
roeland
OctaneRender Team
Posts: 1822
Joined: Wed Mar 09, 2011 10:09 pm

Yes, this is a problem with reduced precision. I have looked at it and it seems to be worse than in 2.52, so the new geometry processing introduced in 2.55 is probably less precise than the previous system.

--
Roeland
User avatar
siriolsd666
Licensed Customer
Posts: 58
Joined: Sat Mar 05, 2011 1:13 am
Location: Olbia, Sardinia, Italy
Contact:

Yes, a real problem! :cry: :cry: :cry:
Attachments
In this picture, the ant is about 0,7cm long.<br />Correct size but with BUG!!!
In this picture, the ant is about 0,7cm long.
Correct size but with BUG!!!
In this picture, the ant is about 70cm long.<br />Incorrect size and no BUG.
In this picture, the ant is about 70cm long.
Incorrect size and no BUG.
AthlonII X2 6400+ 2.81GHz, 4Gb RAM, Gainward GF 460 GTX 2048Mb, Win7 64bit
User avatar
Karba
OctaneRender Team
Posts: 2300
Joined: Sat Jun 11, 2011 9:05 am

siriolsd666 wrote:Yes, a real problem! :cry: :cry: :cry:
This is not a problem. You have to work with proper unit scale.
Post Reply

Return to “Autodesk 3Ds Max”