Fixed in SVN:

BGE: Fix Orthographic mode and viewport scaling.

- The BGE now uses correct glOrtho projection for orthographic
camera.
Scale setting in camera data block represents the largest extent
of the
zone covered by the camera in game unit. This corresponds to
the outer
dotted line in the 3D view when viewing the scene through the
camera.
- Fix culling when using overriding camera is in orthographic
mode.
- Fix old culling method with orthographic camera
(normally not used since DBVT is the default culling method)
- Fix scaling problem with viewport:
camera in viewport would be scaled by 3D viewport scaling.
Viewport will now render the area within the outer dotted line
when viewing the scene through the camera.
- ImageRender did not take into account the aspect ratio
settings
in the render panel when computing the view frustrum.
ImageRender
will only render the area in dotted line as with viewport.
- Disable eye correction in stereo mode for orthographic camera:
stereo doesn't make sense for orthographic camera, so
orthographic
render will only be "on screen"

Author: ben2610
Date: 2009-05-14 15:47:08 +0200 (Thu, 14 May 2009)

Log Message:
-----------
BGE modifier: generate correct physic shape, share static derived mesh, share display list.

This commit completes the support for modifiers in the BGE.
- The physic shape is generated according to the derived mesh.
This is true for all types of shapes and all types of
objects except soft body.
- Optimization for static derived mesh (mesh with modifiers
but no armature and no shape keys). Replicas will share
the derived mesh and the display list: less memory and
faster rendering. With this optimization, the static
derived mesh will render as fast as if the modifiers were
applied.

Known Limits:
- Sharing of mesh and display list is only possible between
in-game replicas or dupligroup. If you want to instantiate
multiple objects with modifiers, use dupligroup to ensure
best memory and GPU utilization.
- rayCast() will interact with the derived mesh as follow:
Hit position and hit normal are the real values according
to the derived mesh but the KX_PolyProxy object refers to
the original mesh. You should use it only to retrieve the
material.
- Dynamic derived mesh have very poor performance:
They use direct openGL calls for rendering (no support
for display list and vertex array) and they dont't share
the derived mesh memory. Always apply modifiers on dynamic
mesh for best performance.
- Time dependent modifiers are not supported.
- Modifiers are not supported for Bullet soft body.

You can now use at least the color and energy values of lamp ipos (I haven't tested the others, but I don't think they'll work). Also, you can change the color and energy of lamps with Python. This isn't in any of the RCs though, but it will be in the next one.

ebrain a écrit:
Ils ont dit que ça serait une bonne technique pour faire des micropolys à la ZBrush par exemple.

TeTine a écrit:
Citation :

ebrain a écrit:
Ils ont dit que ça serait une bonne technique pour faire des micropolys à la ZBrush par exemple.

Qu'ouïs-je? Un Zbrush like pour le sulpt mode?
Ils ont donné des précisions la-dessus? ou alors c'est juste une possibilité éventuelle pour une 2.60-et-des-brouettes?

Technical targets
* High detail multi-res modeling (sculpting) and render (micropolygons?)
* Fire/smoke/volumetrics & explosions
* Compositing using tiles/regions, so it becomes resolution independent
* Crowd/massive simulation (fix animation system to allow duplicates)
* Improve library system for managing complex projects
* Deliver in 4k digital cinema (depending agreement with sponsor)
* Make the Blender 2.5x series fully production ready.