@Spacetrucker
I did not make PIS, that’d be KNOBs. PIS was a big inspiration for me but I did not write that script ^^
@Captain_Waterloo and @JAMYBBOYJD
The issue with the radialmenu (X) is surely related to the resourcename. Have you renamed your resource to be all lowercase, i.e. pd5m ? This has to be done otherwise the exact error you describe will happen.
ESX and vRP are only supported on a basic level. This resource is intended to be used standalone.
@Captain_Waterloo
Regarding the issue with E-Menu: Do you have ESX or vRP installed? If yes please check if you got the job ‘police’ set. If not please contact me privately, I’ll have to look into this in detail.
@PolarisSurvivor
The Tow- and Coroner-Script has been “fixed” after 1.1 to not get the cars stuck indefinitely. Seems like my fix doesn’t work so I’ll need to provide a better script to fix the issue with cars getting stuck. Will try to fix it this evening.
Regarding the notifications this is a compability issue. This naturally happens since E is a pretty often used key for interactions.
The reason the notifications show is because of the way I code. Pressing E will trigger the following if-clause:
if IsControlPressed(0, 51) and not (atheal or at[insert-location-here]) then
if IsAimingAtPed -- not an actual function but you get the idea
.
else
Notify('No peds or cars close')
end
end
atheal is short for player is standing at a heal point. I have defined these variables for every of the PD5M-interaction-points (like garage etc).
What I can offer is another variable atCustomLocation. This would be controlled using one thread:
local CustomLocations = {
{x=500.12, y= 611.34, z = 20.43}, -- my custom location
}
local playerped = GetPlayerPed(-1)
local distance = 0
atCustomLocation = false
while true do
local playerpedcoords = GetEntityCoords(playerped)
for i, Location in ipairs(CustomLocations) do
distance = Vdist2(playerpedcoords.x, playerpedcoords.y, playerpedcoords.z, Location.x, Location.y, Location.z)
if distance < 5.0 then
atCustomLocation = true
while distance < 5.0 do
Wait(5000)
distance = Vdist2(playerpedcoords.x, playerpedcoords.y, playerpedcoords.z, Location.x, Location.y, Location.z)
end
atCustomLocation = false
end
end
Wait(0)
end
What this does is it activates the variable atCustomLocation if you are closer than 5 meters. The custom locations can be defined in the list CustomLocations. The only thing that would need to happen now is that you define the locations where to disable the E-menu by setting the coordinates in the list.
Would that be something I should add?
