OTOY Forums

Hey All,

just downloaded the newest demo for 3dsmax but it behaves strange.

When I open the OctaneRender viewport to see the scene, it only shows a very raw rendering.
The viewport seems to stop refreshing the renderiterations right from the start.

When I hit the "pause" button or change the tonemapping "camerafilters" I can see that the render is improving over time really quickly (just as it did with the older demo) - but if I don't force the viewport to refresh with these "actions" I only see a very rough rendering. All the stats in the top are also frozen until I "force refresh".

System details:

demo 2.17
win 7 x64
3dsmax 2011 x64
Geforce Titan
i7 3770k

hope you guys can help.

What is your maxsamples set to in the kernel settings?
Maybe it's set low and the rendering is actually finishing.

I didn't change anything so it's the default value. 16000?

And it doesn't hit the max because I can see the render has improved once I hit the "pause" button or do anything else that forces the renderview to refresh.

The stats show 0 seconds, 0 iterations etc. all the time - unless I force it to refresh.

I could make a video-screencapture if you don't really understand what I mean.


Maybe I should also try it on a different computer. Could it be that there are problems with the older demo? Or some other plugins that I have installed?

It pretty much completely destroys octane - since it's taking away the most important feature of the workflow.

Hi,

Thanks for the video you have sent through to the support mailbox.
Now that I have clearly seen this, it looks like it's definitely an issue with 3ds max 2011 and the recent plugin version. (Rather than just a problem with the demo version).

Usually we only support the latest and two releases back eg: 2016, 2015 and 2014. Sometimes the API changes too much for us to continue supporting older versions of the host application.

So, it looks like this is a bug and I don't think we will be fixing this sorry. We will most likely be dropping support for 3ds max 2011 soon.

I would recommend you hold off purchasing until you have a later release of 3ds max - I know it can sometimes be a pain and costly to update, but it's also very hard for us to keep supporting so many different versions so we need to draw the line somewhere.

Thanks
Chris.

thank you for your reply.

That is very sad news.

Would it be possible to purchase the Octane 2.X plugin and use/install the old 1.25 version?

Yes, the 2.x licenses are backwards compatible with any version of octane, and the release posts are never removed from the forum.
So current licenses will work with this version: http://render.otoy.com/forum/viewtopic.php?f=27&t=37853

Or any of the later releases found here: http://render.otoy.com/forum/viewforum.php?f=80
Or other old ones posted here: http://render.otoy.com/forum/viewforum.php?f=27

hey FooZe,

thank you for the info.

I don't really understand why. But first installing any version except for the oldest one didn't work.

Now after retrying a couple of weeks later, even the newest version of the 3dsmax plugin works just fine. Even the aforementioned bug isn't there anymore.

Either way. I am glad I bought the license. This renderer is amazing. Thank you for your help.

Hey,

not really sure if you are still interested in this bug but I probably found a reason:

If I change my viewport driver to DX10 the octane viewport does not update render iterations as I explained above.

Switching the viewport driver to DX9 or OpenGL makes the OctaneViewport work just fine.


Maybe you can make use of this info somehow. Please do not drop 3dsmax2011 support.
Thank you!
alex