OJS

I love the new design, fancy!

I love the new design, fancy!

I love the new design, fancy!

You're trying to reference SuspectVehicle's model on line 48, but you don't create the vehicle until line 64.

I love the new design, fancy!

I love the new design, fancy!

Very much is a giant leap forward! So much work went into this and I am very impressed with the finished result! 🙂

Thank you so much!

As far as i know LSPDFR is randomizing the files itself.
 
By using this for the string "UNITS_RESPOND_CODE_02", lspdfr will choose "_01" or "_02" to randomize these files. (as soon  as you have "UNITS_RESPOND_CODE_02_02.wav"
)
No need to write your own speech randomizer.

Out of curiosity: Why are you even attaching a blip to the suspect yourself? LSPDFR will do that automatically.

I use the same code for a stolen vehicle callout in my pack and it functioned correctly, though I have noticed that if I'm using the License plate Randomizer plugin (To get rid of the default plate, 47EEK or something like that), it will sometimes cause the details on the vehicle to change when it changes the license plate. Other than that I can't think of a reason why it wouldn't be working.

There are different locations in OpenIV for textures.
 
You can find a lot of textures in: update/update.rpf/x64/textures/script_txds
The one in the example is in: x64b/data/cdimages/scaleform_generic

If you want to use textures in the notifications, you can use:

Example:
Game.DisplayNotification("web_lossantospolicedept", "web_lossantospolicedept", "Blaine County Callouts", + System.Reflection.Assembly.GetExecutingAssembly().GetName().Version.ToString() + " has loaded successfully", "thank you for downloading!"); Instead of "web_lossantospolicedept", you can use other textures located in OpenIV,

Hey there! Looking to create a callouts plugin of your own? Well, I'm here to help you.
So, let's get started. The requirements are as follows:
1) Have some general knowledge of C#, to learn the basics of C# I recommend reading Sections 1-17 here: http://rbwhitaker.wikidot.com/c-sharp-tutorials
2) Have Visual Studio Community Free, or any other version other than a trial, found here: https://www.visualstudio.com/en-us/visual-studio-homepage-vs.aspx
3) Have the files "RagePluginHookSDK.dll" and "LSPD First Response.dll", found in the downloads of RPH and LSPDFR.
 
Alright, once you have met those requirements, we can move onto the steps of starting your first callouts plugin!
1) Create a folder called "References" anywhere easily accessible to you.
     - In this folder, place your files "RagePluginHookSDK.dll" and "LSPD First Response.dll".

2) Open Visual Studio.
     - Once VS has fully loaded, at the top right click "File", "New", "Project".
     - At the left click the arrows next to "Installed", "Templates", and click on "Visual C#".
     - Then, in the middle box click "Class Library".
     - Under "Name" at the bottom, in the box type whatever you want your project/callouts plugin to be called.
     - Under "Location" choose where you want to save the project, this is recommended to be an easily accessible area.
     - Click "OK".

3) When all loads in, you should get a screen of code like this:
 
4) First, click "Project" at the top of the screen, then "Add Reference..".
     - A window will pop with a bunch of gibber jabber on it. Click the arrow next to "Browse".
     - At the bottom left, click "Browse.."
     - Once in Windows Explorer, navigate to your folder "References".
    - Hold the left control key and select both the files in the folder References (Rage SDK and LSPD DLL).
    - Make sure both boxes for the two files are ticked. Then, click "OK".

5) At the top of your code where everything says "using blahblah;". Replace all of those with the following lines below:
These basically state what references you're using, simple as that.
6) Over to the right, rename Class1.cs to Main.cs.
7) Then, you need to replace the code below the using statements with the following (explanations in the code, after "//"):
So this basically concludes our Main.cs file, all we have to do later on, as stated near the end of Main.cs above our method RegisterCallouts(), is register the callouts that we make, which we are about to do.
8) Next, we need to double click on "Properties" to the right. Under the dropdown box "Target framework:" select .NET Framework 4.6.
     - Then click Control+S and exit the Properties tab.

9) Over to the right, right click on ExamplePlugin and click "Add" then "New Folder", naming it "Callouts".
     - Then, right click on the "Callouts" folder, click "Add" then "Class..".
     - Name it whatever your callout name is, for this example we're going to be creating a simple "Pursuit in Progress" callout, so name it "PursuitinProgress.cs".

10) In it, use this code below:
Everything is explained in the code to help you out. I recommend you experiment with it to change things to your liking.
11) Now, go to Main.cs and under the RegisterCallouts() method you need to add the following:
12) Lastly, double click "Properties" to the right. Then, click "Build" to the left. Under "Platform Target:" select x64.
     - Thank you @Stealth22 for informing me of this!

Save and you're good to go! You got your first callout. You can ultimately expand upon this information I have provided with you to make your own unique callouts plugin!
     - To actually use the plugin, you have to click "Build" at the top of VS, click "Build Solution", make sure there are no errors, then go to wherever your project "ExamplePlugin" is located, go into bin > Debug. There you will find your references that were used and your "ExamplePlugin.dll". Drag and drop this file into GTA V > Plugins > LSPDFR and boot up GTA V! Also, if you want to quickly debug and make solving crashes easier, install "ExamplePlugin.pdb" to the same spot you installed ExamplePlugin.dll.

 
If you have any questions, please ask me!
If I forgot something or messed up something (as expected), please let me know.

It is easiest to get coordinates, yes. In-game, drive to where  you want it to spawn and you can type in PrintInfo in the console to display coordinates.

Try updating the drivers, if you haven't already or just play with the display settings, maybe just google it. 

Yes its good enough