search

citizenfx / fivem

The source code for the Cfx.re modification frameworks, such as FiveM, RedM and LibertyM, as well as FXServer.
https://cfx.re/
3.56k stars 2.1k forks source link

Increase of likelihood of crashes in past few days #2912

Open alberttheprince opened 1 day ago

alberttheprince commented 1 day ago

What happened?

The likelihood of users crashing while moving around the map (possibly because of streamed assets) has increased significantly over the past few days.

A report has been made on the forums: https://forum.cfx.re/t/sudden-increase-in-game-crashes-crashed-gta5-b3258-exe-sub-140777e18-type-errors/5280338

A number of client crash logs have been uploaded. We understand the vertex errrors, but these were all present a few days ago before any significant increase in crashes.

We have not made any changes to maps, clothing, or vehicles in the past few days, and see a significant increase in the number of client crashes occurring. Staying in one spot on the map will not cause users to crash, but people moving around will cause them to crash. If they try to connect to the server (usually after their character is loaded, so the user is teleported from the character select screen to the rest of the game world) they will crash immediately.

Clearing the client cache will fix this.

Expected result

No Crashes

Reproduction steps

  1. Stream Assets
  2. Move around the map
  3. Eventually crash
  4. Can no longer join server without crashing
  5. Clear client/FiveM cache, you are now able to connect to server without crashing
  6. Eventually clients will crash

Importancy

Crash

Area(s)

FiveM

Specific version(s)

FiveM B3258

Additional information

We use many streamed assets, and we understand there are some vertex issues. However, these crashes (usually lake-Edward-helium) have only recently started to occur. We have made no changes to maps and always attempt to optimize any added assets.

https://cfx.re/join/dppv4d

LivedBackwardss commented 20 hours ago

Not sure if it's related to this or similar..

https://github.com/citizenfx/fivem/issues/2889 https://github.com/citizenfx/fivem/issues/2799

alberttheprince commented 19 hours ago

Not sure if it's related to this or similar..

2889 #2799

If the issue is bad map makers, if there was a way to refund all these MLOs this wouldn't be an issue, but we're stuck with the cancer that is Tebex, meaning 0 accountability from these creators.

LivedBackwardss commented 19 hours ago

Not sure if it's related to this or similar..

2889 #2799

If the issue is bad map makers, if there was a way to refund all these MLOs this wouldn't be an issue, but we're stuck with the cancer that is Tebex, meaning 0 accountability from these creators.

Exactly my point, it never happened before and now out of the blue it happens. I've opened numerous tickets with creators and they say "the error does nothing" or don't reply nothing. This crash never happened before but some how in the update it starts to happen.

alberttheprince commented 14 hours ago

Not sure if it's related to this or similar..

2889 #2799

If the issue is bad map makers, if there was a way to refund all these MLOs this wouldn't be an issue, but we're stuck with the cancer that is Tebex, meaning 0 accountability from these creators.

Exactly my point, it never happened before and now out of the blue it happens. I've opened numerous tickets with creators and they say "the error does nothing" or don't reply nothing. This crash never happened before but some how in the update it starts to happen.

out of 10 creators I've contacted, 1 has fixed the issues, 1 said "I should just delete that map", and 1 has said "it shouldn't be a problem".

I've reverted back to an older server artifact, but I'm not sure if that would be related. Hoping there's more insight from someone who would know.

LivedBackwardss commented 14 hours ago

Not sure if it's related to this or similar..

2889 #2799

If the issue is bad map makers, if there was a way to refund all these MLOs this wouldn't be an issue, but we're stuck with the cancer that is Tebex, meaning 0 accountability from these creators.

Exactly my point, it never happened before and now out of the blue it happens. I've opened numerous tickets with creators and they say "the error does nothing" or don't reply nothing. This crash never happened before but some how in the update it starts to happen.

out of 10 creators I've contacted, 1 has fixed the issues, 1 said "I should just delete that map", and 1 has said "it shouldn't be a problem".

I've reverted back to an older server artifact, but I'm not sure if that would be related. Hoping there's more insight from someone who would know.

Which artifact? It's not just us having the issue other people too.

Legacy-TacticalGamingInteractive commented 10 hours ago

I can say with absolute certainty that those vertex errors (poly edge references) being fixed in real time adds up to the overhead that is required by a client while playing. THAT indeed causes crashes. Especially when you have multiple maps in one area causing this. Collision files that have broken poly edges will cause crashes more often than broken .ydr's for whatever the reason.

Most mappers do not know how to fix the problem. But even when you tell them how to do it such as using the Poly Edge Fixer tool by Smallo, they then take MONTHS if at all to get back to you. They don't give a shit because they have your money and they don't even run servers themselves.

I've dealt with this issue extensively.

There MAY be other things at play here, but I just wanted to mention my experience on the matter as well as being a definite cause of crashing in general for clients.