OTOY Forums

For what is worth I am extremely excited about the features you've implemented in the 2020 time period. The LiveViewer speed up on high res outputs is amazing and it doesn't only make everything easier to use but it also adds new workflows. Because its so much faster now I sometimes up the resolution ratio in the LV to "zoom in" on certain areas to fine tune them. It's a really welcome addition (sort of like real zoom in FStorm)!

I also really like the material multithreading (could be more stable though? It can cause issues...) and the new "extra" node creation workflow... Along with a bunch of other stuff. I suppose I'd still welcome that copy button though

All in all, really awesome job Ahmet! Thank you for all your hardwork!

aoktar wrote:

stuz0r wrote:It's very possible that this was already addressed.

There seems to be that jagged / stepping issue with displacement maps in this version. I reverted back to 2020.1 RC4 and the displacement stepping / jagged issue is not there. Just wanted to give you heads up.

Thanks for all your hard work man!

Sorry give an example scene. I don't think there's a revision for this.


Very strange, all you guys just talking about problems. There's lot of improvements and fixes, would it be great to hear some words about experiences. Otherwise, you're making me think that doing these for just for me.

@ fibernaut, It's not plugin related. Remove all other plugins for testing and close other programs while working.

Ahmet, ur doing an excellent job on the plugin. U are the reason i switched from 10 years of vray to octane
All new features are excellent btw, trying stuff as we speak.

People dont have bad intentions, they just wanna help out in fixing stuff or ask features and make the plugin even better than it is.
I think this is the purpose of posting in forums, cause other than that everyone really appreciates ur effort and the hard work u put in, thats a fact.

Cheers!

thanulee wrote:Ahmet, ur doing an excellent job on the plugin. U are the reason i switched from 10 years of vray to octane
All new features are excellent btw, trying stuff as we speak.

People dont have bad intentions, they just wanna help out in fixing stuff or ask features and make the plugin even better than it is.
I think this is the purpose of posting in forums, cause other than that everyone really appreciates ur effort and the hard work u put in, thats a fact.

Cheers!

Many thanks! Sure forum is for any kind of feedback and for solving the problems to help the community.

thanulee wrote:Ahmet, ur doing an excellent job on the plugin. U are the reason i switched from 10 years of vray to octane
All new features are excellent btw, trying stuff as we speak.

People dont have bad intentions, they just wanna help out in fixing stuff or ask features and make the plugin even better than it is.
I think this is the purpose of posting in forums, cause other than that everyone really appreciates ur effort and the hard work u put in, thats a fact.

Cheers!

Well, welcome, I immediately advise you to set up backup of your scenes in cinema.

Dear Ahmet

thanks for the Release R6, seems in many ways faster and good...but I have serious problems with the compression of texture. Apparently you worked on this.
Assigning multiples textures a compression does not work, I have to click as many times as textures are selected.
Multicore cpus are not running crazy which is good! Unfortunately rendering does not work, device memory runs crazy... I could not start any rendering....
please have a closer look on this part again.

Thanks in advance for your help.

kind rregards from cologne

Martin

martinzip wrote:Dear Ahmet

thanks for the Release R6, seems in many ways faster and good...but I have serious problems with the compression of texture. Apparently you worked on this.
Assigning multiples textures a compression does not work, I have to click as many times as textures are selected.
Multicore cpus are not running crazy which is good! Unfortunately rendering does not work, device memory runs crazy... I could not start any rendering....
please have a closer look on this part again.

Thanks in advance for your help.

kind rregards from cologne

Martin

What you are doing exactly? I don't see problems like these and what I changed that's for avoiding for similar behavior. In fact you can't assign different compression for same file names in a scene.

stuz0r wrote:It's very possible that this was already addressed.

There seems to be that jagged / stepping issue with displacement maps in this version. I reverted back to 2020.1 RC4 and the displacement stepping / jagged issue is not there. Just wanted to give you heads up.

Thanks for all your hard work man!

Share a sample with me please

divasoft wrote:Well, welcome, I immediately advise you to set up backup of your scenes in cinema.

As you should certainly be doing in any 3D app for the last 30 years. I suggest auto incremental saves every 15 minutes and keep the last several hours worth. Crashes happen. It's the nature of the beast. This is not text editing.

aoktar wrote:Updated to new build(R7)

stuz0r wrote:It's very possible that this was already addressed.

There seems to be that jagged / stepping issue with displacement maps in this version. I reverted back to 2020.1 RC4 and the displacement stepping / jagged issue is not there. Just wanted to give you heads up.

Thanks for all your hard work man!

Share a sample with me please

I shared 2 images above that show how it handles displacement in different ways. Do you want me to share c4d file?