Cyan

We should use 429 however, for legacy reasons, this will not be possible at this time. There is a note on the API page as to why this will not work for every file, basically a reprocessing has to happen for older files, this hasn't been done yet, but when it's done I'll update this thread.

We're seeing excessive use on some of these APIs. Requests without a User Agent will soon be throttled by IP address to 20 req/minute. However, we will try to avoid throttling requests from LSPDFR plugins based on some data we have. Requests with a valid User Agent (e.g. something like in the linked API page that shows what and how to contact the author of the plugin/service) will soon be throttled by IP address to 60 req/minute (1req/s). Requests that exceed this will receive 403 errors and excessive 403s will cause temporary blocks. If you have a specific use case which requires calling these APIs more than once a second, please reach out with your use case and what efforts you've done to reduce calls (e.g. caching). We can make special exceptions for some user agents.

Once the trust is gone, it's hard to obtain again. Personally I wouldn't go near anything by an author who ever thought that was acceptable, but we all make mistakes. Doesn't change the fact that people are still using it and enjoying it though. If you don't trust it, don't use it.

Great - I've moved this thread to GTA V as it's not directly related to LSPDFR. Hope your solution helps someone else.

Firewall wouldn't be causing this, anti-virus would. RPH isn't tagging anything as containing viruses, it's trying to load files and the WIndows API is returning the AV message as the failure reason. This suggests there is still an anti-virus running somewhere.

Hello, yes, this is the result of the false positive detection. See the message boxes around the site or on the LSPDFR download page for more information.

SHV isn't used by LSPDFR or RPH. Yes, the callouts will work provided they are all compatible with the latest LSPDFR and placed in the correct place (the plugins LSPDFR folder).

They are LSPDFR plugins, not RPH ones. They do not load as RPH plugins nor will they show there.

Hello Lucas, thanks for your continued interest and concern! This happens the first week of every RPH/LSPDFR release. Your option is either to wait the ~2 weeks for Microsoft to flag it manually or via ML as ok, or add an exemption to your GTA folder. Sometimes the GTA folder exemption is not enough and the AV software needs turned off until RPH has successfully started the game, then your AV software can be turned back on again. This message is also included on the LSPDFR download page, just encase you miss it all over the site otherwise.

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

This happens the first week of every RPH/LSPDFR release. Your option is either to wait the ~2 weeks for Microsoft to flag it manually or via ML as ok, or add an exemption to your GTA folder. Sometimes the GTA folder exemption is not enough and the AV software needs turned off until RPH has successfully started the game, then your AV software can be turned back on again.

Due to an unforeseen issue, we will ship the normal compatibility update first, then add support for the new DLC vehicles. Don't worry, this should come very shortly after our compatibility update (it's already there, just a minor fix needed that we didn't want to delay the release for).

Yes, provided no major time blocker or bug appears around this we should support these in the next update. I'll try to make sure LSPDFR supports the new vehicles and livery options and provisionally I've added them to the LSPD agency, but breaking these out to individual agencies might be something left up to the community and individual preferences.

LSPDFR has been heavily optimized already - there's not that much room for optimization in base LSPDFR. e.g. when playing on a completely unmodified game without LSPDFR plugins, my FPS is pretty much the same between LSPDFR unloaded, loaded and on-duty.

LSPDFR versions need to match the game version you are playing. This is because LSPDFR versions are tuned (e.g. memory offsets) to the exact version of GTA they were released with. This is the reason that LSPDFR receives compatibility patches every GTA update. The LSPDFR 0.3.x series is the last version of LSPDFR which does not depend on game version compatibility. Using old versions or downgraded versions of GTA is not supported by us for this reason.

If you didn't make a backup, sadly there is no legal way.

The revert function hasn't worked in some time. You may need to wait for an update.

Heads up, folks: The GTA5-Mods forums are shutting down. They've set the closure date for January 24, 2024. Before that, starting December 19, 2023, the forums will switch to a "Read-only" mode. This move is reportedly a result of security concerns and their aging forum technology. Whilst I hope they archive the site, or at least migrate forum data to their also-owned NexusMods forums, it seems possible that some of the years of community posts and discussion might be lost. For those who've relied on these forums for information or discussion, now's the time to back up any crucial posts or data you might need. For the complete details on this closure, check out their announcement here.

This box will only show logged in viewers. The total count is incremented by all views, including guests and bots.

You'll have to wait for an update to become available.

SHVDN has/had a fundamental design flaw which means that it will not work for people with certain combinations of mods/systems/moon alignment. This isn't an LSPDFR issue and there's nothing LSPDFR can do to work around the problem. This has been worked around in later SHVDN code commits, but sadly, they still haven't shipped a later release which actually includes this fix. You could try one of their nightly builds, but the issue is I'm unsure if these would be compatible with the SHVDN mods you are using. There was a more compatible build floating around, maybe someone can chime in with it.

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

This isn't a supported flag, and shouldn't be used. And yes, it causes the error you've described.

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

This is a good idea; I'll look into adding this shortly.