OctaneRender™ Standalone 1.18

[kavorka]

More testing.
Installing 1.1 and loading up a sphere mesh then loading an HDRI works fine, no problems. Loading a scene saved with 1.18 into 1.1 has the HDRI error.
Saving the 1.1 working scene and loading it into 1.18 has the HDRI error.

[ROUBAL]

Loading a scene saved with 1.18 into 1.1 has the HDRI error.

Why doing that ? Isn't it like trying to open a Blender file made with 2.6x into Blender 2.49 !

[kavorka]

Loading a scene saved with 1.18 into 1.1 has the HDRI error.

Why doing that ? Isn't it like trying to open a Blender file made with 2.6x into Blender 2.49 !

I wanted to see if the problem only existed in newer versions. This also showed me that it was a scene problem because it exists in older versions.

[roeland]

More testing.
Installing 1.1 and loading up a sphere mesh then loading an HDRI works fine, no problems. Loading a scene saved with 1.18 into 1.1 has the HDRI error.
Saving the 1.1 working scene and loading it into 1.18 has the HDRI error.

Can you send us a simple scene showing this problem?

--
Roeland

[pimpuppy]

I have run into an HDRI error.
When rotating the HDRI, the image becomes very pixelated.
As you can see in the images attached, it is not the HDRI at fault. I have also tested this with other HDRI images and have the same problem. I didnt have this problem before.

Hello,
I had the same problem with the HDRI rotating and pixelating.

It appeared in 1.17. Did not tested in 1.18.
If the HDRI is set back to 0 on rotation then it is back to normal. I did not test on the vertical rotation, only the horizontal.

[kavorka]

More testing.
Installing 1.1 and loading up a sphere mesh then loading an HDRI works fine, no problems. Loading a scene saved with 1.18 into 1.1 has the HDRI error.
Saving the 1.1 working scene and loading it into 1.18 has the HDRI error.

Can you send us a simple scene showing this problem?

--
Roeland

I sent one in response to the PM I got from you guys

[ROUBAL]

I wanted to see if the problem only existed in newer versions. This also showed me that it was a scene problem because it exists in older versions.

I am not sure that this kind of test could lead to reliable interpretation because scenes may not be fully compatible. So, bad results could be due to compatibility troubles as well...

Scenes created with most recent release, openened and saved with old version, and opened again in recent version ... and saved again could imho lead to corrupted scenes...

A better testing method would be to create the same a totally new simple scene with every concerned releases and compare the result.

[kavorka]

I wanted to see if the problem only existed in newer versions. This also showed me that it was a scene problem because it exists in older versions.

I am not sure that this kind of test could lead to reliable interpretation because scenes may not be fully compatible. So, bad results could be due to compatibility troubles as well...

Scenes created with most recent release, opened and saved with old version, and opened again in recent version ... and saved again could imho lead to corrupted scenes...

A better testing method would be to create the same a totally new simple scene with every concerned releases and compare the result.

i also did that, and saw that in 1.1 it was fine. So I brought the scene that was broken into 1.1 to see if it was purely a problem with the 1.8 version, or if it had something to do with scene settings. Just trying to be thorough. If I brought the scene into 1.1 and it had no problem, that would get rid of several possibilities and possibly help the devs find the solution. Yes, it still being broken in 1.1 doesn't tell you too much cause there are other variables, but it might tell the devs something, and if it was ok, it would tell them even more.

[Elvissuperstar007]

bug 1.18

[abstrax]

bug 1.18

I couldn't reproduce this problem here. Could you give us step-by-step instructions or a test scene or a video that shows this problem?

Thanks,
Marcus