FiveM for GTAV Enhanced: Early Access Hotfix 3 #176
Replies: 6 comments 1 reply
|
sick |
|
I know suggestions are not being taken but can some form of stack trace be outputted to the client log (or even dumps) when the game crashes and the server is set in developer mode? Trying to assist in reporting issues/sourcing crash reasons is proving difficult considering outside of the crash ID (where sometimes none is provided at all) no useful info can be provided for an issue in here. Pinpointing certain types of crashes is proving mere impossible. |
|
🧀 |
|
Crashing when loading in after switching to this new build. Edit: Client update just went out and this crash is now resolved |
|
Can someone confirm if RemoveDecal native is functioning? I had some issues with mine, but I am not sure if its because of my implementation or actual bug. |
Uh oh!
There was an error while loading. Please reload this page.
Hotfix 3 is live. It rolls up another round of community-reported bugs from our GitHub Discussions, plus a set of client and server crash fixes.
What's fixed in this patch:
GetSafeCoordForPedwork again (#88)ui_pageURLs no longer return HTTP 403 (#128)GetInvokingResourcereturns the resource name again instead of nil when triggering an event inside the same resource (#154)CreateRuntimeTextureFromImageto report files as not found (#149)minimap.gfx, apply again (#92)IsPlayerAceAllowedaccepts a string forplayerSrcagain instead of requiring an integer (#134)RegisterCommandis no longer always empty (#60)GetVehicleTypenow returns the correct type for non-networked vehiclesGetIsVehicleElectricis now exposed (#118)SetPedHairTintandSetPedHeadOverlayColorwork again (#67)defer.donewhen passing the wrong typeGetVelocitycrash when a vehicle id points to a player pedIsDuplicityVersionandGetInstanceIdwhen called outside a scriptWe appreciate everyone taking the time to file detailed reports. Keep them coming on the Discussions tab.
All reactions