[Bug] GTA Launches in Base Game Instead of FiveM when altering graphics

[TechGeek285]

Summary

When restarting to apply graphics effects, GTAV loads into the base game and not back into FiveM. Further, the rockstar games launcher opens each time you start FiveM enhanced

Issue type

Client

Repro rate

Always

Server build version

FXServer-early-access b95 win32

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

SSD NVMe

Connection type

Ethernet

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Enter FiveM enhanced and change graphics settings ( unsure which one causes a restart but if you change them all, it triggers the "Restart Required Screen". )
2. Comply with the restart as requested and wait,
3. GTA launches into the game instead of the FIveM version

Expected Behavior

The game should launch back into the server you were just in, connecting again properly.

Actual Behavior

Base game GTAV launches and puts you into the main menu

FiveM goes from waiting for ticket to the connection failed error as below.

It is worth noting that the Rockstar Games launcher always launches when I start FiveM enhanced ( doesnt happen on legacy ).

Evidence

Additional Context

My GTAV is installed on Steam. I have both GTA Enhanced and Legacy installed on my system. This happens consistently for me.

[Gogsi]

This seems inconsistent at least. I had it launch GTA V Enhanced once and actually FiveM Enhanced once

[TGIANN]

Also, Steam gives a warning saying GTA: Enhanced is already running.

[dalekenium-cfx]

Thanks for the report! I've fixed restarting on our end and the fix should be included in the next patch.

[Gogsi]

A fix for this bug has been implemented and is available in the August 4 patch. Please try again and let us know if the issue persists. Thanks for your help!