Cyan

Definitely. We've been sending messages out to people who have been reported reminding them that file descriptions should be about the files and not other services they offer. This doesn't just affect one author's files, so a lot of authors will find themselves receiving this message. We don't want to be unfair and only apply our rules to certain people. People will be given time to comply and non-complaint files will be hidden after a grace period if no changes are made. We've also rolled out our external link protection system, reminding users when clicking external links to exercise caution.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future. This is an English speaking community, please include an English translation so a more broad section of our userbase can help you.

Sadly due to block caching this is bug with the software suite we use. It's not easily fixable as it would require changing core block code, but we'll consider this for a future update.

Please see the warning on the LSPDFR download page for more information.

Yes, of course. @Back12 please report these messages to us using the reporting tool. That will allow all of our moderation staff to easily access the private message thread, along with full message histories and edit metadata to take appropriate action. In regards to leaks, if someone on the site is using assets without permission then this isn't allowed per our File Guidelines. Please encourage the author of the asset to report this to us via our reporting tools or if this is not possible to get in touch via e-mail (management at lcpdfr dot com) with evidence. In this particular case, most of it comes down either: it happened off site (the original post) or it wasn't reported to us. If it happened on DIscord, you may want to reach out to Discord Trust & Safety. If it happened here, report this to us using our reporting tools. I'm sorry you feel that people on the site are "protected" in some way. I'll be genuinely honest and express that simply isn't the case - you can chose to believe this or not. The reality is we refuse submissions all the time due to incorrect credits, permissions issues and most of my outgoing messages are following up on reports or other file concerns. If we cared about nothing but clicks we wouldn't put half of this effort in. We've built process and systems to prevent fly-by leaking, multiple accounts and all sorts of other community nuisance behaviour. Maybe we should talk about these systems a little more as it would show the effort that we do go through in protecting the community and assets of those who don't even upload here.

Check to see your antivirus is not blocking RPH from correctly starting. Also, can you launch GTA V by itself?

Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future. https://www.microsoft.com/en-gb/download/details.aspx?id=26999

Are you having issues? Your log seems to end with you going into the pause menu, not with a crash. You are having ambient blip errors but these are being caught normally by LSPDFR.

This is a 7 year old post. I don't think it happened.

Does GTA V start normally without RPH?

The message does and always has applied to both. I will change the language to make this more clear.

One of your plugins has bad XML data, did you change the XML file for one of your LSPDFR plugins?

We mention this on the LSPDFR download page.

Some anti-virus software programs mark LSPDFR as a virus. This is known as a false-positive. LSPDFR and RAGEPluginHook make extensive use of memory hooking to achieve a lot of what they do, which can look malicious to anti-virus software. If your anti-virus marks LSPDFR as unsafe or you have odd issues running RPH/LSPDFR, you will either need to exclude LSPDFR and RPH's files (refer to your antivirus documentation for more details) or you will have to disable the anti-virus software.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

It's probably being blocked by Windows Defender or whatever other AV you are using. This generally happens when a new version of RPH/LSPDFR is released. You can either try the manual installation or exempting the setup file in Windows Defender.

This looks like a random issue - could you try playing again and then post another log after if it crashes?

Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

Looks good to me.

There is no newer version. See the red banner on the homepage.

It's update season! We've released a compatibility update for LSPDFR 0.49 (Build 8564) which adds support for the new version of GTA V (v3028.0). This build also includes some minor fixes for LSPDFR: Fix possible crash in ProcessFleeingStart Fix potential null reference when spamming keys and opening the backup menu in certain situations Although this build has been tested before being made available to you, there's always the chance there's issues - please report any issues or bugs with LSPDFR on the new game version, if you find any, on the support forums. If you do think you've found an issue, please make sure you're on the latest patch, RPH and LSPDFR version and you've tested the issue is not your mods folder needing an update (e.g. your game runs normally without RPH/FR). As always, the new version of the RAGE Plugin Hook which is required for LSPDFR to work on the new GTA V update is included with the new LSPDFR download. The RAGE Plugin Hook website has not yet been updated, so you should not download the RAGE Plugin Hook from there but instead use the included version with LSPDFR. Please ensure that you now update your game to the latest version of GTA V before playing this new version of LSPDFR 0.4.9, which you can find on the main LSPDFR page.

Please note there's just been an update, so you should wait until the new version of RPH/LSPDFR gets released.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

You can see our updates page and summarise how long it might take by looking at previous updates.