Updated LSPDFR and GTA, whenever I launch rage and hit F4 the game pauses but the console doesn't show. I'm able to still launch plugins but I just can't see the console itself. I also don't seem to be able to see the UI from various plugins like Callout interface, Nexus Dispatch Radio or the radar from Nexus MDT.RagePluginHook.log Any help would be appreciated : )

Do you have ScriptHookVDotNet installed?

8 minutes ago, Lennyy said:

Do you have ScriptHookVDotNet installed?

Yes, the most recent version.

Remove it and try again.

10 minutes ago, Lennyy said:

Remove it and try again.

Still not showing the rage console or callout interface

Looking at your log, all your plugins (CalloutInterface, NexusDispatch, NexusMDT, Policing Redefined, and NPCI) are loading fine, and the game is registering your key presses.

When the console opens and pauses the game but fails to draw on screen, or when plugins load without their UI elements appearing, it means RAGE Plugin Hook’s DirectX 11 overlay rendering engine is failing to draw over the game’s display window.

How to Fix

1. Change Game Display Mode (Most Common Cause)

RAGE Plugin Hook often fails to draw its DirectX overlay if GTA V is set to Exclusive Fullscreen.

1. Open GTA V and go to Settings > Graphics.

2. Change Display Mode from Fullscreen to Windowed Borderless (or Windowed).

3. Save changes and test hitting F4 or opening your plugin menus (like Nexus MDT via Q or Callout Interface via F8).

2. Disable Hardware Overlays (DirectX Conflicts)

Third-party overlays steal DirectX rendering hooks from RAGE Plugin Hook, causing invisiblity issues. Disable or turn off screen capture/overlays in the following applications:

• Discord: Go to Settings > Game Overlay > Turn off "Enable in-game overlay".

• NVIDIA GeForce Experience / ShadowPlay: Open In-Game Overlay settings and disable it.

• GeForce / AMD Software: Disable instant replay or desktop capture while playing.

• Windows Game Bar / Game Mode: Turn off Xbox Game Bar in Windows Settings.

3. Adjust RAGE Plugin Hook Settings

1. Launch the game by double-clicking RAGEPluginHook.exe while holding down the Left Shift key on your keyboard until the configuration menu appears.

2. Under the Game Settings tab, go to Command Line Switches.

3. Check Force DirectX11 and Force Windowed.

4. Save and launch. Once in game, you can toggle back to Borderless Windowed mode.

Are you running any graphic enhancements like ReShade, ENB, or QuantV alongside your plugins?

7 minutes ago, lushchak said:

Looking at your log, all your plugins (CalloutInterface, NexusDispatch, NexusMDT, Policing Redefined, and NPCI) are loading fine, and the game is registering your key presses.

When the console opens and pauses the game but fails to draw on screen, or when plugins load without their UI elements appearing, it means RAGE Plugin Hook’s DirectX 11 overlay rendering engine is failing to draw over the game’s display window.

How to Fix

1. Change Game Display Mode (Most Common Cause)

RAGE Plugin Hook often fails to draw its DirectX overlay if GTA V is set to Exclusive Fullscreen.

1. Open GTA V and go to Settings > Graphics.

2. Change Display Mode from Fullscreen to Windowed Borderless (or Windowed).

3. Save changes and test hitting F4 or opening your plugin menus (like Nexus MDT via Q or Callout Interface via F8).

2. Disable Hardware Overlays (DirectX Conflicts)

Third-party overlays steal DirectX rendering hooks from RAGE Plugin Hook, causing invisiblity issues. Disable or turn off screen capture/overlays in the following applications:

• Discord: Go to Settings > Game Overlay > Turn off "Enable in-game overlay".

• NVIDIA GeForce Experience / ShadowPlay: Open In-Game Overlay settings and disable it.

• GeForce / AMD Software: Disable instant replay or desktop capture while playing.

• Windows Game Bar / Game Mode: Turn off Xbox Game Bar in Windows Settings.

3. Adjust RAGE Plugin Hook Settings

1. Launch the game by double-clicking RAGEPluginHook.exe while holding down the Left Shift key on your keyboard until the configuration menu appears.

2. Under the Game Settings tab, go to Command Line Switches.

3. Check Force DirectX11 and Force Windowed.

4. Save and launch. Once in game, you can toggle back to Borderless Windowed mode.

Are you running any graphic enhancements like ReShade, ENB, or QuantV alongside your plugins?

None of them work, I already had it launching in forced windowed mode. Nexus MDT and Policing Redefined load their UI fine its just the rage console, callout interface GUI's wont launch.

All the overlays are already disabled

Since Nexus MDT and Policing Redefined draw their UI using external/WPF windows, but the RAGE Console (F4) and Callout Interface are failing to render, this confirms that RAGE Plugin Hook's internal DirectX draw calls and DPI scaling coordinates are drawing off-screen or failing to hook into the game's active swapchain.

The resolution recorded in your log shows an unusual height (1920x1081), which is a clear signature of Windows Display DPI Scaling stretching the window coordinates.

Here is how to fix it:

Step 1: Fix High DPI Scaling Behavior

Windows DPI scaling (125%, 150%, etc.) causes RAGE Plugin Hook's drawing layer to render outside the visible screen area while the game still registers the pause state.

1. Navigate to your main Grand Theft Auto V folder.

2. Right-click GTA5.exe $\rightarrow$ Properties $\rightarrow$ Compatibility tab.

3. Click Change high DPI settings.

4. Check Override high DPI scaling behavior.

5. Set the dropdown underneath to Application.

6. Click Apply and OK.

7. Repeat the exact same steps for RAGEPluginHook.exe.

Step 2: Match GTA V's In-Game DirectX Version

In your screenshot, RAGE Plugin Hook is forcing DirectX 11. If GTA V's internal graphics settings are set to DirectX 10 or 10.1, the RPH console will render behind the game buffer.

1. Launch GTA V.

2. Go to Settings $\rightarrow$ Graphics.

3. Ensure DirectX Version is explicitly set to DirectX 11.

4. Match your screen resolution to your monitor's native display (e.g., 1920x1080).

Step 3: Check for Duplicate RAGENativeUI.dll

Callout Interface relies heavily on RAGENativeUI.dll. If there is a version conflict between your main game directory and plugin subfolders, the GUI will silently fail to render.

1. Go to your main GTA V folder.

2. Ensure you have the latest RAGENativeUI.dll located directly in your root GTA V folder (not in plugins or plugins/LSPDFR).

3. Delete any copies of RAGENativeUI.dll sitting inside plugins/LSPDFR/ so that every mod uses the single root version.

Step 4: Reset RAGE Console Settings in RagePluginHook.ini

If the console window was dragged off-screen in a previous session, it stays off-screen.

1. Open RagePluginHook.ini in your main GTA V folder using Notepad.

2. Locate the [Miscellaneous] section.

3. Ensure the following values are set (or add them if missing):

   Ini, TOML

   [Miscellaneous]
   ConsoleKey=F4
   ConsoleScrollAmount=4
   AlwaysShowConsoleOutput=False
   ShowOnScreenWarnings=True
   

4. Save and close the file.

Once applied, launch via RAGE Plugin Hook in Borderless Windowed mode and test hitting F4 and F8.

15 minutes ago, lushchak said:

Since Nexus MDT and Policing Redefined draw their UI using external/WPF windows, but the RAGE Console (F4) and Callout Interface are failing to render, this confirms that RAGE Plugin Hook's internal DirectX draw calls and DPI scaling coordinates are drawing off-screen or failing to hook into the game's active swapchain.

The resolution recorded in your log shows an unusual height (1920x1081), which is a clear signature of Windows Display DPI Scaling stretching the window coordinates.

Here is how to fix it:

Step 1: Fix High DPI Scaling Behavior

Windows DPI scaling (125%, 150%, etc.) causes RAGE Plugin Hook's drawing layer to render outside the visible screen area while the game still registers the pause state.

1. Navigate to your main Grand Theft Auto V folder.

2. Right-click GTA5.exe $\rightarrow$ Properties $\rightarrow$ Compatibility tab.

3. Click Change high DPI settings.

4. Check Override high DPI scaling behavior.

5. Set the dropdown underneath to Application.

6. Click Apply and OK.

7. Repeat the exact same steps for RAGEPluginHook.exe.

Step 2: Match GTA V's In-Game DirectX Version

In your screenshot, RAGE Plugin Hook is forcing DirectX 11. If GTA V's internal graphics settings are set to DirectX 10 or 10.1, the RPH console will render behind the game buffer.

1. Launch GTA V.

2. Go to Settings $\rightarrow$ Graphics.

3. Ensure DirectX Version is explicitly set to DirectX 11.

4. Match your screen resolution to your monitor's native display (e.g., 1920x1080).

Step 3: Check for Duplicate RAGENativeUI.dll

Callout Interface relies heavily on RAGENativeUI.dll. If there is a version conflict between your main game directory and plugin subfolders, the GUI will silently fail to render.

1. Go to your main GTA V folder.

2. Ensure you have the latest RAGENativeUI.dll located directly in your root GTA V folder (not in plugins or plugins/LSPDFR).

3. Delete any copies of RAGENativeUI.dll sitting inside plugins/LSPDFR/ so that every mod uses the single root version.

Step 4: Reset RAGE Console Settings in RagePluginHook.ini

If the console window was dragged off-screen in a previous session, it stays off-screen.

1. Open RagePluginHook.ini in your main GTA V folder using Notepad.

2. Locate the [Miscellaneous] section.

3. Ensure the following values are set (or add them if missing):

   Ini, TOML

   [Miscellaneous]
   ConsoleKey=F4
   ConsoleScrollAmount=4
   AlwaysShowConsoleOutput=False
   ShowOnScreenWarnings=True
   

4. Save and close the file.

Once applied, launch via RAGE Plugin Hook in Borderless Windowed mode and test hitting F4 and F8.

Still nothing, ReShade is loading now though so there's some progress.

RPH Crashes when I force duty now,

3 minutes ago, RalphT5123 said:

Still nothing, ReShade is loading now though so there's some progress.

The fact that ReShade is now loading is a huge clue. ReShade injects its own dxgi.dll into the GTA V folder to hook DirectX 11. When ReShade and RAGE Plugin Hook fight over the DirectX 11 swapchain, RPH's internal draw calls (like the console and RAGENativeUI elements) get rendered behind ReShade or fail to output entirely, while external WPF windows (Nexus MDT) still appear fine.

To fix the DirectX hooking conflict between ReShade and RAGE Plugin Hook:

1. Rename ReShade's DLL (The Most Common Fix)

RAGE Plugin Hook needs priority when hooking DirectX.

1. Go to your root Grand Theft Auto V folder.

2. Find dxgi.dll (this is ReShade's main file).

3. Rename it to d3d11.dll.

4. Launch the game via RAGEPluginHook.exe.

Note: If d3d11.dll already exists in your folder, rename dxgi.dll to ReShade64.dll or dxgi.dll.bak temporarily to test if the console appears without ReShade active.

2. Disable ReShade's In-Game Overlay During Boot

If ReShade initializes its overlay before RPH initializes its renderer, RPH gives up on drawing.

1. Open ReShade.ini in your root GTA V folder.

2. Find ShowOverlay= and set it to 0.

3. Save and launch via RPH. Once in-game, hit F4 first to verify the console, then use your ReShade keybind (usually Home or Pos1).

3. Clear Reshade / ENB ASI Loaders

If you have an asi loader for ReShade (like ReShade64.asi), remove it from the main directory and keep only the renamed .dll.

Does renaming dxgi.dll bring back the F4 console and Callout Interface UI?

7 minutes ago, lushchak said:

The fact that ReShade is now loading is a huge clue. ReShade injects its own dxgi.dll into the GTA V folder to hook DirectX 11. When ReShade and RAGE Plugin Hook fight over the DirectX 11 swapchain, RPH's internal draw calls (like the console and RAGENativeUI elements) get rendered behind ReShade or fail to output entirely, while external WPF windows (Nexus MDT) still appear fine.

To fix the DirectX hooking conflict between ReShade and RAGE Plugin Hook:

1. Rename ReShade's DLL (The Most Common Fix)

RAGE Plugin Hook needs priority when hooking DirectX.

1. Go to your root Grand Theft Auto V folder.

2. Find dxgi.dll (this is ReShade's main file).

3. Rename it to d3d11.dll.

4. Launch the game via RAGEPluginHook.exe.

Note: If d3d11.dll already exists in your folder, rename dxgi.dll to ReShade64.dll or dxgi.dll.bak temporarily to test if the console appears without ReShade active.

2. Disable ReShade's In-Game Overlay During Boot

If ReShade initializes its overlay before RPH initializes its renderer, RPH gives up on drawing.

1. Open ReShade.ini in your root GTA V folder.

2. Find ShowOverlay= and set it to 0.

3. Save and launch via RPH. Once in-game, hit F4 first to verify the console, then use your ReShade keybind (usually Home or Pos1).

3. Clear Reshade / ENB ASI Loaders

If you have an asi loader for ReShade (like ReShade64.asi), remove it from the main directory and keep only the renamed .dll.

Does renaming dxgi.dll bring back the F4 console and Callout Interface UI?

There's no ShowOverlay option in the Reshade INI. I've renamed the files and still nothing

Fixed it, it was an issue in the Nvidea display options. How are you doing today?