Page 1 of 1

Problem with demo version

Posted: Fri Jan 28, 2011 6:53 pm
by Przytulanka
Hi, :)
I have a problem with importing mesh object into octane. WhenI have a lot of things in my scene, program just shuting down himself. When I tryied whit something smaller everything was ok. So I'm wondering, is there any sense in buying beta version, cause I don't have any sure that it want happend in the future.

Does anyone have the same problem?

And one more question... Beta Version is also a free standing program, or it can be use as a plugin, for example in Sketchup?

Re: Problem with demo version

Posted: Fri Jan 28, 2011 7:31 pm
by matej
It's not Octane's fault, you are probably running out of memory on your graphic card.

Scenes with big amounts of geometry need also a considerable amount of VRAM. What graphic card do you have?

Re: Problem with demo version

Posted: Fri Jan 28, 2011 8:06 pm
by Przytulanka
I have GeForce 285 1GB.

I've rendered the same scene in V-ray plugin in Sketchup, and there was written :
Beginning render sequence
Preparing renderer...
Preparing scene for rendering.
[RenderView] startCameraTime=0.000000, endCameraTime=0.033333
[RenderView] numCameraTMs=2, numFrames=1, frameSamples=2
Initializing built-in VFB.
[RenderView] startCameraTime=0.000000, endCameraTime=0.033333
[RenderView] numCameraTMs=2, numFrames=1, frameSamples=2
Starting DR
Using 0 hosts for distributed rendering.
Preparing camera sampler.
Preparing scene for frame.
MtlMulti (noname) "mtls" parameter is deprecated; use "mtls_list" and "ids_list" instead.
MtlMulti (noname) "mtls" parameter is deprecated; use "mtls_list" and "ids_list" instead.
MtlMulti (noname) "mtls" parameter is deprecated; use "mtls_list" and "ids_list" instead.
MtlMulti (noname) "mtls" parameter is deprecated; use "mtls_list" and "ids_list" instead.
MtlMulti (noname) "mtls" parameter is deprecated; use "mtls_list" and "ids_list" instead.
MtlMulti (noname) "mtls" parameter is deprecated; use "mtls_list" and "ids_list" instead.
MtlMulti (noname) "mtls" parameter is deprecated; use "mtls_list" and "ids_list" instead.
MtlMulti (noname) "mtls" parameter is deprecated; use "mtls_list" and "ids_list" instead.
MtlMulti (noname) "mtls" parameter is deprecated; use "mtls_list" and "ids_list" instead.
Compiling geometry.
Preparing ray server.
Creating and initializing 4 thread(s).
Allocating memory for build data of 257907 faces (7221396 bytes, 6.9 MB).
Initializing face build data.
Creating 'done' event.
Starting first thread.
Waiting for thread completion.
Releasing thread resources.
Preparing faces for intersection tests.
SDTree statistics:
Total number of faces stored: 257907
Max tree depth: 43
Average tree depth: 26.4071
Number of tree nodes: 47313
Number of tree faces: 651238
Number of tree leafs: 20254
Average faces/leaf: 32.1535
Memory usage: 15.87 MB
Scene bounding box is [32735.5,-214389,-711.772]-[253232,1276.32,336339]
Scene bounding box is too large, possible raycast errors.
Preparing direct light manager.
Preparing global light manager.
Irradiance sample size is 84 bytes
Photon size is 56 bytes.
Light cache sample size is 120 bytes.
1 interpolation maps registered
Rendering interpolation maps with minRate=-3 and maxRate=0

So how much memory I should have? :)

And, about second part of my first post... In Features there is that
Octane Render (Commercial Version) includes free plugins for:

Autodesk 3D Studio Max
Autodesk Maya
Autodesk Softimage XSI
Blender
Maxon Cinema 4D
Sketchup
Modo

Does Beta Version that is available now inculde the same plugins?

Re: Problem with demo version

Posted: Fri Jan 28, 2011 8:58 pm
by matej
Well, 1 GB is enough for small & medium scenes. Strip down the problematic scene a little until you can render it, and see what is the memory usage in Octane (File -> Device manager). You must take into account also textures, HDRI, film size... You also can't compare memory usage with other programs like that.

Octane has exporter plugins for all major 3D packages (sketchup included), which are available only to licensed users.

Re: Problem with demo version

Posted: Fri Jan 28, 2011 10:27 pm
by Przytulanka
Thank you for help. :) I will join to licenced users soon. :)

Re: Problem with demo version

Posted: Sat Jan 29, 2011 12:46 pm
by Przytulanka
"Strip down the problematic scene a little until you can render it, and see what is the memory usage in Octane (File -> Device manager)".

I've tried, and now I'm sure that this problem is Octane error. At the end I creat simple box - 6 faces and only one material - and Octane did not open even this object. It can't be probem whit not enough memory, because earlier I've opened bigger scene and everythings was ok.

I tried to reinstaled Octane, but this problem still exist.

What can I do?

Re: Problem with demo version

Posted: Sat Jan 29, 2011 1:02 pm
by matej
What's your system specification (OS, driver versions, etc...)? - write it down in your signature, to prevent redundant questions

What does Octane say? in console / GUI?

When does it happen - during voxelizing, image loading, etc...

Try the demo suite in the downloads section, to see if everything works with it. It might be a problem with your geometry (lone vertices or edges). Just a thought.

Re: Problem with demo version

Posted: Sat Jan 29, 2011 9:18 pm
by Przytulanka
It is happenig while Octane says "Compiling mesh... Voxelizing". Than program start not answered, and I can't do anything. I can only close it.

I've already seen those tutorials, and I have now idea what can be wrong. This object file contents only one box - 6 faces, it can't be something wrong in geometry.

Re: Problem with demo version

Posted: Sat Jan 29, 2011 9:31 pm
by matej
Maybe the problem is how you export the .obj from sketchup? Try to play with export settings, to easier pinpoint why some scenes work and some don't. You can also post here a scene that doesn't work, and we will have a look. (ziped with everything)

I don't know sketchup, but hopefully someone with sketchup experience will post some advices for exporting.