Before you start
You need
- GTA V PC with LSPDFR and RAGE Plugin Hook already working together.
- .NET Framework 4.8.
- The compiled VibeDispatch-Dev03.zip package.
You do not need Visual Studio to install the compiled plugin.
Find the game you actually launch
Open the GTA V installation containing GTA5.exe and RAGEPluginHook.exe.
The Rockstar Games folder in Documents usually contains user data. It is only a valid destination if the game itself is installed there.
Two files. One destination.
Close GTA V and RAGE Plugin Hook
If replacing an earlier Vibe Dispatch build, keep a copy of its DLL and INI first. Keep only one installed Vibe Dispatch DLL.
Extract the package
Right-click
VibeDispatch.zipin File Explorer, choose Extract All…, then open the extracted folder.Inside
plugins\LSPDFR\, you should findVibeDispatch.dllandVibeDispatch.ini.Copy the DLL and INI into the game
Place both files directly in your actual game's
plugins\LSPDFR\folder. Create the LSPDFR subfolder if needed, after confirming LSPDFR is installed.Detected Legacy installation on this computer:
C:\Program Files\Rockstar Games\Grand Theft Auto V Legacy\plugins\LSPDFR\
Another installation was detected at
C:\Program Files\Rockstar Games\Grand Theft Auto V\. Use the installation you launch with LSPDFR. If Windows requests permission to copy into Program Files, approve it only for these two Vibe Dispatch files.Do not place them inside an extra
VibeDispatchsubfolder. Do not copy SDK references or replace any LSPDFR core DLL.Check the final layout
Your GTA V folder\ ├── GTA5.exe ├── RAGEPluginHook.exe └── plugins\ ├── LSPD First Response.dll ← existing LSPDFR file └── LSPDFR\ ├── VibeDispatch.dll └── VibeDispatch.iniLaunch and go on duty
Start the same GTA V installation through RAGE Plugin Hook. Load LSPDFR using your normal setup, then go on duty. LSPDFR should load Vibe Dispatch from its plugin folder.
Look for VIBE DISPATCH — SYSTEM ONLINE. Do not load a second copy separately through the RPH console.
Try your first dispatch
- Go on duty and stand outdoors near a road.
- Press F7. Look for a call such as VD-1001, its priority, incident type, street and description.
- Press Y to accept. A GPS route should appear. Press G to restore it if needed.
- Press F8 to clear the call. Its route should disappear and the result is stored in session history.
- Press F7 again, then N to test declining an offered call.
| Key | Action |
|---|---|
| F7 | Create a test call, or show the current call again. |
| F8 | Clear the current call. |
| Y | Accept an offered call and request GPS. |
| N | Decline an offered call. |
| G | Show call details and retry GPS for an accepted call. |
The on-screen actions use keyboard controls; they are not clickable buttons. P1 means Critical, P2 High and P3 Standard. P1/P2 can request multiple responders, subject to the configured cap and LSPDFR availability.
Adjust your settings
Open VibeDispatch.ini beside the installed DLL with Notepad. Edit the values, save the file, then restart the game so the plugin reads them again. Preserve the .ini extension.
| Setting | Default | What it does |
|---|---|---|
AutomaticCalls | true | Set false to use F7 only. |
MinimumIntervalSeconds | 15 | Minimum automatic-call interval; 5–3600 seconds. |
MaximumIntervalSeconds | 30 | Maximum interval; at least the minimum, up to 7200 seconds. |
AutomaticBackup | true | Set false to disable automatic backup requests. |
MaximumRespondingUnits | 3 | Cap of 1–8. This prototype requests up to 3 for P1 and 2 for P2. |
NotificationDurationMs | 15000 | Panel duration in milliseconds; 1000–60000. |
DebugLogging | false | Set true for extra logging. Errors are always logged. |
TestCallKey / ClearCallKey | F7 / F8 | Change the test and clear controls. |
AcceptKey / DeclineKey / GpsKey | Y / N / G | Change the response and GPS controls. |
Use distinct key names, such as F9. Duplicate bindings reset all controls to defaults. Automatic calls require being on duty with no active Vibe Dispatch call.
If something does not work
| Symptom | Check |
|---|---|
| No online message or F7 response | Confirm you copied into the installation you launched, both files are directly in plugins\LSPDFR\, and LSPDFR is loaded. Go off duty and back on. Check that another mod is not using the same key. |
| Plugin fails to load | Check the RPH/LSPDFR logs for VibeDispatch, [Vibe Dispatch] and dependency errors. Confirm compatible GTA V, LSPDFR and RPH versions. The developer SDK used for this build is older; runtime compatibility still needs verification. |
| No automatic calls | Check AutomaticCalls=true, go on duty and clear any active call. The default interval is 15–30 seconds. |
| No GPS | Accept with Y first, then press G to retry. Declined or cleared calls have no route. |
| No suitable location | Move outdoors near another road and retry F7. The plugin skips locations it cannot validate. |
| No backup or fewer units | P3 does not request automatic backup. Check the backup switch and unit cap. LSPDFR controls responder selection and may fail to provide a unit; inspect the log. |
| Panel disappeared or overlaps another mod | F7 redisplays the existing call. Increase the notification duration if needed. This prototype shares the game's subtitle area. |
| Nothing happening at the location | Expected in this prototype: dispatch descriptions do not yet spawn an incident scene. LSPDFR's normal calls may also continue. |
Update or remove
Update
Close the game. Back up your existing Vibe Dispatch DLL and INI, then replace only those files. If keeping custom settings, compare your INI with the new version before restarting.
Uninstall
Close the game and remove VibeDispatch.dll and VibeDispatch.ini from the LSPDFR subfolder. Keep LSPDFR's own files in place.
Session history resets when the plugin reloads. Backup vehicles are owned by LSPDFR and are not forcibly deleted when you clear a Vibe Dispatch incident.