OctaneRender® 1.024 beta 2.48b TEST (lin/win) [OBSOLETE]

[OctaneFX]

kubo wrote :
"there is a small bug that I don't know if it's been reported, at "night" using the daylight system there is "negative" light throwing shadows, quite amusing."

It seems that I had a similar issue with the daylight system in beta 2.47 (not tested yet with beta 2.48b). My issue was solved by changing the material and the render kernel.
Detailed explanation bellow :

[Populus]

I have a strange bug. If I save a scene in 2.48 or 2.48b and try to open it again I get a black screen in vieport. I have to open this scene again in 2.47 and save to be working in 2.48b version.

I noticed a similar thing in 2.48b, if you save the scene with the camera response set to "linear/off" the render window will be black the next time you open your *.ocs file. However if you change the response back to a preset camera response the render will show up again, then you can change to linear again.

[mib2berlin]

Hi, testing 2.48b and get the same problems with pmc kernel like 2.47.
All files render brighter and brighter and turning white or light grey.
Tested at least with the latest demo suite files (ocs and obj).
This release is more stable for me and i have no more problems on closing octane or loading pictures.

Toolkit 4.0.17 and 275.09 driver.

Thanks, mib

[FamilyGuy]

I have a strange bug. If I save a scene in 2.48 or 2.48b and try to open it again I get a black screen in vieport. I have to open this scene again in 2.47 and save to be working in 2.48b version.

I noticed a similar thing in 2.48b, if you save the scene with the camera response set to "linear/off" the render window will be black the next time you open your *.ocs file. However if you change the response back to a preset camera response the render will show up again, then you can change to linear again.

Thanks. Your tip works great! But they should fix it.

[graffer]

Hi all!

There was a problem with displaying the device in the new release 2.48b 64bit win. Downloaded this one file - Windows 64bit: http://www.refractivesoftware.com/rcdow ... in_x64.zip. I can not test the new release.
Drivers 275.33-desktop-win7-winvista-64bit-international-whql. What to do?
Thanks in advance!

Previous release 2.47 PMC stable.

[Isotemod]

While not a bug specific to this version (and perhaps not really a bug) if the material file for the imported object has the opacity texture reference map_d capitalized ie map_D like it does with exports from Daz studio it doesnt recognise it. Any chance of this being tweaked for this version?

[abstrax]

I tried yesterday 2.48b finally and it seems PMC is slower than on 2.47. I tried to render the very same interior picture, i rendered on 2.47 before, i just changed the material for carpet from Diffuse to Glossy (so its possible this was the reason for the slowdown). On 2.47 it took 30 min to get cca 3200 samples (and the sample rate was 4,55 Ms per second). On 2.48 it managed only 2100 samples in the same timeframe with a sample rate of 2,88 Msps.
On the positive side, the mesh relink button works fine as already reported by ROUBAL.

Can you let it render for 30min and then compare the noise? Although the samples/second is lower in beta 2.48b than in beta 2.47 it should have less noise. Could you please verify this?

Thanks,
Marcus

[face]

I have a strange bug. If I save a scene in 2.48 or 2.48b and try to open it again I get a black screen in vieport. I have to open this scene again in 2.47 and save to be working in 2.48b version.

Same here. After reload a saved scene with 2.48b, i get a black screen...

face

[kivig]

I have a strange bug. If I save a scene in 2.48 or 2.48b and try to open it again I get a black screen in vieport. I have to open this scene again in 2.47 and save to be working in 2.48b version.

Same here. After reload a saved scene with 2.48b, i get a black screen...

face

Same here.

[abstrax]

Regarding the black screen when loading a scene with linear tonemapping: Thanks for the report and it will be fixed with the next release.

Cheers,
Marcus