-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Describe the bug
This is a difficult one to pin down, even if it's simple to demonstrate. With Hammer (via P2CE) I am having a persistent issue where the amount of stuff drawn in the 2D view causes massive performance drops in the whole program. With nothing in the 2D views, it's perfectly smooth, operating up to and beyond my refresh rate. But as soon as things start to come into view in 2D, everything starts to suffocate. Here's a video that shows it pretty well:
2026-02-04.16-33-32.compressed.mp4
In general it's directly linked to how many individual lines (I guess) are being drawn in 2D, and it stacks over multiple viewports. Disabling vertices in 2D, for instance, improves the speed, as does disabling models. But even then, it still becomes unusably slow for a map of any appreciable size.
I am not able to test on different hardware presently. My current system is:
- CPU: Ryzen 5700X
- GPU: RTX 3060
- OS: Debian 13
- Drivers: Debian packaged nvidia driver 550
- Desktop: KDE desktop with X11 backend (also tried on Wayland, but have other issues with wayland presently so can't rule out X11 being the cause)
I have tried a large number of different settings in hammer as well as methods of launching it, with and without DXVK installed under Wine, with not really any success. Removing the -winecompat flag from the launch command slightly improves it, however it reintroduces framebuffer issues, and is still very sluggish when panning the 2D views (I learned from speaking to developers that -winecompat also forces per-frame redraws on all viewports, which explains why it's less sluggish without it until you move the view)
I have also checked CPU usage during these slowdowns and it is minimal, less than 10% of a single core. And also tried with the stable, unstable, and previous branches of P2CE on steam.
I've pretty much run out of ideas for things to try, but I'm still fairly sure it's something with my setup.
To Reproduce
Explained above and demonstrated in the video. Put more of a medium sized map or larger into the 2D viewport(s) and watch performance degrade (if you are one of the rare people affected)
Issue Map
N/A
Expected Behavior
Buttery smoothness! Which is normally the case in a very simple map and feels sooo good.
Operating System
No response