....Hope this helps those other helpless people trying to reach their deadlines and facing such inexplicable problems that come from nowhere in GMS2.
Thanks
@Nocturne for the leading folder.
Mate! - and of course
@Nocturne - Thank you so much for this info / workaround!
I am STILL having the exact same problem - I can't generate adaptive icons, as I'm using source control, and get a weird error - thought it might be to do with spaces in the path, but nope, moved project, same issue...
Also tried moving the source images into the project etc, as I was getting this error:-
"
fatal: C:\GMS: 'C:\GMS' is outside repository"
The root folder for my projects was "GMS Projects", so I replaced the space with an underscore - same issue... Simply won't work. The irony is that it still PRODUCED these images (I checked, and they're actually built, in my project), but just completely ignores them when building...
Anyway, 2 things...
1) Yoyo? - It's a bit **** that this is STILL not working correctly, and needs all manner of fudging to actually do what should be a 10 second automated task. Not impressed....
2)
@Nocturne @MarceloP - You guys are legends! - I was beyond frustrated with this
- (I've also got the correct logos etc, all in place, and completely ignored by GMS' android builder...) ...so THANK YOU!
Also, just to add - when adding a reasonably-sized .ico to your HTML5 project, THAT's also screwed, by the looks of it... 32px etc show fine, but if I add a basic 128px, 512px, etc .ICO, that works fine everywhere else, the colours are screwed - seems to be a channel issue.
Also tried different source images, and producing one using the popular online favicon tool, and same thing - a normally coloured .ICO, is shown as some weirdly different hued version. I'm going to see if it's actually wrong in the resulting build, as opposed to
just inside the IDE....
Another example:-
They should look like this!:-
PS - To those about to say, "have you tried the latest build?" - (2022.8.0.50, which admittedly has a huge number of fixes!) - Yep, I tried it. IT completely broke my HTML5 collision - I'm smashing into thin air, between 2 objects (works fine in 2022.5.0.8) - I'll add debug code when I get a chance, to see what's happening, but no, at present, I daren't 'upgrade' - especially as it breaks the legacy format for anything opened in it..... argh...