It seems that I might understand what's going on and why it does not work, at least for me. If you use OneDrive, it uses virtual Documents folder, while "real" one is not used and usually empty. (Also Documents folder can be moved to other place even without OneDrive, so that's also might be an issue, just like having localized folder name) It works if you copy your openmw.cfg with same path into "real one", but issue seems to ultimately arise from virtual OneDrive synced folders.
Any hope you can also look for OneDrive documents folder in next version? Or, well, just allow to specify path to openmw.cfg in command line for executable? Thanks)
Not all light sources actually have the fade in/fade out (flicker) effect, the only ones that do are torches, how do I get lanterns and Candles to flicker?
I must join others to sadly say its not working. I guess the issue may be localized windows so if "My Documents" is in different language it wont find it and wont generate anything. Best and easiest thing for you would be to check for the file in same folder and users would run it from folder with config.
EDIT: I managed to overcome the issue. Until its fixed you must create exactly same folder structure and place config in there on your windows drive. So if you have windows on C drive you need this structure. If your folders are named different create new ones like this and put config in last one: C:\Users\*yourname*\My Documents\My Games\OpenMW\
The executable can't find the openmw.cfg, because it uses double slashes for some reason:
?
Would it be possible to let us specify the path to the openmw.cfg ourself, or have the executable run in the same folder as the openmw.cfg? This would probably be the easiest fix.
22 comments
It works if you copy your openmw.cfg with same path into "real one", but issue seems to ultimately arise from virtual OneDrive synced folders.
Any hope you can also look for OneDrive documents folder in next version? Or, well, just allow to specify path to openmw.cfg in command line for executable? Thanks)
EDIT:
I managed to overcome the issue. Until its fixed you must create exactly same folder structure and place config in there on your windows drive. So if you have windows on C drive you need this structure. If your folders are named different create new ones like this and put config in last one:
C:\Users\*yourname*\My Documents\My Games\OpenMW\
Would it be possible to let us specify the path to the openmw.cfg ourself, or have the executable run in the same folder as the openmw.cfg? This would probably be the easiest fix.