OTOY Forums

poison wrote:Ahmet good evening, what i meant is:
AB comparison seems not to work.
It does not show the divider line in the center, (like it should) also when image is added to store buffer, store buffer does not keep any new image, the store number increases, the the image is the one that is currently being rendered in all buffers.

For what it's worth, Ahmet, I just tried R6 and noticed the same thing. The list of frames in the pulldown increments with each Store Render Buffer, but the frames are not viewable and renaming them does not update the pulldown list, although if you go back to the Rename dialog it has stored the new name. There is also no A/B comparison slider.
This is in C4D R21, Mac OS 10.13.6

frankmci wrote:

poison wrote:Ahmet good evening, what i meant is:
AB comparison seems not to work.
It does not show the divider line in the center, (like it should) also when image is added to store buffer, store buffer does not keep any new image, the store number increases, the the image is the one that is currently being rendered in all buffers.

For what it's worth, Ahment, I just tried R6 and noticed the same thing. The list of frames in the pulldown increments with each Store Render Buffer, but the frames are not viewable and renaming them does not update the pulldown list, although if you go back to the Rename dialog it has stored the new name. There is also no A/B comparison slider.
This is in C4D R21, Mac OS 10.13.6

I have also noticed: the comparison feature doesn't work very well, sometimes it divides, others it doesn't. Sometimes the division slides and then disappears... things like that.
Thanks for the hard work, Aoktar.

Am I the only one noticing that with R6 C4D doesn't properly save crashes any more? Every other crash causes the C4D so save that file under the typicaly bugreports folder but that file can't be opened anymore due to an "out of memory" error reported by C4D. What I'm noticing is that every corrupt file that is typically under 1mb in size - even if the original scene was 100mb.

Never had these issues with the early 2020.1 releases.

I get constant crashes when working in live viewer. As soon as i move something around it crashes.

CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to download symbol(stats data)
device 2: path tracing kernel failed
CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to wait for event
device 0: path tracing kernel failed
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to launch kernel(kernel54)
device 1: failed to update AI light
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to copy memory to device.
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to clear linear device memory
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to clear linear device memory
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to clear linear device memory
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 1: path tracing kernel failed

This was also the case on R5 and R6 and i had hope that it will be gone in the next release. Drivers are the newest studio drivers and were completely reinstalled a couple days ago (with clean uninstall etc).

It is not a heavy scene and i do not have those issues in redshift at all. Any idea how to fix this?

Thanks

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!

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.

aoktar wrote: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.

Sadly, that's the way it seems to mostly work; western culture is quick to complain, slow to compliment. At least here in the Otoy forum, though, with the exeptions of those few people who just obviously like to complain, I think you can take it mostly as attempts to give helpful feedback. That's certainly the case when I point out issues I've noticed.

I think I've said it elsewhere, Ahmet, but the node editor additions have been great. There are still some rough spots, but it has been a big improvement, and is much appreciated. Multiple frame buffer comparisons are going to be super helpful, too. As someone else said, a huge amount of Otoy's and Octane's success is based on C4D, and that responsability rests squarely on your shoulders. The fact that you even participate directly in these forums is a rare and special thing that I don't think many users understand or appreciate. You are incredibly responsive at fixing many issues and getting them out to the users in a very short time. I don't know how you do it, and I hope you are very well compensated.

Also, whoever decided to hire Jay Roth to join OTOY and contribute support on the forum, buy that person a beer every Friday afternoon for life!

You are far too kind, Frank And you're right: Ahmet is amazing and extremely dedicated!

aoktar wrote:
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.

My experience with the c4d plugin and octane in general is great. Don't get me wrong when i try to find out why i can't get it to be stable, at least while working with the ipr. I have had these issues a while back when reverting from e.g. R7 to R5 fixed the crashes. Thats why i adressed this here.
You do a great job Ahmet and i said that before. Really. I love how octane is integrated inside c4d as much as i loved it in LightWave. Its fast und comfortable to use. I love octane and i love your plugin.

Don't suppose that I wish some appreciation, just want to hear some user feedback for the latest improvements and talk about how it goes. I wish to make it just works! Thanks for all!