Patrick16
-
Joined
Reputation Activity
-
Patrick16reacted to Officerphillips69 in Ragehook F4 not working.Try making your RagePluginHook.ini file in your GTA V folder look like this
[Miscellaneous]
IsDeveloperModeEnabled=True
PluginTimeoutThreshold=10000
ConsoleKey=F4
They forgot to add the line to the ini file in the latest Ragehook download. Simple overlook.
Personally I chose to make it F3 instead, that way I can bring up ScriptHook V in my F4 button and my Ragehook F3 button console works fine now
-
Ok this thread will more than likely get Closed and that is fine. I have found a solution for those that are having the Pressing F4 and no console.
In your GTA V folder you will find your RagePluginHook.exe look below that and you will see the RagePluginHook.ini file
It probably looks like this
[Miscellaneous]
IsDeveloperModeEnabled=True
PluginTimeoutThreshold=10000
It needs to look like this
[Miscellaneous]
IsDeveloperModeEnabled=True
PluginTimeoutThreshold=10000
ConsoleKey=F4
It appears the people that coded the new RagePluginHook forgot to add a line in the ini.
So why am I posting this here instead of the RageHook forums? Well its simple. Their site is having extreme difficulty with lag. You can barely get from one topic to another and also people ask a question and it goes days without answer. In short, their support is not supportive. Thought users might find this helpful.
Feel free to close, but please don't delete otherwise you will find yourself having to close a lot of these type of threads, when the problem was just <SOLVED>
Thanks!
-
Patrick16reacted to Officerphillips69 in Crash when press shift on-dutyOk here is a small solution that may work for those having SHIFT crash problems. I think this is highly related to a .NET framework issue. Go to your Programs. Find .NET Frameworks. You should have 4.5.1 RC installed. Go to Uninstall, and it will prompt you to either REPAIR or REMOVE. Try to Repair. Then look around again, see if you have an older version installed as well. I had a 1.1.1 installed for some reason still. I removed that one and left the 4.5.1 alone. So far no crashes.