Forum Rules

  • Items changed, or highlighted for future attention, on 20 July 2013 are highlighted in yellow.
Global Rules
  • Forum moderators may or may not be Tripwire Interactive staff members, but either way, please respect them, as they are the authority of the forums. Speaking to them with intentional spite will not be tolerated and may result in the loss of your forum privileges.
  • Any decisions made by any member of staff or moderator are final and not subject to discussion. Doing so may result in a ban from the site. The owners of Tripwire Interactive Forums reserve the right to remove, edit, move or close any thread for any reason, as well as to remove access to the forums for any individuals with or without warning for breaches of the rules.
  • If you have a complaint regarding another user, PM the appropriate moderators, or if you have an administrative issue, [RO]schneidzekk.
General Behaviour
  • Use the search function before posting. Chances are your question has already been answered.
  • Use a title that describes the content of your post. Don't use all caps or special characters to draw attention either in the title or the body of the post.
  • Up to 10 emoticons are allowed in a post
  • Political discussions are prohibited.
  • Flaming - We do not tolerate abusive, malicious, personal attacks. You will be banned if you persist in this behavior.
  • Trolls - Anyone deliberately antagonizing other forum users by posting 'flame bait' type messages is not welcome. You will be banned (possibly without warning depending on the severity of the issue) if you persist in this behavior.
  • Personal insults (directed at anyone) will result in a ban. If the behavior is not corrected, it will be made more permanent.
  • Constructive criticism is welcome. However keep in mind we (and other forums goers) may not agree with you. If you can't keep the conversation civil, you will be removed from the forums.
  • The use of hyperbole, one liners, and images as part of a forum debate is likely to get you infracted. You have many ways to participate and be a constructive part of this community, even when you disagree.
  • To make the highlighted bits above 100% clear to everyone, the following WILL NOT BE TOLERATED:
    1. Personal attacks, insults, antagonism of any forum-goers, moderators or Tripwire Interactive staff.
    2. Breaches of confidentiality and privacy of any sort.
    3. Any form of racism, bigotry or attacks on race, creed or color.
    4. Linking to posts on other forums related to ANY of the above, whether you are the originator or not, without exception.
  • There has been too much in the way of abhorrent personal behaviors in the past. These will cease. It doesn't matter who started it or who reacted to it - it will all result in moderator action. If you have to indulge your hatreds, for whatever reason, go do it elsewhere - and do not try and drag our forum-goers over to enjoy your hatreds.
  • We understand that people have strong feelings about our games, what we do for a living and how we respond (or don't) to comments on the forums. We all aren't going to agree about everything. So, BE CIVIL in your disagreements!
  • DO NOT Transmit any message, information, data, text, software or graphic files, or other materials ("Content") that is unlawful (including illegal drug usage), harmful, threatening, abusive, harassing, defamatory, vulgar, obscene, libelous, hateful or racially, ethnically, sexually or otherwise objectionable. This includes publicizing private information, such as individual's real names, IP addresses and anything else that might be used to identify them to the freakier members of the internet. This also means you may NOT publically share private communications (PM, email or anything else) without the original poster's permission.
  • DO NOT Post or transmit any Content that contains a virus, Trojan horse or other mischievous Content.
  • DO NOT Post or transmit any unsolicited advertising, promotional materials, "junk mail", "spam", "chain letters", "pyramid schemes" or any other form of solicitation.
  • DO NOT link to posts on any other forums, or any other form of media, that breaches our rules. It will be treated just the same as if you had posted it here.
  • DO NOT Double Post, cross Post or restart closed threads.
  • DO NOT Intentionally or unintentionally violate any applicable local, state, national or international law, rule or regulation.
  • DO NOT Upload or transmit any Content that infringes any patent, trademark, trade secret, copyright or other proprietary rights ("Rights") of any party.
  • DO NOT complain about being banned from a server and DO NOT complain about other players on servers - that is between you and the admin, no need to get the community involved.
Username, Avatar and Signature Rules
  • Multiple registrations result in a ban.
  • No offensive user names
  • Avatars:
    Avatars are disabled.
  • All signatures should not exceed the following size limits, you can have both text and images
  • - For text signatures: 4 lines normal size, 8 lines small size and up to 100 chars per line. Font sizes above 2 are not allowed. (Blank lines count as lines.)
  • - For images in signatures: 1 image up to 400 pixels wide, 150 pixels tall and 100kb in size plus 2 lines normal size text and up to 100 chars per line
Netiquette: Written text has no inflection, and, as such, you should be careful how you write your messages as interpretation will vary from person to person. Please take advantage of the built-in emoticons to add such expression to your words. Please remember the golden rule: to treat other forum users the way you would like to be treated. Please use common courtesy, and enjoy using Red Orchestra's forums
Offensive material
The following is a list of some things that MAY be considered "offensive" by the moderators and the team. This is NOT an exclusive list and it does depend very much on context.

Crossing the line into "offensive" territory is likely to get you asked to change your name, sig or avatar or to withdraw/delete posts. This will be done politely by the moderators. If you refuse to comply further action WILL be taken once started, ultimately leading to banning from the forums.

A key point: please attempt to use your brains. What is mild humour to you may well be deeply offensive to others. While we have no intention of acting as politically-correct "thought police", we are on the lookout for those things that can cause offense and, in some cases, are actually still illegal in some jurisdictions.
  1. Names recalling notorious war criminals or personalities.
  2. Names recalling atrocities and war crimes in general, or units with particularly odious histories.
  3. Use of obscenities and expletives.
  4. Blatant racism, mysogynism or many other "ism"s.
  5. Use of symbolism and regalia recalling Nazism or Fascism; this does not include pics of soldiers who happen to have such symbols on their uniform, unless we feel this has been done to provoke. Please note that many Nazi symbols (including the Swastika) are still illegal in Germany and other countries and considered deeply offensive by many Europeans.
  6. Use of symbolism and regalia recalling Stalinism.
  7. On both the previous two, the moderators' views on the intention and impact of use of such symbols will be final - not yours. Please be understanding if you are advised to change something.
  8. In general, if a sig/avatar represents your allegiances in-game and is clearly "in part", it is likely to be fine; if the moderators feel you are trying to demonstrate unpalatable political allegiances, or to use it in an attempt to ridicule or provoke others you WILL be asked to change it. RO is NOT the place to make any extremist political statements of any kind.
So people get the idea, some examples that would be considered offensive, numbered as above:
  1. "Hitler", "Beria"
  2. "NKVD Blocking Detachment", "Einsatzgruppen"
  3. This one should be pretty obvious...
  4. So should this - and it includes calling all Germans "Nazis" and all Soviets/Russians "Commies". It got boring 50 years ago, so stop it.
  5. Use of swastikas, fasces, SS-runes and so on for the Axis.
  6. There is actually very little overt symbolism from the Stalinist era; the hammer-and-sickle isn't offensive per se.
A simple rule-of-thumb: many Europeans find Nazi symbolism of any sort offensive; many Americans still find Soviet symbolism offensive. Engage your brain before using.

Final Note: this is NOT open to debate, so please do NOT start whining and moaning if a moderator asks you to change something. They will advise at first, giving reasons, then, if you take no notice, they will step up the pressure through to banning.
See more
See less

Will HoS present the netcode disadvantages of UE3?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Will HoS present the netcode disadvantages of UE3?

    Hello everyone,i would like my first post to be about something very important for me,netcode.Having been a UT3 and AA3 player,i am totally dissapointed by UE3 when it comes to interaction between player/server

    What i mean ; In both games,there is a noticeable fire delay.When you fire the plasma rifle for example,the particle is shown after 0.3-0.5 sec ...In Americas army,the exact same thing happens

    Why this bothers me ; It is obvious,it destroys any form of enjoyment online,i have to predict where to fire so my bullet hits the target when he is there,despite the weapon being hitscan and my ping being 60.To be honest i don't even know if the actual bullet is lagging or it's just the particle effect

    I have noticed this fire delay phenomenon on every online UE3 game and in Quake live only(if it is somehow connected).I would like to know if this game will have the same problems,as i doubt i can do anything about it or that it is my PC's fault(1200

  • #2
    The spec of your PC isn't as important as the quality of your connection...if it's taking 300-500ms for your shot to register, then I'd suggest you need a better connection.


    • #3
      Originally posted by SheepDip View Post
      The spec of your PC isn't as important as the quality of your connection...if it's taking 300-500ms for your shot to register, then I'd suggest you need a better connection.
      I said that my ping is about 60...i never even play at servers with more than 90 ping.It can't be my connection.Btw,have you played UT3?,and if yes,was everything fine?


      • #4
        I made a thread about this, asking why the bullets took that time the hit even in CQC.This is because UE3 doesn't have any lag compensation so it takes some time to send the info to the server and receive it.


        • #5
          Originally posted by Brozex View Post
          I made a thread about this, asking why the bullets took that time the hit even in CQC.This is because UE3 doesn't have any lag compensation so it takes some time to send the info to the server and receive it.

          Thanks a lot.I was actually going to buy this game,fortunately i know what to expect now


          • #6
            Originally posted by VodkaGR View Post
            Thanks a lot.I was actually going to buy this game,fortunately i know what to expect now
            that wasn't my goal


            • #7
              Originally posted by VodkaGR View Post
              Thanks a lot.I was actually going to buy this game,fortunately i know what to expect now
              no u dont. If you join a low ping server, there's no bullet lag. and hitboxes are spot on, no lagging behind playermodel.


              • #8
                Originally posted by Leopardi View Post
                no u dont. If you join a low ping server, there's no bullet lag. and hitboxes are spot on, no lagging behind playermodel.
                In UT3 i have joined servers with 50 ping(that's the lower i have ever found though,i am usually about 60) and it was disgusting.If it is a slow game it will probably not be so bad,but then the enemy is jumping around you...meh.
                I guess we will just have to wait and see


                • #9
                  There is no "disadvantage" to the net code of UE3. It works quite similar to UE2, and Red Orchestra 1 was widely regarded as having some of the best net-code around - with the game being very playable even up to a ping of 200ms. And considering I'm the guy that did the multiplayer network coding for RO1 and I'm doing a lot of it for RO2, you should see similar results in the end. Regarding AA3, I can't speak to it's network code since when I tried to play it it was back when the game wouldn't even function online right after it was released.

                  When it comes to visual representation of hits (i.e. displaying hit effects/particles) there are two methods possible, and both have their advantages/disadvantages.

                  Method 1) Calculate hit effects on the client. With this method you get instant feedback on where your bullet would hit (with hitscan weapons). This is great but there is one major flaw - where you see your bullet hit on the client doesn't actually represent where your bullet hit on the server since they are both calculated independently. This was the system that was used in Americas Army 2.X (which I worked on). This system is exasperated by randomness or cone fire, since to simulate the shot on the client you have to simulate the randomness you would also have on the server. The problem is, since it is random the client and the server will have different locations where the bullet will go. This is why in AA2.X you would very often actually see puffs of blood coming off of an enemy that you were shooting, but in reality you didn't hit them at all. Your client side simulated shot had hit them, but your server shot had not.

                  Method 2) Display hit effects on the client in the proper place by sending the information from the server on where the "real" hit actually happened. The disadvantage of this system is that there is a slight delay between when your shot is replicated to the server and when the hit location is replicated back down to your client. The advantage of this system is that when you see a hit effect appear it actually appears where the real hit happened on the server. In other words, when you see that you blood puffs appearing on an enemy that you shot, you are ACTUALLY damaging them.

                  In the original RO and since then I have been using method 2. I find the slight delay until the hit effect appears is far outweighed by never getting "false positives" and knowing where my bullets actually hit. Combine this with a non-hitscan system with full bullet ballistics where even if you are playing a non-network game there is a slight delay between when you fire and when your bullet hits, then the delay when playing online is almost not noticeable with a ping < 100 ms.

                  Also, in your case where you say your ping is 60 ms, but there is a delay 0.3 to 0.5 seconds (300-500ms) either there has to be something wrong with your network, the network between you and the server, or the people coding that particular game. Because in the standard "Method 2" system above, with a 60ms ping it would be about 120ms (or .12 seconds) before you saw the hit effects. Most likely it is a problem with your network, your computer, or your perception of time.

                  Finally, there are the games with the so called "lag compensation". I've never been a fan of this so called lag compensation because of the side effects it causes. If you have ever been playing an online game and walked completely around a corner only to die when noone could possibly have shot you, it was likely do to lag compensation. With these systems the server stores a list of locations and where a player was at a particular time. Then when a player shoots on his client it sends the firing info and a timestamp to the server. So when the server receives this information it basically "rewinds" back to the point in time when the client fired and checks to see if the shot from some time in the past would hit the player back then. The problem with this system is, that depending upon players ping everyone playing the game has a different view of where the other players are at a particular time. This is why on your machine you could be behind a wall, but the player (who you may not even be able to see on your machine) who has a higher ping than you sees you where you were a short time ago and shoots and kills you. So this is why I think lag compensation sucks

                  I prefer the Unreal net code methodology which uses client side prediction instead of lag compensation. When a programmer knows what they are doing and uses the Unreal net code properly client side prediction gives all of the clients connected to a server a very very close picture of where the other players are actually at on the server at all times. It does this by predicting the physics and movement of the other players. It does this pretty good for super-fast games like UT, and when you slow this down to real world movement speeds like in Red Orchestra this system is rock solid. In other words, in RO when you shoot at someone you can pretty much guarantee they are at where you see them at (up to a ping of 200ms). Likewise when you get SHOT by someone on RO, it was because they could see where you are currently at, not where you WERE a short time ago.

                  After coding MP network games for nearly ten years, this area is a bit near and dear to my heart, so I'll stop ranting now
                  [I support "RO Forums Classic" mode!!!]


                  • #10


                    • #11
                      Good to see a post on the net code.

                      Awesome post Ramm


                      • #12
                        Couldn't you make a mixture of both?


                        • #13
                          [QUOTE=Brozex;662935]Couldn't you make a mixture of both?
                          [I support "RO Forums Classic" mode!!!]


                          • #14
                            OK.But in Rost I had to do it, so if the netcode is similar...that would be similar?


                            • #15
                              Great post.

                              I don;t know much about net-code but it is one of the reasons i quit BC2. That game not only has terrible blood splatter no hit issues. And it tries to use lag compensation where not only will you die behind cover like mentioned in the post..... but sometimes you will have to fire BEHIND a target ..

                              In a game with bullet time... instead of leading a target you have to sometimes shoot behind it.... lol

                              I hope tripwire does a much better job than dice because im very close to quiting FPSs