Conversation
Remove the mention of winecompat from the launch command, fix and clarify the winecompat flags to possibly use on Wine 11, and add another method to improve Hammer performance.
Add a bit more detail to winecompat and mark as deprecated, alongside adding in the nowinerenderfix option
OrsellGit
left a comment
OrsellGit
left a comment
There was a problem hiding this comment.
Some details need to be changed but thank you for what you have done so far!
|
|
||
| Run `winecfg` in a terminal, navigate to "Graphics" and adjust the DPI as desired under the "Screen resolution" section. | ||
|
|
||
| ### Hammer performs terribly! |
There was a problem hiding this comment.
While yes this is technically true for some people, there is no need to be blunt about the fact. I would recommend replacing this with "Current Issues With Hammer" or similar.
There was a problem hiding this comment.
Ye I could change that, only reason I had the exclamation mark as well was due to some earlier sections having one too.
Perhaps something like "Low Performance in Hammer" could work?
|
|
||
| ### Hammer performs terribly! | ||
|
|
||
| This is a side effect of how the 2D viewports are rendered, when larger portions of the map are visible in the 2D viewports, Hammer will degrade in performance. |
There was a problem hiding this comment.
I would recommend bullet-pointing issues, maybe excluding the cause, and adding any possible solutions to the issue.
There was a problem hiding this comment.
I'll look into adding some bullet points and simplifying things a bit!
2 participants
Thought I would try to help add a little more info to the Linux tool documentation. Started with adding some info about resolving some performance issues in Hammer.
I feel like I can do some more but thought I'd ask for a little more info and see if I should change more things. Like should the -winecompat parameter be replaced with -nowinecompat? Or how should I handle mentioning the two versions of the parameter?