Oops

https://fstormrender.ru/fstorm-1-2-5/

Hi Paride,

unfortunately not. I left Octane when v3 came out and materials from v2 did not work anymore (or was it 2.something, don't remember). We had already converted hundreds of assets and projects that we need to revisit. By that time there was no autoamtic conversion available for a long time ...

paride4331 wrote: > 15.800.000 polys > GPU mem 3.85 GB 4554 objs time to voxel > 20 secs.
When Octane V4 will be released, I think there won't be much more for any of render engines.

Meanwhile the competition stays lightyears ahead. This is “another gpu renderer“ on the market:

suvakas wrote:How familiar you are with 3ds Max? Have you used it before?
I'm asking cause writing the plugin is not all about the tech and code, but you would need to understand the workflows also.

I'm also curious to know.

Are u using PMC? Or are the pool caustics also working with PT?

+1 for max plugin developer replacement

I think this is getting a bit harsh here. I can understand diappointment for business decision from our perspective.

If you run a big comapny like Otoy you may have an exit strategy to get bought by an even bigger company and live a good life. Like Radiance did it years ago. Old members may ...

https://render.otoy.com/forum/viewtopic.php?f=7&t=54969
Wow, one year after it was requested by the community Otoy is looking for one guy to help with Standalone development. They need at least 20 by looking at all this mess.
But all this is too late now, they screwed it up BIG TIME and they know ...

Having the same problem with 3ds Max - its not a gamma issue, the difference is too subtle but still noticable; the saved frame is missing a bit of contrast and color dynamic.

Regarding the converter, we have confirmed that direct conversion from 2.x to 3.x works (on another note, scenes done with a 2.25 plugin opens in v3 correctly as well). Eliminating edge cases remains a primary focus (as mentioned previously on the thread). Issues caused by certain texture file ...