matej wrote:Considerably lowering your render speed just to (possibly?) avoid that simple manual step of re-setting the model to origin, is not a solution.
Maybe Octane could check if the geometry is very far from the origin and automatically recenter it, but I don't see them changing the whole architecture, just to "solve" this very rare issue.
It's the job of the artist to produce a clean and normalized model, before exporting it (no overlapping geometry, no inverted normals, proper scale, etc...)
wow Matej - thank you for your non-solution...this is not laziness on my part, and I am not the first or second person to bring this up...this has got nothing to do with normals, manifold geometry, overlapping etc.
As I stated - the objects are not that far away from the origin, and I was pretty sure that my suggestion is aimed at the Octane team to improve the engine to be able to do more for larger scenes.
I have already moved the entire scene so this part of the geometry lies at the origin - the problem now is all the other geometry that was previously sitting at the origin is now as far away as the problem bits I had....What you see in the image is part of a room for a building which the viewer flies into from the street and then moves through out the building.
This issue is only rare to people doing small scenes to be honest. - IF Otoy wants Weta and other studios to use their renderer ( see Avatar indirect lighting compute ) , I'm sure its not going to go well to say " please don't make your scenes too big".
Maya 2013 / W7 64bit / Intel i7 980 / 24GB / Gigabyte gtx 580 3GB + 2*EVGA gtx 680 4gb / MB Gigabyte X58A-UD3R / NZXT Phantom - white/black case
Maya 2013/W7 64bit/Intel i7 3820/16GB/ MB Gigabyte GA-X79-UD3 /4*EVGA gtx 680 4gb/SSD 6Gb.s /CM HAF X case