Time Nick Message 13:31 MTDiscord IIRC the parent node scaling has issues in Godot too. 16:18 MTDiscord planning to merge #16141 in 10m 16:18 ShadowBot https://github.com/luanti-org/luanti/issues/16141 -- Fix handling of skinned meshes for nodes, second try by appgurueu 16:37 MTDiscord done 16:39 sfan5 5.12 is ready 🎉 16:39 Krock \o/ 16:40 sfan5 theoretically at least 16:44 Krock @luatic: Do you have any suggestion of the working? This is the best I came up with: 16:44 Krock > Skinned mesh models: skinned mesh nodes used to have inconsistent scaling. Parent nodes (not bones) should not have transformations. 16:45 Krock s/skinned mesh nodes/skinned meshes/ 17:00 SFENCE_arch So RC or Release without RC? 17:00 Krock we do RC as in "Release & Communicate on the forums" 17:01 MTDiscord the node and gltf fixes are two separate things 17:01 MTDiscord the node-related fixes i'd word like this: 17:02 MTDiscord - Fix some models not rendering correctly as nodes. (due to transforms not being applied, but that detail can be left out of the changelog) 17:02 MTDiscord - Fix visual_scale not applying to skeletally animated meshes when used for nodes. 17:06 MTDiscord The gltf bugfix now is that local transforms do not affect a skinned mesh, as they should not. For models that also work on versions that don't have the fix, modders should avoid the gltf validator warning NODE_SKINNED_MESH_LOCAL_TRANSFORMS - "local transforms will not affect a skinned mesh". 17:06 SFENCE_arch For last two releases wi did tag like 5.11.0-rc1 and 5.10.0-rc1. 17:07 MTDiscord the "getting rid of the skeletal animation for rigid animation" hack isn't really important in the changelog tbh, can subsum that under code quality improvements, refactorings etc. it probably has some tangible memory usage and maybe even some minuscule performance benefit but that wasn't the main point. 17:08 MTDiscord despite delaying the release further, i think a release candidate would probably be a good idea 17:08 Krock 5.12.0-rc1 vs 5.12.1 at this point it doesn't matter too much 17:09 Krock actually it does in terms of notifying distros for package updates... 17:10 SFENCE_arch Well. 17:11 sfan5 just link a windows CI build and tell the community to test it? skips the working of adjusting the version number and tagging etc. 17:11 sfan5 it's not like distros will care about an rc release for two entire days 17:21 Krock two days aren't much for RC testing, though. I also don't care whether to delay it by a few days or not. So in theory we could still provide the builds like in 5.11.0-dev/rc1 17:23 SFENCE_arch Just in case, I should build and sign RC build for macOS if we do RC build. 17:25 sfan5 my thought was that two days + a bunch of community members suffices to find out if the model change broke something relevant 17:25 sfan5 a decent amount of people already run git master anyway (see: first instance of model commit that broke MTG) 17:28 [MatrxMT] Do we want #16146 merged for the release? 17:28 ShadowBot https://github.com/luanti-org/luanti/issues/16146 -- Formspec: make style bgimg_middle pixel-perfect by SmallJoker 17:29 sfan5 gui_scaling_filter is niche IMO 17:29 Krock it's an old bug and the one person (me) who found this will be compiling from master anyway 17:29 Krock you can easily ignore this 17:31 [MatrxMT] doing a short RC to get testing for the model change sounds good 17:31 [MatrxMT] also, today is the day of the Play Store deadline 17:32 Krock did they make us raise the minimum ABI version again? 17:32 sfan5 no, the account verification thing 17:33 sfan5 actually 17:33 sfan5 >Dein Entwicklerprofil und alle Apps werden am 21. Mai 2025 aus Google Play entfernt 17:33 sfan5 it's tomorrow 17:35 [MatrxMT] I guess the date it says depends on your time zone then 17:36 [MatrxMT] the Matrix bridge has quite a high delay today 17:38 [MatrxMT] well, there isn't anything I can do about it 17:38 sfan5 short of a terrorist attack on the google HQ, probably not 17:39 [MatrxMT] but it still makes me mad because I have invested a huge amount of time into improving the Android app in many different areas over the last two years 17:44 [MatrxMT] (not all hope is lost) 17:44 MTDiscord wait what do we have to do 17:47 MTDiscord was it the thing which @celeron55 or @nrz0 need to do, or can someone else do it? 17:56 MTDiscord nrz would need to do it since he's the legal owner of the dev account 17:57 MTDiscord It's in the process to move to @celeron55 , we did it today 17:57 MTDiscord ah that's good 17:57 MTDiscord oh yay 17:57 MTDiscord and hello, sorry for being a bit inactive on IRC 17:58 MTDiscord for people on discord 17:58 MTDiscord https://cdn.discordapp.com/attachments/747163566800633906/1374446165503770704/image.png?ex=682e143d&is=682cc2bd&hm=18af9ef412bc3e0647b01fbbd89f4a8c81df49c54d434fc20c77ddbf63c68317& 17:59 [MatrxMT] grorp: There is still F-Droid; and the touchscreen improvements also benefit other users (e.g. mobile Linux, see FOSDEM; although it is admittedly a smaller field than Android users) 18:03 [MatrxMT] nrz0: that's great, I hope it still works out! 19:46 rubenwardy I think it might just unpublish the app, I've found support threads about going through approval and reinstatement after the deadline