Bad texture size and compression format for mobile GPUs

[CalibriLight]

Android

[htv04]

Yikes, might need to use a different compression format for Android devices, currently working on an ETC1 variant for all graphics

It's worth noting that Android isn't one of the officially supported platforms right now

[CalibriLight]

Yikes, might need to use a different compression format for Android devices, currently working on an ETC1 variant for all graphics

It's worth noting that Android isn't one of the officially supported platforms right now

Sad, can i put my bf image? If i can tell me how plz

[AM7999]

Just to add a somewhat "plausible" closure to your issue. As HTV04 has stated there will need to be a ETC1 variant of all the sprites, the reason i can think of him going this route is most android devices may not have enough VRAM (note this is not something you can adjust on your phone) and secondly (unrelated to the first point of HTV04 saying you need ETC1) Even if you can plug in a USB keyboard into your phone using adapters and whatnot it wouldn't be the most (how do i say this) elegant solution as i personally think that having touch buttons corresponding to the note would make the game a bit more "accessible" to the average user who would probably not have the adapters to plug in a USB keyboard.

And finally You also last asked

Sad, can i put my bf image? If i can tell me how plz

One way you could probably do it is to download and install Android Studio if you have a computer and figure out how to export images to ETC1

Hold up, I have that same exact issue on my Raspberry Pi, I hadn't read this until now

[AM7999]

Hold up, I have that same exact issue on my Raspberry Pi, I hadn't read this until now

@GalaxytedYT The reason for this is because Raspberry pis have similar hardware to a modern smartphone (arm SoC (system on a chip))

Hold up, I have that same exact issue on my Raspberry Pi, I hadn't read this until now

@GalaxytedYT The reason for this is because Raspberry pis have similar hardware to a modern smartphone (arm SoC (system on a chip))

@AM7999 Then how come the Switch doesn't have that issue? I've heard it's an SoC as well, also I don't really mind the issue just as long as the songs work.

[htv04]

Hold up, I have that same exact issue on my Raspberry Pi, I hadn't read this until now

@GalaxytedYT The reason for this is because Raspberry pis have similar hardware to a modern smartphone (arm SoC (system on a chip))

@AM7999 Then how come the Switch doesn't have that issue? I've heard it's an SoC as well, also I don't really mind the issue just as long as the songs work.

It has a Tegra X1 SoC with more RAM and support for compressed textures, while the Raspberry Pi has a much less powerful SoC.

[Fordi]

(Doing this on a Pi 400)

I'm attempting to in-place (in the most recent beta release .love file) add a pkm imageType and set it as an option in the hardwareCompression setting. Will report back later.

[Edit: whoa, etc1tool does not compress well. It's fricken slow, and, as an example, girlfriend.png went from 5.6M to 33M. Might have something to do with that file being 256M raw, though]

[Edit: haha. Not better. Not only do the images not show, but they don't have transparency either.]

[AM7999]

Fun Fact: i have already gone ahead and done this whole dance with etc1tool it did not work as the textures still did not show up

[Edit] I didnt fully read yours so i though you didnt already get the same result i did :/

[Fordi]

Yeah, I think it's more an issue with löve being unable to decompress the whole image into memory (which, as I noted for the GF, is like 256M). It fails to allocate and just displays whatever. Tried PNGquanting girlfriend.png down to 16 colors / 8 bit alpha as well as a hail-mary - still no löve.