OctaneRender™ Standalone v1.0 RC 2 (obsolete)

[enricocerica]

Hi,

I'm working with a huge scene, lot of meshes and many nodes.
I also manage to have several geometry groups for diffrent situations and also different configurations in the preview configuration corresponding to diffrent views (cameras) and environment to quickely switch from one situation to another.

The loaded meshes size is about 1.5Gb and Octane process takes about 13Gb (out of 16Gb) of the ram

Octane is very unstable and if often crashes when swithching from one camera to another, after changing environment or simply when I select another geometry group. Even if I first stop the rendering it crashes and I need to restart Octane very often. Considering that the scene loading takes about 10 min, it's very annoying.

Any suggestion to avoid that ?

Thanks

[smicha]

Hi,

I'm working with a huge scene, lot of meshes and many nodes.
I also manage to have several geometry groups for diffrent situations and also different configurations in the preview configuration corresponding to diffrent views (cameras) and environment to quickely switch from one situation to another.

The loaded meshes size is about 1.5Gb and Octane process takes about 13Gb (out of 16Gb) of the ram

Octane is very unstable and if often crashes when swithching from one camera to another, after changing environment or simply when I select another geometry group. Even if I first stop the rendering it crashes and I need to restart Octane very often. Considering that the scene loading takes about 10 min, it's very annoying.

Any suggestion to avoid that ?

Thanks

Try to increase voltage on your GTX 580 3GB.

[jmfowler]

Well, I have finally found some time to open the new RC2 release :

I opened the exact same scene I am currently working on, without moving the camera, without touching anything, and I notice that RC2 is slower.

I have only tested with Pathtracing, as it is the current setting in my scene, and the speed has fallen from 1.36 Ms/sec with RC1 to 1.18 Ms/sec with RC2.

Second VERY BAD surprise, is that this versions is very memory consuming !

For the exact same scene, RC2 uses 1867.3 MB versus 1759.6 MB with RC1 !

107.7 MB lost ! Thats really annoying. I am optimizing everything I can, and just because of an update, I loose more than 100MB of precious memory space !

What happened with memory management ?

You can verify the values in the Proof screen shots :

edited - nvm.

[abstrax]

Well, I have finally found some time to open the new RC2 release :

I opened the exact same scene I am currently working on, without moving the camera, without touching anything, and I notice that RC2 is slower.

I have only tested with Pathtracing, as it is the current setting in my scene, and the speed has fallen from 1.36 Ms/sec with RC1 to 1.18 Ms/sec with RC2.

Second VERY BAD surprise, is that this versions is very memory consuming !

For the exact same scene, RC2 uses 1867.3 MB versus 1759.6 MB with RC1 !

107.7 MB lost ! Thats really annoying. I am optimizing everything I can, and just because of an update, I loose more than 100MB of precious memory space !

What happened with memory management ?

You can verify the values in the Proof screen shots :

The problem is that we are trying to make the ray-tracing more robust, to sort out those issues reported during the last weeks (that triangles are not rendered or that there are visible gaps between triangles). These are all numerical issues which require us to add some margins. Adding margins can have an affect on the size of the acceleration structure and ray-tracing performance.

Could you send the scene to us? Feel free to strip it down as much as you want, as long as it shows your problems (more memory usage and less performance). We can then investigate those issues.

Cheers,
Marcus

[treddie]

Octane remembers folders now after quitting and restarting! Thank you Octane render team!!!

[ROUBAL]

@Marcus : As always, my scene is huge : more than 1.8 GB in Octane. I can simplify it, but as I think that the extra memory amount will be probably a percentage of the whole amount, it may not be noticeable on small scene, and obviously, it is on big scenes that saving memory is important !

I will see what I can do, but I will have very few time in the next days.

[ROUBAL]

EDIT :

@Marcus :

No need to upload a big scene :

In order to help you reproduce the trouble, I have done a quick test with Octane template scene "Hallway" , with the default settings (Direct Light kernel), and the two screen shots below show that even on a small scene, the amount of memory used by RC2 is bigger :

48.9 MB versus 48.3 MB with RC1 : 1.22% on this small template scene but the percentage of lost memory is 5.76% on my current big (and growing) London city scene.

The render time on this scene with Direct Lighting is 36.30 Ms/sec with RC1 versus 36.55 Ms/sec with RC2, and when using pathtracing, 4.70 Ms/sec with RC1, versus 4.72 Ms/sec with RC2.

The main problem is memory consumption, because even if it is a small percentage, with huge scenes it means more than 100 MB, in an area where every MB counts to avoid entering in the swap process on machines with 8GB of RAM, and get huge loading times ! Or simply being short of VRAM to host the scene !

In my current scenes, I have deleted many textures to gain few megabytes, and I loose 107MB with the RC2 update ! It is painful !

[convergen]

Hi There,

Just was wondering what the future of the RIB import function will be? has it been scrapped? is there an alternative that is in the works?... seeing as it was a initial feature that has now disappeared from the features page of octane render.

[Synthercat]

TO ROUBAL :

I know it's a little of topic but I saw your London scene and can't help but wonder... what do you do to use an object of show many materials on another scene?

I PLEAD FOR LOCAL DB...

What is YOUR way to do it? I mean say you want to use that same bus on another scene... you have to
1) Export all mat nodes connected to the bus from the London scene
2) Load new scene
3) Import all those nodes
4) Connect the right node to the right mat-slot?

I don't have time for that!!! I NEED LOCAL DB To do it automatically for me

[A2Zen]

I can open 2 windows of OCTANE, one for original another for new scene...
select multiple nodes that I want from original... then Ctrl+C
go to another window of OCTANE for a new scene and Ctrl+V
....