It glads me a lot to hear that theres focus on performance early on, personally the biggest issue that Ive had with the current Eevee implementation is how GPU hungry it quickly gets as soon as either shader graphs are even remotely complex or as soon as you start getting up in the millions for polycounts (in addition to using a few lights and expensive rendering effects that all add up).
So the plan is not to merge a full featured engine, but to move its development into master while polishing what has already been done. I would also like to state that even after all this time, there are still features in research phase. Simply having something drawn will take a lot of sub-modules to be ported. Other milestones are yet to be defined because of their order and dependency. This should be testable with the old engine and should not bring any regression. This part of the code cannot be branched depending on the render engine. This means making the new BSDF paradigm compatible with the old eevee codebase. The first milestone is to merge the codegen changes. This has already been done over time and the changes were quite local to the modules. The zero milestone was to merge the GPU and DRW module changes. However, I do not expect to deliver a fully featured engine anytime soon given my other duties. We currently do not enforce this requirement for the rest of Blender but this is likely going to change in the next release (or the one after).įor each milestones, I will be collecting feedback. It is important to notice that EEVEE-next will require OpenGL 4.3 support minimum. The engine is hidden under an experimental option that you need to enable in the preference panel under the experimental tab (only visible if developer extra is also enabled). Each steps will be commited to master and will be ready to be tested under the new (temporary) render engine named “EEVEE next”. We are now entering a phase where we think it is better to merge it to master to better review each feature and make the developpement less abstract. This topic is about communicating about the state of the EEVEE rewrite.įor about a year now, EEVEE rewrite has been conducted in a dedicated branch.
0 kommentar(er)
