[Bf-committers] Viewport project - plan of action

[Jacob Merrill]

The upbge team would like to work closer with the viewport team,

maybe the upbge team can have a 2.8 ge branch in upbge git that pulls down
from your branch?

Whenever you think the new draw calls are ready I am sure panzergame and
youle and twister_GE are ready to integrate it.

panzergame has done quite a bit of drawing code mods in upbge
maybe some of these commits can help the viewport team?

Will the game engine be using evee?

On Dec 16, 2016 8:29 PM, "Mike Erwin" <significant.bit at gmail.com> wrote:

> Jacob Merrill <blueprintrandom1 at gmail.com> wrote:
>
> > will instancing and static draw call batching be planned for the realtime
> > render?
> >
>
> Not sure to what extent we can do these, but high performance & low
> overhead continue to be goals. This includes instancing & sharing draw
> data. Remember that this is primarily for editing/creating. Game engines
> have a natural performance advantage vs. an interactive viewport.
>
> is forward+ rendering possible with a 3.2 glsl profile?
> >
> >
> If so we'll have to use OpenCL for the light culling part. GLSL doesn't
> provide compute shaders until version 4.3. Btw we're targeting GL 3.3 now,
> a small step up from 3.2.
>
> Mike Erwin
> musician, naturalist, pixel pusher, hacker extraordinaire
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>