BF2 Netcode sucks at times [video clip proof]

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • IVfluids

    #16
    Re: BF2 Netcode sucks at times [video clip proof]

    Originally posted by newiq
    Well, calculating and dishing out game-event/voip/recorder packets takes out it's toll on a server. So I think you're right on that part. I don't believe the hit detection is faulty unless PROVEN otherwise. As in a 1vs1 match on a overpowered server with both clients on the same load/lossless LAN trying to shoot eachother when standing still. Not trying to be rude, but this discussion feels like someone with a Ferrari asking why his car is behaving irrationally at 500km/h on a bumpy road.


    So to make it short: Physics+64clients+underpowered hardware = people believing that the netcode is crap.
    Recorder doesn't actually record the footage of the game, it takes samples of player and projectile positions X amount of times per second. When you play it back, it uses that information and your game install basically plays everything back based on that information. Which is the reason why BFR files are small and also the reason you can go and view the replay from different spots in the game.

    Here is just one clip from a site using it for gameplay performance review:
    Battle Recorder. If the server allows it, this records the game and allows playback from any player in a third person camera mode or a roaming camera. Unfortunately this does not allow playback from the first-person perspective. Using a demo from our own Battlefield 2 server with 64 players we played back a file from the Gulf of Oman map using FRAPS to recreate results. As a warning, due to the lack of first-person playback in Battle Recorder the results are not likely to be 100% accurate to real gameplay performance as we couldn't move the camera in order to sure results could be recreated perfectly for our testing.
    I'm trying to find where I read the info on BFR taking samples, it is out there, but that is how it records.

    Comment

    • specter

      #17
      Re: BF2 Netcode sucks at times [video clip proof]

      no crap bf2 has bad netcode

      Comment

      • newiq

        #18
        Re: BF2 Netcode sucks at times [video clip proof]

        Originally posted by specter
        no crap bf2 has bad netcode
        Okay, because of your indepth expertise on this subject and very elaborate explanation why it sucks I assume that you're the developer who wrote the code?

        Comment

        • Leeus

          #19
          Re: BF2 Netcode sucks at times [video clip proof]

          The way I solved this for myself was only to play on servers that are pinging at less than 100. I've put what looks like 5 tank shells into an apc and nothing happened on high pinger.

          Comment

          • =Yes=Overkill

            #20
            Re: BF2 Netcode sucks at times [video clip proof]

            Simply BF2 is combination of bugs and bad netcoding...Strange things are happening way to offten, like when I'm in the chopper (as a pilot or gunner)...flying around...and somebody fires SRAW towards me...I can clearly hear hit and choppers shakes due to impact, but there is no damage to chopper...not that I'm not happy about it but still...

            Comment

            • dommafia
              Member
              • Jun 2007
              • 103

              #21
              Re: BF2 Netcode sucks at times [video clip proof]

              I'm sorry but if the game had bad netcode it would affect EVERYONE and not just some. I've never had problems with hitting a target. I play on servers that ping 50ms or less to me. You have to take into account the system that the server is running on too. They might be running a 64 player server on a machine that cant really handle it.

              If you play on a server with 51ms+ ping then u have to compensate for that lag when u aim at a moving target. It's been this way in every online game i've ever played. There are some games where the hit detection is based on the client side (cnc renegade), which is the stupidest thing in the world as u can easily lag hack to get many kills.

              Comment

              • shiftymoves

                #22
                Re: BF2 Netcode sucks at times [video clip proof]

                :laugh:
                Originally posted by AliasJay
                Tell you what ...dont need proof to know this games coded by people with a community college understanding of programming.
                BaaWAaa. Thats just to funny. You left out the quality control, bunch of stoners. With less than high school! Don't forget, the very FIRST patch!

                Comment

                • Leki
                  Member
                  • Mar 2007
                  • 361

                  #23
                  Re: BF2 Netcode sucks at times [video clip proof]

                  Originally posted by dommafia
                  I'm sorry but if the game had bad netcode it would affect EVERYONE and not just some. I've never had problems with hitting a target. I play on servers that ping 50ms or less to me. You have to take into account the system that the server is running on too. They might be running a 64 player server on a machine that cant really handle it.

                  If you play on a server with 51ms+ ping then u have to compensate for that lag when u aim at a moving target. It's been this way in every online game i've ever played. There are some games where the hit detection is based on the client side (cnc renegade), which is the stupidest thing in the world as u can easily lag hack to get many kills.
                  i only play on decent servers that play ranked 32 player maps and that are close to me and my ping is in the 20 something range. The guy i was shooting at also had a low ping and he was lying down still so nothing to compensate for. If im shooting a guy and i see im hitting him, the battlfield recorder file shows im hitting him and i have had clan mates tell me i was hitting them due to them hearing the sound and seeing the smoke but not taking damage then something is definitely wrong. Just like when firing missiles at a vehicle that isn't moving only to see the missle go right through. The game has problems and if you haven't seen them then you haven't played enough or your not observant enough.

                  Comment

                  • IVfluids

                    #24
                    Re: BF2 Netcode sucks at times [video clip proof]

                    Originally posted by Leki
                    ...clan mates tell me i was hitting them due to them hearing the sound and seeing the smoke but not taking damage then something is definitely wrong...
                    Yah, that is kind of the same thing I was saying about sniping my friend. Only I didn't have any confirmation that I hit him, we were the only two in the server testing gun accuracy on USI mod and he heard and seen the impact detail when he got hit, he didn't take any damage. I'm not sure that is bad netcode or a bug that is serverside, but it was quite the oddity.

                    Comment

                    • specter

                      #25
                      Re: BF2 Netcode sucks at times [video clip proof]

                      Originally posted by newiq
                      Okay, because of your indepth expertise on this subject and very elaborate explanation why it sucks I assume that you're the developer who wrote the code?
                      lols n0 but i do play bf2 sometimes

                      Comment

                      Working...