You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
required sync value in altv.toml is true (cefFrameSync)
Like the screen shows the game get stuck on shutdown longest wait 10 Minutes then killed over taskmanager
connect to a server
using F6 (open zigger dev tools) (stay open or close)
used F8 console command quit
freeze
no crash handler/log entries
quit with the exit button on Start page = no issue instant exit
quit with F1 Exit button on connected
only connected and press F1 = small freeze 5-20s then exit
using F8 console command after connect (without any script/webview/ofterstuff) = instant quit
CPU: AMD 2800X
GPU: Nvidia 1660S with driver 560.94
Windows 10
By submitting this ticket, I affirm that I have verified the presence of this issue on the latest RC (Release Candidate) version available at the time of writing this ticket.
The text was updated successfully, but these errors were encountered:
Description of the problem
required sync value in altv.toml is true (cefFrameSync)
Like the screen shows the game get stuck on shutdown longest wait 10 Minutes then killed over taskmanager
connect to a server
using F6 (open zigger dev tools) (stay open or close)
used F8 console command quit
freeze
no crash handler/log entries
quit with the exit button on Start page = no issue instant exit
quit with F1 Exit button on connected
only connected and press F1 = small freeze 5-20s then exit
using F8 console command after connect (without any script/webview/ofterstuff) = instant quit
CPU: AMD 2800X
GPU: Nvidia 1660S with driver 560.94
Windows 10
altv.toml
Reproduction steps
qa-tools.zip
connect to a server
using F6 (open zigger dev tools) (stay open or close)
used F8 console command quit
freeze
Expected behaviour
quit and not freeze
Additional context
No response
Operating system
Windows
Version
alt:V build #16.2.25-rc.13
Crashdump ID
No response
Confirmation of issue's presence
The text was updated successfully, but these errors were encountered: