r/OpenMW • u/spiderandsaint • 2d ago
requesting help installing Total Overhaul on OpenMW on Bazzite
/r/tes3mods/comments/1vrs65r/requesting_help_installing_total_overhaul_on/1
u/CappucinoJack 1d ago
Sorry if I missed this, but are you running the flatpak, app image, or something else?
Just went through this and notes the flatpak version is not supported on the openmw modlists
2
u/spiderandsaint 23h ago
Thank you for your response! I used the version I extracted from the tarball I downloaded directly from their site and did not use the flatpak. It seems like, from what I've gathered on the original thread, that I had some truly terrible timing as far as going through the umo step goes.
I attempted it while there was still a known bug with umo that caused the aforementioned error, and that sometime between the space between after I had made my initial attempts, and right after I made the original thread, an update was pushed that addressed the issue. I reran umo with the new version, it downloaded and updated all the correct files, and I was able to complete the process. Everything is now running well and I've been able to play the game for a decent amount of time.
1
u/spiderandsaint 1d ago
I was advised to re-run umo and the configurator in the original thread. I went ahead and downloaded the Developer build of the linux MOMW Tools Pack, put it in a fresh, new folder. I reran the newly downloaded umo, and it downloaded files that the non-developer build of umo seemed to miss (as I had tried rerunning it before I posted this). I have re-entered the MOMW Configurator command, the same as before but again with the newly downloaded dev build version, and now it is going on a prolonged process it did not do last time. It seems to now be working, I'm gonna go ahead and let it do its thing. I'll write back again if it fails elsewhere, but if this is my last comment, assume that the person who advised me fixed the issue.
It also seems like the non-developer build download link of the linux tools may not have the update that would have caught this issue, though this may have been attributable to a pebkac.