Can't save rule

[lagun]

Version

1.4.1

Windows Version

Windows 11

Reproduction Steps

Threadpilot didn't remember my save rule.
I always set cpu priority everytime when lauch rimworld.

Expected Behavior

remember my rule.

Actual Behavior

Not remember my rule.

Logs and Diagnostics

No response

[PrimeBuild-pc]

Thanks for reporting. I'll fix it as soon as possible.

[PrimeBuild-pc]

Thanks for the report — we verified that saving and loading persistent rules works correctly in general, including CPU priority settings.

Could you please help us narrow this down?

1. Try creating the same CPU-priority rule for another running app or game.
2. Restart ThreadPilot and check whether that rule is still present and applied.
3. Let us know whether the issue happens only with RimWorld or also with other executables.

For RimWorld specifically, please also share:

• the exact process/executable name shown by ThreadPilot;
• the full executable path, if available;
• whether you launch it through Steam or another launcher;
• any ThreadPilot logs captured just after starting RimWorld.

This will help determine whether the saved rule is not matching the actual game process, or whether applying the priority is failing for that process.

[lagun]

I tried with privazer and CPU-priority rule work but not rimworld. i guess other app work fire too.

when open computer and Frist launch it work.

close and launch again not work. will work again when restart and Frist launch.

[PrimeBuild-pc]

Thank you — this is very helpful. Your screenshots confirm that the rule is being found and the auto-apply path is running for RimWorldWin64 (the activity log reports successful auto-apply), so this is not a rule-saving or executable-name matching problem.

However, the process is shown as Normal priority afterward. We will investigate why the priority is being reverted or why a successful apply is being reported without the value remaining in effect, especially across closing and relaunching the game.

The executable path and process name in the screenshots are exactly the details we needed. No further action is needed from you for now.

[PrimeBuild-pc]

Thanks again for the detailed screenshots and for helping us investigate this.

I’ve attached a private diagnostic build of ThreadPilot. This is not a final hotfix or public release yet.

The build includes additional verification around saved CPU-priority rules. Previously, ThreadPilot could report that a rule had been applied as soon as the priority-setting call completed, without confirming whether the process actually remained at that priority afterward.

This diagnostic build now checks the requested priority immediately after applying it, and again after short delays. It helps us distinguish between:

• the requested priority never being observed;
• the priority being applied and then reverting shortly afterward;
• the process exiting or becoming unavailable during verification;
• another ThreadPilot configuration applying a different priority afterward.

Before testing

Please extract the ZIP into a separate new folder and run ThreadPilot from there. Please do not overwrite your normal installation.

Before testing RimWorld, please check that there is no other ThreadPilot configuration for RimWorldWin64 that could set CPU priority to Normal, such as:

• a power-plan association;
• a saved process profile;
• a duplicate persistent rule;
• any other manually configured priority action.

For the cleanest test, keep only the persistent rule that sets RimWorldWin64 to High.

Test 1 — comparison application

Please first test one application that you already know works correctly with ThreadPilot, such as PrivaZer.

1. Close the application completely.
2. Keep ThreadPilot open with monitoring enabled.
3. Start the application.
4. Check the process priority after it appears.
5. Take screenshots of the process list and Activity Log:
   • immediately after it appears;
   • about 1 second later;
   • about 3 seconds later;
   • about 10 seconds later.

Test 2 — RimWorld

Then repeat the same test with RimWorld:

1. Close RimWorld completely.
2. Keep ThreadPilot open with monitoring enabled.
3. Start RimWorld normally through Steam.
4. Take screenshots of the process list and Activity Log:
   • immediately after RimWorldWin64 appears;
   • about 1 second later;
   • about 3 seconds later;
   • about 10 seconds later.

Please include all activity/log entries related to RimWorldWin64, especially any messages containing:

• requested priority;
• observed priority;
• verification phase;
• PID;
• rule ID;
• “not observed”;
• “verification unavailable”;
• “reverted”;
• access-denied or process-exited errors.

What we need back

Please reply with:

1. Whether the comparison app stayed at High;
2. Whether RimWorld showed High immediately after launch;
3. Whether RimWorld later returned to Normal, and at approximately what time;
4. Screenshots for both tests;
5. The relevant Activity Log lines for both applications;
6. Confirmation that no other ThreadPilot rule, profile, or association was configured to set RimWorld to Normal.

These results will let us determine whether this is:

• a general application issue;
• a priority value being overwritten by another ThreadPilot configuration;
• a real post-launch reversion caused outside the saved-rule path;
• or a UI/reporting issue.

Thank you again — this information should give us a much clearer basis for the next fix.

Download here

[lagun]

All default setting. test with ThreadPilot-1.4.1-priority-diagnostics-test-win-x64
privazer. i don't get any warning log.

RimWorld showed High

RimWorld returned to Normal.

[PrimeBuild-pc]

Thanks — this is enough information for us to proceed.

The diagnostic logs confirm that ThreadPilot successfully applies and verifies High priority first, but the same game process returns to Normal a few seconds later. Since your ThreadPilot settings are otherwise at their defaults and PrivaZer does not show the same behavior, we have isolated the issue to a post-start priority reversion rather than rule saving, process detection, or the user interface.

We are now working on a general improvement that can detect and handle this kind of post-start reversion without adding a RimWorld-specific workaround. No further testing is needed from you at the moment. Thank you again for the detailed screenshots.

[PrimeBuild-pc]

Thanks again for the diagnostic results.

I’ve attached a new private test build of ThreadPilot.

This build includes a general improvement for cases where a process initially accepts a saved CPU-priority rule, but then changes its own priority shortly after startup.

What changed:

• ThreadPilot still applies and verifies the saved priority normally.
• If the same process later changes from the requested priority back to another value, ThreadPilot now performs one limited retry.
• The retry is only attempted once for that process launch.
• ThreadPilot then verifies the final result again.
• It does not use continuous polling or unlimited retries.

This is not a RimWorld-specific workaround. It is a general behavior for any process that resets its priority shortly after startup.

Please test RimWorld once

1. Extract the ZIP into a separate folder.
2. Do not overwrite your normal ThreadPilot installation.
3. Start this new test build.
4. Keep ThreadPilot open with monitoring enabled.
5. Start RimWorld.
6. Wait at least 15 seconds.
7. Please send screenshots of:
   • the RimWorld process row and its final CPU priority;
   • the Activity Log entries related to RimWorldWin64.

Please select the related Activity Log entry so that the details panel is visible.

We are especially looking for messages similar to:

• priority verified as High;
• priority reverted to Normal;
• retry scheduled;
• retry verified as High;
• retry reverted again;
• retry skipped or retry failed.

Please also let us know whether RimWorld remains at High after waiting 15 seconds.

If the priority remains High after the retry, that confirms the new general handling works correctly. If it returns to Normal again, the logs will tell us whether the process is overriding the priority repeatedly or whether another configuration is involved.

Thank you again for helping test this.

ThreadPilot-private-diagnostic-test.zip

[lagun]

Test with ThreadPilot-private-diagnostic-test.zip

RimWorld showed High still remains at High after waiting 15 seconds. high all the time.

RimWorld showed High but show High after waiting 15 seconds. show normal at first and change to high after 15sec.

I think my problem solve. i just don't want to set to high manually but now threadpilot auto change from Normal to high after wait some second.
if you want more information or more test. please feel free to rest me know.

Thank you so much.

[PrimeBuild-pc]

Great, thank you for testing the new build and for sharing the screenshots.

The results confirm that the fix works as intended: ThreadPilot detects the post-start priority reversion, schedules one limited retry, verifies the retry successfully, and RimWorldWin64 remains at High priority afterward.

We’ll include this general fix in the next official release. It is not specific to RimWorld and will also cover other processes that reset their CPU priority shortly after startup.

Thanks again for your patience and for helping us diagnose and validate the solution.