Jump to content

OfficerFive0

Members
  • Content Count

    3010
  • Joined

  • Last visited

  • Days Won

    17

Reputation Activity

  1. Like
    OfficerFive0 reacted to OfficerUnderwood in OfficerUnderwood's DEV models thread (Current project: Who the fuck knows)   
    Fixing up this piece of shit because it got fucked it in the ass too damn much. Replacing some of the shit with stuff from Carface's. Not smart enough to do a Suburban to Tahoe conversion like GeorgieMoon or I would.

  2. Like
    OfficerFive0 reacted to OfficerUnderwood in OfficerUnderwood's DEV models thread (Current project: Who the fuck knows)   
    Fixing this up and releasing it. Needs ton of work. Got the polys down from 290k something to round 230k just removing the 3d logo, headlights, tailights, & radiator. No telling what's going on in the interior.

  3. Like
    OfficerFive0 reacted to Twurtleee in TurtleGod3000's DEV Parts WIP   
    Partition pack I've finished and plan on releasing today or tomorrow once textured

    Also just released the other Valor that's been on my pc forever and I forgot about it being finished
    Also working on a new Silverado, a pushbar pack for various vehicles, and some other goodies to be released here soon
    Silverado is in the crunching process, when I get further in I will release some pictures of everything
  4. Like
    OfficerFive0 reacted to flwpheonix in At a distance ELS does not emit coronas   
    Otaku, actually ELS does use LOD coronas to supliment when you get further away from the vehicle. They are placed where the axis is located for for the extra. Most people turn the detection distance to 800-900 as using LOD coronas in this manner causes floating coronas if the modeler do not pay attention to where the axis is.
     
    To answer this problem, it is a little more difficult. In the visualsettings.dat there is a way to tweak the distance of the bloom but I am not 100% certain on how it works or how to do it. I personally have not experienced this problem on my system, so I cannot help further. What I would do, is make a backup of your visualsettings.dat file and search for bloom within the file and start tweaking numbers. If something gets screwed up, you always have your backup.
     
  5. Like
  6. Like
    OfficerFive0 got a reaction from Sgt.Kanyo in Dull looking lights at sunset or sunrise   
    NaturalVision, it causes it. the author stated on the mod page that it was either good looking lights, or good looking sunset (something along those words).
  7. Like
    OfficerFive0 reacted to Him1250 in Patty Mayo FPIU   
    It's god awful and looks absolutely atrocious 
  8. Like
    OfficerFive0 reacted to Him1250 in Patty Mayo FPIU   
    God no.
  9. Like
    OfficerFive0 got a reaction from riquebr in [WIP] LAPD/LASD/CHP FPIU (2014)   
    So you dont have any experience modding in V, you dont know anything about setting up models in V, yet you call someone with experience and knowledge negative because he said something impossible cant be done.
  10. Like
    OfficerFive0 reacted to liverlande in [WIP] Grande Callouts   
    Grande Callouts is an LSPDFR plugin which aims to add a variety of different callouts of no distinct category. This plugin does not aim to add lengthy or otherwise complex callouts, the majority will be quick service calls that are resolved mostly through already existant game scripts and mechanisms.
     
    Callouts:
    Green - Stable, works in game
    Yellow - May or not be stable, a prototype is in the script
    Red - Not scripted, but is planned.
     
    Law Agency Assist: Distress Call
    Tow Truck Operator Assist
    Medical Emergency Assist: Heart Attack
    Medical Emergency Assist: Stabbing
     
    Current Prerequisites:
    LSPD First Response 0.3.1 - The base LSPD First Response modification is required for use.
    RAGEPluginHook 0.51+ - This plugin will only work with RAGEPluginHook 0.51+ or above.
    Legal version of Grand Theft Auto V - This plugin will only work with legal copies of Grand Theft Auto V.
     
    Compatible Plugins:
    I believe that good plugins should be compatible with any variety of additional scripts. All plugins listed here are optional, meaning this plugin will work without them. Some functionality may not be offered without these plugins, however.
    ComputerPlus+: this plugin is used to store information relevant to the current (and past) callouts triggered by this lugin. "Status Updates" may be provided throughout the course of the call.
     
    Additional Features and or Things To Brag About:
    Smart Exception Handling: A majority of possible exceptions will be caught by the script in the event that they do occur. Where possible, exceptions will be recovered from. For all exceptions (even those not caught locally), a variety of exception information will be printed to the RAGEPluginHook log file. Some exceptions can not be recovered from.
    Configurable Settings: Self explanatory and expected. There are some settings you can configure, such as what callouts to enable, minimum and maximum spawn distance for callouts, keybindings, and more.
    Minimal Performance Impact: This plugin is designed with performance and CPU use in mind. Separate threads are used where applicable, continual processes are only run when necessary.
    Hopeful Consistency: My goal is to keep this plugin consistent where possible. This means keeping the script organized and using uniform functions across callouts and other parts of the plugin. This brings the benefit of being able to introduce modifications to the plugin with relative ease, including adding new callouts.
     
    What I Want From You:
    What do you want to see from a plugin such as this? Do you have any ideas for callouts or other scripts that can be added in? Are there any released plugins that could add additional functionality (note: these plugins must provide sufficient APIs)? Would you rather variables such as amount of suspects, vehicle models, et cetera be hardcoded, or would you rather be able to configure such variables through an .xml file?
     
    Release Date:
    TBA
      
  11. Like
    OfficerFive0 reacted to Giordano in Recommended handlingIds for your police vehicles   
    So you downloaded a fancy 2015 Tahoe and installed it in the police3 slot, only to find that it rolls more than your eyes when your boss is talking to you.  Does your Silverado not drive like a truck should? or maybe your '15 Charger doesn't feel right.    There are a lot of options to choose from when deciding which handlingid you want to use for your car.  I've compiled a list of what I use for handling lines, and thus far, all have worked just fine.  For some of them, such as the Silverado and Expedition, someone else might of found a better handling, and if that's the case, please comment below letting me know what you're using and I'll give it a shot. 
     
    Some people like to edit the handling.meta.  This is not a requirement, the handlingid is all you need to touch if you just want the basics.  Handling.meta is there for those who know a bit about modding and want to refine the handling lines to feel realistic.
     
    For those that might be confused on what the handlingid is, it's one of the top lines in the vehicles.meta.
     
    Here's an example:
     
    <handlingId>police3</handlingId>  
    All of these will be for police vehicles, I will not be covering modded civilian cars.  Also note that this topic really only applies to those who have modded their police fleet.
     
     
    Crown Vic
     
    police  
     
    Charger
     
    If 09-10 version, police2   
    If 2013+ version, buffalo2  
     
    Taurus, Caprice and Impala 
     
    police3 fugitive (this will make the vehicle feel heavier)  
     
    Explorer 
     
    gresley  
     
    Tahoe 
     
    baller  
    Expedition
     
    fbi2  
    Silverado
     
    bison (sadler works if you want the truck to feel a little heavier)  
    Dodge Durango
     
    gresley  
    Dodge Challenger
     
    gauntlet  
    Ford Mustang
     
    dominator  
    Ford Fusion
     
    tailgater (There is most likely a very better choice out there, I'm just not sure which would work)  
    BMW motorcycle
     
    policeb  
    Ford F-150
     
    sadler  
    Ford F-350
     
    sadler  
    Chevrolet Corvette
     
    coquette  
    Chevrolet Avalanche
     
    sandking  
    Chevrolet Camaro
     
    gauntlet  
    Nissan GTR
     
    elegy
  12. Like
  13. Like
    OfficerFive0 reacted to OfficerUnderwood in OfficerUnderwood's DEV models thread (Current project: Who the fuck knows)   
    Hurk's Exploder
    police3_hi = 4.6MB & police3= 12.1MB (Oof) 165,849 polys 50 textures & 35 materials Hurk's Exploder modified alot by OfficerUnderwood
    police3_hi = 3.8MB & police3= 7.4MB 151,647 polys 43 textures & 33 materials I'll upload pictures in a bit. Just gotta fix some bugs.
     
  14. Like
    OfficerFive0 reacted to Rarity in Rarity's - Works in progress   
    This topic will be updated with my new and up coming vehicle projects and development models. Once available for download, the topic will be updated with links.

    Development Models
    Coban TopCam Gen II
     
    Panasonic Toughbook CF-29
  15. Like
    OfficerFive0 reacted to OfficerUnderwood in OfficerUnderwood's DEV models thread (Current project: Who the fuck knows)   
    Moved from the Tahoe. Now working on Hurk's Exploder so I can make an actual model instead of a DEV. Thing needs a good bit of work for it being 165k polys. Guessing it's the 3D Police Interceptor badge, 3D Radiator, 3D Headlights, & etc that could be a simple 2D texture with a bumpmap. The interior needed work on the decals since they weren't the right font nor symbols. Added a good looking badge plus trying out the DuDv bumpmap stuff. The yellow looking bumpmap, not the purple looking one.

  16. Like
    OfficerFive0 reacted to MetCam in Identify this lightbar?   
    Thanks for that! I was searching everywhere. I did think it'd be a Whelen Justice but the fact that they usually have clear lenses made me think maybe not...
  17. Like
    OfficerFive0 reacted to Scuderio in Scuds' CA stuff   
    Small ones kinda. Besides my personal life I am modding a bit, improving some stuff and remodeling a lot stuff since I want to go lower on the polys. I also create some LODs for the parts that don't have them. I saw a lot of models getting released with just "LODS" that basically were just polycrunched L0 models that still were highpoly so, about as bad as just having no lods. So yea doing some stuff, but not that much that I can process so fast, but I'm trying. 
    -
    Sorry to everybody that I don't really update you guys on the stuff and also sorry that I don't release the stuff, I'm just not happy with the models at the moment.
    A small hint on the current stuff, I am working on a setting up a new Arjent S2 with a Fed Sig ALPR for a special car with now accurate equipment 😉
     
     
  18. Like
    OfficerFive0 reacted to t0y in Walters' WorkShop | Too Many Things   
    ... Do you ever read what you're complaining about before whining? I said "ballistic plates, glass, interior" what else do you want me to do? Hold your dick while you piss? You need to have more independence than that, and I'm not sure how that list isn't helpful. I'm saying for this pack to be accurate you need to include the ballistic/bulletproof panels that almost the entire NYPD fleet has (including unmarked) and including the 2018 dodge charger naturally, and include the ballistic/bulletproof glass, that again almost every car has. You also need to basically redo that interior interior from the ground up. Not only is it not accurate, and quite empty, the parts aren't scaled or placed right, emissives are incorrect, and the materials are far from right. Sure this is an upgrade from your old pack, but really anything would be, the bar isn't that high. Just because someone scratch modeled you two laptops and keyboards doesn't make them accurate lol, I've had the entire NYSP interior scratch modeled yet you and your friends try to cry about that. Get over yourself.
     
     
     
  19. Like
    OfficerFive0 got a reaction from Slendis in Walters' WorkShop | Too Many Things   
    ^ and please use the proper emis . Linear emis on a tir led is no bueno.
  20. Like
    OfficerFive0 got a reaction from Slendis in Walters' WorkShop | Too Many Things   
    ^ and please use the proper emis . Linear emis on a tir led is no bueno.
  21. Like
    OfficerFive0 got a reaction from Slendis in Walters' WorkShop | Too Many Things   
    ^ and please use the proper emis . Linear emis on a tir led is no bueno.
  22. Like
    OfficerFive0 reacted to c13 in LSPDFR 0.4 - Ambience   
    I was playing last night and I got in pursuit of a suspect who was flying over route 1 and eventually on the Pacific coastal highway. Due to heavier traffic, I fell back a bit and was responding behind two other units. It gave a sense of realism where I wasn't always the first one to a call, where I am always reacting to what was going on and having to call backup myself. It was one of my favorite moments in a while.
     
    After talking to others, a common issue we have is a sense of being alone on shift. I feel like I have a solution that can mitigate it, and should be fairly simple to implement.
     
    Back in LCPDFR, there was a kind of hidden feature where if you set a waypoint, you could call for backup and a unit would spawn next to you then respond to the waypoint alongside you. Such a feature could easily be implemented, and with features that didn't exist before like code 2 backup, it will give a sense of an actual department responding instead of a lone player who shows up first and reacts to everything. A nice feature would also be the ability to have backup stick around until dismissed, like in OnScene backup.
  23. Like
    OfficerFive0 reacted to LibertyDesigns in Guide to Writing a Quality File Description   
    Guide to Writing a Quality File Description
    For modification developers on LCPDFR.com

    T. Jennings | October 2018
    https://www.lcpdfr.com/profile/341940-t-jennings/
     
    This work is copyrighted. Any unauthorized exploitation, modification, or reproduction by any means is strictly prohibited and will result in consequence. The contributors to this file will not be held responsible for any damage this guide causes if it is used for any means other than it’s intent.
     

     
    Introduction:
    This guide is aimed at assisting you in writing a descriptive and informative file description for your mod’s web page. In this guide you’ll find the process of; what information to include, formatting, and file archive structure. To begin, it’s suggested to draft a template of sorts in a word document. Make sure your document is set up so all information is easy to find and able to be understood.
     
    Title:
    When drafting your title, be sure it explains your file in 8 words or less. Attempt to avoid a prolonged title, as it drives traffic away from your download page. Viewers want to know what they’re clicking on, this is why a short, but descriptive title is preferred.
     
    Author’s Note:
    Viewers like knowing some background information on the file they’re looking to download. When drafting your file’s description, be sure to include a short author’s note explaining what the file is, the inspiration behind it, etc. It adds to the connection between an author and his file users. It’s suggested to have at least a paragraph for your author’s note.
     
    File Information:
    Under file information, you should include general information about the file. That includes (but is not limited to); the mod’s inspiration, what other mods the file is compatible with, and any optionals that come in the file (i.e. red/blue lights, blue/blue lights).
     
    More Details:
    Include additional details about the file that may not be extremely important, but can be notable. This includes things such as amount of liveries, amount of vehicles, suggested system strength, etc.
     
    What’s Included:
    As self explanatory as it may sound, many people lack this in their file descriptions. What to include in this section of your file description:
    Type of vehicles
    Year of vehicle model
    Base vehicle model
    Any other immediate info to what’s included
     
    Disclaimers:
    To avoid being held responsible for someone not knowing how to install your mod, or misusing it, you really should add a disclaimer to your file description to prevent any chance of being responsible for fixing someone's game/system. In your disclaimer, you should include the following:
    Not to rip/steal your work(s)
    Do not exploit for any form of gain
    The file contributors will not be held responsible for possible damages
     
    Logo:
    Don’t be afraid to add the logo of your modding group, or even your own to the description! Logos match your work with you, and help people assign a look to an account. Rarely do people go out of their way to see who published a file, so if you include a visible logo in your upload, your work will more easily be remembered.






     
    Designing a “More Information File”
    Further customizing the look of your file’s web page

    T. Jennings | October 2018
    https://www.lcpdfr.com/profile/341940-t-jennings/
     
    This work is copyrighted. Any unauthorized exploitation, modification, or reproduction by any means is strictly prohibited and will result in consequence. The contributors to this file will not be held responsible for any damage this guide causes if it is used for any means other than it’s intent.
     

     
    Introduction:
    If you’ve been around LCPDFR.com for a little while, you may have noticed some authors (such as BxBugs123, Era Modding, Walters) have designed a custom image for their file description instead of the default text. You can do this as well, as long as you have a program to design a More Information File (MIF)!
     
    Suggestions:
    In order to create an easy to understand MIF, you must have all information gathered previously in the Quality File Description Guide. Once you have all of this information, it’s time to move on.
     
    Design:
    Design is completely up to the user, but make sure the format is easy to understand, as your main goal is to have as few obvious questions in your comment section. If you’re having trouble formatting, use this template:
     
    Category (in order):
    Info to Include:
    Author’s Note
    What’s this mod? Why’d you make it? What is the inspiration behind the mod?
    File Information
    Where/what is the mod based? For what other mods is this one compatible?
    More Details
    Include some additional details about the file that may not be pertinent, but are notable
    What’s Included
    Tell what you included in the file archive
     
    Uploading to LCPDFR:
    In order for your MIF to appear in it’s maximum (readable) size, you must first upload to imgur.com. Save your MIF as a PNG, then go to https://imgur.com/ and sign up or log in. Go to your images tab, upload your MIF. After it’s uploaded, click to open it. Once you click to open it, you should have a few links available to copy. Find the “BBCode” option, and copy it. Paste it into your file description on LCPDFR, and save. It should now pop up in your description.
  24. Like
    OfficerFive0 got a reaction from Mikofiticus in [WIP] LAPD/LASD/CHP FPIU (2014)   
    Yes, the architecture is similar, but very much not the same. 
     
    Regarding your issue with the steady burns, Im fairly certain thats a problem on your end. perhaps you edited the xml? No-one else seems to be having this problem and i tested it and never encountered this issue.
  25. Like
    OfficerFive0 got a reaction from Mikofiticus in [WIP] LAPD/LASD/CHP FPIU (2014)   
    Yes, the architecture is similar, but very much not the same. 
     
    Regarding your issue with the steady burns, Im fairly certain thats a problem on your end. perhaps you edited the xml? No-one else seems to be having this problem and i tested it and never encountered this issue.
×