Announcement

Collapse
No announcement yet.

To Epic: Latest beta overlooks several key issues

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

  • replied
    Bersy - For the record, I haven't experienced any 0 damage bugs while using the 2.0 beta, although it wasn't extremely common before. But the game generally feels a lot smoother online overall, so I would be surprised if it isn't fixed.

    Leave a comment:


  • replied
    nah its not.. its evil forces, i think mantas can stop it...

    Leave a comment:


  • replied
    Here is a list of stuff relevant to the netcode:

    Networking bandwidth use optimizations.
    Improved prioritization of actor replication.
    Improved network pawn position update smoothing using mesh translation.
    Improved dynamic netspeed system based on player counts.
    Don't dynamically adjust listen server client netspeed above max client has requested (for modem clients).

    The most likely key fix being in bold..

    Leave a comment:


  • replied
    Originally posted by Bersy View Post
    Since the netcode has been substantially improved I am guessing you guys will notice fewer of these "0 damage" situations. It would all come about from the client seeing his opponent in one place, appearing to take a hit when he actually hadn't, but in 2.0 pawn position updating has been improved, meaning what you see on screen should be more reliable. I have heard quite a few reports that online matches feel considerably more responsive now, I am willing to bet this will improve people's perception of not only the avril but sniper and shock feel as well..
    Nice

    10chars

    Leave a comment:


  • replied
    Since the netcode has been substantially improved I am guessing you guys will notice fewer of these "0 damage" situations. It would all come about from the client seeing his opponent in one place, appearing to take a hit when he actually hadn't, but in 2.0 pawn position updating has been improved, meaning what you see on screen should be more reliable. I have heard quite a few reports that online matches feel considerably more responsive now, I am willing to bet this will improve people's perception of not only the avril but sniper and shock feel as well..

    Leave a comment:


  • replied
    Originally posted by bclagge View Post
    I assume that's just lag.
    I don't think so, I've been hit full-force in the face by a rocket and not taken any damage. This was in a duel where both of us had pretty good ping; it definitely evoked a "wtf?" from him.

    This bug has been around since UT2004, though I definitely don't think it was as prevalent. Maybe just not as noticeable, considering it appears to be projectile-related and UT2004 was dominated by hitscan.

    Leave a comment:


  • replied
    Originally posted by phalanx View Post
    avril 400 damage bug.. what about the 0 damage bug
    I think someone found the problem was with the netcode so the 0 damage bug should be sorted at the same time.

    Leave a comment:


  • replied
    I assume that's just lag.

    Leave a comment:


  • replied
    avril 400 damage bug.. what about the 0 damage bug

    Leave a comment:


  • replied
    Originally posted by BlueCloud View Post
    My main (unfixed?) gripes are:

    1. Server cpu lag -- All Warfare servers start lagging as player count goes up. Example: 60ms with 10 players, 120ms with 24 players. ONS servers running on the SAME box with 32 players playing don't have this problem, so it's not network lag.

    2. Random damage avrils - Avrils causing 0, 200 or 400 damage randomly. You pickup a deemer on Downtown and get into a scorpion while your prime's taken and your core is being hit. As you try to head towards a safe place, an Avril comes and takes off ALL your 300 points, and you probably couldn't bail out in time because of issue #1 above.

    3. No ingame server browser - Makes it harder to shop around for better servers but not wanting to quit the current game if none are found.

    4 No showing of enemy names like in 2k4 - Knowing who the enemy player is, helps aiming, dodging, weapon selection etc. The demo guy bug exacerbates this by not even allowing one to identify people by their skin.

    The demo guy bug is fixed. I don't know if the server cpu lag is fixed. There are a lot more issues, of course. But those are my main gripes keeping me from enjoying the game.
    Thanks Epic for fixing the 400 Damage Avril in the latest beta of Patch 2.0! #2 off the list!! And I think #4 is fixed too?

    Leave a comment:


  • replied
    Originally posted by HideInLight View Post
    People making extremely long names to obscure peoples' vision
    I believe the game scales down the font to make it all fit on the standard size "billboard".

    Leave a comment:


  • replied
    Originally posted by tqz View Post
    I agree, FOV >100 is absolutely necessary.
    Absolutely! Epic please?

    Originally posted by HideInLight View Post
    that calculator suggest me to have a fov of 110
    and look at that, its just he fov i like to play with!

    Why not use the freefov mutator? Its not allowed in some official matches.

    Leave a comment:


  • replied
    Originally posted by hypno View Post
    it's not giving sounds for armor pickups/weapons/etc, that must be fixed.
    Wow, that's pretty much worse than all the other things I listed combined. Considering I only duel nowdays, if that doesn't get fixed I probably won't be playing much UT3 regardless of other fixes. Have you reported this to Epic?

    Leave a comment:


  • replied
    I've just tryed the beta patch 2, I was quite happy with the demo playback improvement, would be awesome if you could add UI control, there's still a problem with the sounds tho, it's not giving sounds for armor pickups/weapons/etc, that must be fixed. Besides that I haven't tryed anything else, since there aren't many server with beta patch 2 at all

    Leave a comment:


  • replied
    Na it should definitely just be an option, because it's useful to know who you're fighting, so you can adjust your style accordingly. At the very least, use small text and only display a name when your crosshair is REALLY close to the player, a la UT2004. Haven't tried beta 2 yet, so I can't say how well it's implemented.

    Leave a comment:

Working...
X