KTX2 is like a container format. Various other things can be inside. Most are also part of vulkan, a
KTX2 is like a container format. Various other things can be inside. Most are also part of vulkan, and are likely supported on the GPU natively
RI was just referring to a standard .pak or .vpk file
RThat could just store arbitrary data
RAnd really most people don't need GPU compressed textures, I don't even know of a good way to write them to disk from standard image formats (and I prefer being able to parse the texture data on the CPU side first anyway, so it does not really give me much to have GPU compressed textures I would then decompress lol)
Ayes, you do have to make some tradeoffs though
if you want the most realistic looking game in the world then you'll probably have to use uncompressed textures, and then use sparse texturing on top of that if you want to load them all at once
but for most usecases a bit of quality loss is fine
if you want the most realistic looking game in the world then you'll probably have to use uncompressed textures, and then use sparse texturing on top of that if you want to load them all at once
but for most usecases a bit of quality loss is fine
RIt also wouldn't surprise me if the GPU already compresses the texture data into a native format transparently
Afar as i know gpus use whatever it is you give them
it's the reason why you tell it the texture format
it's the reason why you tell it the texture format
AGPU compressed textures have a load of uses
RThat doesn't mean they Don't transform it into their own internal representation
RTrying to reduce space utilized transparently
RI'm not disagreeing, in fact, even for realistic open worlds, i think is still probably a good usecase
RThey don't look that bad compared to the originals
ROf course again, I would prefer to parse everything into RGBA on CPU anyway so I don't get anything from GPU compressed textures
RXD
RBut that's me personally
Abased on the fact that my game is a large open world I do have a bias towards gpu compressed textures
Aalso from what i've seen gpu compressed textures are a bit faster as well since there's less data, both when it comes to drawing the texture itself and also transferring from cpu to vram
PI need some help with assimp, I'm trying to limit bones used by meshes to 6 so I did this:
however meshes still have more than 6 bones, am I applying the property the wrong way?
however meshes still have more than 6 bones, am I applying the property the wrong way?
Rnot suprising
Ridk, I just like being able to uncompress the texture on the CPU and send it in RGBA to the GPU
KI mean sure, but you have worse performance for no reason
A^
Ragain, I just like doing it
Rthat's fine, performance is still nowhere near terrible even still
Rand how many times are you loading textures from disk repeatedly
Ain an open world game you can do it rather frequently
Rand most of the time even removing them from GPU
Aalso the performance is the gpu performance
Anot the loading performance
Rdepends on the Open world game
Rultimately for me doing it is not that big an issue.
KYour texture is also using more memory with no gain in quality. Data that's been uncompressed from a lossy format inherently stores useless information.
And that then eats into memory throughput & usage for no reason
And that then eats into memory throughput & usage for no reason
Rgood thing I don't use lossy formats
HThis is what I've been thinking of doing. Since that way it's easier to pack and I can automate most parts since i use a custom editor GUI app thingy. My game engine is 2d only for now and focuses on 2d. So i think i could do it in raw bytes yeah just for faster startup time (on final builds) but when in editor just load the raw PNGs or JPEGs or etc.
Halso most of my textures will be auto packed to single atlas or few atlases by the editor
Rafter all, if I am going to send an image in RGBA to the GPU, why would I create lossy versions of textures to store on disk
Abecause then you can upload it to the gpu in a compressed format so it uses less vram and gives a (slight) performance boost?
Rnot if I am going to uncompress it before loading it on GPU... like I previously stated would prefer to do...
Awhy would you do that though
Tfactorio compresses its texture atlases :)
Athere is literally 0 point in doing that
Ayea ive not seen compressed textures for 2D games but im assuming it can look okay
Rbecause I prefer having the textures in a format easily read on CPU and easily authored by myself
Abit like a jpeg
Ayou load in textures and make changes to them directly before uploading them to the gpu?
RIdeally yes. I would like to be able to stamp things on top of various textures
Ror at runtime generate textures to use.
RI would also not like to have to deal with a dozen variously compressed texture formats
Rand authoring said textures.
Tyou are argumenting as if one is not allowed to compress textures at runtime 
RI am arguing as though I don't want to deal with the overhead or dealing with compression/decompressing the textures at runtime