Sam

Does it work without?

Problems related to the retail version shouldn't be anything to do with LSPDFR. According to the website, there's a new version of RPH which fixes a bug present in the retail version. At the end of the day, LSPDFR is the same on both the retail and Steam versions, but how RPH executes it is not. I'm hoping this is a one off! At least, though, I hope it can give everyone an insight into the work that goes on behind the scenes here to do what we do. I especially hope that it can also shed some light on how we've been listening to your feedback about RPH and pushing for changes to it, and I certainly hope we can be in the position to push forward with some positive changes to the hook, like: Toning down the branding and notifications. I don't think there's any more doubt as to the name of the hook, and those screens get seriously annoying!Removing/significantly redoing the redundant plugin verification system (LSPDFR is the only verified plugin, and it is always a version behind, meaning new releases are never verified)I know a lot of people are keen to see the removal of the anti-piracy measures. I do, however, understand the ethics behind them, but I don't think it is a modification developer's place to be enforcing Rockstar's intellectual property rights (especially since the process behind making RPH directly contravenes the EULA of the game, and the name/logos of the hook are quite possibly a violation of these rights itself!). This is also something that we've mentioned multiple times.

I can see he did connect to the Teamspeak server. Forum PM would have been a better idea, but oh well. Regardless, I'm working on compiling LSPDFR against the new RPH just now. I probably won't be able to do as much testing of it as I'd like to, but it is what it is.

Nope, you'll need to ask the RPH team. I know that a lot of stuff is different in the retail version.

No. The last time I was in contact with MulleDK19 was a couple of weeks ago. I actually expressed concern about the state of RPH, with so many useless additions (such as plugin verification and logos everywhere) being added, and was told in response there was a "simple solution to that". The implication being not to use RPH.

Well I had certainly hoped that was the case, but it sure didn't look like it. I was certainly surprised to see that comment. I'm not sure what there is wrong with LSPDFR that would result in it not working on the retail version though.

You don't need to get all 'passive aggressive' with me. I never mentioned anything about a retail version. My concern was the lack of communication, which might I add, is still ongoing.

I highly doubt the police killed her. Also it says she was arrested for assaulting a police officer. Perhaps there was something wrong with the arrest itself, but for the police to actually kill someone in a jail cell? Seems a bit far fetched, even in Texas!

Nothing different. At the end of the day, this is simply bad news for people that want to play LSPDFR. It means that we'll be downloading RPH at the same time you, and everyone else is. We then have to compile the mod against the new version, give it a test, make sure everything's still working okay, and only then do we get to release it. From what I understand, compatibility for the Steam version (which I use), has been there since early this morning. If there'd been the foresight to recognize that developers of modifications using RPH might appreciate the opportunity to prepare their modifications for the latest version, then assuming everything did work, we'd be in a position to release an updated version of LSPDFR almost as soon as RPH itself was released. Instead, we're left in the dark and being forced to find out information from other people.

Sure, LMS helps to develop the RPH but he's away on a business trip just now. I believe that MulleDK19 is the one organizing everything at this moment in time, and we've had zero communication from him about anything.

The only thing that annoys me is how we're being left in the dark about this. I know for a fact that LukeD, one of the other few people with a published plugin for RPH, hasn't heard anything either.

Audio is part of the game files. Redistributing those files with the mod is dodgy. Our code which interacts with the game isn't part of the game. If we can play the audio directly from the game without including the files, no copyright is violated.

How comforting to know that none of the people that actually have released mods making use of this hook are getting to test it.

Well, I'd note as well that we don't want to be including all of these audio files with the mod for much longer as: The filesize of the 0.2 is something like 3000% larger than 0.1. This will only increase as new audio is added.It is technically copyrighted.So, it might be a little bit before we figure out a better solution.

That's the first I've heard of this.

How many topics do we need about this. https://www.virustotal.com/en/file/f26eb7b4ac8951be55de7c625baa1c25a81819ede24301328f3bfe52f17c82ff/analysis/

I've spent about three long days in total researching GTA V audio. I've got about 1,000 audio files dehashed and waiting to be used. What you've seen in 0.2 is only the beginning, trust me.

Has to be in the folder.

http://www.lcpdfr.com/forums/topic/52674-chrome-is-blocking-my-02a-download/ Not sure why, but Chrome seems to have flagged the website for some reason. If you're unsure, you can view the VirusTotal analysis of LSPDFR here: https://www.virustotal.com/en/file/f26eb7b4ac8951be55de7c625baa1c25a81819ede24301328f3bfe52f17c82ff/analysis/

We've added a couple of new API functions in LSPDFR 0.2a. These were intended to be in the first release of our API, but were unfortunately left out due to time/other constraints: You can now play police scanner audio with the LSPDFR 0.2a API.You can now retrieve full pedestrian Persona data with the API. I've included an example of some code that I used to test the functions earlier: Audio Example Functions.PlayScannerAudioUsingPosition("WE_HAVE CRIME_RESIST_ARREST IN_OR_ON_POSITION", Game.LocalPlayer.Character.Position);This code will play the following audio files: A randomly selected variant of "WE_HAVE" from Police Scanner/WE_HAVEA randomly selected variant of "CRIME_RESIST_ARREST" from Police Scanner/CRIMESThe area (or street) that the local player is currently in (or on), preceded by the appropriate conjunctive ("in" or "on").Note that "IN_OR_ON_POSITION" is a special keyword recognised by this function. The other special keywords are: "POSITION" - to play just the street or area."AREA" - to play just the area (and not the street)Of course, the position used is the one specified in the second parameter for this function. A separate function also exists to play paramaterless audio. Persona Data Persona pedPersona = API.Functions.GetPersonaForPed(Game.LocalPlayer.Character, null); Game.DisplayNotification(String.Format("My name is {0} and I am a {1}, born on {2}.", pedPersona.FullName, pedPersona.Gender.ToString().ToLower(), pedPersona.BirthDay.ToShortDateString()));Used in conjunction with Game.DisplayNotifiction as shown above, This example might produce the following output: My name is Will Peavey and I am a male, born on 16/01/1991

LCPDFR will soon be getting its own section like LSPDFR currently has.

We've released a small update to LSPD First Response 0.2, including a number of fixes to reported issues. Ever since the release of LSPDFR 0.2, we've been working to identify the most serious problems and glitches, and hope to have fixed all of these with this new update, LSPDFR 0.2a. Among the fixes and changes included in this update are the debut of non-lethal stun guns, easier arresting and better first person view compatibility. Also included are a couple of new LSPDFR API functions for developers, including the ability to play audio over the new police radio that we introduced in 0.2, and better access to pedestrian persona data. You can find LSPDFR 0.2a, along with a full list of changes, on the LSPDFR download page.

Not impossible, but quite tricky.

This is a known issue and will be fixed.