Skip to content
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

Upscale and add SVG versions of some common textures #220

Merged
merged 1 commit into from
Jan 9, 2021

Conversation

qwertychouskie
Copy link
Contributor

VRAM usage should still be acceptable, and these high-res versions look a lot better on modern systems (no visible pixelation anymore).

VRAM usage should still be acceptable, and these high-res versions look a lot better on modern systems (no visible pixelation anymore).
@parasti
Copy link
Member

parasti commented Dec 8, 2020

This is cool. Will go over this when I can.

@Neverball Neverball deleted a comment from ersohnstyne Dec 8, 2020
@parasti parasti merged commit 803a93a into Neverball:master Jan 9, 2021
@qwertychouskie qwertychouskie deleted the upscale_1 branch January 9, 2021 20:25
@qwertychouskie
Copy link
Contributor Author

Cool, thanks!

parasti added a commit that referenced this pull request Jan 24, 2021
This reverts commit 803a93a, reversing
changes made to 81f63d1.
@parasti
Copy link
Member

parasti commented Jan 24, 2021

Damn, I messed up.

It's kind of dumb, but due to the way texture coordinates work in .map files, if you change a texture's resolution and simply recompile the .map file, the texture coordinates will not scale to the new resolution. You have to actually open the .map in Radiant and fix it...

I didn't test this before merging, so on my first recompile (just now), goal textures are kind of not in a good place.

I reverted the merge for now. I'll put some time into figuring out a solution that isn't "edit all the .map files", because that's not what I'm about.

@qwertychouskie qwertychouskie restored the upscale_1 branch January 24, 2021 22:21
@qwertychouskie
Copy link
Contributor Author

Maybe the map compiler could check the expected resolution based on the .map, and the actual resolution, and adjust accordingly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants