Octane Live Platform Testing Release (pre-23) [obsolete]

[sam75]

I think we all need to learn a lesson from this and let them do their thing.
We pushed them to release it to early, now radiance will wake up to 10 pages of problems.

Take your time with the update

this is what betas are for, this way problems will be found and resolved faster.

[rfox]

This new version runs very slow in my laptop comparing to v.2.2b

[julianb]

Emitters actually work in exteriors. I placed a huge sphere outside my building and being set as an emitter affected the brightness of the building. Although I must say emitters sometimes do not produce light and only after restarting Octane work as they should.
By the way I just love the way emitters bring to live LCD displays or TVs in our scenes. When texture emission is used the display looks perfect.
By the way every now and then my Aperture keeps resetting to its initial values for no apparent reason.

I must say I am really pleased with the new improvements. Of course there will be problems, but they will be fixed pretty soon I suppose.

P.S. What happened to copy/paste materials? Did I get it wrong or we were suppose to be able to right click on a material, copy it, then right click on another material and paste it. Just like in 3DS Max. Did I missunderstand something again?

Cheers.

[MaTtY631990]

Everytime I import a mesh it seems to crash and is unstable while configuring materials, emitters etc.
Is this anything to do with the one server that's active due being connected to the internet I could it be just a system/driver issue.

[acc24ex]

I think we all need to learn a lesson from this and let them do their thing.
We pushed them to release it to early, now radiance will wake up to 10 pages of problems.

Take your time with the update

Well the purpose of testing release is to do the testing phase faster, that approach is great, so when we test the next version we can get used to working with the new options..
so ..
the next problem, I can set only 1 emitter material
when I change the supersample I get garbage on the screen (like those mentioned before), and what does supersample do for us now? I want touch it now..
And pressing on "material macro" crashes
Also, it's firefly happy, even with no specular or glossy nodes

And it's so bright.. maybe too bright it's like looking directly into the sun

Ok, when the garbaged window appears and than change the resolution to something much higher the image comes back.. 1600x500
And I think also got a black line at the bottom of the window. and after that a crash when trying to save a
picture..
still nice to play with

[sathe]

Yeh I understand what you are saying but the fact is, the version we are testing is stripped of certain features that where meant to be in this release, which may be causing some of the instability.
Instead, they released what they had so we would stop bitching for it.

I highly doubt we would have as many problems if they released it when they where happy.

[cpember]

agreed


I was just testing my 460 here and it still lists the core count at 224, so I dont think the newer stuff for that part of it is working.. on the benchmark scene it's a touch slower, i was getting 1.72ms/s (178 smaples in one minute) with last beta and with new build 1.59ms/s (164samples in 1 minute)

cheers

cp

ps: i vote for "when it's done" next time

Yeh I understand what you are saying but the fact is, the version we are testing is stripped of certain features that where meant to be in this release, which may be causing some of the instability.
Instead, they released what they had so we would stop bitching for it.

I highly doubt we would have as many problems if they released it when they where happy.

[sam75]

agreed


I was just testing my 460 here and it still lists the core count at 224, so I dont think the newer stuff for that part of it is working.. on the benchmark scene it's a touch slower, i was getting 1.72ms/s (178 smaples in one minute) with last beta and with new build 1.59ms/s (164samples in 1 minute)

cheers

cp

ps: i vote for "when it's done" next time

Yeh I understand what you are saying but the fact is, the version we are testing is stripped of certain features that where meant to be in this release, which may be causing some of the instability.
Instead, they released what they had so we would stop bitching for it.

I highly doubt we would have as many problems if they released it when they where happy.

someone forced you to download ? let us try those betas and come back "when it's done" ok ?

[pixelrush]

I really dont see whats going on in my case.
9 times out of 10 it 'needs to close' either immediately after loading (click on node) or a little time after.
I did actually have a good run in one case that I was able to bring up a material ball with the LiveDB and step through the provided mats however it did eventually close and then it wouldnt work at all when I restarted Octane straight after. On other occasions I could get none or one or two.
I looked at the network traffic and small regular things seem to be happening every so often however I did notice that although Octane said it was going through the phases and voxellising etc there didnt seem to be any processor activity or pagefile growth associated with it and then it wanted to close.
I got the impression that when rendering is actually starting that there was quite a bit extra info sent and Octane was waiting to get an ok? but didnt get it? there seemed to be quite a pause there that wasnt in the process before the rendering image came up... dunno...
In some cases I was able to open a .osc and more rarely .obj but they all needed to close after a little while. Even exactly the same files werent consistent.
Earlier today in the one experiment that went well I was able to change the red pawn in the chess set to be emissive and make some other tweaks but I couldnt actually get any where near doing that again anytime I tried again before it needed to close.
BTW 'open' is in the menu twice.
It seems to be random or variable. I think myself it has to do with successfully phoning home and continuing to make contact but I think we have actually seen the non voxelise bug before??.
I havent ever noticed any connection issues with my pc before though.
BTW I connect through another pc using IC share but there is no issue with a browser etc and quite obviously there is some connection being made to the Refractive server so it doesnt seem blocked.
Weird indeed HTH the debugging.
BTW2 shouldnt Refractive be telling us at this time about ports, protocols and/or IP address or something for firewall reasons?

[havensole]

I've been getting the same thing. Not sure if it is a connection issue or server load issue, or something completely different. I've yet to get a render to go for more than a few seconds before Octane crashes. I'll try it on my work system later which has a much higher rated internet connection and see if the problem still exists.