Page 5 of 8

Re: OctaneRender 2.45 screenshot/preview

Posted: Sat Apr 02, 2011 12:16 pm
by steveps3
from you top screen shot, the render is obviously not square. I've just tried to recreate the problem and the resultant image was as square as could be. Was the width originally 1000pixels and you reduced it? I have had a few occasions where I have changed the width only to find that the change doesn't actually take effect.

Re: OctaneRender 2.45 screenshot/preview

Posted: Sat Apr 02, 2011 12:53 pm
by Jaberwocky
Steveps3


I just set it to 900x900 in Octane.Cooked it and save the png file.

Opened it in photoshop and checked the size.That was it.i have not resized it in anyway.

I'll try a different size and see if i get the same problem.This was a previously saved job and i reopened it to run it again with the new size.So maybe there is a problem with doing it that way.

Anyways i'll try again and see what happens.

Thanks for your feedback.

Re: OctaneRender 2.45 screenshot/preview

Posted: Sat Apr 02, 2011 1:11 pm
by Jaberwocky
Definately recreateable at 1000 x 1000 except this scene now comes up at 1000 x 1920.

Different scene loaded and set to 1000x1000 - same mis match of resolution output.

other Resolutions set seem to be ok so maybe there is just a bug when you load a scene and set it to 1000x1000

not sure.Could someone else load one of their existing scenes and set it to 1000 x 1000 and see what happens ?

Cheers

Re: OctaneRender 2.45 screenshot/preview

Posted: Sat Apr 02, 2011 1:21 pm
by GeoPappas
Jaberwocky wrote:It was set to 900x900 pixels but photoshop shows it as 900 x 1000
I'm not sure if this is your issue, but when changing the resolution, if you input the x and y together (at the same time), sometimes they both don't take effect. I would change the resolution to 1000 x 1000, wait till it finishes, then change the resolution to 1000 x 900, wait till it finishes, then change the resolution to 900 x 900.

Re: OctaneRender 2.45 screenshot/preview

Posted: Sat Apr 02, 2011 2:54 pm
by Jaberwocky
GeoPappas wrote:
Jaberwocky wrote:It was set to 900x900 pixels but photoshop shows it as 900 x 1000
I'm not sure if this is your issue, but when changing the resolution, if you input the x and y together (at the same time), sometimes they both don't take effect. I would change the resolution to 1000 x 1000, wait till it finishes, then change the resolution to 1000 x 900, wait till it finishes, then change the resolution to 900 x 900.

Geopappas thanks

when i have five minutes spare i'll give that a try.

If that is the case then it's more of an input bug and therefore still needs addressing.

Re: OctaneRender 2.45 screenshot/preview

Posted: Sat Apr 02, 2011 4:33 pm
by GeoPappas
Jaberwocky wrote:
GeoPappas wrote:
Jaberwocky wrote:It was set to 900x900 pixels but photoshop shows it as 900 x 1000
I'm not sure if this is your issue, but when changing the resolution, if you input the x and y together (at the same time), sometimes they both don't take effect. I would change the resolution to 1000 x 1000, wait till it finishes, then change the resolution to 1000 x 900, wait till it finishes, then change the resolution to 900 x 900.

If that is the case then it's more of an input bug and therefore still needs addressing.
Yes, I wrote this up a while ago:

http://refractivesoftware.com/forum/vie ... =33&t=5125

Re: OctaneRender 2.45 screenshot/preview

Posted: Sat Apr 02, 2011 4:49 pm
by dadou351
Hello,

Will we have the instance function in this version? (As proxy on vray?)

Thanks,

David

Re: OctaneRender 2.45 screenshot/preview

Posted: Sat Apr 02, 2011 6:01 pm
by Jaberwocky
Geopappas

looked at that thread.That explaines it nicely.The bugs not gone yet , looks like it's still on their to do list ;)

Re: OctaneRender 2.45 screenshot/preview

Posted: Sat Apr 02, 2011 9:33 pm
by vinz
a new octane release is always a great new, and this one was heavily awaited ... especially for lights improvements !!!
thanks for your big work guys :)

Re: OctaneRender 2.45 screenshot/preview

Posted: Sat Apr 02, 2011 10:13 pm
by abstrax
To Jaberwocky/GeoPappas: GeoPappas is right. Size changes via the numeric edit fields don't get through all the time. The actual problem is very hard to solve at the moment, but will hopefully go away with the CUDA framework changes we are currently working on. If we find some time, we may add a temporary solution for beta 2.45

To dadou351: No instances in beta 2.45. It might actually take a while, until they become available.

Cheers,
Marcus