Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Actually, they'll always stay greyed out, even when something is fully researched.
https://gist.github.com/HugsLibRecordKeeper/b1e95200f6ad90d75bd5aaae9f9674e0.
Thanks for the effort and great mod!
https://pastebin.com/EjEB1uui
Thanks for the mod!
I'm using Research Powl for the research UI, so if it's a conflict there, my apologies.
Repro:
1. Load a game
2. Select a pawn. Right click something (ex. prisoner or items).
3. Observe Player.Log is flooded with 100s of "GUI Error: You are pushing more GUIClips than you are popping." a second.
4. Observe FPS drops by 100+ when context menu is open.
Fix:
Once right click menu is closed the FPS returns and Player.Log is no longer flooded
Context:
- 50+ mod list (bug is avoided if this one is off): https://pastebin.com/D19PTLWj
- Currently research project is carpets which has a massive list
- I disabled needing research kits
Ive had a few other reports of NREs (unfortunately with much bigger modlists), so itd be helpful for narrowing it down.
My suspicion is either really long lists or this special case that isn't handled: https://i.imgur.com/C9CVose.jpg
Here's a log with no more spam https://pastebin.com/7chdyi8w
Frame_CompleteConstruction_Patches - TranspilerForQuality - failed to apply patch (instructions not found)
And some like this:
GenRecipe_PostProcessProduct_Patches - failed to apply patch (instructions not found)
Unfortunately, I don't see an easy way to track down the mods with issues apart from doing the old binary search method...
Would it be possible to please log the name of the research where patching fails? This would make it a lot easier to quickly spot mods that have issues so I can cull them and keep this awesome mod instead :)
Thanks!
If you grab a hugslib log, it has all patches including transpilers listed for every patched method near the top. You can use that list to narrow it down to mods that transpile the same methods - moving research reinvented above those should fix the issue. Either way Id appreciate the hugslog so I can track it down myself.
Edit: Log file is here -
https://gist.github.com/HugsLibRecordKeeper/7761f976dd880126845e8e46c415e46b
At a glance, I'm guessing it's PerformanceOptimizer as that seems to touch a ton of things.
I went the easy route and made a personal RimPy rule to move Research Reinvented up just under Allow Tool and that seems to have resolved all of the messages.