Multi threading problem with Distant land
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?
I couldn't really tell as vanilla doesn't use my cpu well
- What is your operating system?
Windows 11 Pro 21H2
- What version of OpenMW are you using? If you used a bleeding edge build, state the exact revision used.
0.47.0
- 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?
GOTY Edition from gog, english
- Do you use any mods? If so, does the problem also occur in a clean vanilla install without any mods?
I use mods, and it doesn't occur.
- What are the exact steps to reproduce the problem?
Using distant lands with 4 cells (viewing distance = 28635), which are the only settings with resolution and mouse sensitivity I changed.
Loading the game in Balmora, then travel or quick save to Vivec
- What did you expect to happen? What happened instead?
The use of 3 of my cpu cores goes down as the last one goes to 100%, which doesn't happen if I travel to Vivec on foot.
I can precise that the number of draw calls go from around 11 to 20. The fps obviously take a serious hit.
- 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: