New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More additions and fixes #364
Conversation
Also, the current WR https://steamuserimages-a.akamaihd.net/ugc/844837307597188745/7E34B1B514D1103BF1269A026FACE4340BF06B90/ wayyyyyyyyy too big |
I don't think that can be corrected with the timer, as far as I know game_text channels don't work properly in CS:GO and certain resolutions affect the text size. Valve is keeping track of it here and it looks fine for me on 1920 x 1080. |
I was using 1920*1080 and it was that large
… On 19 Jun 2017, at 19:06, strafe ***@***.***> wrote:
I don't think that can be corrected with the timer, as far as I know game_text channels don't work properly in CS:GO and certain resolutions affect the text size.
Valve is keeping track of it here and it looks fine for me on 1920 x 1080.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@strafe Wait, that screenshot was taken on our speedrun server. Are you working for 3kliks or is this just a coincidence cuz this server is not fully public yet. BTW the text won't disappear for some reason, idk if it's a config problem or something. (!hud doesn't work aswell) |
Works fine for me in-game on 1920x1080, just like @strafe has it. You can disable it from the However, any feedback about snapshots and practice mode? @Nickelony anything in error logs? I haven't done any recent changes to the HUD command/menu so I don't think anything was supposed to break :(. |
sm_style
menu so it's more spaced, shows your current style and disables the ability to select it.shavit-rankings.phrases.txt
.sm_cpmenu
) will use the new snapshots, as requested in checkpoints #313.velocity
as a style setting. (New 'velocity' style setting #363)Things that I should probably do before merging this pull request: