OctaneRender® 1.0 beta2.46b [OBSOLETE]

[Jaberwocky]

Yep tried it.Can still alter the node.

and yes... it has bombed out.

It's probably best if you lock that node off so it cannot be edited.

[abstrax]

Yep tried it.Can still alter the node.

and yes... it has bombed out.

It's probably best if you lock that node off so it cannot be edited.

Ok, we will take another look at it. Didn't think that the output node of the macro is a problem, too.

Thanks for testing,
Marcus

[danilius]

Just a quick note to point out that regular incremental releases such as has been happening now is very much a confidence builder, and I for one appreciate it very much. If you release bug-fixes every week or two, however minor, then we can easily observe the progress, which is not the case with the occasional tid-bit being fed into the forums.

Many thanks; more power to your collective elbows, and pedal to the metal all the way!

[GeoPappas]

Just a quick note to point out that regular incremental releases such as has been happening now is very much a confidence builder, and I for one appreciate it very much.

+1

[radiance]

Just a quick note to point out that regular incremental releases such as has been happening now is very much a confidence builder, and I for one appreciate it very much.

+1

Hi,

The reason why there are very regular releases recently is because they are minor updates, with a few bugfixes and some smaller UI related changes. (IES being the largest new feature, but even in it's own right it's not a very big feature do implement)

The next 2.5 release won't happen in a few days or 1-2 weeks, but more than that as it is a new major release with a few invasive, large changes (new cuda multi-gpu framework, new render kernel, etc...)

So, from now, you will all have to be a bit patient for the coming weeks, but it will definately be worth it.
If everything goes according to plan (and as you all know by now, with GPGPU development it always never does), 2.5 will be the long awaited big release, on par with the amount of innovation between the prior 2.2 and 2.3v5 releases.

Me, marcus and roeland will be working each on a major new feature during the next 3-4 weeks (minimum), combined with me doing the new site aswell.
I think the 2.5 release will bring much more satisfaction, than these regular/small releases, and will come together with a new website with many new online tools for the community.

Radiance

[danilius]

Radiance, thanks for that update. Might I suggest that at this juncture regular (bi-weekly) updates regarding your progress would be equally welcome? This can range from negative feedback (~@{*&@% nVidia and cuda holding the &*%$£ up) to various important milestones towards the next big release (yay, we've discovered how to convert your PC into a quantum computer for under a tenner*).

In this way, we can all have a far more realistic perspective of we can expect. A major blow to the development process does not have to result in a PR disaster - far from it. If everyone knows that the release has been pushed off due to some horribly stupid choice on the part of nVidia, then we can all sympathize and reset our internal clocks. In this way no-one gets upset (if slightly disappointed, but not with yourselves), and you have the benefits of our collective sympathy.

To this end, a useful tool would be a developer's blog from yourself, Abstrax and Roeland. For the half an hour every second day or so it would take to simply pour out your thoughts and how you feel you are doing, you would be garnering more support and allowing the rest of us to join, if only vicariously, in the development process. Almost all of us, I would assume, do not necessarily want blow-by-blow detail and the breakdown of your code, but would like to hear whether you were pleased or frustrated by your current progress, and anything small but funny that might have occurred. This gives us an almost tangible impression of how things are panning out, which is important since we are hitching our wagons to your horses.

And finally, ignore the whiners. Whether they leave or stay, they won't enjoy the journey that is Octane anyway. Hopefully, they represent a vocal minority.

*If you actually do discover how to do that, I have a fantastic t-shirt you can use for the marketing campaign.

[danilius]

BTW, if my network connection drops for more than a minute or so (haven't tested the exact duration yet) Octane quits with an "illegal instruction" log message.

[matej]

Radiance, don't worry, while waiting for the next release, we will entertain ourselves with a "When will Octane 2.5 be out" thread...

[bepeg4d]

@ radiance: thanks for the info but any news about instancing?

@ matej: you're incorrigible, and me too

ciao beppe

[8Eggar8]

nvidia will only let me go back to a driver for my card that implements CUDA 3.1
Does 3.1 avert the new speed problems introduced by the 3.2? And is 3.1 a decent enough version

(not that detailed a question - but I'm getting slammed by work right now) TIA


Would it be the 'Cuda Driver' or the 'Cuda Runtime' that should get set back to 3.0?

BTW: I notice (when direct lighting is selected) the speed is at around 30f/s with all 3 of my cards active. pulling the lesser of the 3 cards (the 260) I notice that the speed jumps to 36 f/s (that's with the 2 460's active). The factory o.c.'d 460 is about 23 f/s alone, while the 460se card alone gets around 19. My Runtime now is Cuda 3.0 (driver version 3.2). and my video driver is th 366.58 version. Do you belive the 3rd card (in the future) will add any benefit to the overall speed of the render?