OctaneRender™ Standalone v1.0 beta3.01 [obsolete]

[roeland]

heya.. i cant start it. Message: Could not connect to OctaneLive

What can i do?

Check if your firewall is blocking Octane. It makes a standard https request to the OctaneLive server.

--
Roeland

[awund]

firewall was set, but i had to start it as an administrator. thanks

[roeland]

That is weird. Octane (and other programs) should be able to connect to the internet without administrator rights.

--
Roeland

[matej]

Please consider writing both the absolute & relative paths to resources in the .ocs, instead of the user having to choose one of the two options in the general settings and stick to it. This would make the ability to move your project around much more robust and flexible as we could mix both path types in the same .ocs

I use absolute paths with my projects, but would like to use relative paths when I need to share (some of) the project files (say a few specific macros). Embedded image files are a less than ideal "solution" for sharing, because the images are stored in raw format, such files can be hundreds of megabytes big (instead of just a few megabytes for .jpg encoded images). This is not an option when sharing bigger projects across the net. A better option is to have a texture folder relative to your project folder and put your images there.

Paths for a resource could be easily stored as xml tag parameters, so instead of this:

Code: Select all

<linkedfilename>/xy/project/maps/texture.png</linkedfilename>

you would have this:

Code: Select all

<linkedfilename abs="/xy/project/maps/texture.png" rel="./maps/texture.png"></linkedfilename>

or this for backward compatibility:

Code: Select all

<linkedfilename abs="/xy/project/maps/texture.png" rel="./maps/texture.png">/xy/project/maps/texture.png</linkedfilename>

When loading the parser would look for the resource in both paths and use the first that it finds (or the one that is specified as having higher priority (abs or rel) in the general settings).

[grimm]

I wanted to try out this new version, but my Fedora 15 install was old and moldy. I have since upgraded to Fedora 17 and now Octane runs. But when I try and render either the test scenes or one of my own (.ocs or .obj) the console says:

Code: Select all

CUDA device 0: KERNEL FAILED!!!

I have updated my systems information in the sig, not much has changed except the NVIDIA driver version. I'm running akmod so maybe that's the issue?

[roeland]

I have no experience with akmod, but you can try to install a driver directly from NVIDIA, and then to reinstall the CUDA toolkit.

--
Roeland

[grimm]

Thanks Roeland,

Akmod is basically a yum installed package that has the NVIDIA and other drivers pre-compiled when the Linux kernel is updated. This way you don't have to re-compile the driver on every kernel update. It hasn't caused any problems before, but something has changed. I compiled and installed the latest Nvidia driver (304.43). Re-installed cudatoolkit_4.0.17_linux_64_fedora13.run and tried this version of Octane again, no luck. I also tried earlier versions but they had the same error. Should I try an older version of the Nvidia driver? I have NVIDIA-Linux-x86_64-275.09.07 still lying around that I could try and load.

Jason

[abstrax]

Thanks Roeland,

Akmod is basically a yum installed package that has the NVIDIA and other drivers pre-compiled when the Linux kernel is updated. This way you don't have to re-compile the driver on every kernel update. It hasn't caused any problems before, but something has changed. I compiled and installed the latest Nvidia driver (304.43). Re-installed cudatoolkit_4.0.17_linux_64_fedora13.run and tried this version of Octane again, no luck. I also tried earlier versions but they had the same error. Should I try an older version of the Nvidia driver? I have NVIDIA-Linux-x86_64-275.09.07 still lying around that I could try and load.

Jason

What do the device preferences say? Could you post a screenshot? Is the error message still "KERNEL FAILED" or something else?

Cheers,
Marcus

[grimm]

Thinking about this some more and I realized that it's probably not a problem with this version of Octane but something with my system that is causing the problem. As the older versions of Octane respond with the same error.

Jason

[grimm]

Everything else in Octane appear to be working. I can see the device preferences, nodes, etc. It just will not render. The error hasn't changed it's still the same.

Code: Select all

[jason@gemong graphics]$ cd octane.2.49
[jason@gemong octane.2.49]$ ./octane
CUDA device 0: KERNEL FAILED!!!

I can get a screen shot for you but It will have to be tomorrow. Thanks Abstrax.

Jason