AwsomeAnonymus

I hate you now.

To follow on from the previous update I posted yesterday, we're still hard at work preparing LSPDFR 0.2 for release.  At this time, it would appear that all issues caused by the latest update to GTA V have been resolved.  Indeed, I spoke of the problem and its solution in more detail in the previous update regarding 0.2.
Unfortunately we're still experiencing issues with LSPDFR 0.2 which appear to be unrelated to the recent update and more of a problem with the modification itself.  These are in the form of script crashes that some, but not all, have encountered during pursuit testing and this is something we've been looking in to.  Unfortunately this seems to be quite a tricky problem to find as different users are experiencing different results.  Nonetheless, I'm hopeful that we'll find the problem and resolve it relatively soon.
While LMS has been hard at work debugging most of our issues (both the ones caused by Rockstar's protections and ones of our own making), I've taken advantage of the extra time to add more polish to LSPDFR 0.2, and even introduce a new feature which I know will be very popular.  To complement the police computer in a vehicle, here's a sneak peek of the equivalent system on foot:

Bear with us as we work this out.  I guarantee you that LSPDFR 0.2 won't disappoint.

Following on from the massive debut of LSPDFR on GTA V a mere two weeks ago, we're proud to announce the next installment in the series - LSPDFR 0.2 - featuring not only numerous enhancements and fixes, but also some highly requested features.
Indeed, while originally versioned as 0.1.1, the number of changes introduced in 0.2 seemed too significant to be represented by only a minor increment. LSPDFR 0.2 goes some way in adressing much of the feedback after the first public release and is our first response, pun most definitely intended, to thousands of the comments we've received since then through the forums, YouTube and social media.
From the electroshocking glory of stun guns, to a blast from the past with the LCPDFR style search areas and pursuit blipping, LSPDFR 0.2 packs a serious punch and is a major improvement from our first offering.

Asking for ID in traffic stops - one of the many suggestions that have made their way into LSPDFR 0.2.
 
For those of you familiar with LCPDFR 1.1, the lack of search areas and blips in LSPDFR pursuits might have been confusing.  Fear no more, however, as we've reintroduced the system with much the same aesthetic style as that of before.  There are, however, some notable improvements including the way in which each unit in the pursuit is now being uniquely marked on the game's map.  This means that the legend at the side of the map can be used to highlight each different type of police vehicle currently involved.
We'll have more to share regarding the features in LSPDFR 0.2 tomorrow, when we'll move away from the pursuits and action sequences, and take a look at how 0.2 brings about better support of routine police work - something I know a lot of people are looking for.

First up, we're all sorry for the problems we encountered with the release last night.  Unfortunately, there was a game breaking performance issue which was found only a few hours before we intended to release and this has required some time to investigate.
The good news is that we've done our best to mitigate this problem, related to the way in which Rockstar has started to introduce anti-modding protections.  For those of you interested in the technical detail, here's a snippet of a performance test ran by Alexander Blade and LMS:
Performance difference between GTA V version 372 and 393 Calling SET_CURRENT_PED_WEAPON 1000 times via ScriptHookV and RAGEPluginHook: 372: ~582ms (RPH: ~585ms) 393: ~2480ms (RPH: ~2490ms) Performance on version 323/350 is most likely even better due to even less/no obfuscation than 372.In short, on the previous patch (372), it took 585 milliseconds for the function to be executed 1000 times.  On the newest patch (393), it took 2490 milliseconds, which is roughly 2.5 seconds, to be executed 1000 times.  This means that this particular function takes five times longer to execute on the latest patch than it did previously.  LSPDFR 0.2 and 0.1 call this function a lot, mainly to stop other police officers from killing suspects, as we force them to be unarmed when appropriate by using it.  As such, during a pursuit with even a couple of units, performance takes a hit.
With the problem identified, we've managed to come up with an alternative way of doing things that doesn't have such a dreadful impact on performance.  This version is currently undergoing testing, and we hope to be in a position to release 0.2 as soon as possible.  Note that I won't commit to a date, as it is possible we run into further issues, and we'd like to avoid a situation similar to last night's, but there is still the possibility that we can release today, and we'll keep you updated as to our progress.
Sam.

Sam, you and the whole team are just amazing. There's no need to apologize considering how hard you all are working to fix this issue.
 
Great work.