Comments on: Developer Meeting Notes (Blender 2.5 Report) 11-08-09

By: shawn kearney

shawn kearney — Thu, 12 Nov 2009 17:14:41 +0000

hey guys. I don’t mean to nag. I really don’t. And I know that you developers have so much more important things to be doing. But…

I really like using blender nodes in my photography workflow. I know it’s weird, and I’m prob the only one doing any type of serious work this way, but for some things, blender works really well.

I’d really like to start using Blender 2.5 as it is more stable when dealing with large images in complex pipelines. I want to use blender’s built-in color management. And 2.5 is so close to being useable for this, as far as I can tell, except for one thing that makes it completely unusable for me.

Please fix the image editor mouse release bug. The bug number is 19514. If this is a difficult fix for some reason I understand you have bigger “difficult” things to do. But if it’s an easy thing to do, and I’d imagine it would be, please, pretty, pretty please can someone out there fix this?

By: nemesis

nemesis — Thu, 12 Nov 2009 09:36:23 +0000

Brilliant, thank you for sharing your good work.

By: Vladimir

Vladimir — Wed, 11 Nov 2009 13:56:48 +0000

@Spamagnet: Lighting – sorry.

@playbass06: You can see textures, but you don’t see the actual real time lighting, so when you move objects or lamps, the light does not move with it. Which would be the most important update (in terms of how easy it would be to work with Blender)

By: playbass06

playbass06 — Tue, 10 Nov 2009 06:01:48 +0000

@vladmir:

I thought this was already possible, just use the GLSL shaders and texture draw mode for a rough preview. Or Shift+P for a preview render window.

By: Socceroos

Socceroos — Mon, 09 Nov 2009 23:15:29 +0000

I agree with calling it an alpha release. Also, I agree with Gryphon’s comments regarding the issue with 2.5 and 2.6.

By: Blob4

Blob4 — Mon, 09 Nov 2009 21:27:38 +0000

For the BGE Node Input/Output:

There is the OSC protocole to take in consideration as several interesting programs are already able to handle it, notably PureData (via an external) wich is an increadible multimedia prototyping software.

By: Gryphon

Gryphon — Mon, 09 Nov 2009 20:37:46 +0000

It doesn’t really matter what they call it at this point. What gets confusing is, at the end of all this, what do they call the “final” release? If the plan is to work toward a 2.60 version, this upcoming release should be called Blender 2.60 Beta 0 (followed by 2.60 Beta 1, etc.). Or, from the other perspective, if we have a series of 2.5 alpha/beta releases, the “full” release (next year?) should be Blender 2.50. A pre-release version number should match that of the final release — it just makes sense.

@Iconoclast:
I’m in for the next game project, too. Yo Frankie! resulted in way too much BGE goodness to be ignored.

PS: I’m glad Blendernation is back up. It was scary when it was missing this morning.

By: rgdfhdfhdryerztetz

rgdfhdfhdryerztetz — Mon, 09 Nov 2009 20:25:11 +0000

If there are more features going to be implemented, it’s best to call it an alpha.
+1

By: dude

dude — Mon, 09 Nov 2009 16:00:04 +0000

let’ s stick with alpha. +1

By: Iconoclast

Iconoclast — Mon, 09 Nov 2009 15:38:31 +0000

Thanks for the notes!

Spamagnet: Maybe the n key sticks? :D

I think alternating the open movie to open game pattern would help to keep blender current in both respects, but that would slow down the production of both. But I guess what I’m trying to say is:

Where do I stick my money in for an open game to happen again?

(as if it matters, we all know I’m going to stick money in until something happens. and then do it again. ;)