mtasa-blue icon indicating copy to clipboard operation
mtasa-blue copied to clipboard

Windows 11 24H2 triggers ancient bug causing Skimmer plane to get propelled to broken coordinates on spawn

Open holmes000 opened this issue 9 months ago • 5 comments

Describe the bug

Very detailed explanation here: https://cookieplmonster.github.io/2025/04/23/gta-san-andreas-win11-24h2-bug/

Short: Missing vehicles.ide values should have always caused issues, but only in 24H2 fgets/LeaveCriticalSection uses enough stack to scramble the stale values in CFileLoader::LoadVehicleObject.

Fix in SilentPatchSA by CookiePLMonster: https://github.com/CookiePLMonster/SilentPatch/commit/881aded7237067202025934796cc2313104cba8c

Steps to reproduce

  1. Install Windows 24H2
  2. Launch MTA:SA
  3. Spawn Skimmer through freeroam (spawns nearby, teleports to invalid coords, you don't get to see it) or through admin panel (spawns and warps you inside, you get launched to invalid coords)

Version

No response

Additional context

No response

Relevant log output


Security Policy

  • [x] I have read and understood the Security Policy and this issue is not security related.

holmes000 avatar Apr 26 '25 11:04 holmes000

Unable to reproduce, updated my PC to latest KB5055627

Image

https://github.com/user-attachments/assets/d909a8d4-f11f-48f7-bc83-5b8b40163ae9

Xenius97 avatar Apr 29 '25 12:04 Xenius97

MTA is likely hooking the IDE loading in a way that remedies this bug already. The main point is just those few potentially-uninitialized values.

CookiePLMonster avatar Apr 29 '25 12:04 CookiePLMonster

I created this issue after reproducing it in latest debug build of MTA from master branch, Windows build 26100.3909, KB5055627

holmes000 avatar Apr 30 '25 13:04 holmes000

I've updated everything on my PC and i can't figure out what and why causes. Everything looks normal. I have latest Windows & latest nVidia drivers. RTX 3060 + i5-10400

Xenius97 avatar Apr 30 '25 14:04 Xenius97

As this is caused by uninitialized variables, it's likely that this either only manifests in Debug builds or only in Shipping builds. It's easiest to just check the IDE loading code, the bug is understood well enough that you don't particularly need to reproduce it to fix it.

CookiePLMonster avatar Apr 30 '25 14:04 CookiePLMonster