Meshes dont function properly in newest snapshot on linux v4.4.alpha.mono.gh [106ba51fe]

[WildstarStudios]

Tested versions

reproducable in v4.4.alpha.mono.gh [106ba51]

System information

Linux Mint 22 xfce

Issue description

when i scale meshes with the tools and not through the values the values don't change and when modifying the values they dont fix it.

Steps to reproduce

make a mesh3d scale it through the editor not the values.

Minimal reproduction project (MRP)

new-game-project.tar.gz

[WildstarStudios]

[Spartan322]

First you should not trust any GH to report bugs, there are many things that they don't do that and many other things they do actually do that could cause false positive bug reports, if you want to report master bugs you need to compile the engine yourself. This aside we are not work at all on fixing 4.4 stuff, we defer to leave that to Godot while we focus on 4.3. Can you replicate this from Godot's master? Can you replicate this in 4.3 of Godot and Redot? Also you did not give us enough information in the issue report, the issue template instructs you what you must do in full.

---

When reporting bugs, please follow the guidelines in this template. This helps identify the problem precisely and thus enables contributors to fix it faster.

• Write a descriptive issue title above.
• The golden rule is to always open one issue for one bug. If you notice several bugs and want to report them, make sure to create one new issue for each of them.
• Search open and closed issues to ensure it has not already been reported. If you don't find a relevant match or if you're unsure, don't hesitate to open a new issue. The bugsquad will handle it from there if it's a duplicate.
• Verify that you are using a supported Redot version. Please always check if your issue is reproducible in the latest version – it may already have been fixed!
• If you use a custom build, please test if your issue is reproducible in official builds too. Likewise if you use any C++ modules, GDExtensions, or editor plugins, you should check if the bug is reproducible in a project without these.

Tested versions

To properly fix a bug, we need to identify if the bug was recently introduced in the engine, or if it was always present.

• Please specify the Redot version you found the issue in, including the Git commit hash if using a development or non-official build. The exact Redot version (including the commit hash) can be copied by clicking the version shown in the editor (bottom bar) or in the project manager (top bar).
• If you can, please test earlier Redot versions (previous stable branch, and development snapshots of the current feature release) and, if applicable, newer versions (development snapshots for the next feature release). Mention whether the bug is reproducible or not in the versions you tested. You can find all Redot releases in our download archive.
• The aim is for us to identify whether a bug is a regression, i.e. an issue that didn't exist in a previous version, but was introduced later on, breaking existing functionality. For example, if a bug is reproducible in 4.2.stable but not in 4.1.stable, we would like you to test intermediate 4.2 dev and beta snapshots to find which snapshot is the first one where the issue can be reproduced.

System information

• Specify the OS version, and when relevant hardware information.
• For issues that are likely OS-specific and/or graphics-related, please specify the CPU model and architecture.
• For graphics-related issues, specify the GPU model, driver version, and the rendering backend (GLES2, GLES3, Vulkan).
• Bug reports not including the required information may be closed at the maintainers' discretion. If in doubt, always include all the requested information; it's better to include too much information than not enough information.
• Starting from Redot 4.1, you can copy this information to your clipboard by using Help > Copy System Info at the top of the editor window.

Issue description

Describe your issue briefly. What doesn't work, and how do you expect it to work instead?
You can include images or videos with drag and drop, and format code blocks or logs with ``` tags, on separate lines before and after the text. (Use ```gdscript to add GDScript syntax highlighting.)
Please do not add code examples or error messages as screenshots, but as text, this helps searching for issues and testing the code. If you are reporting a bug in the editor interface, like the script editor, please provide both a screenshot and the text of the code to help with testing.

Steps to reproduce

List of steps or sample code that reproduces the issue. Having reproducible issues is a prerequisite for contributors to be able to solve them.
If you include a minimal reproduction project below, you can detail how to use it here.

Minimal reproduction project (MRP)

• A small Redot project which reproduces the issue, with no unnecessary files included. Be sure to not include the .godot folder in the archive (but keep project.godot).
• Having an MRP is very important for contributors to be able to reproduce the bug in the same way that you are experiencing it. When testing a potential fix for the issue, contributors will use the MRP to validate that the fix is working as intended.
• If the reproduction steps are not project dependent (e.g. the bug is visible in a brand new project), you can write "N/A" in the field.
• Drag and drop a ZIP archive to upload it (max 10 MB). Do not select another field until the project is done uploading.
• Note for C# users: If your issue is not C#-specific, please upload a minimal reproduction project written in GDScript. This will make it easier for contributors to reproduce the issue locally as not everyone has a .NET setup available.