Description
The problem:
Was trying to mod Cyberpunk2077 so I downloaded 2.5.2 version of mo2 and launched it. Instead I received an Error and I can't get past over 'Creating new instance'.
To Reproduce:
Steps to reproduce the behavior:
- Go to mo2 install folder
- Click on ModOrganizer.exe
- Error pops up
- Goes to create new instance
- Both portable/global instance creation choice won't recognize CP2077
Environment:
- Mod Organizer Version that exhibits the issue: 2.5.2
- Last Mod Organizer Version that did not exhibit the issue (if applicable): 2.4.4
- Desktop OS/version used to run Mod Organizer: WIndows 11
Details:
If necessary, describe the problem you have been experiencing with more details and pictures.
I've reinstalled steam itself, CP2077 multiple times and yet this happens. It mentions about UnicodeDecodeError: 'cp949' coded can't decode byte 0xec in position 245: illegal multibyte sequence and I have no idea how to fix it. Version 2.4.4 is having no issue on running. Python version installed is 3.11+ and Microsoft Visual C++ is 14.42.34438.
When I try to create new instance(both portable and global), it says Unrecognized game. The folder C:/Program Files (x86)/Steam/steamapps/common/Cyberpunk2077 does no seem to contain a game Mod organizer can manage..
Link to Mod Organizer logs:
Right click on the log window at the bottom of MO2, set log level to debug, restart Mo2 and reproduce the problem.
To access the log files you can press the Open folder icon over the modlist and select "Open MO2 Logs folder".
I can't get past the instance part, so unfortunately I don't think I can follow instructions above.
USVFS:
Create a GIST which is a paste of your latest USVFS log, and link them here.
Do NOT paste your full USVFS logs here, as it will make this issue very long and hard to read!
If you are reporting a bug, always include the USVFS logs!
I'm sorry I failed to find where the log is stored.
MO Interface:
Create a GIST which is a paste of your mo_interface logs, and link them here.
Do NOT paste your full mo_interface logs here, as it will make this issue very long and hard to read!
If you are reporting a bug, always include the mo_interface logs!
I'm sorry I failed to find where the log is stored.