pixelated shadows Pixelated Shadows,Texture Pop Ins,Low Draw Distance in all games

[App4that]

13 minutes ago, SpeedUp10 said:

sadly he will not understand that  , our problem is something completly diffrent from what he is thinking.

Other than a fondness for pitty parties, what specific problem? 

[SpeedUp10]

12 minutes ago, App4that said:

Other than a fondness for pitty parties, what specific problem? 

Why u always reply on me man, here are enough people saying the same reply on them.

I cant tell you why, i cant tell you how, i cant tell you that. All I know is what I see.

My friend comes up again with his Amd card, if its happen again to fix it temporaly I will record It and can show side by side.

[App4that]

2 minutes ago, SpeedUp10 said:

Why u always reply on me man, here are enough people saying the same reply on them.

I cant tell you why, i cant tell you how, i cant tell you that. All I know is what I see.

My friend comes up again with his Amd card, if its happen again to fix it temporaly I will record It and can show side by side.

So you don't know what's happening, but it's bad? That's why I'm replying to you. If you want your problem solved then let's get it solved for you. But first you have to HAVE a problem, not just a feeling.

[SpeedUp10]

4 minutes ago, App4that said:

So you don't know what's happening, but it's bad? That's why I'm replying to you. If you want your problem solved then let's get it solved for you. But first you have to HAVE a problem, not just a feeling.

Can you read for one time what im writing? " I cant tell you why, i cant tell you how, i cant tell you that " // What the problem does were explained several times. U cant read I guess. God "feeling" are you fking kidding me? You think I waste 4 months of time for a simple "feeling"? Please read or stfu .

You think anybody waste months/years for just a "feeling" man I feel like u never gamed well.

[App4that]

4 minutes ago, SpeedUp10 said:

Can you read for one time what im writing? " I cant tell you why, i cant tell you how, i cant tell you that " // What the problem does were explained several times. U cant read I guess. God "feeling" are you fking kidding me? You think I waste 4 months of time for a simple "feeling"? Please read or stfu .

You think anybody waste months/years for just a "feeling" man I feel like u never gamed well.

If you were that tenasious you wouldn't give up and value having a problem more than fixing it, which is what this is about. 

 

Give us everything, every last detail on what happens, when it happens, and even where it happens. 

 

 

[TalosXT]

So guys, here's an update after a week of researching:

 

First of all thanks for those who submitted the D3D AF Tester results. I also grabbed some off of internet to see it running on different cards.

 

Second of all, It appears all of us are facing different issues here. Similar symptoms but different kind of problem. But the funny part is that all the problems are affecting LoD Bias and ultimately messing with draw distance.

 

I fixed Witcher 3 a few days ago by forcing nvidia inspector to turn off LoD bias Driver Control, meaning I gave all the LoD calculation responsibility to the Witcher 3's engine. IT FIXED IT (except the CSMs). This means that the game engine is doing it's job correctly however the GPU was interfering with it, and instead of aiding the game in the LoD calculations, it messed it up resulting in shimmering, flickering, Alaising and ultimately CSMs. Now in order to prove the theory, I installed Stonghold Crusader 2 (2014) which uses a cheap engine that rests on Hardware based post processing. The problems were back again.

 

Now why do I think it's different for everybody? This is where D3D AF tester comes in play. let's look at @Zemzemma's. As you can see, the hardware based Anisotropic Filter is smoothing the beginning of the tunnel but as it progresses through it appears as it is warped horizontally. even though the LoD bias is set to -8, the filter is clamping it to 0 (transition from smooth to jagged) but beyond that it can not process. That should not be happening. for me it's a different case. the filter is allowing the the negative bias to pass through even though I've forced it to to clamp to 0. *** NOW this can be because of many different reasons. These LoD problems have DIFFERENT sources and are yielding DIFFERENT RESULTS. But ONE THING COMMON between the results is that it's messing with the draw distance calculations.

 

I'm willing to bet my money that this is the root to all of our problems. I will try to continue researching even though I may not have enough time since I'm a student but ONE thing i'm damned sure of is  that there is NO MAGICAL SOLUTION for everyone. Some people can fix it with driver's install, Some with UPS Stabilizer, Some with building a new PC, or some with neither. This is why we can't get to a solid solution for years.

 

@iiNNeX The problem that you're facing is similar to CSM. It's hard to tell since it's a top down camera but that's because the LoD bias cannot tell how accurately to draw the pixels so the computer is making a safe assumption that the shadow is very far and renders it in low quality (AKA realtime low rez Lightmap bakes). It make's it better when the game is dynamically lit (games with a day night system). Have you tried forcing the driver to stop calculating the LoD bias and let the engine do it? (If the engine has that option built in).

[SpeedUp10]

3 minutes ago, App4that said:

If you were that tenasious you wouldn't give up and value having a problem more than fixing it, which is what this is about. 

 

Give us everything, every last detail on what happens, when it happens, and even where it happens. 

 

 

Oh man u literally just jumped in here without reading. I will tell u that tommorrow as I go to sleep now.

For now u can read the Nvidia Thread or this if u go some pages back.

[SpeedUp10]

9 minutes ago, ElijahDar said:

So guys, here's an update after a week of researching:

 

First of all thanks for those who submitted the D3D AF Tester results. I also grabbed some off of internet to see it running on different cards.

 

Second of all, It appears all of us are facing different issues here. Similar symptoms but different kind of problem. But the funny part is that all the problems are affecting LoD Bias and ultimately messing with draw distance.

 

I fixed Witcher 3 a few days ago by forcing nvidia inspector to turn off LoD bias control, meaning I gave all the LoD calculation responsibility to the Witcher 3's engine. IT FIXED IT (except the CSMs). This means that the game engine is doing it's job correctly however the GPU was interfering with it, and instead of aiding the game in the LoD calculations, it messed it up resulting in shimmering, flickering, Alaising and ultimately CSMs. Now in order to prove the theory, I installed Stonghold Crusader 2 (2014) which uses a cheap engine that rests on Hardware based post processing. The problems were back again.

 

Now why do I think it's different for everybody? This is where D3D AF tester comes in play. let's look at @Zemzemma's. As you can see, the hardware based Anisotropic Filter is smoothing the beginning of the tunnel but as it progresses through it appears as it is warped horizontally. even though the LoD bias is set to -8, the filter is clamping it to 0 (transition from smooth to jagged) but beyond that it can not process. That should not be happening. for me it's a different case. the filter is allowing the the negative bias to pass through even though I've forced it to to clamp to 0. *** NOW this can be because of many different reasons. These LoD problems have DIFFERENT sources and are yielding DIFFERENT RESULTS. But ONE THING COMMON between the results is that it's messing with the draw distance calculations.

 

I'm willing to bet my money that this is the root to all of our problems. I will try to continue researching even though I may not have enough time since I'm a student but ONE thing i'm damned sure of is  that there is NO MAGICAL SOLUTION for everyone. Some people can fix it with driver's install, Some with UPS Stabilizer, Some with building a new PC, or some with neither. This is why we can't get to a solid solution for years.

 

@iiNNeX The problem that you're facing is similar to CSM. It's hard to tell since it's a top down camera but that's because the LoD bias cannot tell how accurately to draw the pixels so the computer is making a safe assumption that the shadow is very far and renders it in low quality (AKA realtime low rez Lightmap bakes). It make's it better when the game is dynamically lit (games with a day night system). Have you tried forcing the driver to stop calculating the LoD bias and let the engine do it? (If the engine has that option built in).

I can do that LOD Bias test tommorrow, as it may help us.

[john j rambo]

i hope someone find a real fix this annoying

[KenjiD5]

Hello Motherfloppers... is this flopping issue flopping fake for you you motherfuckers? huh? you think we are fucking with you? the guy who dont have these problems.. answer me!! do you think we are here just to troll you guys... we dont need your message "The problem never exist" or "This is just how the game works" or sometimes we dont want to pick a fight with you.. were here to get some solution not some ass prick who will say this issue never exist.... now if you dont have this problem go away.. this problem exist.. why are we having pixelated shadows,reflections,anti aliasing and low draw distance?? why?? i downloaded normal ini files for the games... and it doesnt do anything.. now tell us why are we having jagged shadows,reflections,anti aliasing and low draw distance? tell us you prick.. 

 

also dont remove this moderators

im just saying something

[aandredor]

People , this is a problem and  "." There are too many having same situation ,and too many that made a compare for their system with one that worked . I can see the difference in ps4 for AA in trees and I know how AA looks , but my pc should run better than my ps4 and it doesn't.   

 

Now , this is my opinion : I don't believe it's a virus but I believe it has to do with drivers, arhitecture of chipsets, compatibility, amd, nvidia, microsoft and money (aka 4k-5k and powerful cards ) . At this moment I tgink game developers had no choice but to lower distance for LOD as a gpu would be a lot more loaded for 4k content . 4k brings more money, more expensive gpu, etc .

 

I'm sure companies know about LOD but is confidencial and nothing can force them to make it public . They hope probably to have it passed in 5 years with the new technology that we will buy . 

[SpeedUp10]

35 minutes ago, aandredor said:

People , this is a problem and  "." There are too many having same situation ,and too many that made a compare for their system with one that worked . I can see the difference in ps4 for AA in trees and I know how AA looks , but my pc should run better than my ps4 and it doesn't.   

 

Now , this is my opinion : I don't believe it's a virus but I believe it has to do with drivers, arhitecture of chipsets, compatibility, amd, nvidia, microsoft and money (aka 4k-5k and powerful cards ) . At this moment I tgink game developers had no choice but to lower distance for LOD as a gpu would be a lot more loaded for 4k content . 4k brings more money, more expensive gpu, etc .

 

I'm sure companies know about LOD but is confidencial and nothing can force them to make it public . They hope probably to have it passed in 5 years with the new technology that we will buy . 

No... what randomly happened to us is not normal or intentionally did. Its just a fking bug/virus or whatever u call it. And its doesnt matter what kind of PC u have 5k PC or 300 euro PC It will be the fking same. I belive Its somehow LOD Bias related as ElijahDar said. But what is causing that to happen and why not everyone etc etc. We have to keep on work on this LOD Bias theory.

[SpeedUp10]

11 hours ago, ElijahDar said:

So guys, here's an update after a week of researching:

 

First of all thanks for those who submitted the D3D AF Tester results. I also grabbed some off of internet to see it running on different cards.

 

Second of all, It appears all of us are facing different issues here. Similar symptoms but different kind of problem. But the funny part is that all the problems are affecting LoD Bias and ultimately messing with draw distance.

 

I fixed Witcher 3 a few days ago by forcing nvidia inspector to turn off LoD bias Driver Control, meaning I gave all the LoD calculation responsibility to the Witcher 3's engine. IT FIXED IT (except the CSMs). This means that the game engine is doing it's job correctly however the GPU was interfering with it, and instead of aiding the game in the LoD calculations, it messed it up resulting in shimmering, flickering, Alaising and ultimately CSMs. Now in order to prove the theory, I installed Stonghold Crusader 2 (2014) which uses a cheap engine that rests on Hardware based post processing. The problems were back again.

 

Now why do I think it's different for everybody? This is where D3D AF tester comes in play. let's look at @Zemzemma's. As you can see, the hardware based Anisotropic Filter is smoothing the beginning of the tunnel but as it progresses through it appears as it is warped horizontally. even though the LoD bias is set to -8, the filter is clamping it to 0 (transition from smooth to jagged) but beyond that it can not process. That should not be happening. for me it's a different case. the filter is allowing the the negative bias to pass through even though I've forced it to to clamp to 0. *** NOW this can be because of many different reasons. These LoD problems have DIFFERENT sources and are yielding DIFFERENT RESULTS. But ONE THING COMMON between the results is that it's messing with the draw distance calculations.

 

I'm willing to bet my money that this is the root to all of our problems. I will try to continue researching even though I may not have enough time since I'm a student but ONE thing i'm damned sure of is  that there is NO MAGICAL SOLUTION for everyone. Some people can fix it with driver's install, Some with UPS Stabilizer, Some with building a new PC, or some with neither. This is why we can't get to a solid solution for years.

 

@iiNNeX The problem that you're facing is similar to CSM. It's hard to tell since it's a top down camera but that's because the LoD bias cannot tell how accurately to draw the pixels so the computer is making a safe assumption that the shadow is very far and renders it in low quality (AKA realtime low rez Lightmap bakes). It make's it better when the game is dynamically lit (games with a day night system). Have you tried forcing the driver to stop calculating the LoD bias and let the engine do it? (If the engine has that option built in).

This is what I get with LOD BIAS -8 , and the other one is after I pressed Start. I dont know why It doubled the Png.

[KenjiD5]

so im one motherflopper.. i deleted nvidia files(gpu driver) and amd files(cpu driver) and that means i deleted some of the driver files now i cant do anything with any nvidia programs or amd programs... am i dead?

[KenjiD5]

oh no i been warned  because of my harsh words or sentences

 

anyway dudes where is the solution??  

[BuckGup]

13 hours ago, ElijahDar said:

So guys, here's an update after a week of researching:

 

First of all thanks for those who submitted the D3D AF Tester results. I also grabbed some off of internet to see it running on different cards.

 

Second of all, It appears all of us are facing different issues here. Similar symptoms but different kind of problem. But the funny part is that all the problems are affecting LoD Bias and ultimately messing with draw distance.

 

I fixed Witcher 3 a few days ago by forcing nvidia inspector to turn off LoD bias Driver Control, meaning I gave all the LoD calculation responsibility to the Witcher 3's engine. IT FIXED IT (except the CSMs). This means that the game engine is doing it's job correctly however the GPU was interfering with it, and instead of aiding the game in the LoD calculations, it messed it up resulting in shimmering, flickering, Alaising and ultimately CSMs. Now in order to prove the theory, I installed Stonghold Crusader 2 (2014) which uses a cheap engine that rests on Hardware based post processing. The problems were back again.

 

Now why do I think it's different for everybody? This is where D3D AF tester comes in play. let's look at @Zemzemma's. As you can see, the hardware based Anisotropic Filter is smoothing the beginning of the tunnel but as it progresses through it appears as it is warped horizontally. even though the LoD bias is set to -8, the filter is clamping it to 0 (transition from smooth to jagged) but beyond that it can not process. That should not be happening. for me it's a different case. the filter is allowing the the negative bias to pass through even though I've forced it to to clamp to 0. *** NOW this can be because of many different reasons. These LoD problems have DIFFERENT sources and are yielding DIFFERENT RESULTS. But ONE THING COMMON between the results is that it's messing with the draw distance calculations.

 

I'm willing to bet my money that this is the root to all of our problems. I will try to continue researching even though I may not have enough time since I'm a student but ONE thing i'm damned sure of is  that there is NO MAGICAL SOLUTION for everyone. Some people can fix it with driver's install, Some with UPS Stabilizer, Some with building a new PC, or some with neither. This is why we can't get to a solid solution for years.

 

@iiNNeX The problem that you're facing is similar to CSM. It's hard to tell since it's a top down camera but that's because the LoD bias cannot tell how accurately to draw the pixels so the computer is making a safe assumption that the shadow is very far and renders it in low quality (AKA realtime low rez Lightmap bakes). It make's it better when the game is dynamically lit (games with a day night system). Have you tried forcing the driver to stop calculating the LoD bias and let the engine do it? (If the engine has that option built in).

This. Thanks you. Someone who doesn't just say. Yeah I see this stuff and you can't but I see it. Just random stuff. This is logical

[KenjiD5]

Hello i am watching too many videos of call of duty ghosts,total war and other indie games and i see pixelated shadows... i think we have to come to conclusion (not really) that the jagged shadows are really normal right now or we have to come to conclusion we are all or everyone is having this problem

[SpeedUp10]

4 minutes ago, SamStrecker said:

This. Thanks you. Someone who doesn't just say. Yeah I see this stuff and you can't but I see it. Just random stuff. This is logical

The point is noone can explain It like u want is, nobody ever experienced these kind of problems, Its hard to prove something that u cant even explain and reproduce. So at the end im pretty sure this LOD Bias is a very plausibel reason why this happen. So now what? Can you help us now?

[KenjiD5]

Hello, this is our solution list

 

SOLUTIONS:

 

1. Ups + Stabilizer - we discovered this "solution" from a youtube comments and we cant just trust them but if this is really something about the electricity then it this might solve our issue

 

2. SSD/HDD - even though we know this wont work and this only have a 0.1% possibility that might fix these issues but i think this will fix the low draw distance or the low rendering system we are facing right now or if not then just for speeding up games

 

3. New PC PARTS - i know some of you have done getting a new pc but no luck.. but this might do for some people

 

4.New House, New Location - im possibly sure this is a SOLUTION! i heard people going out of town and bringing their pc's with them... i know it sounds weird or sh*t but it is not the point here.. it means this is a electricity problem.. i mean the wiring in our house must be damaged or some sh*t... there is a possible little chance that this might not work and that means it is occuring because of the hardware.. but im sure this do but hell nah i dont have the money to buy a rest house or a new house

 

5.Buying completely new pc and new room in your house - this might do and if doesnt then the thing is this is really a electricity problem..

 

I think this is a little help for all of y'all.. thanks BROFIST 

[BuckGup]

31 minutes ago, SpeedUp10 said:

The point is noone can explain It like u want is, nobody ever experienced these kind of problems, Its hard to prove something that u cant even explain and reproduce. So at the end im pretty sure this LOD Bias is a very plausibel reason why this happen. So now what? Can you help us now?

I need a side by side image of the "problem" and the not problem. Once I see it I will agree for now you still sound like mad men

[KenjiD5]

6 minutes ago, SamStrecker said:

I need a side by side image of the "problem" and the not problem. Once I see it I will agree for now you still sound like mad men

dude... we cant.. we cant take picture of aliasing you know that.. we can take picture of pixelated shadows and low draw distance if you want but not jaggies which is the big case for us

[BuckGup]

2 minutes ago, KenjiD5 said:

dude... we cant.. we cant take picture of aliasing you know that.. we can take picture of pixelated shadows and low draw distance if you want but not jaggies which is the big case for us

Use a phone or something. Anything will help understand the problem

[KenjiD5]

2 minutes ago, SamStrecker said:

Use a phone or something. Anything will help understand the problem

here i show you my videos 

 

 

[KenjiD5]

here is from a other guy who is experiencing the same issue like us.. just look at the window edges

 

[BuckGup]

5 minutes ago, KenjiD5 said:

here is from a other guy who is experiencing the same issue like us.. just look at the window edges

 

I can tell you this one is normal. It happens when a texture doesn't fully wrap the object. 

5 minutes ago, KenjiD5 said:

here i show you my videos 

 

 

I now get what you mean by the jagged edges. Gives it a shimmering look. As for draw distance what GPU do you have?