Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

PNGTuber Plus

Get more out of your png tubing experience. 路 By kaiakairos

Image file optimizations

A topic by GeneralTekno created 18 days ago Views: 352 Replies: 9
Viewing posts 1 to 6
(+1)

So seeing the posts last night about how active support is discontinued now prompted me to finally fork the code and dig in to see if there was anything I could do about some of the gargantuan memory size pngtuberplus can use.

And I'm happy to say I found a bunch of optimizations!

I don't have access to submit pull requests, but I DID go ahead and commit updates to my own fork. Getting rid of a bunch of the unnecessary caching/doing some texture storage optimization dropped both the GPU memory usage down and dramatically shaved off the RAM usage of the software. Myself and other friends have used the software in the past to make very complex models (mine tend to be 40+ items) so I was able to cut the usage from several gigabytes down to a few hundred megabytes.

If this stuff could get tested by kaiakairos to confirm/put into a release it'd be an amazing quality of life upgrade! (I see several people have also submitted pull requests on the Github, incidentally, to add features.)


https://github.com/kaiakairos/PNGTuber-Plus/compare/master...michaelivey:PNGTube...

Hiyaa! How arte you?~
I played a bit with your optimizations that you did, and found a slight problem, animated sprites get bugged, it's not centering the sprites

Oh cool, thanks for the heads up. I've not played with animated sprites, but I can guess at where that's happening in my code.

And yeah I've worked out the bug; it's due to the texture cropping I was doing to save on texture memory in the GPU.

Reworking my logic so that if an animation is being used it does not crop the texture. (And if you add/remove animations it'll thus reload the texture in GPU memory with/without cropping off.)

The cropping optimization is there more because if you have large image files that's a LOT of empty pixels taking up GPU memory - and say if you have images with mostly empty space that are a few MB apiece in texture memory, and 40 of them... that adds up fast

Hiyaaa! I found another problem, when you go to save a model, it gives you the options to save it, but it doesn't actually save it. Other than that, everything is fine, thank you very much for your effort in optimizing this program!

(1 edit)

What steps were you taking when you tried this?

Asking given that when I'm debugging this, saving does work.
EDIT: Never mind! I only tried saving files without any newly created textures... fixing this now

I'll have to doublecheck that then! I thought I had saving working when I ran tests.

But yeah, aiming to fix these bugs this weekend.

(+1)

I made an account just to say this but thank you for taking your time to make optimizations and fixes to this program! I was sad to see that it's been dropped but the thought that community members could fix it up a little and make it more stable makes me really happy so thank you!

Alright, thanks everyone for bringing up those bugs to me! Both should now be fixed in that branch.

Thank you so much for your hard work and taking the time to do this! 馃┓