OctaneRender® pre-Beta 2.3 v4 (win/lin/mac) [OBSOLETE]

[matej]

Do any other users have the same issue ?

I tried it and Octane keeps rendering without any problems

[lechu]

Well, exact steps were:

1. exporting scene + camera from Blender 2.49
2. Octane launches right from the Blender script, everything works fine
3. Material, resolution, environment tweaking etc.
4. Rendering, GPU Fan going faster after a few minutes
5. After maybe 500 samples I can hear GPU fan slowing down, check the Octane and see - status: disconnected
6. Try to save an image, pan or something but the screen is freezed. However I can still click pause render/ start render buttons, but nothing goes on.
7. After a few seconds of intense tries of doing something with Octane, it freezes completely.
8. Launching Windows Task Manager, killing Octane, but after it dissapeares from the desktop, it's still visible in the Manger.
9 Tried to launch another Octane, it even loads the *.ocs files but cannot display anything in the viewport.
10. Restarting Windows, after the monitors fade out, the PC is still running and needs manual restart. Windows then launches without any problems.

[radiance]

Well, exact steps were:

1. exporting scene + camera from Blender 2.49
2. Octane launches right from the Blender script, everything works fine
3. Material, resolution, environment tweaking etc.
4. Rendering, GPU Fan going faster after a few minutes
5. After maybe 500 samples I can hear GPU fan slowing down, check the Octane and see - status: disconnected
6. Try to save an image, pan or something but the screen is freezed. However I can still click pause render/ start render buttons, but nothing goes on.
7. After a few seconds of intense tries of doing something with Octane, it freezes completely.
8. Launching Windows Task Manager, killing Octane, but after it dissapeares from the desktop, it's still visible in the Manger.
9 Tried to launch another Octane, it even loads the *.ocs files but cannot display anything in the viewport.
10. Restarting Windows, after the monitors fade out, the PC is still running and needs manual restart. Windows then launches without any problems.

ok thanks, we'll try to reproduce it by pulling the ethernet cable after 20-30 minutes.
one last thing, if you try it again, and once you see the 'disconnected', don't touch your machine, until it's 'connected' again, and if this A. happens and B. you can continue working.

Thanks,
Radiance

[matej]

Can anyone confirm this:

If I try to load a scene which contains an imported material macro (from .ocm file) and was saved with it, the scene doesn't want to load anymore (message below).

Also, some of my material macros (saved in .ocm) got corrupted (I'm not sure when or how) and also wont import (with the same error)

I will be possibile to not store image files into macros (.ocm), instead just have a link to where the image is? This way the image could be edited, and on every import / reload the macro would have the last update of the image - no need to resave the macro everytime you edit the images. So basically two creation options; a packed .ocm for upload to LiveDB and an 'linked' one, for use in your filesystem.

[Hawker]

i tested the new 2.3v4 before i used a 2.2b

there are the little problems i found for now:
-when clicking ok in the account prefernce panel, it is very long to close (and a crash once)
-scenes take more time to start to compute than the 2.2b
-touching the nodes make that the engine recompute the render

and i have a question ( i have a 460 but only 224 core are activated, is that normal (a cuda driver issue) ?

[afecelis]

Guys, can anyone try this too. Octane crashes when trying to load the simple checker material from the DB:

[matej]

Guys, can anyone try this too. Octane crashes when trying to load the simple checker material from the DB:

Same here.
But that's the only material that crashes Octane. Others work fine.

[kubo]

i tested the new 2.3v4 before i used a 2.2b

there are the little problems i found for now:
-when clicking ok in the account prefernce panel, it is very long to close (and a crash once)
-scenes take more time to start to compute than the 2.2b
-touching the nodes make that the engine recompute the render

and i have a question ( i have a 460 but only 224 core are activated, is that normal (a cuda driver issue) ?

Yeap, is a cuda driver limitation for now, it's expected to be implemented in future cuda versions to have access to the rest of the cores.

[radiance]

as said before, 'simplecheck' is the first macro we made a long time ago and it's broken, we're removing it now

Radiance

[8Eggar8]

Any chance an upcoming build will have the option to turn off the 'texture environment' background 'off' leaving just the reflections and/or refractions on?