Incorrect frustum culling at non-16:10 screen resolutions
If you're reporting an issue specific to a fork, e.g. TES3MP for multiplayer or OpenMW-VR for OpenXR VR, please report it to that fork's author instead of here.
If you're reporting an issue specific to an open merge request, the comments for the merge request are probably a good place to report.
Describe the issue as detailed as you can. Below is a list of questions that should be answered in the description (if they apply).
-
Is the problem OpenMW specific or does it also happen in vanilla Morrowind?
- OpenMW-specific
-
What is your operating system?
- macOS 10.15.7
-
What version of OpenMW are you using? If you used a bleeding edge build, state the exact revision used.
- 0.48.0 revision 64d925ea
- (the problem does not occur in 0.47 release)
-
What version of Morrowind are you using (i.e. retail CD or Steam)? What addons (Tribunal, Bloodmoon) do you have installed? What language is your Morrowind install?
- retail GOTY CDs, Morrowind + Tribunal + Bloodmoon
-
Do you use any mods? If so, does the problem also occur in a clean vanilla install without any mods?
- Problem occurs with no mods and a default settings.cfg
-
What are the exact steps to reproduce the problem?
- Set the video resolution to anything with an aspect ratio other than 16:10. My display's native resolution is 3072 x 1920 (16:10). The problem is most noticeable at 1024 x 768 (4:3).
-
What did you expect to happen? What happened instead?
- Frustum culling removes objects far too early as I move the camera around.
- Untitled
-
Are there any error messages in your
openmw.log
file?- No
-
Where is the in-game location this problem can be observed? Avoid vague statements such as "west of town X". Instead, open the console (
`
key by default, the key above Tab), click on the problematic object, then use the betacomment (bc
) instruction to get useful information about the object that you can copy and paste into the bugreport:- Anywhere