Won't Start: My documents is in another drive

[sweetsosweet]

It gives me an error saying openmw.cfg doesn't seem to exist, but it's looking in the standard "my documents" location on C: drive. I have my computer set to put "my documents" on another drive, which is where openmw automatically put my files. It's located at this address: G:\My Documents\My Games\OpenMW. As a workaround, if I copy my cfg file to the standard C drive location, will this tool still work as intended? Or do I have to get it to point to the right place?

Edit: I'm on Windows 10 if that makes a difference.

[jmelesky]

Interesting. I'm using a library to determine where your home directory is, and then going from there. I'll look and see whether there's a way for me to determine where your My Documents is when it's outside of your home directory.

In the meantime, you're right that it should work if you copy your cfg to a "My Documents" inside your user directory. However, it's very likely to create the new module in "my games\openmw\data" in the fake "My Documents", so you'll have to move it back to your real location.

I hope that workaround helps while I work on fixing the problem more generally.

[jmelesky]

I forgot to add: There is a -c command-line argument to omwllf.py which can be used to pass in the full path to the config file, if needed. That would skip you having to move or copy your conf file around.

Unfortunately, it doesn't solve the problem of the new module going into the wrong place.

I'm working today on two three things:

1. correctly detecting the My Documents directory on windows
2. adding a second command-line argument for module directory
3. updating the documentation accordingly

I'll update this ticket when that's done.

[jmelesky]

Okay, these changes are all in place, and the new version should work for your situation.

Thanks for reporting this, and please let me know if you have any problems in the future.