-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MO2.5 encounters an error on startup, but it seems to work normally. #1928
MO2.5 encounters an error on startup, but it seems to work normally. #1928
Comments
Did you use the installer to update? If you use the archive version and extracted over a 2.4 installation then you will need to clean old files manually, as explained in the release notes. |
I have tried multiple times to do a fresh installation, including changing the installation location, but it had no effect. |
It looks like it's trying to load a system python library instead of using the packaged python libraries. It really shouldn't do this by default, though at one point there was a setting to allow this. I do not recommend it. |
I conducted a rough and simple survey and came up with the following questions:
|
|
This is also happening to me, even after uninstalling, removing leftover files and reinstalling. MO is trying to use my user installation of Python 3.11, which I'm using for various stuff so who knows what state it's in. For now I downloaded an older version (Mod Organizer 2-6194-2-4-3-1640472667) that works perfectly fine. |
You can try going to the settings and then disable the Python proxy in the plugins. However, be aware that this will prevent all plugins that rely on Python from working. Alternatively, you can use an editor to open [INSTALL DIRECTORY]\plugins\basic_games\origin_utils.py and delete or comment out the line import psutil. Doing so will temporarily eliminate error reports. Regardless, this is just a temporary solution to alleviate the experience. It only makes the warning invisible but does not solve the underlying problem. Of course, you can also choose to ignore it, as it's just a minor warning. You may choose to wait for Silarn to address this issue in subsequent releases. |
Can you try the The file should go in |
it works, the error has disappeared. and after the error was fixed, the startup speed noticeably increased. |
Yeah, probably because it's no longer attempting to load every Python package on the system path. I'll probably put out a dev 2.5.1 build soon with a few fixes. |
I used MO2 a long time ago... probably 8 months or more since I used it. I was on version 2.2.1 if that helps with timing. I wanted to start clean so I installed into a new folder entirely. When I ran the exe, I got the same error listed above with freeze this and that. I downloaded this runner file and it worked - cleared all the errors. I don't know if that helps, but there you go. I have made some path file updates for python to support some development I was doing. I've also been playing with Stable Diffusion which may have involved some config that got in the way. I hope that gives enough detail to narrow down why some of us are getting errors. |
I'm not quite sure what you mean, but if you've encountered a similar issue, I suggest using version 2.4 until the update to 2.5.1. The root of the problem is the incorrect use of the system's Python by the Python proxy plugin, instead of the Python that's pre-installed in the plugin. Anyway, this issue will be fixed in the next version. If you still have similar issues, I recommend opening a new issue with your log. This issue will be closed, so please do not reopen or respond to it. |
It works, finally! Thanks my friend :) |
This fix has already been merged into version 2.5.1 RC 2, so theoretically, you shouldn't need to use the patch from this issue. |
I just found I was still using 2.5.0, so no wonder I met this issue... Thanks for your notice, I will try 2.5.1 instead. |
The problem:
It looked like it was trying to read my local environment's psutil and raised an unknown error
To Reproduce:
Steps to reproduce the behavior:
2.running MO2
3.Get error
Environment:
Details:
psutil version 5.9.6 has been installed in local environment(Python 3.11.6)
the path has been correctly set.
Link to Mod Organizer logs:
The text was updated successfully, but these errors were encountered: