Hello everyone sorry if this is in the wrong area or there is already a post about this (this is my first time posting)

 

I was playing LSPDFR .4 with radiance V and Redux installed and noticed that when I went on duty I started to experience really bad missing/blurry textures that I wasn't experiencing while off duty here are the steps on how I managed to fix this problem.

 

1. Open up your main GTA V directory and click on the LSPDFR folder 

 

2. Open the lspdfr.ini and make sure  Main.PreloadAllModels is set to false, once that's done save and close it.

 

That's it, you can now start GTA up again and head back on patrol (this time without any texture loss)

now what exactly does that setting do ? 

 

what are we taking away experience wise ? 

I tried this and it still was losing textures, so is there any other way to keep away from losing textures???

3 hours ago, MDC2005VIPER said:

I tried this and it still was losing textures, so is there any other way to keep away from losing textures???

Agreed, game running very smooth with massive texture loss even with the most recent gameconfig.

Bro, you are the best, you solved all my problems, now my LSPDFR 0.4 works perfectly, thank you very much!

Edited March 4, 20197 yr by noobcrafting

I'm so surprised that it actually worked. Now I can finally see the road when I'm on a chase. Though there are still some missing textures but they are extremely rare, unlike what it used to be(there's no road that could be seen). Thank you very much. And I experienced about 5-10 fps increase in the wild and 1-5 fps gain in the city. Don't know if it's related but it sure fixes the texture issue. Thanks bud.

Not really help, still have this problem with my 2080Ti... Now I am thinking it is a problem with my GPU.

7 hours ago, babibada said:

Not really help, still have this problem with my 2080Ti... Now I am thinking it is a problem with my GPU.

Not a GPU problem, I can assure you. 

On 3/3/2019 at 2:53 PM, MDC2005VIPER said:

I tried this and it still was losing textures, so is there any other way to keep away from losing textures???

Same here, I actually have like 4 or 5 other lines I was told to put in that systematically disables half of lspdfr 0.4 from ambient crimes to ambient police, anything to "free up" resources for lspdfr to use - I still get SEVERE texture loss in paleto, texture loss after 10 minutes of play in Sandy, and texture loss after 15-25 minutes in los santos, as well as ANYTHING remotely stressful on the game and vehicle models will decrease in LOD right in front of you, from interior assets like steering wheels turning invisible to exterior issues like someone dumped chrome on your car. 

This may work for some people but not for everyone, and the fact that everywhere you turn for help and still get this solution is not only redundant but frankly a bit irritating if this is ALL you can find. We need a PERMANENT fix to this that either doesn't disable half of lspdfr 0.4 or finds a way to make it use less resources on our systems so this texture loss crap doesn't happen. 

I have similar issues... I turned off the preload, which helped a lot, but I still start losing textures after about 10 minutes

The only other thing that seems to help, is reducing the amount of add-on cars and high-poly cars. I had about 20+ cars and my game would be unplayable almost immediately after going on duty. After I cut it down to about 10, it still does it, but it's after 30-ish minutes.

On 3/7/2019 at 7:38 AM, SamuelOlson1701 said:

Not a GPU problem, I can assure you. 

Same here, I actually have like 4 or 5 other lines I was told to put in that systematically disables half of lspdfr 0.4 from ambient crimes to ambient police, anything to "free up" resources for lspdfr to use - I still get SEVERE texture loss in paleto, texture loss after 10 minutes of play in Sandy, and texture loss after 15-25 minutes in los santos, as well as ANYTHING remotely stressful on the game and vehicle models will decrease in LOD right in front of you, from interior assets like steering wheels turning invisible to exterior issues like someone dumped chrome on your car. 

This may work for some people but not for everyone, and the fact that everywhere you turn for help and still get this solution is not only redundant but frankly a bit irritating if this is ALL you can find. We need a PERMANENT fix to this that either doesn't disable half of lspdfr 0.4 or finds a way to make it use less resources on our systems so this texture loss crap doesn't happen. 

I honestly don't see them fixing this sadly. as soon as I go on duty I can only play for about two minutes.. I have six vehicles, all with 2k textures.... yeah.

 

On 3/7/2019 at 7:38 AM, SamuelOlson1701 said:

Not a GPU problem, I can assure you. 

Same here, I actually have like 4 or 5 other lines I was told to put in that systematically disables half of lspdfr 0.4 from ambient crimes to ambient police, anything to "free up" resources for lspdfr to use - I still get SEVERE texture loss in paleto, texture loss after 10 minutes of play in Sandy, and texture loss after 15-25 minutes in los santos, as well as ANYTHING remotely stressful on the game and vehicle models will decrease in LOD right in front of you, from interior assets like steering wheels turning invisible to exterior issues like someone dumped chrome on your car. 

This may work for some people but not for everyone, and the fact that everywhere you turn for help and still get this solution is not only redundant but frankly a bit irritating if this is ALL you can find. We need a PERMANENT fix to this that either doesn't disable half of lspdfr 0.4 or finds a way to make it use less resources on our systems so this texture loss crap doesn't happen. 

I'm hoping a modder on the website will devise a fix for this soon

I have similar issues . I have turned off the preload , but still start losing textures.

 

Please devise.

I have this problem too. brand new PC with : intel i9, 32 GB Ram and 2080, NVIDIA GEFORCE RTX 2070. 

All the correct settings in LSPDFR .ini and all textures in 2k.

 

Please do something to fix it... 😞

 

I Have the same BAD texture issues :(..I turned off the preload  but stil the same.

 

LSPDFR 0.4 is really unplayable at this time for me!

I turned off preloads last night and experienced massive texture loss for the first time ever.  Turning it back on.

Hi! It looks like I found out what caused my Texture problem. I deleted a bunch of my Addon Cars, played for like an hour, and no more texture loss!

Here is what I use for the moment:

 

- gameconfig with 1x traffic 1xpeds (Means Gta base)

- 1 Addon Car as a DLC

- medic4523's Fire/EMS pack (also a DLC)

- police, police2, police3, police4, sheriff and sheriff2 in patchday20

 

I am not sure if the amount of cars caused this problem or if it was a specific car (too high polygons maybe). I'll keep on trying to add cars and eventually find out where my Limit is.

I hope this helps your Problem as well.

Edited March 13, 20197 yr by Spike O'Hara

I managed to fix my texture loss by lowering all vehicles from 4k to 2k, using gameconfig with .5peds .5 traffic and lowering my textures to normal.. Played for over 2 hours and no texture issues.. 

 

This new 0.4 is very demanding. 

That did not solve my problem.It worked fine for a few days.Today nothing but texture loss.No changes were made!

 

Edited March 15, 20197 yr by billiarboy

8 hours ago, billiarboy said:

That did not solve my problem.It worked fine for a few days.Today nothing but texture loss.No changes were made!

 

 

You need to keep lowering the texture sizes in the custom vehicle files (The skin is a good start, but you can lower the size of other textures as well), or ditch unnecessary custom vehicles, until you find a balance that works.

5 hours ago, zach016 said:

 

You need to keep lowering the texture sizes in the custom vehicle files (The skin is a good start, but you can lower the size of other textures as well), or ditch unnecessary custom vehicles, until you find a balance that works.

What a pain in the ass.

I do not know how to lower the size!

 

Fixed 0.4.1 the issue for anyone?