Page 4 of 5

Re: OctaneRender® for 3ds max® v2.24.2 - 2.10 [TEST]

Posted: Sun Oct 18, 2015 10:34 am
by Rik
Looks like it could be a ray epsilon issue? Have you played with the values?

Re: OctaneRender® for 3ds max® v2.24.2 - 2.10 [TEST]

Posted: Mon Oct 19, 2015 7:14 pm
by acc24ex
moveable proxy behaves like a copy when I apply a bend modifier to a group of proxies .. ?!
- starts taking up memory as much as a normal copy of an object

Re: OctaneRender® for 3ds max® v2.24.2 - 2.10 [TEST]

Posted: Tue Oct 20, 2015 7:21 am
by boris
acc24ex wrote:moveable proxy behaves like a copy when I apply a bend modifier to a group of proxies .. ?!
- starts taking up memory as much as a normal copy of an object
that's 3ds max. when you apply a modifier over a group it converts them to references. open the group select one single object and look at the modifier stack, there you see the reference space between the object and the bend modifier. or look it up in track view. you have to understand reference copy in 3ds max then you understand why octane cannot treat it like an instance.
http://knowledge.autodesk.com/support/3 ... 2-htm.html

edit: quoting myself:
boris wrote:as far I understand movable proxies: they do not work that way as you wish them to work. a movable proxy can be scaled (also non-uniformaly) , moved or rotated but as soon a deformation will alter the relation between the vertices that new information has to be stored somewhere. the memory consumtion of that information depends on the vertex count of the base object and can be huge of course. that's why motion blur for deformable meshes takes so long to get into your gpu's: because for every frame the proxy is unique for octane, as it has been deformed.
another example: a reference copy of an object with an additional modifier on top will be treated as a unique proxy because that modifiers information cannot be stored by octane right now, so octane just acts kind of brute force and adds a new proxy definition to the scene. the 3ds max file size keeps being low while gpu memory consumtion gets doubled for a slightly modified object.
correct me if i am wrong.

Re: OctaneRender® for 3ds max® v2.24.2 - 2.10 [TEST]

Posted: Tue Oct 20, 2015 12:25 pm
by acc24ex
oh, thanks a lot for clearing that, yeah it makes sense now.. I tried references, same issue

- everyone else, it's a feature not a bug :), take notice of this issue if you get a sudden increase of Vram usage

Re: OctaneRender® for 3ds max® v2.24.2 - 2.10 [TEST]

Posted: Wed Oct 21, 2015 6:32 pm
by JimStar
I delete here anything regarding "internal convertor" that has been already discussed and explained in early 2.X threads.
Regarding Vray convertor: you still need to wait before I will get the possibility to improve it. Karba was supplied by Vray license by Otoy, but I still have not been supplied by Vray license, I still don't have it. I asked many times about it. So, I can't develop anything related to Vray for 3ds Max at the time.

Copy Image to framebuffer

Posted: Fri Oct 23, 2015 7:21 am
by rogerteddy
Copy Image from Octane framebuffer to Max Image framebuffer is not working here anymore .

kindly

rog!

Re: OctaneRender® for 3ds max® v2.24.2 - 2.10 [TEST]

Posted: Sun Oct 25, 2015 7:28 pm
by Phil_RA
I get hangs when I refresh the renderer, it will just freeze for a long time and then suddenly update the image. Eventually it will refresh at the expected rate. If I change any material parameter it will do the same, always an update then a freeze for a while. My ram is barely used so it's probably not related to my PC. Almost can't work.

Re: OctaneRender® for 3ds max® v2.24.2 - 2.10 [TEST]

Posted: Mon Oct 26, 2015 12:10 pm
by acc24ex
so this is how my library material always tends to show up - I can clear it if I change renderer to standard and then back
- I thought it had issue with corona render, which I removed, still shows up

- anyone with similar issues?
max 2016
Capture.JPG

Re: OctaneRender® for 3ds max® v2.24.2 - 2.10 [TEST]

Posted: Mon Oct 26, 2015 12:13 pm
by oguzbir
acc24ex wrote:so this is how my library material always tends to show up - I can clear it if I change renderer to standard and then back
- I thought it had issue with corona render, which I removed, still shows up

- anyone with similar issues?
Capture.JPG
I dont have that..
is this problem same with the old material Editor?
And which max version does this take place.
Does other max versions act the same way?

Re: OctaneRender® for 3ds max® v2.24.2 - 2.10 [TEST]

Posted: Mon Oct 26, 2015 12:32 pm
by acc24ex
.. oh yeah, I edited it - max 2016 .. don't have this kernel on 2015 so didnt test

- and it happenes in slate material editor sometimes.. really though it was because of corona, maybe there's something else with my max - so if anyone runs into this might as well be a bug..