Cyan

Have you seen any improvement?

As you can see, adding the warning is the easy part. Knowing when we should do that is another story. We are working on quite a large website update right now and we will include something to mark files as outdated / broken. It's likely this will be based on community intelligence/marking and moderator oversight but will be able to overridden by the author of the file. It's likely the ability of an author to override the judgement will not lead to any issues, as most of the files that we have that are chronically outdated usually the interest has dissipated to keep the file up to date anyway. I like @PNWParksFan's suggestion of giving creators fair notice as to when this is going to happen, and that's likely how we will implement this.

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

Can you upload a new log file? It's likely you didn't change it correctly or that there is a different issue now.

Of course it's copyright. If you create something, you own copyright on it (generally). Part of that copyright is controlling the distribution of your work. Just because you offer something for free doesn't invalidate rights on the distribution. See the RPH license, which governs your rights to use their software. Do not upload to anywhere, and do not include RAGE Plugin Hook in your plugin releases, without prior written permission. Edit: I'm also not a RPH developer, so I cannot say exactly why old versions are made unavailable, but it's definitely their right to do so. It's likely the reasoning is similar to LSPDFR. For LSPDFR, historical versions in the 0.4.x series are not made available due to additional support burden and the fact that most updates are compatibility or bug fix releases. 0.3 is still made available for those who prefer it over the 0.4.x series.

Update LSPDFR to latest build

Because it is somebody's copyrighted work.

This topic has been closed by LCPDFR.com staff as it is a support topic concerning an unsupported version of LSPDFR. We do not support old versions of LSPDFR, and recommend you use and download the latest version (LSPDFR 0.4) (http://www.lcpdfr.com/files/file/7792-lspd-first-response/ ) If you feel that this topic has been closed in error, please report this post.

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

Can you give me an example log.

Rename mods to _mods, this really looks like a non-related GTA V mods folder crash to me (you most likely installed something incorrectly). If that fixes it, you'll have to undo your most recent changes to that folder or re-create it.

Download WinRAR or 7zip.

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

Your log file literally shows you are running an outdated build; [9/4/2020 6:45:29 AM.358] LSPD First Response: [INFO] Running LSPD First Response 0.4.7 (0.4.7383.491) [9/4/2020 6:45:29 AM.358] LSPD First Response: [INFO] Compiled on 18 Mar 2020 23:16:21 UTC

[9/5/2020 5:34:00 PM.504] LSPD First Response: Exception type: System.InvalidOperationException [9/5/2020 5:34:00 PM.504] LSPD First Response: Exception message: Could not spawn new vehicle. Your game is failing to spawn new vehicles. Potentially an issue with one of your install vehicle mods.

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

I'm up for adding markings to outdated files, however I'm not too much a fan of removing them outright. You'd be surprised the amount of people still using LSPDFR 0.3 for example, and who have never really updated their game.

With that many plugins I would expect a FPS drop. I also wouldn't expect a 13" MBP to play the game with any decent framerate -- especially with multiple plugins taxing the thermal solution. As for your crash, you haven't included any information to debug this. Start with your RAGEPluginHook.log file.

What are you talking about? The E:\ drive you are seeing in this log is debugging information for the LSPDFR developers. It tells us on which line an error occurred from the absolute path in which LSPDFR was compiled on the build machine. It has absolutely nothing to do with your system and bears no relevance there. It's used for us tracking where in LSPDFR's code an error occured. Please attach your log file so we can diagnose your installation issue.

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

LSPDFR is a single player modification. In regards to your third party plugins not working, please provide your RAGEPluginHook.log file.

Just an FYI, that error has no connection to ambient events. It occurs when LSPDFR tries to hide story mode ambient game blips. If it fails, it is caught and an error is logged. Even if it fails, it has no effect on the game.

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

Your error is not caused by LSPDFR, then. Try disabling mods folder (rename mods to _mods).