Search found 2353 matches
Is the new version you've tried 0.47, a dev build, or a 0.48 release candidate? We've made some changes to some text encoding stuff recently, so there's a chance we've broken the situation where the local eight-bit encoding doesn't match the game encoding.
- 26 Nov 2022, 01:37
- Forum: Organisation and Planning
- Topic: Folders in OpenMW launcher mods
- Replies: 1
- Views: 62
What you're describing are really mod manager features. There are issues with making our launcher into a mod manager, such as: It being a massive task - there are mod managers that have far more lines of code than OpenMW does. What makes a mod manager good is highly subjective - the best mod manager...
In the openmw.cfg in the same directory as the OpenMW binary, you'll find this: data-local="?userdata?data" user-data="?userdata?" config="?userconfig?" Change it to data-local="./data" user-data="./userdata" (including getting rid of the config line...
- 15 Nov 2022, 00:24
- Forum: Feature Requests and Suggestions
- Topic: Suggestion: Add a default content pack to downloads section to help get wider exposure and contributions
- Replies: 1
- Views: 212
Re: Suggestion: Add a default content pack to downloads section to help get wider exposure and contributions
We've got the Example Suite that's on its way to becoming this, and has a couple of regular contributors, but unsurprisingly, making something like this from scratch is a big task. We can't really use anything from existing mods as even in the rare cases that mod authors are okay with opening up the...
I don't think the people maintaining the part of Mesa that deals with cards this old are actually AMD employees, so it might not matter that AMD doesn't care as someone else might. In fact, I think AMD's contributions to the open-source drivers for their cards didn't start for years after these card...
The filesystem on the Deck isn't set up in the normal way by default, so certain paths that are usually read/write, but not strictly required to be, end up read-only, and this trips up quite a bit of software.
There's a decent chance this is down to a bug in the graphics driver, and it might have shown up when using OpenMW just because OpenMW happens to do a sequence of calls that none of the other applications you normally run ever do. If you report the problem to Mesa, they might have some idea of troub...