I recently upgraded to a 4K monitor. NCrunch does not render its controls properly in its tool windows. Attached are pictures that demonstrate the issue better than I can describe. If I slightly resize the tool window, NCrunch will adjust its controls. If I debug (which doesn't have the NCrunch tool windows) when I come back, the controls are too small for the window again. It's minor, but it is very annoying over time.
Notice the large amount of dark gray background around the controls:
[img=https://i.pixi.mg/i/5a60c8206adc669b19470f01.png]4K UI issues[/img]
[img=https://i.pixi.mg/i/2d1d030be834f5003d9c82eb.png]4K Progress[/img]
Daily Usage Issues
NCrunch Tool Window UI in VS2026 invalid on 4K monitor
Started by robmen on 10,819 views
Remco NCrunch Developer
#18667
25 Feb 2026 23:04 UTC
Hi, thanks for sharing this issue.
Can you confirm what your DPI settings are? Also your IDE version? Do you have multiple screens?
Can you confirm what your DPI settings are? Also your IDE version? Do you have multiple screens?
Display
3840x2160@60Hz at 125%
IDE
VS2026 18.2.2
Multiple screens:
Yes, three total, the other two are both: 2560x1440@60Hz at 100%
3840x2160@60Hz at 125%
IDE
VS2026 18.2.2
Multiple screens:
Yes, three total, the other two are both: 2560x1440@60Hz at 100%
Remco NCrunch Developer
#18669
25 Feb 2026 23:15 UTC
Thanks for confirming this.
In VS, under Tools->Options->All Settings->Environment->Visual Experience, you'll see an option called 'Optimize rendering for screens with different pixel densities'. If you disable this setting and restart the IDE, does this resolve the problem?
In VS, under Tools->Options->All Settings->Environment->Visual Experience, you'll see an option called 'Optimize rendering for screens with different pixel densities'. If you disable this setting and restart the IDE, does this resolve the problem?
NCrunch does render its controls properly with that setting disabled. VS is also noticeably blurrier and hard to look at. After reenabling the setting (and restarting VS again), NCrunch controls rendered properly for a moment, then snapped to their broken sizes.
Remco NCrunch Developer
#18682
26 Feb 2026 23:12 UTC
Thanks for confirming this. I'm hoping you might be able to share some more details to help me understand where in the lifecycle it's getting out of sync.
- When you first start the IDE and open your solution, do any NCrunch tool windows that are automatically shown on the screen have the correct layout?
- If you specifically open a tool window (that was previously closed), does it open with the correct layout?
- When you drag windows between screens with different DPI settings, do they adapt their layout correctly?
- You mentioned that resizing a tool window fixes the layout. Does it stay fixed for the remainder of the session? Is there anything that breaks it again?
I'm not sure if this is easy for you (don't bother if it's hard), but it would also be interesting to know if you experience the same behaviour under VS2022.
- When you first start the IDE and open your solution, do any NCrunch tool windows that are automatically shown on the screen have the correct layout?
- If you specifically open a tool window (that was previously closed), does it open with the correct layout?
- When you drag windows between screens with different DPI settings, do they adapt their layout correctly?
- You mentioned that resizing a tool window fixes the layout. Does it stay fixed for the remainder of the session? Is there anything that breaks it again?
I'm not sure if this is easy for you (don't bother if it's hard), but it would also be interesting to know if you experience the same behaviour under VS2022.
1. No. All of them are wrong when opening the solution
2. Opening an NCrunch tool window does display correctly. If I close a broken NCrunch tool window and open it again, it also displays correctly
3. Dragging NCrunch tool windows across monitors works correctly
4. It does get broken again when I debug (NCrunch tool windows are not displayed in debug mode). Aha! Opening any NCrunch tool window will break the "Trace Output" of the NCrunch tests window. In fact, dragging any tool window to another monitor breaks the "Trace Output" window. Also, undocking any tool window will break the NCrunch "Trace Output" window. There are a lot more ways it gets broken than I realized, which explains why I felt like this was happening more often than when I restarted VS.
I'd have to dig VS2022 out of mothballs... but could try if it would really be helpful.
2. Opening an NCrunch tool window does display correctly. If I close a broken NCrunch tool window and open it again, it also displays correctly
3. Dragging NCrunch tool windows across monitors works correctly
4. It does get broken again when I debug (NCrunch tool windows are not displayed in debug mode). Aha! Opening any NCrunch tool window will break the "Trace Output" of the NCrunch tests window. In fact, dragging any tool window to another monitor breaks the "Trace Output" window. Also, undocking any tool window will break the NCrunch "Trace Output" window. There are a lot more ways it gets broken than I realized, which explains why I felt like this was happening more often than when I restarted VS.
I'd have to dig VS2022 out of mothballs... but could try if it would really be helpful.
Remco NCrunch Developer
#18686
27 Feb 2026 07:09 UTC
Thanks for all your help in pinning this down. I can reproduce the problems now exactly as you've described them. At the moment it doesn't look like this will be simple to fix. I'll let you know when I have more information on a resolution.
Remco NCrunch Developer
#18692
02 Mar 2026 02:55 UTC
Would you be interested in trying the build below to see if this solves the problem for you?
NCrunch_Console_5.21.0.5.msi
NCrunch_Console_5.21.0.5.zip
NCrunch_GridNodeServer_5.21.0.5.msi
NCrunch_GridNodeServer_5.21.0.5.zip
NCrunch_LicenseServer_5.21.0.5.zip
NCrunch_Rider_5.21.0.5.7z
NCrunch_Rider_5.21.0.5.zip
NCrunch_VS2017_5.21.0.5.msi
NCrunch_VS2017_5.21.0.5.msi.7z
NCrunch_VS2017_5.21.0.5.zip
NCrunch_VS2019_5.21.0.5.msi
NCrunch_VS2019_5.21.0.5.msi.7z
NCrunch_VS2019_5.21.0.5.zip
NCrunch_VS2022_5.21.0.5.msi
NCrunch_VS2022_5.21.0.5.msi.7z
NCrunch_VS2022_5.21.0.5.zip
NCrunch_VS2026_5.21.0.5.msi
NCrunch_VS2026_5.21.0.5.msi.7z
NCrunch_VS2026_5.21.0.5.zip
NCrunch_Console_5.21.0.5.msi
NCrunch_Console_5.21.0.5.zip
NCrunch_GridNodeServer_5.21.0.5.msi
NCrunch_GridNodeServer_5.21.0.5.zip
NCrunch_LicenseServer_5.21.0.5.zip
NCrunch_Rider_5.21.0.5.7z
NCrunch_Rider_5.21.0.5.zip
NCrunch_VS2017_5.21.0.5.msi
NCrunch_VS2017_5.21.0.5.msi.7z
NCrunch_VS2017_5.21.0.5.zip
NCrunch_VS2019_5.21.0.5.msi
NCrunch_VS2019_5.21.0.5.msi.7z
NCrunch_VS2019_5.21.0.5.zip
NCrunch_VS2022_5.21.0.5.msi
NCrunch_VS2022_5.21.0.5.msi.7z
NCrunch_VS2022_5.21.0.5.zip
NCrunch_VS2026_5.21.0.5.msi
NCrunch_VS2026_5.21.0.5.msi.7z
NCrunch_VS2026_5.21.0.5.zip
I was also seeing strange layout in one of my projects: the trace output/execution steps splitter became vertical and that pane moved over to the right.
I tried the build in this thread but it made no difference. What fixed it was a `git clean -xdff`
I tried the build in this thread but it made no difference. What fixed it was a `git clean -xdff`
Remco NCrunch Developer
#18741
18 Mar 2026 22:15 UTC
sjkirk wrote:I was also seeing strange layout in one of my projects: the trace output/execution steps splitter became vertical and that pane moved over to the right.
I tried the build in this thread but it made no difference. What fixed it was a `git clean -xdff`
There is an option on the toolbar that enables this mode (vertical layout). It's saved in your NCrunch user config file, which would likely be discarded or reset by the git clean command.
Post a reply
Log in to reply.