8 hours ago, LegionGL said:

Would love to Beta test if you need more help. Looks really great.

 

Would it also be possible to add key commands to specific calls. Say a suspect crashes during a pursuit or you start a foot purusit, you dont want to waste seconds digging thru  a menu to select something when a simple button press or combo could activate it.

 

Just a suggestion

 

I have been thinking about adding something like this, I have noticed there is a lot of down time in situations like that if you use the menu. I might add it for shots fired, both vehicle/foot pursuit, and the crash as you've said. Thank you for the feedback!

 

UPDATE

 

Added/fixed:

• Location included when on traffic stop/shots fired, eg: "Dispatch show me on a traffic stop on Bay City Ave, vehicle occupied once."
• Moved the option to say you are transporting suspect under the "Suspect is..." tab for consistency
• Fixed bug where if you use radio while entering a vehicle you would immediately exit.

Plan to add:

• Keyboard shortcuts for priorities, probably numpad buttons
• Translating most of the updates to their corresponding 10-* codes, eg "On Scene" would become "10-23"

After this last little update I believe I will be ready for my first release! Scorponok is working on the video for the most recent version as we speak. I would expect the first release in the next week.

Edited October 13, 20178 yr by Phaxol

Can't wait for the release.

 

Let me know if you need a beta tester. I am working on a few videos and would love to test this out

Here is the log file from the crash

 

Scene prior to crash:

I was in a vehicle pursuit and finally got guy stopped. Got driver out of vehicle at gun point. When I went to use the E key to arrest suspect, it force crashed LSPDFR.

 

A few other things I noticed:

The controls work nicely. Love the Menu and the hot keys.

 

Things found or improvement suggestions:

 

-#2 hot key (Suspect Crashed) did not work for me

-When receiving a call, usually you hit Y to confirm taking call. In your menu you hit 'En Route'. Which is great but it didn't seem to also hit the Y key for you, forcing you to go out of the menu and manually hit the Y key. When you hit 'En Route' in your menu it should automatically hit the Y key for you.

-Suspect in Custody button works great and even auto calls transport for you. But dispatch should inform you that a Transport has been dispatch to your location. More than once I called my own transport because i didn't know the menu did it automatically.

-Instead of having to navigate thru the vehicle or ped description options, it should automatically select the correct ped or vehicle for you. It should be one button press and LSPDFR calls out the correct value. 

-Pursuit button (.) when you hit the . (period button) your character notifies dispatch you are 10-80 and dispatch responds with a generic 10-4, copy.

But what would be better is if your character notifies dispatch that you are 10-80 in a vehicle pursuit and also announcing the vehicle make, model, color and location. Dispatch should then respond back with a "10-4" and announce "(your call sign) is in a vehicle pursuit with make, model, color and location. Any available units start that way." Gives it a more realistic feel.

-update pursuit hotkey (update pursuit I believe is a smart radio function and it gives all the details of your current pursuit over the radio)

-When using the 'Suspect dead'menu dispatch should respond with "10-4, coroner is being dispatched to your location", instead of just 10-4, copy. And then dispatch a coroner for you. Otherwise you call the coroner yourself and now have multiple coroners and possibly could cause a crash.

"In Sight" in your menu is spelled wrong. You have it In Signt and it should be In Sight

 

 

 

 

RagePluginHook.log

46 minutes ago, LegionGL said:

Here is the log file from the crash

 

Scene prior to crash:

I was in a vehicle pursuit and finally got guy stopped. Got driver out of vehicle at gun point. When I went to use the E key to arrest suspect, it force crashed LSPDFR.

 

A few other things I noticed:

The controls work nicely. Love the Menu and the hot keys.

 

Things found or improvement suggestions:

 

-#2 hot key (Suspect Crashed) did not work for me

-When receiving a call, usually you hit Y to confirm taking call. In your menu you hit 'En Route'. Which is great but it didn't seem to also hit the Y key for you, forcing you to go out of the menu and manually hit the Y key. When you hit 'En Route' in your menu it should automatically hit the Y key for you.

-Suspect in Custody button works great and even auto calls transport for you. But dispatch should inform you that a Transport has been dispatch to your location. More than once I called my own transport because i didn't know the menu did it automatically.

-Instead of having to navigate thru the vehicle or ped description options, it should automatically select the correct ped or vehicle for you. It should be one button press and LSPDFR calls out the correct value. 

-Pursuit button (.) when you hit the . (period button) your character notifies dispatch you are 10-80 and dispatch responds with a generic 10-4, copy.

But what would be better is if your character notifies dispatch that you are 10-80 in a vehicle pursuit and also announcing the vehicle make, model, color and location. Dispatch should then respond back with a "10-4" and announce "(your call sign) is in a vehicle pursuit with make, model, color and location. Any available units start that way." Gives it a more realistic feel.

-update pursuit hotkey (update pursuit I believe is a smart radio function and it gives all the details of your current pursuit over the radio)

-When using the 'Suspect dead'menu dispatch should respond with "10-4, coroner is being dispatched to your location", instead of just 10-4, copy. And then dispatch a coroner for you. Otherwise you call the coroner yourself and now have multiple coroners and possibly could cause a crash.

"In Sight" in your menu is spelled wrong. You have it In Signt and it should be In Sight

 

 

 

 

RagePluginHook.log

1. Hmm interesting, does it work if you change the key to something else?

2. Could not get this function to work, I can try to find a way to work it in but I might end up needing to contact VocalDispatch creator and see how he did it

3. This function does not call a transport unit to you, there is nothing in my code which does this. Check if you have conflicting hotkeys or something of the sort

4. I can look into doing this for the vehicles at least, it would be nearly impossible for peds however as I would have to index every ped in the game.

5. Same as above with vehicle, I'll look into it

6. Update pursuit status is a plugin for police smart radio, thus would add 2 more dependencies and I'm trying to keep it as independent as possible. There is an option to update your location to dispatch and if they crashed

7. I have thought of this as well, and thought it best to be left out because of the dependencies it would add and the fact that when I call in that the suspect has died I might not be done investigating yet, I like to secure the scene completely to make sure the coroners are out of danger

8. Fixed typo

 

As for the log, I cannot exactly pinpoint the cause of  the crash. It is probably not a problem with my menu but I am unsure. All of the functions are aesthetic for the most part and would not interfere with you arresting somebody. Has this happened before you installed it? Please continue playing with it and see if you can reproduce the crash every time, if you can, then play without it and see if it continues.

 

Thank you for the feedback! Next time just PM me this, you can post your log in a quote box I believe.

Edited October 13, 20178 yr by Phaxol

ok. and i will keep playing and see what I can find

There is something inherently wrong with the way I have implemented the LSPDFR API, as a result I cannot release this until it is fixed. Currently my plugin is tying up LSPDFR's loading of plugins after mine, as a result I can not release this until I have fixed this issue. This is also the cause of the error thrown in "ForceDuty" when it crashes and general instability. I am going to try and restructure my code completely and clean it up but adding event handlers along with sub-classes as opposed to an infinite loop, but I am not sure how long this will take me. Anyone that has experience with the LSPDFR API, I would appreciate any help you can give me!

 

Thank you for understanding.

Edited October 15, 20178 yr by Phaxol

Issue has been fixed! Should be on track to release sometime this week

https://www.youtube.com/watch?v=kUb79xUvygc

 

Here is a video of the script in action! It is off an older version, but the general idea is still the same!

 

Things added/changed since the video:

• Most options translated into 10-* codes
• Fixed LSPDFR loop bug
• "In Transport" has been moved to the "Suspect is/has..." tab
• Traffic stops, pursuits, and shots fired option now automatically include your location in the radio message
• Telling dispatch you are in pursuit will dispatch 2 units to you to assist
• Keyboard shortcuts added for pursuits, suspect has crashed, and shots fired

I only wish to add one more thing before I release, and that is to make selecting "En Route" accept the callout for you. I have messaged the creator of Vocal Dispatch and am awaiting a reply to see how he did it, I will also be seeing if I can't work past it on my own. I would expect the release Thursday or Friday depending on how busy I am.

 

Thank you all for following the journey of development!

Edited October 17, 20178 yr by Phaxol

Just watched the video and it looks great! 2 minor suggestions I might have;

 

1. Perhaps integrating different responses from dispatch other than "10-4, copy". I imagine that might get a little old after the first few communications with dispatch. I know Vocal Dispatch uses a couple of different responses.

 

2. Perhaps integrating an option to delay the response from dispatch for a couple seconds. I know I would like be saying my communication out loud and with a delay in dispatch response that would prevent me from being cutoff.

 

Otherwise it looks fantastic!

2 hours ago, Slickybp said:

Just watched the video and it looks great! 2 minor suggestions I might have;

 

1. Perhaps integrating different responses from dispatch other than "10-4, copy". I imagine that might get a little old after the first few communications with dispatch. I know Vocal Dispatch uses a couple of different responses.

 

2. Perhaps integrating an option to delay the response from dispatch for a couple seconds. I know I would like be saying my communication out loud and with a delay in dispatch response that would prevent me from being cutoff.

 

Otherwise it looks fantastic!

Thank you for the feedback!

Currently there is a 3 second delay between request and dispatch response, but I may increase that. I do like the idea of a variety of responses though, I will try to implement it before the release

Version 1 of the plugin has been released! Get it here: 

 

What happened with the mod ? It's not available anymore ?

13 minutes ago, PO Anthony said:

What happened with the mod ? It's not available anymore ?

 

Uploading a new version with a fixed bug and added support for Bejoljo's mod as well as OJDoesIt's felony stop mod, file has to be approved by staff before it shows to everyone

Oh, great !

 

Thumbs up by the way, this is awesome !

On 9/28/2017 at 10:47 PM, Reddington said:

I'm big on roleplay, and this is PERFECT.  Nice that we finally have a tool to tell dispatch what we're doing and such.  If I may make a suggestion for the future, there are times where we go unavailable and take a little lunch break, or just take a cat nap in the car (don't tell sarge!).  Would be nice if we had the option to set it as "Show me at lunch" or just something along those lines that says we are unavailable, but not due to a call or traffic stop.

Out at the jail, at courthouse, at property room, etc