OctaneRender® 1.0 beta2.52 >>> download here <<< [OBSOLETE]

[PeterCGS]

Can we expect 2.53 to be stable for animations? I've just tried 2.49-2.52 on three different systems (actually four, because I've used another users license aswell during the weekend just to test everything) and it randomly stops on all different scenes I've tried. All systems are Win 7 64x, with 460, 480(single and dual), 570 and 580GTX Geforce cards. It happens just after Octane saved down a image, and is closing down. It closes down but the process stays open in the task manager. It is very frustrating Im sooo spoiled with using Octane for every gig nowdays, and going back to 2.46 will be soo boring hehe

[ROUBAL]

@Marcus : I'm doing experiments : This time I have relinked exactly the same obj as the one used in the scene, and it restarted rendering normally at the end of the voxelizing process. Then I tried again with the scene with just a plane added and a small object removed (almost a cube : around 18 vertices), and Octane crashed.

I loaded directly the obj used to relink, and it opens fine. Then I started to redo all materials settings, and I tried to relink this time the original obj file : I got a crash as well (frozen).

I will try with a smaller scene asap.

If I remember well, the same problem occured before the 2.46. I believe that it occured with Cuda 3.2, but not with Cuda 3.0. Cuda 4.0 fixed it, and it appears now again...
I may be wrong, but maybe it has something to do with Cuda.

EDIT : @Marcus :

- I have thought about what could have changed since my last successful relink of an obj file in a very big scene. During the summer, I learnt Blender 2.59 and switched to it. So, my current scene project has been made in Blender 2.59 and the obj file currently loaded in Octane has been exported with the unofficial addon for Blender 2.59, instead of the former script for Blender 2.49b that I used previously in my huge "Blenderton Hotel" scene !

Maybe that the export addon for 2.59 makes something slightly different in the structure of the obj or mtl file, creating a trouble when relinking big files...

As I haven't used more than 16 materials per object (the limit in Blender 2.4x serie), my current Blend file should be still compatible with 2.49, and should open in it without damage. Tomorrow, I will open my current project in 2.49b, and export and obj. I will try to relink it to my current ocs created from an obj made with the addon for 2.59. If I get a crash, I will export an obj and mtl from the original file in 2.49. I'll load it ad edit it in Octane, and I'll export a modified version that I will try to relink. If it works fine, I think that the source of the problem will be identified as the exporter for 2.59.

I'll experiment tomorrow !

[abstrax]

Can we expect 2.53 to be stable for animations? I've just tried 2.49-2.52 on three different systems (actually four, because I've used another users license aswell during the weekend just to test everything) and it randomly stops on all different scenes I've tried. All systems are Win 7 64x, with 460, 480(single and dual), 570 and 580GTX Geforce cards. It happens just after Octane saved down a image, and is closing down. It closes down but the process stays open in the task manager. It is very frustrating Im sooo spoiled with using Octane for every gig nowdays, and going back to 2.46 will be soo boring hehe

I will try to solve these problems this week. Unfortunately I can't reproduce it here. Can you send us a scene or give us more information about it? What is your exporter you are using?

Cheers,
Marcus

[abstrax]

Temporary solution for this animation problem would something like following.
decide about the samples/pixel
lets say you want to achieve 2000 samples/pixel.

1. set the sampling level in mesh preview kernel as 1800 (<2000)
2. set the sampling level in Turntable Animation Output as 2000.

hopefully this way, when you will render the turntable animation, it will not have any first or second frame problem..
Here its working perfectly.

does not work for me as workaround. still got every second frame the same render.

maybe i miss understood something..

Sorry, the problem occurs when rendering a pass of the image takes more than 0.5 seconds. There is nothing you can do about it, but wait for beta 2.53.

Cheers,
Marcus

[abstrax]

@Marcus : I'm doing experiments : This time I have relinked exactly the same obj as the one used in the scene, and it restarted rendering normally at the end of the voxelizing process. Then I tried again with the scene with just a plane added and a small object removed (almost a cube : around 18 vertices), and Octane crashed.

I loaded directly the obj used to relink, and it opens fine. Then I started to redo all materials settings, and I tried to relink this time the original obj file : I got a crash as well (frozen).

I will try with a smaller scene asap.

If I remember well, the same problem occured before the 2.46. I believe that it occured with Cuda 3.2, but not with Cuda 3.0. Cuda 4.0 fixed it, and it appears now again...
I may be wrong, but maybe it has something to do with Cuda.

EDIT : @Marcus :

- I have thought about what could have changed since my last successful relink of an obj file in a very big scene. During the summer, I learnt Blender 2.59 and switched to it. So, my current scene project has been made in Blender 2.59 and the obj file currently loaded in Octane has been exported with the unofficial addon for Blender 2.59, instead of the former script for Blender 2.49b that I used previously in my huge "Blenderton Hotel" scene !

Maybe that the export addon for 2.59 makes something slightly different in the structure of the obj or mtl file, creating a trouble when relinking big files...

As I haven't used more than 16 materials per object (the limit in Blender 2.4x serie), my current Blend file should be still compatible with 2.49, and should open in it without damage. Tomorrow, I will open my current project in 2.49b, and export and obj. I will try to relink it to my current ocs created from an obj made with the addon for 2.59. If I get a crash, I will export an obj and mtl from the original file in 2.49. I'll load it ad edit it in Octane, and I'll export a modified version that I will try to relink. If it works fine, I think that the source of the problem will be identified as the exporter for 2.59.

I'll experiment tomorrow !

Thank you very much for your efforts!

Marcus

[face]

Can we expect 2.53 to be stable for animations? I've just tried 2.49-2.52 on three different systems (actually four, because I've used another users license aswell during the weekend just to test everything) and it randomly stops on all different scenes I've tried. All systems are Win 7 64x, with 460, 480(single and dual), 570 and 580GTX Geforce cards. It happens just after Octane saved down a image, and is closing down. It closes down but the process stays open in the task manager. It is very frustrating Im sooo spoiled with using Octane for every gig nowdays, and going back to 2.46 will be soo boring hehe

I will try to solve these problems this week. Unfortunately I can't reproduce it here. Can you send us a scene or give us more information about it? What is your exporter you are using?

Cheers,
Marcus

He uses the Softimage exporter. Another and I have also the same issue. I have already reported it in the 2.49 thread i think...
I open Octane with this ShellExecute function:
ShellExecute(0, "open", (LPCTSTR)cPfad.GetAsciiString(), (LPCTSTR)cPara.GetAsciiString(), NULL, SW_HIDE);
where cPfad is the CString from the Octane executable and cPara the commandline as CString.
The problem is, that i check if a process with name Octane.exe is existing, before i send the next frame to Octane.
I think, the other exporters check only if the image is saved to continue the render process and that is the reason because others haven´t this problem...

face

[abstrax]

Can we expect 2.53 to be stable for animations? I've just tried 2.49-2.52 on three different systems (actually four, because I've used another users license aswell during the weekend just to test everything) and it randomly stops on all different scenes I've tried. All systems are Win 7 64x, with 460, 480(single and dual), 570 and 580GTX Geforce cards. It happens just after Octane saved down a image, and is closing down. It closes down but the process stays open in the task manager. It is very frustrating Im sooo spoiled with using Octane for every gig nowdays, and going back to 2.46 will be soo boring hehe

I will try to solve these problems this week. Unfortunately I can't reproduce it here. Can you send us a scene or give us more information about it? What is your exporter you are using?

Cheers,
Marcus

He uses the Softimage exporter. Another and I have also the same issue. I have already reported it in the 2.49 thread i think...
I open Octane with this ShellExecute function:
ShellExecute(0, "open", (LPCTSTR)cPfad.GetAsciiString(), (LPCTSTR)cPara.GetAsciiString(), NULL, SW_HIDE);
where cPfad is the CString from the Octane executable and cPara the commandline as CString.
The problem is, that i check if a process with name Octane.exe is existing, before i send the next frame to Octane.
I think, the other exporters check only if the image is saved to continue the render process and that is the reason because others haven´t this problem...

face

It seems the C4D exporter has the same problem, because it does the same as your XSI exporter. Unfortunately I couldn't reproduce it yet. The case you reported before, that Octane hangs up when there is just a very small number of samples to render got fixed in beta 2.52 or beta 2.51 (can't remember exactly when). This seems to be a different issue. If you have scene and some "magic" settings that make the problem reproducible, please let me know.

Cheers,
Marcus

[PeterCGS]

Marcus, can I send you a Softimage scene? I don't know how to send you a animation othervise :/

[Mugga]

It seems the C4D exporter has the same problem, because it does the same as your XSI exporter. Unfortunately I couldn't reproduce it yet. The case you reported before, that Octane hangs up when there is just a very small number of samples to render got fixed in beta 2.52 or beta 2.51 (can't remember exactly when). This seems to be a different issue. If you have scene and some "magic" settings that make the problem reproducible, please let me know.

Cheers,
Marcus

Hey marcus,

like i already wrote i've got the same problem. One scene of my animation i'm rendering is the one i send radiance because of the the poor performance (http://www.refractivesoftware.com/forum ... =23&t=8115). He wrote that you will have a look at my scene. So you can use this scene to test.

[face]

It seems the C4D exporter has the same problem, because it does the same as your XSI exporter. Unfortunately I couldn't reproduce it yet. The case you reported before, that Octane hangs up when there is just a very small number of samples to render got fixed in beta 2.52 or beta 2.51 (can't remember exactly when). This seems to be a different issue. If you have scene and some "magic" settings that make the problem reproducible, please let me know.

Hm thats a realy wired world...
I have rendered 2 x 100 frames as exr and all works fine.
The same with 6x20 frames with png output.
Have tested it with different settings as default/camera resolution, default or user aperture/exposure and got no freezes.
But i have no animtions in the scene, will test it with some mesh deformations and camera animation when i come back from work this evening...

Maybe a windows update has solved the problem?

face