tzioneretz

Thanks man @tzioneretz, appreciate your help.

Glad you're back in action, man!  I have the exact same problem: The RPH works flawlessly except that the console is invisible.  Yet, I can type commands into the invisible console and they get executed.
 
You can definitely install mods and plugins.  I'm running a bunch by Albo, a few callouts, E.L.S., the Player Location Display, etc.  Some of them don't render the overlays the same way the console doesn't show (e.g. the Police SmartRadio), but if you know the commands, you're good to go.

Thank you @tzioneretz! I'll try it.

Yes, I can.  Basically, my RPH and LSPDFR and all the plugins work fine EXCEPT that the console and the overlays in some of the plugins aren't showing.  Typing or pressing "blindly" works perfectly.
 
If you can't go on duty, it means your RPH is not even loading.  I had that issue from time to time, when I messed around with the settings.  What fixed it for me was enabling the developer console.  When you click on the RAGEPluginHook.exe hold down the SHIFT key until you get the settings.  Once the settings show, go to Advanced, scroll all the way down, and check the Enable Developer Mode option.  That should make RPH work again.

Guys, it seems we have the same problem (I understand German).  I'm running a number of plugins, and they all load fine.  However, pressing F4 freezes the game but does not display the console.  (The same thing happens if I reassign the F4 key to e.g. F8 or any other.)  If I type while the game is frozen, the commands are accepted, which means the console is there but it's not displaying.
 
I think the same issue is causing my Police SmartRadio and my Computer+ plugins to not show, even though I can use all of them "blindly."
 
I've been searching high and low all over the Internet for days now, and tried everything: reinstall, remove plugins, change the various setup and .ini files, run as administrator, run fullscreen vs. run windowed, etc., etc.  I'm so fed up... :(
 
FWIW, below is my logfile.  However, I suspect this is an issue with DirectX or some Windows component, rather than Rage or LSPDFR...