Code 3 Callouts 1.2.1

I thought police radio was down?

I`ll backup my game and try to get all mods working with the newest rph

thanks !

3 minutes ago, THEDJMX said:

I thought police radio was down?

I`ll backup my game and try to get all mods working with the newest rph

thanks !

Use this updated one:

I got the "Unknown Trouble" with the dead body callout again. I made sure I was extra attentive but I did not receive any help messages on what to do (all my notifications are on). Ctrl+Y does nothing to end the callout, Y does nothing to advance dialog/do anything. It isn't entirely game breaking as you can force another callout and it continue from there, other callouts will automatically come in after you complete one. 

1 hour ago, WmsK411 said:

I got the "Unknown Trouble" with the dead body callout again. I made sure I was extra attentive but I did not receive any help messages on what to do (all my notifications are on). Ctrl+Y does nothing to end the callout, Y does nothing to advance dialog/do anything. It isn't entirely game breaking as you can force another callout and it continue from there, other callouts will automatically come in after you complete one. 

Did you go close up to the dead body?

3 minutes ago, Stealth22 said:

Did you go close up to the dead body?

Yes, I had to get it out of the LS River haha. Tried a lot of key combos but non worked. 

i think its funny how you said "You must have at least v0.3 of LSPDFR", so does that mean there could be an 0.4 version soon ? i thought the first was 0.98 ??

10 minutes ago, joe25 said:

i think its funny how you said "You must have at least v0.3 of LSPDFR", so does that mean there could be an 0.4 version soon ? i thought the first was 0.98 ??

He means you can't use any other version other than v0.3.

I've just been testing callouts to see which ones are working and which to avoid. Likewise to some of the other reports posted above, I have had trouble with 'Unknown Trouble' revolving around the dead body. In one play setting, I received the callout twice, but each time, I received no prompts no matter how you deal with the body. Ctrl+Y does not work to end the call and the yellow search blip remains even when the next callout is broadcast. Pre 0.3 I had no problem with the callout and would get the detective prompt. Its an awesome callout, but it does seem bugged currently, but only the 'Unknown Trouble' callout with the dead body. Everything else is perfect.

1 hour ago, Murphy909 said:

I've just been testing callouts to see which ones are working and which to avoid. Likewise to some of the other reports posted above, I have had trouble with 'Unknown Trouble' revolving around the dead body. In one play setting, I received the callout twice, but each time, I received no prompts no matter how you deal with the body. Ctrl+Y does not work to end the call and the yellow search blip remains even when the next callout is broadcast. Pre 0.3 I had no problem with the callout and would get the detective prompt. Its an awesome callout, but it does seem bugged currently, but only the 'Unknown Trouble' callout with the dead body. Everything else is perfect.

Thanks for the detailed info. Sounds like it broke with 0.3. I'll look into it 

Thanks for your work, I like very much

Edited January 25, 201610 yr by Osopoderoso

On 1/22/2016 at 2:50 PM, Stealth22 said:

[1/22/2016 12:18:38 PM.911] ERROR: Could not load plugin from "C:\Program Files (x86)\Steam\steamapps\common\Grand Theft Auto V\Plugins\Code 3 Callouts.dll". Assembly Code 3 Callouts.dll (Code 3 Callouts, Version=0.5.1.0, Culture=neutral, PublicKeyToken=null) does not have the required Plugin attribute.

You've installed it incorrectly. It goes in the Plugins\LSPDFR folder, and you should not be loading it with RPH, LSPDFR loads it automatically.

The instructions in the readme clearly say:

- Copy the Code 3 Callouts.dll and Code 3 Callouts.ini files into the "Grand Theft Auto V\Plugins\LSPDFR" directory.

You have to create a new lspdfr folder in your plugins folder because the new version no longer creates one automatically, I suggest updating the installation instructions to avoid this confusion. 

Edited January 27, 201610 yr by doradosjenkins

3 minutes ago, doradosjenkins said:

You have to create a new lspdfr folder in your plugins folder because the new version no longer creates one automatically, I suggest updating the installation instructions to avoid this confusion. 

The installation process is manual; folders were never created automatically.

For unknown trouble call out the yellow search area on the map never disappears after you end the call

29 minutes ago, fireboy6117 said:

For unknown trouble call out the yellow search area on the map never disappears after you end the call

Do you know which variant of the call you got? When precisely did you end it? (Was it the homicide, or the false call?)

I'll see if I can reproduce that in testing.

Some were false calls and some where homicides I pressed end key and it said scene clear and the yellow search thing stayed on the mini map

On 1/25/2016 at 6:21 PM, Murphy909 said:

I've just been testing callouts to see which ones are working and which to avoid. Likewise to some of the other reports posted above, I have had trouble with 'Unknown Trouble' revolving around the dead body. In one play setting, I received the callout twice, but each time, I received no prompts no matter how you deal with the body. Ctrl+Y does not work to end the call and the yellow search blip remains even when the next callout is broadcast. Pre 0.3 I had no problem with the callout and would get the detective prompt. Its an awesome callout, but it does seem bugged currently, but only the 'Unknown Trouble' callout with the dead body. Everything else is perfect.

6 hours ago, fireboy6117 said:

Some were false calls and some where homicides I pressed end key and it said scene clear and the yellow search thing stayed on the mini map

I tested the Unknown Trouble call several times tonight. I forced it to spawn the homicide and false call variants only. Each time, the homicide detective popup appeared (you have to walk right up to the body though), and the search blip cleared properly, whether I ended the call prematurely or not.

I also inspected the source code for this call, and it seems fine; I have several lines in there cleaning up the blip, especially whenever the callout is ended.

Has anyone else seen this at all? What versions of GTA V, RPH and LSPDFR are you guys running?

I was testing with GTA build 573, RPH 34, and LSPDFR 0.3.

6 hours ago, Stealth22 said:

 

I tested the Unknown Trouble call several times tonight. I forced it to spawn the homicide and false call variants only. Each time, the homicide detective popup appeared (you have to walk right up to the body though), and the search blip cleared properly, whether I ended the call prematurely or not.

I also inspected the source code for this call, and it seems fine; I have several lines in there cleaning up the blip, especially whenever the callout is ended.

Has anyone else seen this at all? What versions of GTA V, RPH and LSPDFR are you guys running?

I was testing with GTA build 573, RPH 34, and LSPDFR 0.3.

I'm running on  RPH 34, and LSPDFR 0.3 build 573. CD retail rather then steam. I also use Law Enforcement Improvements aka Olanovs detectives and Police back on the beats. Do you think that the modified data may effect the ped spawn? I'll do a test later see If I can force unknown trouble and if I get the callout, I'll grab the ragehook notes, see if that gives us a clue. 

2 hours ago, Murphy909 said:

I'm running on  RPH 34, and LSPDFR 0.3 build 573. CD retail rather then steam. I also use Law Enforcement Improvements aka Olanovs detectives and Police back on the beats. Do you think that the modified data may effect the ped spawn? I'll do a test later see If I can force unknown trouble and if I get the callout, I'll grab the ragehook notes, see if that gives us a clue. 

Ok so I tested with only Code 3 running callout wise with the exception of LSPDFRs built in callouts. I had the unknown trouble callout, but when I arrived, there wasnt even a body, normally I would at least find a body. Then with no prompting or doing anything really, I got a second unknown trouble, which left the search area still visible on the map from the first call. I have attached the relevant notes on a pad document that shows both callouts in succession. Hope it makes sense to you, as I havent a clue. 

RageHook.meta

if cause of this is in this callout code, then it has been put there recently. I had this callout in earlier versions (homicide), and everything was working as expected. As of now my GTA 5 has updated itself (so RPH is broken at the moment), so I can tell you much.

45 minutes ago, Murphy909 said:

Ok so I tested with only Code 3 running callout wise with the exception of LSPDFRs built in callouts. I had the unknown trouble callout, but when I arrived, there wasnt even a body, normally I would at least find a body. Then with no prompting or doing anything really, I got a second unknown trouble, which left the search area still visible on the map from the first call. I have attached the relevant notes on a pad document that shows both callouts in succession. Hope it makes sense to you, as I havent a clue. 

RageHook.meta

There's definitely something going on there...

[29/01/2016 15:02:56.581] LSPD First Response: Error while processing callout: Unknown Trouble: Object reference not set to an instance of an object.   at Stealth.Plugins.Code3Callouts.Models.Callouts.CalloutTypes.UnknownTrouble.OnArrivalAtScene()
[29/01/2016 15:02:56.581] at Stealth.Plugins.Code3Callouts.Models.Callouts.CalloutBase.Process()
[29/01/2016 15:02:56.582] at Stealth.Plugins.Code3Callouts.Models.Callouts.CalloutTypes.UnknownTrouble.Process()
[29/01/2016 15:02:56.582] at ?????????????????????????????????????????.?????????????????????????????????????????() 

I was testing with the newest (un-released) update, although nothing changed with this callout since 0.5.2...I don't think I changed anything, anyway. I can try again with v0.5.2 I guess, or take a look at the code again, since I know its happening on arrival.

The next update will be coming out soon enough, so I'll make sure to take another look before I release it.

Edited January 30, 201610 yr by Osopoderoso

3 hours ago, Osopoderoso said:

Stealth22

First say that I really like your work.

I have the problem that the call "Unknown Trouble" came to the area, explore the Yellow circle and find nothing. It has already happened several times in the downtown area of the city. Would it be possible in the next version that call could be completed with ctrl + y? Is it also possible that in the .ini file could choose which calls are active and which are not?

I was testing with GTA build 573 and 617 , RPH 34 and 35, and LSPDFR 0.3.

Thanks for your work

That's one of the variations of the call. Sometimes you roll up, and nothing is going on. In that case, you take a look around, and if you don't find anything, just end the call. 

Did CTRL + Y not work? 

16 minutes ago, Stealth22 said:

That's one of the variations of the call. Sometimes you roll up, and nothing is going on. In that case, you take a look around, and if you don't find anything, just end the call. 

Did CTRL + Y not work? 

In none of the cases, and there were several, it was removed from the big yellow circle and worked CTRL + Y. And I could be 15 minutes walking around everywhere to see if it was a matter that had something hidden, but nothing.

Edited January 30, 201610 yr by Osopoderoso

I got this just after accepting Police Impersonator, version 0.5.2, LSPDFR 0.3, RPH 0.34 (offline), I never happened earlier (on 0.5.0 for example), at least those few times when I responded to this callout.

On 29/01/2016 at 8:56 AM, Stealth22 said:

There's definitely something going on there...

[29/01/2016 15:02:56.581] LSPD First Response: Error while processing callout: Unknown Trouble: Object reference not set to an instance of an object.   at Stealth.Plugins.Code3Callouts.Models.Callouts.CalloutTypes.UnknownTrouble.OnArrivalAtScene()
[29/01/2016 15:02:56.581] at Stealth.Plugins.Code3Callouts.Models.Callouts.CalloutBase.Process()
[29/01/2016 15:02:56.582] at Stealth.Plugins.Code3Callouts.Models.Callouts.CalloutTypes.UnknownTrouble.Process()
[29/01/2016 15:02:56.582] at ?????????????????????????????????????????.?????????????????????????????????????????() 

I was testing with the newest (un-released) update, although nothing changed with this callout since 0.5.2...I don't think I changed anything, anyway. I can try again with v0.5.2 I guess, or take a look at the code again, since I know its happening on arrival.

The next update will be coming out soon enough, so I'll make sure to take another look before I release it.

I have not been able to re-produce this error at all. Without being able to see it happen for myself, its impossible to tell what's going on. I'll try to add some more error checking and logging to that callout for the next update.

On 31/01/2016 at 5:42 PM, w35 said:

  Reveal hidden contents

[2016-01-31 01:37:38.053] LSPD First Response:
[2016-01-31 01:37:38.053] LSPD First Response: ==============================
[2016-01-31 01:37:38.053] LSPD First Response: UNHANDLED EXCEPTION DURING GAME THREAD TICK
[2016-01-31 01:37:38.054] LSPD First Response: ------------------------------
[2016-01-31 01:37:38.054] LSPD First Response: Origin: Game fiber "CalloutManager".
[2016-01-31 01:37:38.054] LSPD First Response: ------------------------------
[2016-01-31 01:37:38.054] LSPD First Response: Exception type: System.NullReferenceException
[2016-01-31 01:37:38.054] LSPD First Response: Exception message: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2016-01-31 01:37:38.054] LSPD First Response: ------------------------------
[2016-01-31 01:37:38.055] LSPD First Response: Inner exceptions:
[2016-01-31 01:37:38.055] LSPD First Response: ------------------------------
[2016-01-31 01:37:38.055] LSPD First Response: Stack trace:
[2016-01-31 01:37:38.056] LSPD First Response: w Stealth.Common.Models.VehicleColor.????????????????????????????????????????(String , String , String )
[2016-01-31 01:37:38.056] w Stealth.Common.Models.VehicleColor.GetColorName(EPaint paint)
[2016-01-31 01:37:38.056] w Stealth.Common.Models.VehicleColor.get_PrimaryColorName()
[2016-01-31 01:37:38.056] w Stealth.Plugins.Code3Callouts.Models.Callouts.CalloutTypes.PoliceImpersonator.OnCalloutAccepted()
[2016-01-31 01:37:38.056] w ?????????????????????????????????????????.?????????????????????????????????????????() w E:\GTA V\LSPD First Response\LSPD First Response\Mod\Callouts\CalloutManager.cs:wiersz 334
[2016-01-31 01:37:38.057] w ?????????????????????????????????????????.?????????????????????????????????????????() w E:\GTA V\LSPD First Response\LSPD First Response\Mod\Callouts\CalloutManager.cs:wiersz 163
[2016-01-31 01:37:38.057] w Rage.GameFiber.Main()
[2016-01-31 01:37:38.057] LSPD First Response: ==============================
[2016-01-31 01:37:38.057] LSPD First Response:

 

I got this just after accepting Police Impersonator, version 0.5.2, LSPDFR 0.3, RPH 0.34 (offline), I never happened earlier (on 0.5.0 for example), at least those few times when I responded to this callout.

Looks like just a one off...I have not seen that happen at all, and I've been testing Police Impersonator quite a bit lately. Let me know if you see it again.