OctaneRender™ Standalone 3.00 alpha 7

[enricocerica]

When out of core is enabled, the video memory used for the scenes increased significantly, lot of my scenes cannot fit anymore in the video memory.
Edit : Well it doesn't seem to have to do with the out of core, today (with out of core deactivated) I loaded a scene and the video memory usage was 2946Mb, I closed the application, restarted it again and after reloading the scene the memory used was 1306Mb ... very strange.

Impossible to reduce width and height of fixed panes under a given size, previously it was possible to reduce them to quite nothing.

[stratified]

Hi and thanks for the update.
Since one of the beta versions I have no native window mode in Octane, cant minimize or close with X for example.
I tried to delete Preference file but does not help.

Opensuse Leap 42.1 x86_64
Intel i5 3570K
RAM 16 GB
GTX 760 4 GB /Display card
GTX 670 2 GB
Driver 361.42

Octane 3.0 Alpha 7

Thanks, mib

Interesting, there's actually no window border at all. This is how it looks on my laptop using Gnome:

It should work on KDE as well. What desktop environment are you using?

Can you tell me the exact alpha version that this started to happen? Maybe that will give us some clues.

thanks,
Thomas

[mib2berlin]

Hi, it seams it start with Alpha 1 (checked).
I use KDE 5 Plasma 5.5.5-17.1, tested with compositor OpenGL and Xrender
If I use icewm the border is back so it is more on my side with Plasma 5 desktop.
May you can look in to because I mostly miss moving Octane window between different displays.

Cheers, mib

[kommando_2k]

Fume FX vdb tested. its working now! Thank you!

[gardeler]

Fume FX vdb tested. its working now! Thank you!

It does not work here? What OS are you using? I used win 7, and tried this file:

viewtopic.php?f=33&t=52927&start=20

Pleas fix this.

[kommando_2k]

ahh.. gardeler, Go to preferences, make sure tick on "Edit setting before loading new geometry" in Import Tab , once you load the volume geometry, they will pop up "Import setting" and you figure out the grid setting.

[gardeler]

ahh.. gardeler, Go to preferences, make sure tick on "Edit setting before loading new geometry" in Import Tab , once you load the volume geometry, they will pop up "Import setting" and you figure out the grid setting.

Yup, that did the trick! Should not give a read error though. Just pop up and ask for the correct channels.

And now, lets play.

[itou31]

When out of core is enabled, the video memory used for the scenes increased significantly, lot of my scenes cannot fit anymore in the video memory.
Edit : Well it doesn't seem to have to do with the out of core, today (with out of core deactivated) I loaded a scene and the video memory usage was 2946Mb, I closed the application, restarted it again and after reloading the scene the memory used was 1306Mb ... very strange.

Same behaviour on my side. OK with PMC, but when swicth to PathTracing, the memory increase a lot.
When restart the application, it seems OK. But if you start another version and then restart back to alpha 7, same memory issue on DL or PT kernel.

[grimm]

Hi and thanks for the update.
Since one of the beta versions I have no native window mode in Octane, cant minimize or close with X for example.
I tried to delete Preference file but does not help.

Opensuse Leap 42.1 x86_64
Intel i5 3570K
RAM 16 GB
GTX 760 4 GB /Display card
GTX 670 2 GB
Driver 361.42

Octane 3.0 Alpha 7

Thanks, mib

Interesting, there's actually no window border at all. This is how it looks on my laptop using Gnome:

octane_gnome.png

It should work on KDE as well. What desktop environment are you using?

Can you tell me the exact alpha version that this started to happen? Maybe that will give us some clues.

thanks,
Thomas

Hi mib, Thomas, I don't have that issue with my system. Linux Mint 17.3 running cinnamon.

[abstrax]

When out of core is enabled, the video memory used for the scenes increased significantly, lot of my scenes cannot fit anymore in the video memory.
Edit : Well it doesn't seem to have to do with the out of core, today (with out of core deactivated) I loaded a scene and the video memory usage was 2946Mb, I closed the application, restarted it again and after reloading the scene the memory used was 1306Mb ... very strange.

This sounds like a GPU memory leak. Is there a way for us to reproduce the problem?