Cinema4D version 2020.1-RC4 (ReleaseCandidate) 21.04.2020

[aoktar]

Did you make all tests for every cases? You don't know back processes about the renderer and plugin for image storage and processing, even I don't know the renderer side. So I can't claim that's a bug or problem.

I didn't, I don't, and why should I?

On the other hand I did show you pictures in the 2019-thread: Pick a texture > put it in an "image texture" node > look at the Octane Texture Mangager's Vram column.
Now change the (RGB) texture's type to float and, according to the Octane Texture Manager, nothing changes regarding the Vram.
"Works" in v2019 and v2020.

So either the "Float" setting has no effect, or the Texture Manager ignores it. I would call that a bug, even without knowing "back processes about the renderer and plugin for image storage and processing". If it's not the plugin not processing the setting, but the underlying Standalone, just pass it on to the Standalone guys, please.

@kalua - That's where

If you relly to texture manager for this, do not that. It cannot know exact vram usage. Just using a rough formula, the renderer handles everything and plugin cannot know details. I think you didn't watch the video and render info for vram usage. For your request, it doesn't make any sense.

[zoppo]

If you relly to texture manager for this, do not that. It cannot know exact vram usage. Just using a rough formula, the renderer handles everything and plugin cannot know details. I think you didn't watch the video and render info for vram usage. For your request, it doesn't make any sense.

Yes, I did not see the video because I was on my mobile. So it's just the Octane Texture Manager that is not showing the correct values, good to know.

Although it is strange because this does work in 4.05 - I just tested it.

[aoktar]

If you relly to texture manager for this, do not that. It cannot know exact vram usage. Just using a rough formula, the renderer handles everything and plugin cannot know details. I think you didn't watch the video and render info for vram usage. For your request, it doesn't make any sense.

Yes, I did not see the video because I was on my mobile. So it's just the Octane Texture Manager that is not showing the correct values, good to know.

Although it is strange because this does work in 4.05 - I just tested it.

Renderer's internal functionality changed. It's much more complex now. We can't know the real vram usages because of it. At least I don't know ATM.

[colektor]

Work's really fine
The Motion blur + Xparticles work very good

Thanks lot !

[aoktar]

Work's really fine
The Motion blur + Xparticles work very good

Thanks lot !

Thanks for feedback! Let me know any issues

[Kalua]

If you relly to texture manager for this, do not that. It cannot know exact vram usage. Just using a rough formula, the renderer handles everything and plugin cannot know details. I think you didn't watch the video and render info for vram usage. For your request, it doesn't make any sense.

Yes, I did not see the video because I was on my mobile. So it's just the Octane Texture Manager that is not showing the correct values, good to know.

Although it is strange because this does work in 4.05 - I just tested it.

I have been playing with float and normal type with image textures, and althought the texture manager doesn't report changes, the live viewer will apparently give you some more accurate readings: the values floctuates as soon as you start playing with normal/float types.

[nejck]

If you relly to texture manager for this, do not that. It cannot know exact vram usage. Just using a rough formula, the renderer handles everything and plugin cannot know details. I think you didn't watch the video and render info for vram usage. For your request, it doesn't make any sense.

Yes, I did not see the video because I was on my mobile. So it's just the Octane Texture Manager that is not showing the correct values, good to know.

Although it is strange because this does work in 4.05 - I just tested it.

I have been playing with float and normal type with image textures, and althought the texture manager doesn't report changes, the live viewer will apparently give you some more accurate readings: the values floctuates as soon as you start playing with normal/float types.

If you guys want to quickly test if its working just plug in an 8k map in there and switch between normal and float. The difference should be noticeable

[oblivion]

excellent release, I think

I am only working on lighter scenes right now, but no crashes so far, even with RTX turned on. And its BLAZING fast...

I think this was mentioned somewhere before, but is there a difference between "Random walk" and "Randomwalk"?

[paypal-ict]

Will OpenColorIO be suported in the next version? Or will RC4 become the new Stable version?