Staff Applications open to the public! ×
Jump to content
×
×
  • Create New...

tromac

Member
  • Posts

    107
  • Joined

  • Last visited

GPM TrustFactor Score

92% 92%

Recent Profile Visitors

613 profile views

tromac's Achievements

Sergeant

Sergeant (5/9)

  • 1 Year of Service
  • 25 Content Count Rare
  • 75 Content Count Rare
  • 100 Content Count Rare

Recent Badges

20

Reputation

  1. Disregard, they show on the map. Thanks again
  2. Awesome idea, about to test it. Question, you say set stores can you please advise which ones? Thanks for your work!
  3. Think I just spotted it, a double up in the vehicle code3bmw. I'll fix and test.
  4. { "police": [ { "name": "LSPD 2011 Crown Vic", "vehicle": "code3cvpi", "isAvailableForEveryone": true, "availableForDepartments": [11] }, { "name": "LSPD 2013 Caprice", "vehicle": "code3cap", "isAvailableForEveryone": true }, { "name": "LSPD 2016 Impala", "vehicle": "code316impala", "isAvailableForEveryone": true, "availableForDepartments": [11] }, { "name": "LSPD 2010 Charger", "vehicle": "code310charg", "isAvailableForEveryone": true, "availableForDepartments": [11] }, { "name": "LSPD 2016 Taurus", "vehicle": "code3fpis", "isAvailableForEveryone": true, "availableForDepartments": [11] }, { "name": "LSPD 2014 Tahoe", "vehicle": "code314tahoe", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer II", "Officer III", "Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD 2014 Charger", "vehicle": "code314charg", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer II", "Officer III", "Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD 2016 FPIU Explorer", "vehicle": "code316fpiu", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer II", "Officer III", "Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD 2020 FPIU Explorer", "vehicle": "code320exp", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer II", "Officer III", "Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD BMW Motorcycle", "vehicle": "code3bmw", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer II", "Officer III", "Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD Harley Davidson Motorcycle", "vehicle": "code3bmw", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer III", "Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD 2015 F150", "vehicle": "code3f150", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer III", "Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD 2018 F250", "vehicle": "code3f250", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer III", "Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD 2016 Silverado", "vehicle": "code3silverado", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer III", "Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD Durango", "vehicle": "code3durango", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer III", "Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD 2019 Silverado", "vehicle": "code3durango", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD 2016 Dodge RAM", "vehicle": "code3ram", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD 2018 Mustang", "vehicle": "code3mustang", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD 2018 Camaro", "vehicle": "code3camero", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD 2018 Charger", "vehicle": "code318charg", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD 2018 Charger K-9", "vehicle": "code318chargk9", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] }, { "name": "LSPD 2018 Tahoe K-9", "vehicle": "code318tahoek9", "isAvailableForEveryone": false, "useRanks": true, "availableForRanks": ["Officer IV", "Sergeant I", "Sergeant II", "Sergeant III"], "availableForDepartments": [11] } ], "ambulance": ["ambulance"], "airAmbulance": ["polmav2"], "firedept": ["firetruk"], "coroner": ["coroner"], "towtruck": ["flatbed"], "mechanic": ["utillitruck3"], "prisontransport": ["policet"], "animalControl": ["bison"], "taxi": ["taxi"] } I must be blind and missing a basic error in the code. Thanks for checking and having a look at this.
  5. Love the ability to restrict cars to players based on their ranks. My question is, is this limited to only working with a set number of cars? I have set the vehicles.json file up as a test with about 22 cars and only 10 show regardless of the rank being able to access more. I've checked the file incase of any errant commas but all looks good.
  6. Please close, not sure what was happening but it's fine now
  7. We are on a test server running 1.2.8 before pushing it out live on our community server and we've noticed the X key to have traffic stops mimic, follow or go to point is not working. Has anyone else had this same issue? No errors in logs or on F8.
  8. Add the following into your server.cfg file: onesync off onesync_population false
  9. Yes same thing here, I am trying to find out how to set onesync as per the error but not having much luck so far
  10. Like everyone else I'd love to see this callout brought up to date for use with FivePD please.
  11. Had to reinstall our FivePD server thanks to Zap-Hosting screwing up a simple task and in the process I thought I'd check if we can run the current release of FX Server. On watching through the Install video by BGHD he says to use the latest release. So I did however when FivePD loads there are horizontal and vertical scrollbars. I've been testing for nearly a 8 or so hours and have confirmed it is the FivePD resource that is doing it. I have tried with just a fresh 1.1.4 install no additional content or callouts and it still has the scrollbars, as soon as I remark out FivePD it's fine. Any ideas?
  12. I was using that but it errors out for me now on some of the callouts. Specifically I get this error and no idea on how to correct it. ILMerge.Merge: /target not specified, but output file, 'G:\FivePDCalloutMerge\callouts.net.dll', has a different extension than the primary assembly, 'G:\FivePDCalloutMerge\callouts\CarCallouts'. at ILMerging.ILMerge.Merge() at ILMerging.ILMerge.Main(String[] args)
  13. I'm in the process of doing just that, thanks Cipher ? It's all good, just an annoyance.
  14. I have the exact same issue. Just dumped all the community callouts and only have the base FivePD ones. The callouts are back now. But it's annoying that these break every time you guys do an update. We go back to having next to no callouts.

Important Information

Please view the site: Terms of Use, Privacy Policy, and Guidelines. // IMPORTANT: We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.