Unfortunately both the game and MCCC also show LE, something may be wrong
Viewing post in v3.7 Update - Alien Pollination and Expanded Fears comments
Ah, gotcha. I'll try installing BE and see what comes up on my end of things. Would you also be able to send over a copy of your system info log from MCCC?
Edit: I installed BE and still didn't have any warnings or LEs on game start, and no issues with that file during gameplay. I may need both the system info log and sim info log from MCCC to diagnose what's going on (MCCC -> Sim Commands -> Logging Commands, the file will appear in your MCCC folder).
Also, if you use BE to check for conflicts, do you see any conflicts with AR files?
Sure,
- Last Module Called: exceptions_feedback.py
- Last Function Called: _on_exception_occurrence
- Error message: [BE Interceptor] BE intercepted this error from a separate mod log so that it can scan for the issue. (TypeError: 'NoneType' object is not iterable), CategoryID: exceptions_feedback:18
- Last Module Called: mc_woohoo_tuning.py
- Last Function Called: change_buff
- Error message: (TypeError: 'NoneType' object is not iterable), CategoryID: mc_woohoo_tuning:779
Pretty Error CallStack (Click to expand/collapse)
injector.py
_wrapped_function
26
.\WickedWhims_v186.3\turbolib2\services
affordances_service.py
_turbolib_on_tunable_class_tuning_load
498
InstanceManager_buff
E:\Builds\MCCC_2025_1_1\mc_cmd_center
mc_injections.py
inject_load_data_into_class_instances
362
E:\Builds\MCCC_2025_1_1\mc_cmd_center
mc_injections.py
_process_woohoo_tunings
526
E:\Builds\MCCC_2025_1_1\mc_woohoo
mc_woohoo_tuning.py
change_buff
779
<mc_woohoo_tuning.WoohooTuningInjection object at 0x00007FF3D591A150>
| Module | Line | |
|---|---|---|
Ah, I suspect this is a compatibility issue with MC Woohoo and possibly Wicked Whims, then. Most likely they're trying to change some of the pollination coding that I've tweaked. I can try redesigning some parts of this to get around MC Woohoo's intended changes, but because that's all in Python I have limited visibility into exactly what's going on. I don't use either of those so didn't run into any issues.
Good news is that this was a feature update, so you're safe rolling back to v3.62. If you've deleted that, it's still available on Nexus under old versions: https://www.nexusmods.com/thesims4/mods/2342?tab=files