This Lua script is a comprehensive tool designed for crime scene analysis, specifically tailored as an enhancement to the qb-policejob script. It is dedicated to providing law enforcement personnel with advanced capabilities to investigate incidents thoroughly. This script is crafted entirely in Lua and focuses on five key forensic elements: bullet casings, bullets, fingerprints, blood (DNA), and vehicle fragments.
1. Bullet Casings:
The script includes a specialized module to identify and analyze bullet casings found at the crime scene. It allows law enforcement to trace the type of firearm used and potentially link it to other incidents.
2. Bullets:
Another feature enables the identification and cataloging of bullets, aiding in establishing connections between different crime scenes or suspects.
3. Fingerprints:
The script incorporates advanced fingerprint analysis, utilizing cutting-edge algorithms to match and identify fingerprints found at the scene. This facilitates the swift identification of potential suspects.
4. Blood (DNA):
A robust DNA analysis module allows investigators to identify blood samples at the crime scene. Through DNA profiling, law enforcement can link suspects or victims to the incident.
5. Vehicle Fragments:
The script offers a specialized functionality for analyzing vehicle fragments. This helps in reconstructing vehicular incidents, identifying involved vehicles, and potentially tracking down suspects.
Leveraging the DrawLine function, this script provides a unique capability to determine the exact position of the shooter. By visualizing trajectories and impact points, investigators can reconstruct the shooting incident in detail. ( Green DrawLine when the shooter was a Cop and Red DrawLine when the shooter wasnt a Cop )
NOTE:
This script is an edited version of the qb-policejob framework, integrating additional functionalities for a more in-depth crime scene analysis. It empowers law enforcement with advanced tools to solve cases efficiently and effectively.
The high resmon is only client sided ( This means its not that big of a deal ). Its high because im using DrawMarkers/DrawLine which need to be looped with a 0-5ms wait time.
THE SCREENSHOTS ABOVE ARENT ACURATE ANYMORE, I CHANGED ALOT TO MAKE SURE THE PERFORMANCE IS GOOD, REPLACED EVERY DRAWTEXT OR DRAWMARKER WITH DRAWSPRITE, WHICH IS LESS SHITTIE! CHECK IT OUT FOR YOURSELF! ( UPDATED ONE: Release 0.1.2 Added Footprints Ā· LeSiiN/lsn-evidence Ā· GitHub )
Very nice script and the detail of the drawlines is curious.
Iām going to drop an idea to see what you think, using targets or getting very close to the trajectory of a bullet, with some item like a laser pointer you could try to calculate where the bullet comes from, I think that this way you donāt have to be showing all the time the drawlines and it would be something more optimal.
To make sure I am following my intuition properly hereā¦
Would it be possible to integrate this with AXFW Inventory for qb-core? It rewrites major parts of the app.js so the instructions on your github donāt line up.
Looking through the code, I think it could be pretty easy to add support for it. I am currently working to see if I can get that functional.
Hi, i just checked they script, it looks like they just using the Tooltip for the quality of each item, they do not support stuff like the infos(serial number of weapons for example) of each item.
But if u found a way, let me know and i will implement it into the readme
I might experiment with it at some point. Right now > I actually found some issues, and I am not sure where to turn exactly.
I have LSN-Evidence, and Hi-Dev QB Policejob. For some reason, I have noticed when I go to research evidence I collect (via the microscope) I get an error from hi-dev qp-policejob saying there was a script error where it tried to index a nil value. (field āmetadataā). On line 66 of evidence.lua.
Looking at that line, it is passing metadata, donāt see anything wrong with the code. But for some reason, that metadata is nil. I have experimented with a few different options, but couldnāt seem to figure it outā¦ So I started working from the ground up.
I made sure both your script and policejob were completely up to date, configured correctly following the steps on both your github, and hi-devāsā¦ What I found was rather interestingā¦
If a player fires at something, drops casings, etc. When I user the laserpointer, I notice that their lines appear green. I can see the evidence using the flashlight, but after about 30-40 seconds, their lines and evidence vanish. I can no longer see them.
So I am wondering if whatever could be causing that problem, may be what is causing the script error I am having with policejob, as technically, that evidence no longer exists, thereforeā¦ there would be no metadata to pass.
Iād love to find a solution here if you have any suggestions.
All I have done is install Hi-dev Policejob (the 1.3.9 release through tebex, your latest release, and QB-Inventory (since axfw doesnāt currently work.)
Replaced the evidence.lua and main.lua for Hi-dev using the ones you provided. Commented out the AMMO Labels as instructed. Setup config.lua for both plugins. Etc.
After receiving the error, there is also a follow up error saying āQB-Core: SCRIPT ERROR object is not a string.ā
It acts like the metadata for the street and label arenāt there.
Id be perfectly fine zipping up my files and sending them to you if youād like to see. Or I can get on Discord with you and share what is happening. Either way, I donāt plan to give up on making this work. Lol
You are correct about AXFM Inventory using Tooltips and not supporting the serial numbers. There is a way for it to support serial numbers which is just some code you have to add into the app.js. So it would be cool if you could make this script work with that inventory! If you need a copy of the code just add me on Discord which is my username here.