OTOY Forums

Hi Haze,
Honestly, I do personally see an increasing focus on improvement in 3dsmax development. Thanks for that.
But late bugs that weren't there at all are really bugging. Like no textures in viewport.
I kind of support not releasing test versions. But hotfixes are meant for the immediate bugs to keep using the updated beta. Please continue doing so..

Not keen on creating a debate here and no need to answer me...

Obviously, can't know much about your internal tracking system there.
But IMO consequently changing developers left us in a purgatory like state where we do not know what is next on your list and we have no idea.
I would really would love to see what on the shortlist of updates. Why not do it open for licenced users. We dont mean harm to the renderer.

For me max development got a big hit before v3 release and still feel it effects. Hence the need for roadmap questions.
A promise of secret surprise feature for max & maya and turned out to be Octane engine or Octane cloud what ever you call it. I guess there is no more mention of a need for Octane Engine in max , don't see in menus, maybe it's not needed that much at all.. Rendering in server station and display the render in say ipad..
And octane cloud which I think only a handful of people might use it. Also maybe my cheap system is not bad at all with 8gbx4 gpu's. But octane cloud is very slow. And people have much better systems nowadays.
And we had no new features for that big amount of time. And we still have major bugs to deal with.

Correct if I'm wrong but v1.9 material conversion was thankfully solved maybe after a year.

Sad to see about all the secrecy. You had sort of an army of users devoted to report bugs. Maybe some with harsh inputs as well I must admit.
But nowadays I see only few people still continuing reporting bugs.

I personally thank heavens for octane having one time payment system. I have continued projects for years founded on and continuing on Octane for max architecture.
I would have to reconsider if it was montly payment..

Longstory short I believe paid max users did the best they can starting from v1. And I personally think you (company) should be grateful for this and find a way to integrate more (meaningful) users input on the plugin development. (users being those who uses latest builds on actual projects)

I truly hope we'll see more robust and solid updates in the future and more plugin specific features be added to the plugin apart from core engine updates.
Best,

+

I agree with Oguzbir.

To chime in also. And again this is by no means meant harshly, just honestly as my opinion. I paid for V3 but quickly switched back to V2.

I read you thoughts Oguzbir but I think the problem does not lie soley with the 3DSMAX plugin but with the core of V3. Which is why little seems to be done about it.

All other renderers get more efficient over time, octane is proving the opposite to this rule. Whatever you did to the core in V3, everything is worse now. Not only is VRAM consumed more, but also moving more processes over to the CPU has increased amounts of computer Ram too, super long evaluation times, more bugs than ever; and on top of that basic scenes are slower to render unless you use the parallel samples (and take up even more VRAM than the already increased VRAM). My computer literally comes to a standstill when I try to load scenes in V3 that I used in V2. The reason I don't report bugs now is because V3 in my opinion is completely unusable. I cant even get the majority of my scenes to load.

I did report a bug where my scene in V1 of octane took 1.5GB Ram, but would not load in v3 because it was taking over 6GB RAM. I was told by Abstrax that this is not a bug and this due to the way the core works now, large meshes take up much more VRAM. That's a huge increase to me, and makes what I'm trying to do very hard. Scenes which I could load fine in V2 now sit 'evaluating' for so long that I just give up. So where is the incentive for me to continue? if I, as a single user am hitting the limits of this renderer for my short film, how is this ever going to be adopted by bigger productions using far more polys and complex scenes than I?

Now I know things are harder with GPU renderers, but others such as redshift, furryball and Fstorm are not finding that adding features is breaking the core. I love the render layer system, it's one of the best features about octane and was well worth upgrading for in V2, but when you tout 'a new rewritten core' as one of the main reasons to upgrade to V3 - well that's not really a feature, especially when that new core is much more hungry for RAM, CPU, and is slower to perform. There was a long wait between 2 and 3 and the only user feature worth upgrading for me was volumetrics, but the core seems flawed now.

It's sad because I was so excited about V1 and where octane was heading, you might even need to take a few steps backwards before you can move forwards, but I really believe you are heading in the wrong direction. Even I can see the user base dropping off this forum as I'm sure most don't say anything but just stop using it.

Fortunately I can still manage with V2, and it works quite well for what I need (apart from misaligned shadow passes), but with it being an old version it seems I wont get a fix for that specific problem and so I am on the look out for another renderer, which really pains me to say as I've LOVED using octane over the past 3 years. Seriously octane changed the way I worked I think at it's heart its a great little renderer that seems to have been been through developer after developer, all of whom have had their own idea of how to code it. V2 we were told was a rewrite of V1 core, and now V3 is a rewrite of v2 core, but it seems, for the worse.

So here's really hoping I'm wrong and it'll all come together in a few months with bug fixes and patches, but my gut tells me this is a deeper problem with the renderer.

Please! make the integration of 2.26 Pascal, my projects all stand still, render 3.0 the animation is very long

bug stayed with the environment
https://cloud.mail.ru/public/KfDe/c9e8HMJTT

shot compilation = 48 seconds Оо
render = 3 seconds
https://cloud.mail.ru/public/Ks96/jX1BVvyyE

10 releases and has still not corrected render the animation! the wind does not work
make it possible to render the animation octane viewport !!!!
https://cloud.mail.ru/public/Hqo3/emxMjm8gg video
how it was possible so ditch octane, slow, buggy, junk, buggy camera animation is not working (( Cameras vanish in viewport
octane 1 -2 I'm not nervous, version 3 is just nerves!

plants with wind, ( standard camera, Pascal 1080, standard frame buffer 3ds max )

OrangeTree.rar
https://cloud.mail.ru/public/8Trt/TM1yNBY8z
Palm.rar
https://cloud.mail.ru/public/GsSx/ssfevyK3s

Finally fix the problems with the animation

Elvis - architectural visualization ===== do you know where you should look render .... got a tea pot of render ..... I hope this is your last scream
(((( greatly exaggerate ))))
.......................



I also hope that everything will change after this post

....
and we will shut up and will only say thank you very much for the new version of the render .... !!!!