PhillBellic

That was quite the enjoyable read, Albo.

I hope you keep going with your Modding Career, as it brings joy to so many. : )

 
p.s., I would like to read the critical Twitter Posts. Would it be possible to supply some Links?

If this was the 3D Era, you'd not want to be standing so close...

Hi. I hope to see some sweet New Jersey State Police Decals/Liveries soon.

I have a soft spot for them.

Be the change that you want to see.  If you think there's something that you can do that people would like, then do it and share it.
That's exactly what StopThePed started off as - someone wanted to add more/different interactions with peds, so they did it.
 
Maybe people overthink about this.  We make a mod.  Other people make mods, and we make an effort to make both of these things compatible.  It's why mods like StopThePed even exist in the first place.  What's the fun in us trying to do everything ourselves when there are talented people out there, like you mention, who can make things too?
 
And to address the original topic, I think this whole situation is regrettable.  There are many people in the GTA modding community who would do better to keep their negativity and overzealous criticism to themselves.  There are others who would certainly do better not to take so seriously the words of a few internet trolls.
 
If we let ourselves be knocked down a step every time someone said something critical or bad about us, we'd have been stomped away into a different galaxy by now.
But we don't, we just keep doing our thing.

I kind of concur with @chadc78 . First off I can only imagine the pain of having unreasonable impatient complaints by people, who rather think of complaining first then remarking the effort going into developing such sophisticated plugins, it must be devastating...:  Seeing people not recognizing all of your hours of free time going into a project, which could have been assessed semi-professional work at that point.
STPD and UB almost never crashed on my end and updates where frequent with new lore-friendly features coming every once in a while.
With that said I don't want to hurt anybodies feelings by stating that this approach on that matter -  by deleting all of your files relentlessly - might be a little selfish.  A lot of my RP depended and still depends on those plugins and callouts, which eminently enriched my LSPDFR experience to a point, where it is a fully functional police simulator with a level of interactivity never reached by other sims. To completely erase all of your modding history on that page is a huge loss to many of us. Instead, the way of @Albo1125 's communication would have been a more favorable choice. By posting an open and honest statement concerning easily accessible to everyone on this page, keeping your plugins in a sort of legacy state and maybe revealing your source code to the public for everyone to review and refine, to take over the time you need for recreation.  That would have proposed a soft resignation with nobody feeling overwhelmed by such sudden events.  Right now everyone is left irritated and even sorry for not having made comprehensive backups maybe due to limited space or hardware corruption etc.
In conclusion I really understand the fact that they're a lot of people behaving like self-righteous customers, who don't fully understand the concept, the philosophy of a modding community in all of its depth. But there are also people out there appreciating every work submitted, offering support in every aspect.  And there are many.  In contrast this way of assertion didn't leave anyone contented and solely sheds light on the more regrettable part of our community.

It definitely sucks. I’m really glad I was able to get the last update he did. A few days before he removed everything.

Oh I didn't see this, so he is taking a break due to some negative stuff.  I understand, biggest reason modders leave or take a break is due to the constant nagging from users to ''do this/do that''. 
 
Translated from his profile page it comes down to feeling underappreciated and undervalued. Also the fact that brand new users can leave reviews is bothering him, he wishes people only with a good reputation to be able to review. Seen many modders collapse due to this, hopefully he has the energy to still pick things back up, just sad that people can be so demanding and mean when someone is obviously putting his heart and soul into something...for free. 
 
You could get 10 comments about how people love your mod and 1 comment thats negative and you'll forget all about the other positive ones, it sucks.
 
~~~~~~
Edit: He is now hosting his mods on his own website; https://bejoijo256.wixsite.com/bejoijo
~~~~~~

Hey guys, I've never actually commented on any LSPDFR thread, although I believe now is as important a time as ever since we're on the topic of negativity. I completely agree with everyone above's comments about how the negativity is just too harsh, and agree with what Sam said. If the devs of any mod were to give up whenever negative comments stack up, we wouldn't have any mods. I remember when LSPDFR .4 came out, the TERRIBLE criticism the devs got for updating it. I agree, LSPDFR .3 was working great, and when LSPDFR .4 came out it comparably had a few more problems. But I never complained or got mad, because without experimenting and taking the risk of trying, we wouldn't even have new mods or any updates for LSPDFR. Sometimes people will become so selfish that they forget the HUGE FAVOR the devs are doing for us. They don't have to do any of this and you could not have a single thing but the base game to play. But it's because of these peoples devotion and commitment that people like you and me can come home from work or whatever you do everyday and unwind and enjoy GTAV w/LSPDFR. That being said, I couldn't imagine pouring all my free time into something not only for myself but for others to enjoy.  To have someone who's only been modding for a week give you a 1 star review and complain because they most likely don't know how to install the mod and now it doesn't work. That would be VERY discouraging. I just feel sorry for these guys. It was said above they work so hard, and all they ask for is appreciation. Instead of appreciation they just get criticism for things people believe should be done differently, or just because they likely have conflicting mods or a bad install and it doesn't work for them. Just a shame. To all those out there who spend their time working hard to ensure we all have a fun time playing GTAV, thank you. I, along with the large majority of others on here, greatly appreciate everything yall do, and your work is very valued. I honestly have been playing GTA since the 3d era, and I have never had as fun an experience with the game as I have playing LSPDFR. All of your hard work is VERY appreciated by almost everyone, it's just a few unappreciative bad apples who complain and ruin it for everyone. I also agree that people under a week, maybe even a month, should not be able to leave reviews because they just don't understand everything that goes into this, and don't realize the damage they're doing by posting the negativity.  I'm sorry this turned into a book, but I feel it needed said. Again, thanks devs for everything you do to ensure we all have an enjoyable time playing LSPDFR, from Albo to Beojlio(might have spelled wrong) and others, you guys are truly a Great group of people who work hard to give us a more enjoyable experience. Just my 2 cents. 

Check the Version Number. 😛

Provided things go well the update tomorrow I plan on doing a story campaign. Give the officer character a name and hopefully present a good story from the perspective a cop in Los Santos.

Hello again @Sam
 
So problem, 10 codes aren't universal. Do you think I should use LAPDs 10 codes since LSPD is based off them? 10-95 for the Agency in my town is "Officer Needs Assistance"
10-95 according to a chart I'm looking at means "Prisoner/Subject in custody"
 
Also I'm going to update the dispatcher and I'm getting in touch with a friend that does sound effects. That way the dispatcher will do something like this "1-Lincoln-18 we have a 10-31 in *keyboard typing* Strawberry"
 
For the dispatcher I'm going to get as much of the actual codes as I can get done. So someday when LSPDFR reaches that point you're going to have all the audio for the call outs you'll need.
 
I'm getting some more voice actors and actresses and I expect to get going on this soon.

Sorry @Sam I set the tracks to private and used the wrong links 😞
 
Let's see if these will work 🙂
 
Male Cop Test
 
 
 
Female Cop Test
 
Thank you for your interest in this project. I look forward to knowing your thoughts and if there some audio that can be done. Depending on the success of this project and it's usefulness as a resource, I'd like to include more voices for officers, suspects, and citizens. But in the end just clean audio that can hopefully be used.
 
 
 

Introduction
At some point in time, we all have been exposed to the unit circle, whether it was 
in middle school, high school, or even college/university; however, why is it important
in the realm of development and what does it look like?

For starters, the unit circle serves as a way to convert degrees into radians. This is crucial
especially when working with non-els environmental lighting. In Grand Theft Auto V,
Rockstar Games uses radians as a way to manage start and delta values inside carcols.meta.

Notes: Top half of the unit circle represents the driver side and the bottom half represents the passenger side.
Pi represents the rear and 0 degrees represents the nose of the car.
 
 
 
 
 
In order to find how the values were derived in the images, use the equation below!



Converting Degrees Into Radians
The chart above is useful if mathematically inclined; however, for those who are like me
who do not get it right away; I have an easier way to derive values for delta and start.

(degrees°) × (Pi) / 180
NOTES: For all values on the passenger side, use the ones you get on the driver side and make the answer negative.

 
 
 
Q: 'Alright pudding, this is great and all but how is this equation exactly used?! What if I wanted my environmental lighting 35° in carcols.meta?'
A: Just plug and chug! (35) x (Pi or 3.14....) / 180 =   0.610865238


Let's try a few practice problems:

1. If Bobby wanted siren9 reflecting towards the back of his vehicle (180*), what is the Delta Value in the carcols.meta for this specific siren?
(180) x (Pi or 3.14....) / 180 =   3.151592654

2. Jimmy wants his siren1 to reflect on the passenger side of his vehicle at 45*. What is the Delta Value in the carcols.meta for this specific siren?
- [(45) x (Pi or 3.14....) / 180] = - 0.785398163

3. Alex decided that a light was going to face 135* (driver side) on his car. What is the Delta Value? Work this one out and the answer will be in the spoiler below.
 


If you had the answer right, congratulations! Now you know how to convert degrees into radians. I know I have not covered the start value but this value
luckily measures in radians just like the delta value does. 
 
Start values essentially offset the env lighting to start in a specific spot when activating your non-els lights.

What the fuck.
You're insane these are beautiful, it feels like cheating using these. 

Here is some colors for those who dont know how to read them. Took me a while to figure out. In format of color then color value in that color then below the color value.
ie RED-   0xFFFF0000
0xFFFF0000
Put most common colors.
Editing the colors in the carcols under setting <color value="0xFFFF0000"/>
 
Have red, blue, green, yellow, and white and a few others in there. HOPE THIS HELPS
 
 
 

Hot off the release of LSPDFR 0.4 a couple of months ago, we're upping the ante with another update which brings not only sweeping improvements to the LSPDFR 0.4 API, but also some unique features which have long been requested.
 
Originally, the plan was merely to release 0.4.2 as a quick follow-up to 0.4 and 0.4.1 - just simple fixes and changes, plus the API improvements to help developers make the most of 0.4.  Necessary changes, but not really cool enough, right?  So, with that in mind we took a little time to dig back into the archives of LSPDFR and revisit some of our old concepts and ideas.  Now, while some of these are actually in the mod - they're most likely either tucked away as 'easter eggs' or just disabled because they weren't quite right.
 
If you're a connoisseur of traffic stops, for example, you might've noticed that occasionally the unexpected and oh so demoralizing experience of pulling over a federal agent hits you right in the feels as they arrogantly flash their shiny badge, tell you where to stick your comparatively less shiny badge, and drive off.  (If you haven't seen this before, here's a video: https://www.youtube.com/watch?v=HNOxZR2ak0M)
 
Originally the plan was to add this as a feature for players to use, but it just didn't quite fit in with 0.3, and we had some trouble with the animation not being quite as fluid as we'd like.  That was then, though, and given that you now play as your own character both on and off duty, we thought it'd be a bit of a must-have now, so we've tidied it up and are introducing it as a player action in 0.4.2.
 

 
With one quick glance at the shimmering shield, her problems are suddenly your problems.  (Note, a custom badge model is shown instead of the default FIB one - you will be able to define custom models to use on a per-agency basis)
 
Now, not only does this look exceedingly awesome, but it serves a practical purpose too.  Available both on and off-duty, showing your badge will clear any wanted level and may also instill the fear of the law in nearby citizens, potentially de-escalating the otherwise unavoidable confrontations that flare when you walk around Mirror Park without the latest iFruit phone, for example!
 
Of course, that's not all.  Continuing with the idea of adding things that are just generally cool, we know that people have wanted a ballistic shield feature in LSPDFR for quite some time.  Sure, you can spawn one with a trainer or download another mod, but it's just not quite the same is it? 
 
We thought it'd be particularly sweet to have it at your fingertips instead, fully integrated with LSPDFR, ready to kick some butt.
 

 
As if being Frank Tenpenny isn't cool enough...
 
Our ballistic shield, accessed from the Interaction Menu, uses our new animation system in 0.4.2 which we think looks absolutely gorgeous.  There's also the freedom to switch between Stealth and Action mode which will vary your pose accordingly, compatibility with most weapons and the potential for future AI support.
 
Oh yeah, did we mention you can actually arrest people at gunpoint while holding a freaking shield?!
 
Keep your eyes open for LSPDFR 0.4.2, coming soon.
 

Notes for modstaff in spoiler.
Preface
This text was adapted from a document by Eric S. Raymond, titled How to Ask Questions the Smart Way. The full document is available here - the authors of this document are in no way affiliated with G17 Media nor myself, and aren't there to answer your questions about how to get whatever it is you're trying to get working, working.
Introduction
If you're reading this, hi there. I suck at smalltalk and making things sound nice, so I'll open with this: In the world of diagnostics, there are a few right ways to get Solutions... and many, many wrong ways. This post is here to hopefully help nudge you toward the right ways, so that you can get the Solutions you want easier.
Of course, getting a good Solution isn't just on the people helping you solve your Problems - and you're naïve if you think that. A lot of the work needed to solve a Problem falls on you. A vast majority of the time, whether the issue gets solved depends not on the Problem itself, rather what the end user did to troubleshoot and what information they posted in their support threads.
Depending on how you present your issue and what it may or may not contain, your Problem's thread may get zero replies, or a hundred; it may be solved in an hour, a week, or it may remain an unsolved mystery. This post is here to reduce the odds of that last bit.
Still with me? Let's begin.
Before you post:
Reproduce the issue.
Try to reproduce the Problem. If your game is crashing, try to duplicate the crash. If you can narrow the crash down to a certain cause, you're much better off with getting a Solution to your Problem, because if you can reliably reproduce the issue and tell us HOW you reproduce it, we're much more likely to be able to see the Problem ourselves.
Also bear in mind your Problem may just be a fluke. Maybe the stars aligned just wrong. Maybe it just ain't your lucky day. A good rule of thumb is three times - if the Problem appears three times, it isn't "just a fluke".
Research the issue.
Before you present your Problem, do a bit of research. Give the manual or readme of whatever's having issues a read - the manual/readme is certainly there for a reason. They may not have a troubleshooting section, but the Problem could be a simple issue with installation, especially if the Problem cropped up right after you installed a mod or reconfigured one.
If nothing turns up in the manual, it's time to move onto the web. Search the forums for your issue, and look through the results. If you have an error code, search it. There's also a simple method that I use when searching that I refer to as "object-deviation" - as in, "object that's the issue, and deviation from how it normally works". (Side note: This is also a very good way to write your thread's title, as stated in the document linked above.)
Good example: "GTA5 white police lights".
If the Problem is an issue with a plugin, it's a good idea to look through your log files - sometimes, the error will be right there in plain sight, especially if it's a configuration issue.
Note that verbosity isn't necessarily a good thing - a lot of forums will search EVERY word in the search bar, without omitting words like "the" or "are". If it's an issue with a mod, be sure to look through the file comments as well; someone may have had your Problem already and it may be solved already for you.
If you get nothing on the forums, move on to Google, in quite the same fashion that you searched the forums.
Sleep on it.
No, I'm serious. Step away from the Problem for the day/night, regardless of how much you want it fixed here and now. Give it until tomorrow, after you wake up and have a level head, and are all refreshed. It's no use trying to diagnose your Problem while tired; you could easily miss important clues.
When you post:
Post in the correct forum. You'd be surprised at how many get moved or locked because they're in the wrong forum.
Use a descriptive title.
Some people will read every thread in the support fora, and there's nothing wrong with that. However, most people won't open a thread in a support forum unless the title catches their eye. Most people that look through the support fora will skim the thread titles. Using a descriptive title ensures that your Problem will be seen by someone before they even open the thread. As above, a good convention to use is "object-deviation" - "object of the issue-deviation from normalcy".
VERY BAD: "GTA doesn't work" - Saying something "doesn't work" is the absolute kiss of death and will very likely cause the thread to be ignored. Saying it "doesn't work" is like a used-car salesman saying a car has wheels - it tells us nothing we don't already know, for if it did work as intended you wouldn't be asking for support. "GTA doesn't work" is not a question, and we're not interested in playing Twenty Questions to pry your actual Problem out of you.
BAD: "GTA crashes" - It's the bare minimum you can get away with, but you can be more descriptive than that.
GOOD: "GTA crashes when I drive near the prison" - You have a pretty decent, descriptive title here, saying exactly what's going on - GTA is crashing when you drive near the prison. It doesn't leave what the Problem is for guessing - it's all right there.
Don't butcher the English language.
No matter how much of an emergency getting your Problem fixed may seem, THERE IS NO NEED TO USE ALL-CAPITALS IN YOUR TEXT; MOST PEOPLE READ THIS AS SHOUTING. LIKE YOU PROBABLY JUST DID. The only notable exception to not using all-caps is to emphasize A SPECIFIC POINT, in moderation. (writing in all-lowercase is more tolerable, but on some typefaces is very hard to read.) Don't abbreviate unnecessarily, typng n smsspk lik this 2 sv k/s makes u look lik a semi-lit boob.
If you write like you're a semi-literate boob, you're less likely to receive a Solution and more likely to be a zero-reply thread.
Describe your problem and your troubleshooting steps.
At the head of the post, you should re-describe the Problem in further detail and explain what you've tried. If there were any effects on the Problem at all - positive or negative, especially negative - list the effects as well. In doing so, less time is wasted on what you've already done and more can be spent on that which you haven't done.
Attach relevant logs and configs. If it's an issue with a plugin or an ASI mod, attaching the logs could pin down your Problem to an issue. If it's a configuration issue, attaching your config file could help us point out where you went wrong.
Leave questions open-ended.
If you have a question about something, leave it open-ended. Yes-or-no questions get yes-or-no answers; leaving a question open-ended allows room for us to suggest a better way to do whatever it is you're trying to do.
BAD: "How do I get a RGB car paint colour through a trainer?"
GOOD: "I'm looking to get an RGB car paint colour from in the game. I'm trying to do it with a trainer but I don't see a way to do it - any suggestions?"
Note how the way the second example is worded subtly encourages you to suggest something better-suited to the task than the trainer.
Describe the Symptoms, not wild guesses.
It's not useful to tell us your wild guesses as to what you think might be happening sans context - if your diagnostic theories were correct, you wouldn't have a Problem to post in the first place. Write down what your Problem's symptoms are and let us see what we can do. That's not to say educated guesses aren't alright - in fact, they're more than OK if you can tell us how you came to that conclusion; but if you can't give us a logical, rational explanation on how you came up with your guess, you're better off not posting it.
Keep public support requests to public channels.
Problem solving should be public - if someone else comes upon your Problem later, they can look at your thread and see any Solutions that you may be given. There may be reasons for taking something to PM, but unless you're specifically asked to, you should leave it public - taking it to private channels without permission is generally seen as rude.
Now that you've posted:
Keep looking for possible Solutions.
If you find a Solution to your Problem before someone else does, edit your post and tack on the solution, and make the title clear that it's solved. If you say "nevermind, got it" you look like a dick for not posting what you did to fix it, to any future Solution-seeker that may happen to stumble across your thread.

(Above image copyright 2011 Randall Munroe. Link to source)
Don't mistake bluntness for rudeness.
A lot of communications for a lot of people revolve around tact and courtesy - not here. As you can tell by the way this is written, people here to help you solve problems are very seldom here to make you feel warm and fuzzy in doing so. We're not here to offend you, we're just cutting through the unnecessary fluff.
If you feel someone's being rude, keep cool. If they really are being rude, someone will call them out on it. If they don't and you lose your temper, it's quite possible that whoever you just lost it on was behaving within the community's norms. Most flames are best left to burn themselves out - after, of course, you've checked that they're really flames, and not hidden Solutions to your Problem.
Don't immediately demand clarification for Solutions you don't understand.
Yes, you read that right. If you don't understand, you should use the tools you used to try to find your Solution before you posted it (Google, forum search, manuals, logs, etc.) to try to understand the Solution you've been given. If you're still stumped, THEN ask for clarification.
BAD: "What do you mean 'set SECL to DROT'?"
GOOD: "I read the manual, but I didn't see anything about DROT under 'SECL'. I did find DROT under 'PRML', and 'ROTA' under 'SECL', though; is it one of these or am I missing something?"
Don't bump your thread.
No matter how long it's been, have a bit of patience: no response isn't the same as being ignored, though it may be difficult to tell the difference. Bumping your thread may be seen as a sign of impatience to those that may be trying to help. Also, bear in mind the size of the Earth - even if it's high noon where you live, someone with a potential Solution may be fast asleep at 2 in the morning where they live.
In Conclusion
A lot of our ability to give Solutions depends on your ability to provide information. Threads with a lot of useful information are easier to provide Solutions for, whereas Problems with absolutely no information listed are nigh impossible without us having to force the information out of you. By using the above guide, you greatly increase the odds of getting a useful Solution to your Problem, and you may even learn a thing or two in the process.

I'm looking forward to this. It's nice to have different options for the same vehicle sometimes.

If this was the 3D Era, you'd not want to be standing so close...

So you have this great shoulder patch, you spent hours perfecting it so it looks just so. You wanna give it to a ped, but there's a problem: its too smooth! it'll look like it was cheaply screenprinted on the uniform, and that's just not right.
 
You wanna give it a clothy appearance, like a patch that they sew onto the uniform. So first, you're gonna navigate to Effects>Noise>Add Noise. Adjust the color saturation to 0, and the intensity to anywhere between 5 and 25, depending on your personal preference. what you get should look something like this:
 
So you finally have the desired slightly rough, cloth look. But you're not done. You wanna make it look embroidered- real patches aren't just flat. They have bumps in the details and lettering, which are embroidered onto the base patch. So you're gonna select your patch (otherwise the background is gonna get the effect too) and go into Effects>Stylize>Relief and adjust the angle to 90 degrees. the result should look similar to this:
 
And voila! you're done! It has the bumpy embroidered effect AND the cloth look! It's realistic! You can finally save your work and put the patch on a ped.
 

That Necro-Posting, though. LOL. 😉

I can post one but you can really see how well it will look on the model till it gets released. 

First of all sorry for the late reply
Mainly full L0-L4 Lods. unlike other models that copy the L0 to the other lods with tiny changes. 
I've also reduced the number of texuters it uses. Other Vics use 40 or so, Mine is 26
Three wheel options: Hubcap, centre cap and bare rim. 
 
Release should be in the next few weeks if everything goes to plan and I have no unexpected issues. Also expect a 2 more 'Panther' releases from me that I think LSPDFR  will really love. 
 
_________________
 
Also as for lods so far
L0 is 88K 
L1 30K
L2 12K
L3 6K
still need to make the L4 (might just use the Vanila police one) and add an Engine that I have been working on.