OctaneRender for 3ds max v2.0 issues
Posted: Tue Jun 10, 2014 11:25 pm
.. OK karba you should obviously post a sticky on the 2.0 version... let's post on a single thread
- issues so far:
- on max 2011. - when using the lock resolution button on the octane viewport, so the resolution adapts to the window size, the region render doesn't show up, when the resolution lock is disabled, it shows up
- why are the procedural textures like marble not working with displacement
- also while watching the C4D preview video of 2.0 octane, I noticed they are using the c4d built in procedural textures - well, why cant we have that for max? - I am guessing there are workarounds like temporary baking a texture and assigning it.. I already switched from c4d to max way back, almost mainly because of octane live implementation of octane
- received a huge system crash when the displacement was set at a huge value .. (maybe it's my hardware, sometimes it lock up like that.. but this was at this particular time)
- the sweet stuff: displacement
, hard edges
, region render
is even more useful now when I tried it - I can sweep around the render with it, and increase render power on places that are noisy - this might prove to be the greatest thing yet.. it's like 80% of the render looks clean, but you wait for that one shadow to clear up
- issues so far:
- on max 2011. - when using the lock resolution button on the octane viewport, so the resolution adapts to the window size, the region render doesn't show up, when the resolution lock is disabled, it shows up
- why are the procedural textures like marble not working with displacement
- also while watching the C4D preview video of 2.0 octane, I noticed they are using the c4d built in procedural textures - well, why cant we have that for max? - I am guessing there are workarounds like temporary baking a texture and assigning it.. I already switched from c4d to max way back, almost mainly because of octane live implementation of octane
- received a huge system crash when the displacement was set at a huge value .. (maybe it's my hardware, sometimes it lock up like that.. but this was at this particular time)
- the sweet stuff: displacement


