bravozero

I took over the Polpatriot slot with my favorite CVPI because of the handling modifications I made, the car almost rides on rails. So, whenever I call for NOOSE support it always spawns my CVPI. However, I want it to spawn the standard NOOSE cruiser instead of the Police Patriot slot. Is there a way I can remove the Polpatriot from the list of AI-spawnable cars?

Very cool.

Ooooo... very interested in knowing the results of this.

I like how people can come into this thread and say "this sucks" or "this is a fail". I'd like to see you folks try and create a piece of programming that works better. This is very difficult to create and I commend everyone that makes mods for this game.

RIP brother.

Try SaviorENB. There shouldn't be any issues with that one. If there are, then a Timecycle mod might be your only option.

Beautiful Interceptors, can't wait to try them out once they're released!

I had the bouncing problem with one of the DSF Taurus models, yet I contacted the modeler and he said its something on my end and not the car, despite me changing every setting possible. Every other car I've used seems to be fine.

I'm still getting freeze-ups with the latest version. Someone mentioned updating scripthook, advancehook and dsound to help with the freezes. Anyone know where I can find these?

Can you give me an example of how the LOD should be set up and where I'd find it?

My only grip about ELS, aside from the "god mode" bug, is the fact that you can't see the lights from far off, just the reflections onto the environment. Whereas with the stock non-ELS vehicles, you can see the red/white coronas at least two-three times the distance compared to ELS. That, to me, is another realism issue. With today's LED lightbars, you can see them from a great distance away. With ELS, I can't go more than 50 feet away from my cruiser and not be able to see the lights, and this is running a high-end system with view distance and everything turned up.

I've seen the AI not use the lights with the standard non-ELS vehicles in the game, so it's a programming issue with the game it seems.

I've played the main story so many times, so I have the ELFC pack and save the other two stories for legit playing and use the main game for LCPDFR.

I am currently using NickieB's X2100 CVPI and it looks much better when the primary and secondary lights are activated at the same time. However, I have my mouse buttons mapped through SetPoint so that I can activate the primary lights with one of the side buttons, the siren with the other. However, I cannot configure SetPoint to utilize two normal keys at the same time on one button. Has anyone else been able to accomplish something like this?

^ +1, SaviorENB is awesome.

I've been using Savior ENB and it's nice. Dark areas are actually dark, more realistic.

I've been using the Automatic license plate reader v1.5 for a while now, and just recently I experiemented with having the script loaded and trying it without. I've come to realize that with the script loaded, it actually causes the game to run slightly sluggish, as opposed to running the game without it. Anyone else notice this?

Just tried the newest version... holy crap, LCPDFR is a lot more fun to play now. Thank you very much for developing this mod!

Another break-through... got the game running smoothly now. After researching FXAA and how it smooths out the graphics with a minimal performance hit compared to MSAA, I enabled it in the NV Control Panel, and now I'm getting almost constant 50-60 fps (I have a system limit of 60fps due to screen tearing) throughout the game even with ELS enabled, and it looks much better than the in-game MSAA options.

Figured out the problem. I disabled PrecisionX and ran the game (same setup as before... LCPDFR, ENB, ELS, mods/scripts). Loaded and despite being sluggish, it actually ran. Re-enabled PrecisionX, gave me the d3d9.dll error. So, now I have to see if it's the actual PrecX program or another sub-process that's enabled in the program that's causing an issue. EDIT: The process "RTSS.exe" (associated with PrecisionX) is causing the d3d9.dll error, I have the game running as I type this with PrecisionX also running, for FPS limitation and fan control for the GTX670. Hopefully now it continues to run, I'll further configure the graphics until it's running smoothly.

Here's the thing... The game worked almost perfectly before. I had LCPDFR, an ENB, ELS and a bunch of scripts and mods, other than the occasional ELS crash I never had issue. Ever since I reinstalled Windows and this new card, I've had all sorts of problems with the game. Plus, it was running yesterday and all of the sudden it's having issues with this d3d9 file. All I want is for it to work, I can figure out the other graphics issues later.

Removed the existing ENB, ran the game "vanilla" and it was fine. Installed a different ENB and I'm back to having the same problem. I didn't have DX9 installed, so I decided to install it, rebooted and still having the same problem. So it's not DX related I don't think. I'm about to give up on this game.