SkittleKicks Plays

You change that yourself by taking the lighting textures (in the ytd) into PaintDotNet. Carefully highlight a blue section from the texture and move it over to a red section then align it. Do that for all of the lights you want to change to blue. Then go into the ELS file assigned to the vehicle you are working on and change any of the red lighting to blue between the EOVERRIDE tag. Then go into the game and test out the lighting. Just take your time when doing this, and you if you make a mistake just overwrite the ytd with the original (if you saved the zip or made a copy). You can also change the coloring of the spites for headlights, tailights, front indicators, rear indicators, and reverse lights (though blue behind the red taillight looks like garbage) under CARONAS in ELS to blue. SK

Currently this is blacked out in the car once I began driving. As posted in another comment, it can't be fixed in Simple Trainer or in the vehicles.meta file. When I spawn the car in for testing you can see the rear arrow bar, but once I started driving it blacked the windows out (rear drv/pass doors and rear windshield). I'd recommend a lighter tint for those windows. It needn't be clear.

I've enjoyed using the seatbelt plugin since it debuted, and it does what it should. One recommendation is change the F4 key that opens the seatbelt menu. That conflicts with the console window, and most likely will be very annoying to those that want to make adjustments. I do like there are new audio level choices. Unless you knew how to edit the audio files to lower them yourself (which I have and do) the chimes are quite loud. Now there is a 30% and 60% level reduction for all chimes which is fantastic. There are some changes I noticed in the INI file for 1.6.1 (some were removed and some are new) so be sure you copy the settings from your last version to the new one, because overwriting the old will obviously default everything. Great work again Faya! SkittleKicks

It crashes when going on duty. Removing the plugin fixes the issue so it's why I ruled out everything since all plugins are updated and I only use ones for LSPDFR 0.4.9. I also misspoke I am on the latest GTAV release 2944 not 2845 as in my original post.

Hi OJdoesit Through some testing, it now appears that the latest version of RageNativeUI is no longer compatible with Heli Assistant. I'm on GTAV 2845, using RageNativeUI 1.9.2 with a pristine installation of LSPDFR, and the other plugins I used are the most recent. Once forcing duty the console reports that Heli Assistant is what keeps crashing. I verified this by removing the plugin, then reloading all plugins and followed that with ForceDuty. It never crashed again. It shocked me because 1.9.2 is ONLY a minor patch, but I do wonder if something with GTAV 2845 has broken your plugin? No other update did this before.

No problem. We all have to start somewhere. I did notice that when I added the 1.0.3 .dll the file name is different. This time it is TornadoCallout.dll vs TornadosCallout.dll So it won't overwrite the original. Not a big deal, but people will just have to manually delete the older version (or just rename the new file) before launching the game.

This is a great enhancement for the already awesome Callout Interface. This is a mod I HIGHLY recommend for all LSPDFR players (also check the out the rest of the plugins Opus created, they are just as epic). Early on in my tests I had forgotten how to activate the cursor so manipulate the interface (just hold A for a tiny bit and the arrow appears), yeah that's operator error. I know Opus will continue making this plugin even better. And I for one can't wait!!! GRAND SLAM OPUS!!! SkittleKicks

Actually no confusion. Definitely looking forward to the next update. Thank you for your contributions to the the LSPDFR community!

Hey TornadoMac. No big deal. Just wanted to verify that this was indeed the latest one to add. Will there be a future ini file included so we can control which callouts to enable or disable? Oh and one request. Please don't add the bank robbery where the robber is far too OP. Several callouts copied that into theirs, and it is so annoying when a rocket won't even kill him LOL. I usually disable that one.

And for me that's a bit confusing when updating. I guess I would relate the version numbers to reflect that, but that's just me. It's the same issue I've seen with EUP. The OIV version is still 8.3 but it is displayed on the site as version 9x in the title. So one assumes that there has been a version change based on the heading. Imagine if our browsers were version 1.1.0 but the download title says 60.5.1

Just downloaded the folders and zip are correct, but the .dll is still reads 1.0.0.0 in the file properties details.

I'll be sure to try out your callout pack. I have Opus' new Callout Interface in game so it will be nice to see how yours display. SkittleKicks

This is a fun callout. I did find the issue where it was showing older versions. After the update, I had to ReloadAllPlugins vs just going on duty. No idea why that made a difference since this doesn't sit at the root plugin folder. Now that it's working I am thrilled to continue using this.

Don't know if you figured it out or not, but Geoffrey_Gamer did this very mod tutorial and I highly recommend checking it out. He takes you step by step so pay attention and do EXACTLY what he says. https://www.youtube.com/watch?v=01rMBmRzEKs

I've noticed this too. I have no idea why the version number on the LSPDFR page would change but not the actual download names. If there are no changes in the uniforms themselves, or no modification to the OIV then there is no point to changing the version name in the title in my opinion. If that needs to be something, then it should remain an internal to the devs not public. And I 100% agree it's far too confusing to those that use EUP to proclaim it is one version, but in reality ther download itself is not. The only thing I can think of is 9.3.1 is for Patreon contributors, but I have no way of knowing this for certain. I've used EUP for many years, and currently 8.3 seems to be the only OFFICIAL version here on LSPDFR and it's been like that for a while now. SkittleKicks

Hi Ricy. I wanted to offer you some feedback on Police Menu. To be honest it's being updated far too frequently, and frankly not everything requested item has to (or should) be added just because one or two people ask for it. If Police Menu was updated once a month (or 6 weeks per cycle) with a manifest of requested updates that would be fine. As a regular LSPDFR player/YouTube content creator getting notified that yet another update has been released is too much now. It makes it look like there will be higher risks for the mod to break or crash LSPDFR. Due to this, I'm gonna have to stick with Compulite full time. Once Police Menu stabilizes, I'll look at adding into my new LSPDFR build. SKP

You have to run Police Menu once in the game. Once that has been done in the Police Menu folder in plugins/LSPDFR/PoliceMenu/Internal you should see citations and charges xml files (edit those), but make a backup of the default files first. This way if you make a mistake you can revert back to the original ones. SKP

Will do. I did make a error. It is the BALLER2 that is used for the Tahoe and not the Greesley. Sorry about that. SKP

Hey there. Just installed the Charger (non K-9) and Tahoe (K-9). Looking forward creating new video content as a showcase for them. You actually can use the Greesley settings for the Tahoe's handling. It won't flip (this is the one that Emergency Distributors use in their fix files so you could incorporate that into your releases for Tahoe's) when cornering hard. Now it can spin out, but at high speed that is realistic. The liveries look really good too. SKP

Ricy is there anyway to change the pointer icon when hovering of the menu? The middle finger isn't really a good choice. I mean I get it it's supposed to be a funny thing (and personally I don't care), but there are those who might not dig that. SKP

Not a problem. I had a feeling that it might be a bit more complex than I thought to work these changes. The mod is still amazing, and I do appreciate your contribution to the LSPDFR community. SKP

While I was testing the Police Menu computer last night, I was using my scroll wheel to navigate the left side citations bar. Well that apparently enables/disables the airbreak feature. (side note) I have yet to figure out how to remove that entire function from Simple Trainer because it's just useless, and no just deleting the instances of it won't work (nor rebinding of the keys) already tried that. Be aware while using the Police menu Computer. The background image is not transparent and it doesn't pause the game while you are working in it. Which means you can't see what's going on while you are in the computer. Searching for a citation can cause the stopped vehicle to just drive off I noticed (this is due to key binds, which really can't be remapped unless you never use the search citations feature). This then leads to another effect. It will reset the traffic stop details if you try and stop them again (e.g. you stopped the driver initially for suspended license, they get released, and then you stop again this time it's a valid DL.) For the background image, while you could take the background texture (it's in the YTD) into PaintDOTnet and lower the opacity it might have other consequences in the over all appearance, and that still will not pause the game (obviously). That's the thing with Compulite is you can still view what's going on, and since you are not typing it's not going to trigger some random thing like the driver taking off. Probably the best way to design this is make it so that the computer pops up as a window that can be resized (think of a browser window) instead of a static fullscreen background image. This way we can see what is going on, and not lose a stopped vehicle, or a ped leaves. I view this as something that should be addressed before I can really commit to Police Menu full time and retire Compulite. SKP