Cinema4D version 2022.1-XB3-(R4) (Experimental) 23.09.22

[aoktar]

I mean that if you move slider to for example 23% value Octane Live Viewer shows value 22% until you release mouse button. After that it switch to 23% value. But we never see true value if mouse button is pressed. This is issue even with simple box scene any texture. This is mainly noticeable in Transform node when we want perfectly place or scale texture.

Interesting is that this bad behavior is only while using Octane Node editor with Edit Controls enabled. Using controls in different panel works fine.

We don't have a behavior with Octane sliders as you say. See video. Not sure what are you doing?

[SSmolak]

We don't have a behavior with Octane sliders as you say. See video. Not sure what are you doing?

The problem is using mouse over marked red text area while using the same outside Node Editor works mostly fine - without this mouse release lag.

Strange but using new clear scene I have this lag even on outside panel.

mouse_release_lag.zip

(1001.46 KiB) Downloaded 132 times

This is related to all Octane panels even in Scatter object too.

Sliders work fine, text area has lag :

slidersOK_textareaLAG.zip

(753.8 KiB) Downloaded 150 times

[aoktar]

@Smolak,
Probably you're not aware that they are not sliders. It's a text edit attached to slider, and all text GUI elements in C4D that are holding the refresh of the whole UI unless you release the mouse. You can see same behavior if you play with some geometry's parameters.

I'm aware of this kind of small problems since years, but there are not any solutions.

EDIT: you can use slider parts in out GUI element by holding ALT or use embedded GUI in nodes. They can send Redraw commands to avoid this problem. Because they are custom GUI done by me and we can do anything with custom GUIs.

[SSmolak]

EDIT: you can use slider parts in out GUI element by holding ALT or use embedded GUI in nodes. They can send Redraw commands to avoid this problem. Because they are custom GUI done by me and we can do anything with custom GUIs.

Thank you, it sound interesting I will try.

Yes this "feature" is very annoying especially when I had great looking clones using random seed but after release mouse button they are all messed up. It was very bad while I used Lightwave3D but I thought that in C4D it is better done.

But maybe solution is to add +1 value to each fields while moving mouse and reset it after release button ? After release mouse button it should stay at the same value ?

[aoktar]

When we have full stack of stored images there is need to remove last image before add next - if not it will be not stored correctly. It would be great for menu option like "remove all stored images".

It's just a refresh issue when stack is full(max=8 for now). Select another state then select last added. It will show. I'm gonna fix it

[SSmolak]

@Smolak,
Probably you're not aware that they are not sliders. It's a text edit attached to slider, and all text GUI elements in C4D that are holding the refresh of the whole UI unless you release the mouse. You can see same behavior if you play with some geometry's parameters.

But with some things this is Octane fault not C4D itself - for example UV mapping - if you move UV island ( in UV editor panel ) and release mouse button after that you will see that in UV window this island stay at the same position but in Octane LV it will move.

[fpajonk]

Is anyone else getting the "There is no CUDA device which is selected" nonsense on an M1 (Studio 32GB OS X Ventura) and knows how to solve this?

[bepeg4d]

Is anyone else getting the "There is no CUDA device which is selected" nonsense on an M1 (Studio 32GB OS X Ventura) and knows how to solve this?

Sorry maOS 13 Ventura is not supported yet.

You should need to go back to Monterey 12.5 to be able to install this version.

ciao,
Beppe

[fpajonk]

Sorry maOS 13 Ventura is not supported yet.

Why would switching from Monterey with Metal to Ventura with Metal make a plugin scream for CUDA. That doesn't make any sense.

[bepeg4d]

OctaneX 2022.1-XB3 is the first Metal version based on the same CUDA SDK, so the error message is the same.
We should have to replace the word CUDA with GPU, but the concept is the same, the GPU driver is not finding any valid GPU to work with.

ciao,
Beppe