I’m working on a patch that adds a user preference setting for lowering the Eevee viewport resolution and I’d like it considered for inclusion in the official release. As described in this Right-Click Select submission (which I found after I started writing the patch), this feature is useful for GPUs which are not powerful enough to keep up with the resolution of the display. For instance, this applies to practically every currently-produced mainstream Macintosh model (and that’s why I had to write this patch).
The patch is functionally complete and this video shows the feature in action. However, if it were to be merged into the upstream, there are several issues that I think need to be addressed:
- A glitch is visible for a moment after adjusting the rendering scale. This is caused by an uninitialized texture and I think it can be fixed easily.
- For now I just added
struct UserDefby replacing
char _pad13. I’m not certain if this is the right way to do it.
- I saw an “out of framebuffer slots” error. This happened only once and I haven’t been able to reproduce it.
- The required changes might borderline the definition of “extensive”.
Would it be okay if I just submit the patch in the current state for initial review or should it be put on hold until agreement is reached somewhere else?