LMS

What you are describing is expected behavior insofar as you are never really calling in a pursuit, but you are reporting a crime (hence you are holding down ACTION_CRIME_REPORT). This crime, in this case a suspect fleeing from the player, is linked to the pursuit and calls it in. Now I am not sure if I want to make the crime auto-create itself when a pursuit is set as not called in as that might not be desirable in all cases. Also not too sold on a function just for this or yet another overload that then might introduce weird side-effects, just like the not called in one, in the future. I would have to think about it, but I would not expect anything soon. The log entries can be disregarded, they happen during decision tree warmup only.

I pushed an update for LML to add compatibility for b2372 on RGSC/Epic, let me know if that works for you. Thanks @ben_hamilton for testing.

Can you attach your vfs.log and also check eventvwr.exe ->Windows Logs -> Application and look for GTA 5 related entries?

Could you be more specific? Are you getting a (silent) game crash? Also it works fine for me on Steam, are you using it on RGSC/Epic?

Please note that RPH and LSPDFR target .NET Framework 4.8 which is not compatibly with .NET 5 which you seem to be using (.NET Standard 2.0 vs 2.1).

Did you get the help box saying 'If you are connected to LSPDFR Sync while taking a selfie, your character's picture will be refreshed automatically.' after you took the picture?

You can download the file normally and then just extract it and copy it to the LML folder (that's what the download manager does).

Try running as administrator since you game is installed in a location where your Windows user does not have write access.

I hereby grant you permission to bundle it with your mod.

It would make sense in so far as there are many streaming requests LML is intercepting - as to why that only happens on that specific disk (or why it happens at all) I am not sure.

If it works on the same disk maybe fragmentation is to blame - could be worth a shot. But ultimately you will have more fun on a SSD 🙂

The thread mentions the main cause of the issue and that this cannot really be fixed by us. The easiest fix is to have your game on a fast disk and these problems should not occur at all (or everyone would be having them).

The failure indicates it cannot find that file in your LML folder. The path is relative to install.xml so it is looking for "data\vehicles_replace.meta" in your mod folder.

And if you use your files in there with FileEntryReplacement it does not work? That all seems fine to me and works for coastal.

Please post your full xml. If you use the tag I specified above, it should load your changes prior to any other files.

Yes, you can override single entries, but it requires a special syntax as it is a bit hacky internally to achieve this. The tag is FileEntryReplacement and ideally you specify a type too. See the wiki page for an example for vehicles.meta:

How about 0.4.10?

What is the specific error you are getting. If LML tries to convert a mod, it asks you whether you would like to verify the install.xml before heading in-game. You could then have a look and check that. That being said, all you need to do to remove it should be either disable the mod or remove its entire folder.

Renaming it to weapons.meta might already do the trick. If you do not want to do that, you can always manually specify the data file type.

I will defer that to the animation man @Sam

You need to report these incidents yourself and it will only work for non-violent crimes, such as a ped harassing or shoving another ped (or yourself). Once in combat, normal pursuit mechanics will be used.

It means don't worry, you are already using 0.4.9 🙂

There are many different version indicators, including the file version, assembly version, installer file version, installer description etc. and they can mismatch for a number of reasons as they need to be kept in sync and use different systems. The only one that really matters (since it is metadata independent) is the "Compiled on" log string. That one is a compile time constant and will indicate the UTC time LSPDFR was actually built.

Probably did not get bumped up by the build, the file version indicator is meaningless.

The latest LSPDFR updated introduced the proposed API function.