AW: [Bf-funboard] Render Buttons proposal

[William Reynish]

Hi Benjamin.

Yes, I suppose I can see the need for presets that
also affect regular rendering settings. But How about
having two preset dropdowns then? One for settings,
and another for format?

Your idea on how to add custom savable presets to the
UI sounds ok, I just don't know about the "shift-click
on the dropdown to rename" thing. No other dropdown
menu allows this. Maybe it would be better to have a
little popup appearing when you click the 'Save'
button where you could type the name


About OpenGL rendering: It's still there, but it is
now in the 3d Window header as a little mountain icon
like it was before 2.30. LMB click on this icon to
render a still, and shift-click to render animation. I
don't think this icon is very good - it isn't obvious
what it does, and it is clumsy that you have to shift
click it to get an animation. I think the reason why
it was moved back was because it was impossible to
determine which 3D window would be OpenGL rendered.

Maybe a good solution would be to add OpenGL to the
render dropdown menu so that it would look like this:

Blender
Yafray
OpenGL

Or maybe adding back the one in the Render menu would
be nice, and then setting it to always render the
largest 3D window available - who would ever want to
render a smaller one anyway?


-William

 --- Benjamin Freundorfer <benjamin.f@gmx.at> skrev: >
Hi!
> 
> Well, at first I liked the idea very much, presets
> only affect a few
> settings. But then I realised, I would mainly use my
> own customised
> presets to switch between a preview mode and final
> mode:
> 
> for example:
> "2.35-preview": (radiosity, mblur, raytracing, etc.
> turned off, only
> giving an idea of what the animation will look like)
> "2.35-final+yafray": (everything turned on, even
> using yafray as
> renderer)
> etc.
> 
> So, for me they should affect everything, also edge
> settings.
> Nevertheless, the range should NOT be included into
> the presets.
> 
> I think the buttons are very well grouped, as
> William Reynish designed
> them (http://www.shadeless.dk/ui/renderbuttons.htm).
> But two buttons ("save" and "delete"<--pretty
> obvious what they'd do)
> should be added just next to the dropdown of
> presets. And when u
> shift-click an the dropdown u should be able to
> rename the current
> setting. When u change settings, the name could
> either become "custom"
> or "[presetname].001". But when your settings
> eventually match a preset,
> there is no need to automatically switch back to
> that preset.
> 
> Btw, is openGL to be included as renderer? At
> version 3.30 it was. And
> it came in very handy for previewing an animation.
> 
> benjamin
> 
> 
> 
> 
> 
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: bf-funboard-admin@blender.org
> [mailto:bf-funboard-admin@blender.org] Im Auftrag
> von Luke Wenke
> Gesendet: Dienstag, 03. Februar 2004 09:14
> An: bf-funboard@blender.org
> Betreff: Re: [Bf-funboard] Render Buttons proposal
> 
> 
> Hi,
> I think the presets should only affect:
> 
> - width
> - height
> - scaling (100%, 75%, etc)
> - aspect ratio (aspX, aspY)
> - framerate
> - maybe field options (fields, odd [lower/upper], x)
> <- or maybe not,
> otherwise you might need to have PAL/NTSC both
> without and without
> fields.
> 
> The reason for this is that I think the presets
> should be an easy way to
> switch between PAL, NTSC, PAL widescreen, etc. I
> don't think they should
> affect OSA, frame range (start and end frame), etc,
> settings.
> 
> I don't think they should affect xparts, yparts or
> panorama (pano)
> either.
> The reason for this is that the current PANO preset
> sets the image size
> to
> an obscure setting. And if you click the "PANO"
> preset, then "PAL"
> (etc),
> then it undoes the panorama setting when you might
> have wanted it to
> have an
> interesting panorama view. (Like I've done in the
> past - it makes
> straight
> edges curved)
> 
> I think the presets should be:
> PAL
> PAL 16:9
> NTSC
> NTSC 16:9 (though I don't personally use NTSC)
> 640x480
> 
> If fields are part of the presets then there would
> be:
> PAL Progressive (or PAL No Fields)
> PAL Fields (or PAL Even Field First, PAL Even
> Fields, or PAL Lower Field
> First)... (also for NTSC and 16:9)
> 
> I don't think the existing "Full" preset (1280x1024)
> is a very accurate
> description since it seems you can render up to
> about 10,000x10,000.
> Also,
> the highest video resolution is in fact 1920x1080
> (HD video) - in fact,
> After Effects has an even higher preset for cinema
> work...
> 
> If people change one of the variables I listed
> earlier (width, height,
> etc)
> I think Blender should check to see if it matches an
> existing preset. If
> not, it could be called Preset.001 (or *Untitled
> Preset). Then when you
> click on it you could name it - e.g. "PAL 50%" or
> "800x600", etc.
> 
> I know there used to be a "Default" setting, but I
> think it is annoying
> that
> it turns off envmap, ray and radio like it does...
> and "Preview" isn't
> very
> useful - it basically changes the resolution to
> something obscure and
> changes the scaling to 50%.
> 
> So basically I'm trying to minimize the amount of
> fiddling people would
> need
> to do if they want to switch between different
> presets. (e.g. PAL, NTSC,
> 640x480...)
> 
> - Luke,
> 
> ----- Original Message ----- 
> > > http://www.shadeless.dk/ui/renderbuttons.htm
> _______________________________________________
> Bf-funboard mailing list
> Bf-funboard@blender.org
> http://www.blender.org/mailman/listinfo/bf-funboard
> 
> _______________________________________________
> Bf-funboard mailing list
> Bf-funboard@blender.org
> http://www.blender.org/mailman/listinfo/bf-funboard 

Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og virusscan