Page MenuHome

OSX and cycles no non-progessive sample input settings appearing in interface
Closed, ResolvedPublic

Description

Hi, I downloaded the OSX 64 bit official test build, that was released last week.

on the Windows 64 bit version of blender, when in the cycles render tab and I un-check use progressive, new sample settings appear, which is great..

BUT,

on the OSX version these sample settings do not appear at all. The interface stays the same, ie. it shows the same settings as if I am still using the progressive render mode, which I'm not.

I have downloaded other OSX builds and this problem has been in them as well, all it shows it the progressive sampling inputs.

The macs I'm using have ATI cards ( I know ATI cards are not supported) and blender is set on CPU compute and still no non-progressive render options, in-fact the interface doesn't even let me set a gpu compute mode, so that shouldn't be an issue as far as I can tell.

Very strange, so that is why I'm assuming it's a bug unless I've missed something, I must turn on in the interface besides check use non-progressive and set to cpu compute.

Event Timeline

After looking into python code for the ui, this behaviour is indeed intended.

if cscene.progressive or cscene.device != 'CPU': -> show progressive options only

Jens

I think you've miss understood me.

I change cycles to the non-progressive render mode and the setting for non-progressive do not appear, they appear on the windows version. I will upload a pic of what is missing.

Closing this as i see nothing wrong here

Jens

The bug tracker will not let me post an image or a comment on the what is issue.

I found out that if I opened a new file on OSX it would show me the proper non-progressive settings, but if I copied over a blender file from the windows 64 version, the OSX would not show the proper non-progressive settings. So that is definitely a weird bug.

K, ic now this is a general problem with logic of appaearance in UI.
I assign to Thomas Dinges rather ( Dingto )

Thomas: you must rethink the button logic, if inactive, the progressive button remains functional !!! and the non-progressive is not blocked as it should !!

Jens

Fixed in SVN 50550. Thanks for the report.

Thomas Dinges (dingto) changed the task status from Unknown Status to Resolved.Sep 12 2012, 12:55 PM