OctaneRender™ Standalone 1.10

[kavorka]

can you post export/import times of a scene normal and one using the RAM disk?
I'm curious how much faster it is.

[mauricesteenbergen]

can you post export/import times of a scene normal and one using the RAM disk?
I'm curious how much faster it is.

It's really difficult to time such a thing, I really suggest you try yourself.
The tutorial on RAM disks state that they are way faster than harddisks or SSD.

[andw]

Wait, how does this work? It speeds up import time? If this is true, i need to try it to speed up my animations. import/export is 30 sec a frame right now...

RAM Disk created entirely by software (there are many programs, free and commercial, that do it), occupying desired amount of RAM (I've found 4 Gb is optimal value) and presents in system as typical disk partition with its own letter and certain file system (I prefer to use FAT32). After system start-up, the drive is empty (but you can setup it to save its contents when system is shutting down).
I primarily use Poser for scenes composing, and use Python script, which export current scene in OBJ file and collect all textures into one location - folder on RAM Disk. After export (which speed is only limited by one core of CPU) I use Octane to (re)load mesh/open ocs, which also executes incredible fast, bottleneck is only one core of CPU (so I wait for multi-thread OBJ processing ).
Another suggestion: set your program's temp directory to RAM Drive... it's also speeds up program's response.

P.S. On attached image I've compared transfer speed of modern HDD, SSD and RAM Disk. See the difference

[kavorka]

Not sure if I am doing this right, but I put the Octane program directory in my RAM Disk. I then put the folder with all my scene files (including .Obj and image files) into the RAM disk.

I am using Blender. I point my export path to my new RAM Disk partition. I modify my scene so the images are loaded from my RAM Disk directory.
I am testing this with an animation, I want to get my export/import times lower (currently 30 sec on this scene). After testing a couple of frames, I have absolutely no change in export/import speeds.

Has anyone tested this and did timed comparisons? Does it just not help, or am I doing this wrong?

[petermax]

Re animation the single biggest issue is updating the geometry, say you're doing a test, the actual render takes only a few secs to get a simple preview, but the geom update takes 30 secs that means what should only take half an hour, now takes 5-6 hours, for a simple test animation render!!!

I'm using the max plugin all materials are kept in ram, so only the geometry is refreshed, so it must be the voxelization that's the issue, please correct me if I'm wrong?

The most annoying part is, the render is super fast, the materials are in RAM and then the voxelization occurs, there's just one core of 8 chugging along at snails pace!! Why? Why are we still using one thread, when literally every computer is multi core these days??

[itou31]

Hello,

I have a crash problem when I select a node (right click) and select "show in graph editor". It happens in node inspector or outliner.
I also tested it with the v 1.05 and octane crash too.
Someone has this issue (in windows) ?

[roeland]

Hello,

I have a crash problem when I select a node (right click) and select "show in graph editor". It happens in node inspector or outliner.
I also tested it with the v 1.05 and octane crash too.
Someone has this issue (in windows) ?

Does this happen with specific nodes, or with all nodes? We can't reproduce this crash here.

--
Roeland

[PeterCGS]

Well then after that there's SSD.... ~275mb/s for SATA2 and ~550 mb/s for SATA3 effectively.

I use RAM Drive (4Gb space is enough in most cases) for OBJ file and textures placement... so there is no more I/O bottleneck Typical transfer rate is about 6..7 Gb/s... and without any wearing out

Thank you for this tip! Im amazed I've never thought about this for Octane... Its an old trick I used on my old Amiga, but it was soooo long ago

/Regards Peter K

[itou31]

Hello,

I have a crash problem when I select a node (right click) and select "show in graph editor". It happens in node inspector or outliner.
I also tested it with the v 1.05 and octane crash too.
Someone has this issue (in windows) ?

Does this happen with specific nodes, or with all nodes? We can't reproduce this crash here.

--
Roeland

It happens to all nodes.
(windows 8 x64)
Checked with several mesh (obj).

[merid888]

hi roeland in my case i can't use the black body emiter, if i put 100 or 50 or 10 or 1 value in emisor is the same result with out light in the object, maybe is a bug of stand alone version ?