proof that DICE has decreased/screwed the draw distance

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Dr-X

    #61
    Re: proof that DICE has decreased/screwed the draw distance

    This is clearly a LOD issue. Try adjusting your AF settings.

    Comment

    • Drevor

      #62
      Re: proof that DICE has decreased/screwed the draw distance

      Originally posted by Dr-X
      This is clearly a LOD issue. Try adjusting your AF settings.
      ... and disable neg LoD clamp

      Comment

      • A$$a$$ination

        #63
        Re: proof that DICE has decreased/screwed the draw distance

        but what does that have to do with draw distance

        Comment

        • A$$a$$ination

          #64
          Re: proof that DICE has decreased/screwed the draw distance

          ^sorry disregard that

          Comment

          • exocet

            #65
            Re: proof that DICE has decreased/screwed the draw distance

            View Distance != Level of Detail.

            Comment

            • Drevor

              #66
              Re: proof that DICE has decreased/screwed the draw distance

              Originally posted by exocet
              View Distance != Level of Detail.
              thats what Im trying to tell those guys for the last 5 pages

              Comment

              • Talus
                Member
                • Oct 2006
                • 6854

                #67
                Re: proof that DICE has decreased/screwed the draw distance

                Changing LOD clamp didn't seem to fix the problem.

                Choices are:
                -Allow
                -Clamp

                (which should I choose?)

                What do you suggest we do with AF to help?

                Reduce in-game AF?
                Mess with nVidia control panel AF?

                Comment

                • imported_xRandoMx

                  #68
                  Re: proof that DICE has decreased/screwed the draw distance

                  While this particular problem isn't draw distance, it does look like an annoying glitch.

                  I do think they've reduced the draw distance by moving the 'fog' closer in to the player. The place I've noticed it most was on karkand, I was laying behind the train tracks, sniping over the canal. The first flag there, the top of the wall was fogged? wtf, lol. I used to be able to see(and shoot) that far no problem. I also noticed on sharqi, when in the copters, the fog is really bad over the city now, I have to get quite a bit closer to see an enemy copter now.

                  Comment

                  • imported_Wasp

                    #69
                    Re: proof that DICE has decreased/screwed the draw distance

                    View distance is different depending on what objects you are talking about and if you are zoomed in or not. Can't say I have noticed any difference in how far I can see on the maps but it's possible that some objects show up later than they did before. Missing textures can be caused by both drivers and the game. With my ATI card using Cat 5.8 a small temple in Fushe pass was missing it's texture in 1.02.

                    The level of detail or clarity that you see on textures at a distance of say 20-30 meters is determined by the filtering of your graphic card. Unless the fog is very close like Shongua. Nvidia cards when running the default setting of quality uses optimations that seeme to make clarity of textures drop pretty fast at a distance. Increasing to high quality is suppose to turn these optimations off.

                    I run my ATI card at high quality settings on texture and mipmap detail. BTW pixels are used to draw the picture on your monitor. No matter what the engine does to prevent the game from running at 1 FPS it's not by reducing the number of pixels at a distance.

                    Comment

                    • NoSoup4You

                      #70
                      Re: proof that DICE has decreased/screwed the draw distance

                      But if you look at the view distance it is actually FURTHER in 1.03. Look you can see the mountains in the "reverse" camera angle in 1.03 but not in 1.02.

                      Comment

                      • Talus
                        Member
                        • Oct 2006
                        • 6854

                        #71
                        Re: proof that DICE has decreased/screwed the draw distance

                        Hrmm...still no useful fix proposed yet

                        Comment

                        • Talus
                          Member
                          • Oct 2006
                          • 6854

                          #72
                          Re: proof that DICE has decreased/screwed the draw distance

                          Anybody figured anything more out about this yet?

                          Comment

                          • Talus
                            Member
                            • Oct 2006
                            • 6854

                            #73
                            Re: proof that DICE has decreased/screwed the draw distance

                            I will NOT let this thread die...somebody is BOUND to find a tweak or fix for this ...

                            Maybe this thread belongs in Bug Reports or Client Support?

                            Comment

                            • DLWebmaestro96

                              #74
                              Re: proof that DICE has decreased/screwed the draw distance

                              I always found it amusing that you can see the afterburners through the hanger and jet when using 3rd-person view.

                              Comment

                              • glasseye

                                #75
                                Re: proof that DICE has decreased/screwed the draw distance

                                Originally posted by Talus
                                I will NOT let this thread die...somebody is BOUND to find a tweak or fix for this ...

                                Maybe this thread belongs in Bug Reports or Client Support?
                                if you really want an answer you have to remake the thread. the dodgy title just confuses them.

                                Comment

                                Working...