yep it's definitely broken black screens and is unresponsive and then when you exit the game all your mods are disabled

Ts does not work

你好,这个mod似乎和外星人冲突了(Humanoid Alien Races),即使只有core ,这个mod,和外星人都有可能进不去
Hello, this mod seems to conflict with aliens (Humanoid Alien Races). Even if you only have the core, this mod and aliens may not be able to enter.

ломает игру

Jesus, this mod broke my game. corruption, error hell, and literally causing rimpy to cry.

0/10 mod holy error hell

Id love this mod to be the loading screen. also im suprisedno one had made a mod for TPS & or Fps Impact for troubleshooting game perfomance tanking

I released an update

It's amusing to see the stuff about the "not measured" as I came to the comments here to check about the same thing. I do have a mod list that approaches 1000. However, nearly 3/4 of the total startup time is exactly that, and it's mildly frustrating to see. On the note of it being other things, like minimizing and other monitors or whatever, I do have 4 total monitors, but I also leave my entire computer alone when starting up the game. Since I've had the game outright crash about 90% of the time when trying to minimize and to other things while it loads up.

The mod does give me an idea of the biggest things within what it DOES track, but that much is negligible anyways. Not sure if that can be fixed up at all, mind you, but it does admittedly remove much of the reason for using the mod in the first place.

@nitrogenFox The not measured problem is presumably the same as with the original mod, the issue being that the mod does not track properly many parts of RimWorld startup.

This mod has never been very useful AFAIR. Just use devmode's verbose logging.

Yea.. im having trouble compiling it. That's the problem

While examining the DLL files, I noticed that the content within the DLL did not match the source files submitted. Specifically, it still contained the check for thread ID. Consequently, I attempted to recompile the content from the source. After using the newly compiled DLL, the 'thread id too large' issue disappeared. The 'not measured' issue still persists, but its duration is significantly shorter compared to before the recompile (this might be due to something on my end, as I'm unsure what caused a brief period of unresponsiveness during loading). I don't know whether the author forgot to upload the new DLL or if I compiled an unreleased version. In any case, I'm satisfied with the result from the recompiled version.

Hmm weird. I will look soonish at the not measured stuff and the thread id too large

That's just a cap. I don't have a second monitor, I started the game went to do something else and came back and the game loaded in. It still says "not measured" is like 60% of the time spent loading.

The "not measured" shows up if the game is not in focus, so if you're alt-tabbing or using your second monitor etc.

What is the "Not measured" section in the readout supposed to represent? It's the vast majority of my startup time, and I get no information about it. Am I doing something wrong or am I missing something here? Why is there startup process not measured in the first place?

Just had my friend try the new update. It still errors with "thread id too large", but it does seem to work. If you click on the link on the side to open the window, it seems it tracked things. The error spam makes the rest of the log unreadable though. One would have to copy the whole log to clipboard to see it, or check the Player.log that RimWorld generates.

I don't know, I've never used Loading Progress. Or atleast, once, and it was too buggy for my taste. I think there should be no problem using both.

is this compatible with Loading Progress? or even necessary to use both?

Updated it

Oh wait. Haha, I was busy making thread optimisations, but was busy with other stuff. The original creator multithreaded this mod, but that doesn't really work that way on RimWorld (maybe only with RimThreaded). So I made it just single threaded, I had it in my current playlist. So I didn't have these errors. Woopsie daisy. I will test it a little bit and update the mod

@averrin man, I don't know what to say. Both things, are awesome. I will patch the suggested fix as soon as possible. And the PoC of RimSort is just really awesome! Thanks man, appreciate it!

I am also getting a massive number of "Thread ID is too large" errors. Mod list is 504 long.

And created a PoC of integration with RimSort
https://github.com/RimSort/RimSort/issues/1160

It worked after changing it to 5k
I also encountered translation errors (gui showed only translation keys, and it breaks actual numeric values). But maybe it is something on my side, i never worked with mods before this time)

Looks like it won't work for big mod lists because of this line:
https://github.com/WimStienstra/StartupImpactContinued/blob/master/Source/Profiler.cs#L40
If it is the only issue, it should be easy to fix

Thank you for updating this.

I use this to determine if I should cut back on the crack, I mean mods.

I'll have a look

On a list of 656 or so mods, there were a lot of "Thread ID is too large" errors, coming from this mod. Does this only work on smaller lists? It's my friend's list. He wanted to see what was taking so long in his 9-minute boot, but it error'd too much to be useful.

Mod is below harmony and core, but i still get a bunch of errors saying "Thread Id too large" and numbers, when i go to the mod settings, nothing shows up other than the "categories"

oh ok thanks

@NeinDao Definitely not. To clarify, this mod counts the time it takes to startup (if you have if focused, very important). That's all it does. What you can use it for, is to know what mod takes the longest to start, so you can improve your load times by removing one of those mods for example.

It's just a startup time detection tool, Not anything to fix.

is this better than rimpy?

Just before this mod came out I was looking for a 1.6 version. Thanks