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

[bepeg4d]

hi,

thanks for the new release !

but I am using a Mac with OS10.5.8.
This release works with CUDA toolkit 4 which requires OS10.6.

Can this release work with an older CUDA toolkit (3.2 for example) and driver?

best and thanks !

i don't think that it could be possible, i suggest you to upgrade to 10.6 as i see that you have a core 2 duo, snow it's much better than leopard
ciao beppe

[adiarc]

Does this mean the Python console?

No. If you start Blender from the commend line you'll get output in that console. You are probably on Win, I'm guessing there is a way to open a console window alongside starting Blender? The only way I know is to open a console yourself, browse to where you have Blender installed and run the .exe from the console.

+1 for better camera controls - especially 3D navigation with the mouse (but that's already on the TODO list, AFAIK)

Thanks, matej. Blender 2.49 has the console open alongside the application, but 2.59 doesn't. But I think I found the console under Help > Toggle System Console. However, this doesn't give any info I understand. The last line in the console says the exact same "Something wrong happened, please check console logs". I wonder where these damn logs are...

Now I tried exporting from Blender 2.49 to Octane 2.52, and it works just fine. Could be that it is just the exporter that needs to be updated for Octane 2.52 or something. Dunno.

[necko77]

little bug, not so important

Capture.JPG

maximize is not working so i need to move window to the top of the screen to maximaze octane render...

[dave62]

Does this mean the Python console?

No. If you start Blender from the commend line you'll get output in that console. You are probably on Win, I'm guessing there is a way to open a console window alongside starting Blender? The only way I know is to open a console yourself, browse to where you have Blender installed and run the .exe from the console.

+1 for better camera controls - especially 3D navigation with the mouse (but that's already on the TODO list, AFAIK)

Thanks, matej. Blender 2.49 has the console open alongside the application, but 2.59 doesn't. But I think I found the console under Help > Toggle System Console. However, this doesn't give any info I understand. The last line in the console says the exact same "Something wrong happened, please check console logs". I wonder where these damn logs are...

Now I tried exporting from Blender 2.49 to Octane 2.52, and it works just fine. Could be that it is just the exporter that needs to be updated for Octane 2.52 or something. Dunno.

yoyoz last exporter works fine for me under blender 2.59.
just some idea:

did you checked your texture slots? only "image" type is supported, -any other procedural type (eg like clouds) will cause errors. most errors came from wrong texture types in yoyoz 2.5x exporter in my past..

btw better post blender specific stuff here:
http://www.refractivesoftware.com/forum ... m.php?f=32
cheers,
dave

[softline]

Thank you refractive software!

I long for a day wnen you add transform node instead of lonely scale float for non-procedural textures.

[YoonKyung]

The 1st and 2nd, 3rd and 4th, and so on output images of Turn Table Animation are same.

ChessSet000000.png

ChessSet000001.png

ChessSet000002.png

ChessSet000003.png

[t_3]

The 1st and 2nd, 3rd and 4th, and so on output images of Turn Table Animation are same.

did you try to just quit octane, and reload the scene? i had that once happen with 2.49, and after that (maybe i even restarted my pc) it worked...

[teecee2107]

I've been experiencing two strange problems since using version 2.52. :

1.- After having been working on a scene for a few hours without problems, I decided to go to sleep (I need that from time to time ...) so I saved the scene, still no problem. The next day when I want to load that same scene, I got that bad C++ error message (will try to grab a print screen next time) at the end the voxelizing process and I can't load the scene anymore... My only solution is to open version 2.46b and load that same scene. It opens like a charm (at the only condition that I've not been using the PMC kernel) and I can go on working on my scene, but I can never open it in version 2.52 again. I've been experiencing this issue with two different scenes. One solution would be, of course to never quit octane until the very final render is done (not very imaginable ) but any way this would lean me, sooner or later, to issue n°2

2.- Sometimes, when working with version 2.52, my pc freezes so I have to reboot (I've learned to save VERY often, now) and then (even if I can reload the scene) the pc crashes each time I try to change something, or after a few minutes of rendering. So, if I want to go on working with the scene, I have to switch to version 2.46b where I never experience this kind of problem. I've been checking the t° of mu GPU but it stays under 70° which seems to quite reasonable.

Maybe version 2.52 is much more 'ressources consuming' than previous versions, and that my gtx460 with 2Gb is a bit short, or maybe 4Gb Ram are not sufficient, or it's because I'm still using Windows XP 32 bits ... I don't know.
It's not a real problem because I don't rely on octane for professionnal work, just for hobby, but this situation stop me to definitely switch to last vesion. So, if anybody has a clue, ...

Oooops, I forgot to apologize for my bad english, I hope it's 'understandable' ...

[ROUBAL]

Well, if you are on Win XP 32bits, Your OS will see only 3.2GB of RAM, and will allow only 2GB per application if I remember well, so I fear that you are really short of memory...

I think that you would need to switch to Win 7 x64 and add RAM up to 8GB or more if your motherboard allows more.

For my own I have 8GB of RAM (the max supported by my ASUS P5K), and I can load big scenes in my 3GB GTX 580, but at the price of a very long loading time because Windows has to use the swap file due to a lack of physical memory.

[ycarry]

I too use old Vista 32bits 2GB of RAM and have no probs.
But I use last driver 280... maybe thats why?