LSPD:FR =/= Ragehook.

The issue is with Ragehook. Not with the mods that use Ragehook like LSPD:FR nor its installation as I previously stated that EVERYTHING including LSPD:FR works but the console that Ragehook allows.

Basically, this thread is about Ragehook. Not LSPD:FR that uses it.

 

Yes. That's why you misunderstood me. I was referring to a perfectly functioning ragehook with the lspdfr mod. Not sure why did i even think of that, since this thread is clearly about ragehook. Lol sorry. What i meant once again, was that if for example  there wasn't an issue with ragehook and 99.9% of people could open the console and 0.1% couldn't, then that would be on their side. I hope you understand what i meant now. Sorry, wasn't trying to look like a jerk. Note to self: next time before making an ass out of myself, i need to double check if i have the same issue. Derp.

Yes. That's why you misunderstood me. I was referring to a perfectly functioning ragehook with the lspdfr mod. Not sure why did i even think of that, since this thread is clearly about ragehook. Lol sorry. What i meant once again, was that if for example  there wasn't an issue with ragehook and 99.9% of people could open the console and 0.1% couldn't, then that would be on their side. I hope you understand what i meant now. Sorry, wasn't trying to look like a jerk. Note to self: next time before making an ass out of myself, i need to double check if i have the same issue. Derp.

Since we're talking hypotheticals then it'd be considered a minor issue since it's a small subset of the user population that is experiencing issues. Also, hypothetically, it's also not hardware related and thus not the users fault as you're trying so hard to make it be.

It's enough of the population of users that it is reported as a major software problem with Ragehook. It's not minor nor it is the problem of the user. The user cannot recode a issue of DirectX on their end since it's the problem of the developers of Ragehook to fix. If it was hardware related then the user could fix it but it's not.

I tried to start the plugin from the start of games thanks to the startup file, to avoid passing by rage console, and the mods are demarer the launch of games, but are not displayed .. such as the plugin "policeRadio" it is quite active radio opens but is invisible ..

it is therefore a visual problem

Edited July 20, 201510 yr by Marvin El Cørøma

Since we're talking hypotheticals then it'd be considered a minor issue since it's a small subset of the user population that is experiencing issues. Also, hypothetically, it's also not hardware related and thus not the users fault as you're trying so hard to make it be.

It's enough of the population of users that it is reported as a major software problem with Ragehook. It's not minor nor it is the problem of the user. The user cannot recode a issue of DirectX on their end since it's the problem of the developers of Ragehook to fix. If it was hardware related then the user could fix it but it's not.

Right, let's forget LSPDFR and Ragehook for a second here and take another example, since you still are not getting my point across. Let's take for example, a game requires net framework 4.0 to function, one user has it installed, his game works flawlessly. Another user doesn't have net framework 4.0 installed, his game doesn't start. He then blames the game for problems on his own end. This is the point i'm making here. I'm not saying that if it's clearly the software's fault then the other person is doing something wrongly. You get my point now?

I tried to start the plugin from the start of games thanks to the startup file, to avoid passing by rage console, and the mods are demarer the launch of games, but are not displayed .. such as the plugin "policeRadio" it is quite active radio opens but is invisible ..

it is therefore a visual problem

No it's a ragehook problem. Downgrade to an older version of ragehook, RAGEPluginHook_0_16_607_3592_ALPHA and it should work. Atleast other people said so.

I had the issue of rage console not being visible as well as Police Radio. Oddly enough it came back when I took More Control V out of the startup file. Not sure if that's what fixed it or why it would be More Control that had anything to do with it, but it seemed to work for me.  This is on the latest version of Rage Hook, LSPDFR and Script Hook V. 

Hm okay and thus pending a new stable version or the version I could find rage me tell you? because I think the last:

"RAGE Plugin Hook - Open Alpha - 0.17.639.4039"

Right, let's forget LSPDFR and Ragehook for a second here and take another example, since you still are not getting my point across. Let's take for example, a game requires net framework 4.0 to function, one user has it installed, his game works flawlessly. Another user doesn't have net framework 4.0 installed, his game doesn't start. He then blames the game for problems on his own end. This is the point i'm making here. I'm not saying that if it's clearly the software's fault then the other person is doing something wrongly. You get my point now?

You need to stop using hypotheticals and not use hypotheticals that are really unrelated to the issue at hand. Or trying to compare apples to oranges in a way to prove a point.

You continue to try to blame the user and use all these nonsensical points to victim blame. It's exhausting to talk about since you'll make another hypothetical even more unrelated to what we're talking about.

You need to stop using hypotheticals and not use hypotheticals that are really unrelated to the issue at hand. Or trying to compare apples to oranges in a way to prove a point.

You continue to try to blame the user and use all these nonsensical points to victim blame. It's exhausting to talk about since you'll make another hypothetical even more unrelated to what we're talking about.

Yes i know it's unrelated that's why i said it in my other comments above. All of this conversation happened because i'm a dumbass and instead of being intelligent and double checking if i have the same issue, i presumed it works fine on my end and that's why i said in my first comment, that it shouldn't be the software's fault. Also the blame is totally on the user if a game needs net framework 4 and you don't have it( I know this has nothing to do with the thread, just making a point, ffs).

Yes i know it's unrelated that's why i said it in my other comments above. All of this conversation happened because i'm a dumbass and instead of being intelligent and double checking if i have the same issue, i presumed it works fine on my end and that's why i said in my first comment, that it shouldn't be the software's fault. Also the blame is totally on the user if a game needs net framework 4 and you don't have it( I know this has nothing to do with the thread, just making a point, ffs).

You're studying IT so let me inform you. DirectX is something that graphics card support. It's something video games use to function. It's not somehow automatically uninstalled. It's on all cards. However, the Ragehook issue is about how the hook itself trying to use DirectX for its command console to function. It's a software issue because it's related to the code of Ragehook and how it functions on some PCs.

All in all, your point isn't a point. It's unrelated, hypothetical, and you're trying ever so hard to blame the user. 

You're studying IT so let me inform you. DirectX is something that graphics card support. It's something video games use to function. It's not somehow automatically uninstalled. It's on all cards. However, the Ragehook issue is about how the hook itself trying to use DirectX for its command console to function. It's a software issue because it's related to the code of Ragehook and how it functions on some PCs.

All in all, your point isn't a point. It's unrelated, hypothetical, and you're trying ever so hard to blame the user. 

Wow arguing with you is like talking to a brick wall because you cannot understand what i'm even talking about... Do you really think i'm that dumb that i don't know what directx is? Was i even talking about ragehook or directx in the post above? Your comment is unrelated to my point.

Ok new problem, my rage crash from the start now ... -_- alor that I board change anything ... there is nothing more stable I'll wait for the new rage has set day or I do not know that because there is too much

Wow arguing with you is like talking to a brick wall because you cannot understand what i'm even talking about... Do you really think i'm that dumb that i don't know what directx is? Was i even talking about ragehook or directx in the post above? Your comment is unrelated to my point.

Because this entire topic is about Ragehook. Not Net Framework.

Because this entire topic is about Ragehook. Not Net Framework.

Yes and i already acknowledged that. As i said again, my first comment on this thread was out of my own stupidity thinking that this newest version of ragehook works fine and the console opens fine for me, so i assumed it works for everyone and if it doesn't work for you, then you are doing something wrong. Which obviously isn't the case. It IS ragehook's fault. However, my point in there was NOT about ragehook or directx but entirely about something else, and YES i understand it's unrelated. Sorry. All i was saying again, is that if a software functions correctly(which is NOT the case with this newest ragehook) then it isn't the software's fault, but the user's own fault of installing something incorrectly. That's all i'm saying, that's my point. I know it's unrelated and it's the wrong thread to post in. I ASSUMED that ragehook works fine and the user is incorrectly installing it, so it doesn't work correctly. Get it now? Jesus, talk about making a mountain out of a molehill.

Yes and i already acknowledged that. As i said again, my first comment on this thread was out of my own stupidity thinking that this newest version of ragehook works fine and the console opens fine for me, so i assumed it works for everyone and if it doesn't work for you, then you are doing something wrong. Which obviously isn't the case. It IS ragehook's fault. However, my point in there was NOT about ragehook or directx but entirely about something else, and YES i understand it's unrelated. Sorry. All i was saying again, is that if a software functions correctly(which is NOT the case with this newest ragehook) then it isn't the software's fault, but the user's own fault of installing something incorrectly. That's all i'm saying, that's my point. I know it's unrelated and it's the wrong thread to post in. I ASSUMED that ragehook works fine and the user is incorrectly installing it, so it doesn't work correctly. Get it now? Jesus, talk about making a mountain out of a molehill.

You're the one who derailed the topic because you tried so hard to blame the user for the problem.

You're entirely surmising that it was a faulty installation but it's not. We've also discussed this but you're beating a dead horse to try to say it is caused by the installation. We know it's not. You know it's not. So why are you saying it's the user if we all know it's Ragehook?

But it's kind of a saving grace that a new update just went live because now LSPD:FR and Ragehook is broken again till it gets updated again.

Ok new problem, my rage crash from the start now ... -_- alor that I board change anything ... there is nothing more stable I'll wait for the new rage has set day or I do not know that because there is too much

Try installing Ragehook version 0_16_607_3592_ALPHA.  

Again, as stated in earlier post; I had the same issue with the console not popping up and PoliceRadio working fine, but the GUI would not show up.  LSPDFR worked just fine, no issues, just no console or GUI for PoliceRadio.  I installed the above older version of Ragehook (I think it's the previous release) and now everything is back to normal with no issues any longer.

Try this...should work as long as your LSPDFR is not porked.  You could try reinstalling LSPDR 2.0a just to make sure and then install the Ragehook quoted above.

 

Edited July 20, 201510 yr by drdetroit

You're the one who derailed the topic because you tried so hard to blame the user for the problem.

You're entirely surmising that it was a faulty installation but it's not. We've also discussed this but you're beating a dead horse to try to say it is caused by the installation. We know it's not. You know it's not. So why are you saying it's the user if we all know it's Ragehook?

But it's kind of a saving grace that a new update just went live because now LSPD:FR and Ragehook is broken again till it gets updated again.

Yup apparently this update according to the people on steam, is to fix these stuttering issues that a lot of people are having. Personally never had any stutters, except when i ran the keepcalm mod, but hey if it fixes the issue and people can finally play normally, then great. Only problem i have with these two ill gotten gains updates, is that my framerate has decreased somewhat. Not sure if it's related to these updates, but i assume so, since my fps was better, before these two updates.

Try installing Ragehook version 0_16_607_3592_ALPHA.  

Again, as stated in earlier post; I had the same issue with the console not popping up and PoliceRadio working fine, but the GUI would not show up.  LSPDFR worked just fine, no issues, just no console or GUI for PoliceRadio.  I installed the above older version of Ragehook (I think it's the previous release) and now everything is back to normal with no issues any longer.

Try this...should work as long as your LSPDFR is not porked.  You could try reinstalling LSPDR 2.0a just to make sure and then install the Ragehook quoted above.

 

would you have a link to the page with the version of rage I need .. Plz ^^

I tried with the old version of Rage and it is still not working.

I tried with the old version of Rage and it is still not working.

The new update that just came out for GTA V has broken LSPDFR and rage hook. Wait patiently for new updates to LSPDFR and ragehook.

Yip, seems there has been an update...nothing is working anymore, mod wise.