Very high performance drop between older and newer MTA version

[MrDadosz]

Describe the bug

There is very high performance drop between version v23613 and v23900 - 30-60% FPS drop depending of the location.

This is most likely a problem with the fix for the optimization commit from the end of last year that broke custom models. Game now is unplayable on low end devices and much less playable on high end devices.

Steps to reproduce

1. download older version v23613
2. check FPS = almost 100 FPS, game is very smooth
3. download newest nightly v23900
4. check FPS = 40-60 FPS, game is choppy

Version

v23613 - ok FPS
v23900 - bad FPS

Additional context

Maybe just undo the changes, check what's wrong, and commit them again when everything works?

Relevant log output

Security Policy

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

[Xenius97]

I can proof this, i've already mentioned on dev discord.

[keven021samp-dotcom]

That's bad, could you send me version v23613?

[MrDadosz]

That's bad, could you send me version v23613?

https://nightly.mtasa.com/mtasa-1.6-rc-23613-20251122.exe

[blonter]

I can also confirm this but on completely vanilla servers too which don't use any texture mod, custom objects etc. Everything just default SA

[ArranTuna]

v23613 - ok FPS
v23900 - bad FPS

If you want to help fix this, then narrow it down using 'trial and improvement' on the different nightlies: https://nightly.mtasa.com/

So try v23750 then if that is good v23800 and so on.

[MrDadosz]

I'd test it but nightly that worked fine without crashes isn't available anymore - fully stable nightly was around september/october 2025 - never had a problem with texture mismatch and engineRequestModel worked everytime.

• v23613 has a problem with the game freezing when entering the server I'm testing on
• v23652 has a problem with the game freezing when entering the server I'm testing on
• v23715 crashed when I tried to join the server
• v23761 crash on startup (Code = 0xC0000409 (Stack Buffer Overrun) Offset = 0x5e502a0e);
  second try joined but problems with engineRequestModel (wrong model, wrong textures) - 60-90 FPS
• v23798 problems with engineRequestModel (wrong model, wrong textures) - 60-90 FPS
• v23847 problems with engineRequestModel (wrong model, wrong textures) - 60-90 FPS
• v23867 crash on startup (Code = 0xC0000374 (Heap Corruption) Offset = 0x777ac68f)
  second try joined but problems with engineRequestModel (wrong model, wrong textures) - 80-100 FPS
• v23881 problems with engineRequestModel (wrong model, wrong textures) - 60-90 FPS
• v23900 problems with engineRequestModel (wrong model, wrong textures) - 40-60 FPS
• v23926 problems with engineRequestModel (wrong model, wrong textures) - 60-90 FPS

[lamsdevice]

Hey, just confirming there is indeed a bug with custom models.
There's been a massive drop in performance since the last build.
Yet I've been developing on my project for over 2 years without any issues, and trust me, I've added plenty of new models along the way 😅 I downgraded to v23613 and it's working perfectly again.
Fingers crossed for a quick fix!

[lamsdevice]

Build v23613

Last official release build

PC specs:

• GPU: RTX 4060
• CPU: Ryzen 7 2700
• RAM: 24 GB
• Windows: (Win10/Win11)

Custom content / model system:
My server heavily relies on custom content:

• custom player skins (peds)
• custom vehicles
• custom map objects / props
  We load/replace a large amount of custom models using:
• engineRequestModel / free*Model (freeing requested models)
• engineReplaceModel
• engineImportTXD (and COL where applicable)

Build comparison:

• GOOD build: 1.6.0-9.23613.0 → smooth, stable FPS, no stutter.
• BAD build: the latest official/auto-updated 1.6 build (updated normally via MTA) → huge FPS loss in dense areas with many custom models on screen (roughly -30% to -60% depending on the area).

Notes:

• Downgrading back to 23613 immediately fixes the issue for me.
• Reproducible client-side; not related to server load (also noticeable in local/LAN tests).
• No overlays enabled and MTA runs on the correct GPU.

Additional note:

• The FPS drops happen mainly while moving around the map when streaming in my custom mappings and/or entering areas where many replaced models are used. As soon as I drive/walk through those custom-mapped zones (with lots of engineReplaceModel / imported TXDs), FPS drops heavily; outside those areas performance is much better.

[C0DELEVEL]

Feel free to check version 23324 (https://www.mediafire.com/file/n7zw3dbk1rtg17w/mtasa-1.6_%25281%2529.exe/file).

I ran some tests myself and noticed around a 120 FPS difference in CPU intensive DX rendering scenarios (120 FPS vs 240 FPS compared to the older version).
In areas with high vehicle density, the difference is also about 50% (70 FPS vs 140 FPS).

Compared with 23952.

[skazateusz]

The problem returned in the last update (ver. 24056). I am requesting more thorough testing of new features added to the game and any changes related to it, because I have the impression that it is getting worse with each update.

[lamsdevice]

I can confirm this issue as well. It reappeared after the recent updates and seems to be getting worse with each new release. I’m currently using Multi Theft Auto v1.6-release-24060, and I’m experiencing the same problem.

I agree that more thorough testing of new features and related changes is needed before release, as this issue is clearly not fully resolved and keeps resurfacing.