Announcement

Collapse
1 of 3 < >

Upcoming Forum Overhaul

We are starting the work to switch our forums, which have been based on a version of the Vbulletin forum software since their inception with the Red Orchestra mod (then VB 3 and currently VB 5.1) to an all new forum software called Xenforo. After researching it, we feel Xenforo is a better choice for the future as it has a vibrant modding and addon community that will allow us to extend the functions of these forums in ways players will enjoy.

As part of this, at some point in the near future these forums will be locked down so we cant merge over all of the existing content into the new forum database. It will likely then be a few more days as we work on the new forum and correct any issues from the merge.
2 of 3 < >

Privay Policy Update

We’ve updated the Tripwire Privacy Notice under our Policies to be clearer about our use of customer information to come in line with the EU General Data Protection Regulation (GDPR) rules that come into force today (25th May 2018). The following are highlights of our changes:


We’ve incorporated the relevant concepts from the GDPR including joining the EU and Swiss Privacy Shield framework. We’ve added explanations for why and how Tripwire processes customer data and the types of data that we process, as well as information about your data protection rights.



For more information about our privacy practices, please review the new Privacy Policy found here: http://tripwireinteractive.com/policies/privacy-notice
3 of 3 < >

Forum Rules

CHANGES[/SIZE]
  • 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. Name Shaming and Public "Witch Hunts" are also not allowed.
    3. Breaches of confidentiality and privacy of any sort.
    4. Any form of racism, bigotry or attacks on race, creed or color.
    5. Linking to posts on other forums related to ANY of the above, whether you are the originator or not, without exception.[/COLOR]
  • 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 NOTs
  • 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, "necro 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 post cheats or exploits; THIS INCLUDES ALL/ANY REFERENCES TO HACKING, PIRATED SOFTWARE etc.
  • 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
[COLOR=darkred]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.

Examples:
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

Game desperately needs memory optimizations

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

  • Game desperately needs memory optimizations

    Correct me if i'm wrong, but here's the deal.

    My FPS gradually decreases even though the scene intensity (players, particles, ZEDs etc...) remain at about same level. Usually i start the game with 100+ and end up having 50-40 on average.

    Just had a ~2 hours endless online game with ~20 players on it. So i opened console to see how many actors (physical objects placed on map such as players, ZEDs, volumes, projectiles and pretty much everything that makes your game) are loaded in my memory. The result was ~5700. So i restarted the game and reconnected to server and on the fresh connection it showed me only 2500.

    That's 3200 dynamic actors (e.g. non world related such as walls, blocking volumes, spawn points etc...) that my game will never ever use again but which still persist in the memory.

    I have pretty average PC and medium settings, usually my game starts with 4.5gb RAM worth data and it feels smooth and fine but it later gets like twice bigger and stuttering begins. I've noticed that after beta 1 update it takes too long just to boot out of the game after playing for a hour or two, today i had to kill KF2 with task manager for the first time ever because game refused to flush data on its own. I'm talking about "big" endless servers with 32 players. In regular survival mode i suffer no issues but in endless its gets worse progressively.

    I had no chance to scroll through the list of actors, as displayall command provides limited output but i've noticed that at least two there have a lot of instances - the one being KFPerkFXEmitterPool, the other isn't an actor but rather abstract object that still present in the memory - GameExplosion (had 32000 instances of these, with each storing its location, damage, radius etc).
    Last edited by simplecat; 10-03-2018, 07:59 PM.
    Killing Floor 2 stats (spreadsheet)
    http://docs.google.com/spreadsheets/d/1GDpg2mN1l_86U_RaDug0glFx8cZCuErwxZLiBKl9SyY

  • #2
    This probably belongs in the Bug Report section once more details are known.

    It looks like there should be a single instance of KFPerkFXEmitterPool for each player on the server, as it is only spawned once in KFPawn_Human.PreBeginPlay. Interestingly, it is only used for airborne agent's explosion... Do you happen to know the damage or radius values for the explosions? This could be used to determine which type of explosion isn't being cleared from memory.

    Since the output of getall/displayall is limited, next time could you refine your search to narrow in on the problem classes? E.g. getall GameExplosionActor InstigatorController, or getall GameExplosion Damage, getall GameExplosion DamageRadius, etc.

    How did you get displayall to work on multiplayer? I can't use it except on singleplayer, but it would be really useful. Or did you mean getall?

    Comment


    • #3
      Pharrahnox, thanks for your post!

      Getall i meant, yeah.

      I've been thinking about posting it in a bug report section but i feel like this is more of a global optimization issue and i'd love to see what people think about it (maybe even out of context of examples posted above, just some general thoughts). Maybe even get me a TWI employe response (yeah, i'm naive ).

      It does not seem like there even have to be a lvl 25 Medic using Airborne Agent. Game spawns new instances of this class on its own. Seems like this is relevance issue. As soon as you leave and enter other player's relevance area (e.g. for a period of time it stops existing on your machince) game assigns it a new instance. It fact as it closes replication channel it as well destroys a pawn instance too and spawns new one once get back. Hence plenty of PreBeginPlay events hapenning every now and then. I'm refering to this manual https://api.unrealengine.com/udk/Thr...html#Relevancy

      I just joined 6p server as a spectator. At first there was 6 of KFPerkFXEmitterPool s, one for each pawn. Then it turned to 9, 15 and so on ending with 62 before i left.

      Every GameExplosionActor gets flushed just fine, i have very few of them loaded at any given time but their templates (GameExplosion classes) are always in memory, shouldn't they disapper too? It affects all GameExplosion classes - grenades, husk projectiles, ground fire etc...
      Last edited by simplecat; 10-03-2018, 10:13 PM. Reason: typos are bane of my existence
      Killing Floor 2 stats (spreadsheet)
      http://docs.google.com/spreadsheets/d/1GDpg2mN1l_86U_RaDug0glFx8cZCuErwxZLiBKl9SyY

      Comment


      • #4
        (EDIT: I don't know why the top 2 quotes are broken.)
        [QUOTE=simplecat;n2325060]Maybe even get me a TWI employe response (yeah, i'm naive ).[\QUOTE]
        Very naive indeed.

        [QUOTE=simplecat;n2325060]It does not seem like there even have to be a lvl 25 Medic using Airborne Agent. Game spawns new instances of this class on its own.[\QUOTE]
        Which class exactly? KFExplosion_AirborneAgent?

        Originally posted by simplecat View Post
        Seems like this is relevance issue. As soon as you leave and enter other player's relevance area (e.g. for a period of time it stops existing on your machince) game assigns it a new instance. It fact as it closes replication channel it as well destroys a pawn instance too and spawns new one once get back. Hence plenty of PreBeginPlay events hapenning every now and then. I'm refering to this manual https://api.unrealengine.com/udk/Thr...html#Relevancy
        I don't believe that the KFPawn_Human pawn of other players is spawned each time it becomes relevant to the local player. Also I don't see that stated in the relevancy section of the site you linked.
        From my understanding (which is no means guaranteed to be correct, but I've done a substantial amount of netcode in Unrealscript in the past few years), relevance applies to property replication and whether actors should be spawned on the client when the actor is spawned on the server. It does not cause actors to pop in and out of existence on the client as it becomes relevant or irrelevant, respectively. That is, it does not cause the destruction and respawning of actors on the client. I don't know for sure whether the actor channel is closed and reopened as an actor changes relevance, but I doubt it. There would likely be significant overheads (both locally and through message passing) in doing this.

        Originally posted by simplecat View Post
        I just joined 6p server as a spectator. At first there was 6 of KFPerkFXEmitterPool s, one for each pawn. Then it turned to 9, 15 and so on ending with 62 before i left.
        Were many players dying? The KFPawn_Human instances are destroyed when a player dies, and a new one is created when a player (re)spawns. Perhaps the emitter pool is not being destroyed properly when the human pawn is destroyed.

        Originally posted by simplecat View Post
        Every GameExplosionActor gets flushed just fine, i have very few of them loaded at any given time but their templates (GameExplosion classes) are always in memory, shouldn't they disapper too? It affects all GameExplosion classes - grenades, husk projectiles, ground fire etc...
        This is quite interesting. There is very dangerous situation that can happen if an Object contains Actor references that aren't explicitly cleared when the references to the Object are removed. This prevents the garbage collector from cleaning them up. In the case of the GameExplosion for the airborne agent skill, this could prevent the emitter pool from being destroyed since there are still references to it. I haven't checked whether there are any Actor references in the GameExplosion Object, but it's a possible cause if there are.
        Last edited by Pharrahnox; 10-04-2018, 12:23 AM.

        Comment


        • #5
          Sorry for more weird talking. Whoever reads this probably thinking "what a nerd", but hey i'm a cool guy and all the girls around want to hang with me (*lies*)

          Which class exactly? KFExplosion_AirborneAgent?
          a new KFPerkFXEmitterPool, i mean it is initialized regardless, at this point (in PreBeginPlay) game doesn't care of perks and classes yet, just loads what it said to


          No players were dying.


          To be more accurate i was refering to this quote, my bad pointing to the wrong paragraph, this one from below
          Spoiler!


          What makes me think that constant cycle of spawning and destroying actors on client is an issue is the fact that when you get off their relevance area and come back, the player's pawn class instance changes.

          Say you just joined the game and all your teammates are next to you, relevant. Their pawn classes have names kfpawn_human_0, 1... kfpawn_human_4...

          But when you get away and come back their names change and now they are kf_pawn_human_5, 6... 8 and so on.


          Not just airborne agent. Every template ever used by explosion actor that is a long time goner stays loaded.
          Last edited by simplecat; 10-04-2018, 01:26 AM.
          Killing Floor 2 stats (spreadsheet)
          http://docs.google.com/spreadsheets/d/1GDpg2mN1l_86U_RaDug0glFx8cZCuErwxZLiBKl9SyY

          Comment


          • #6
            Originally posted by simplecat View Post
            What makes me think that constant cycle of spawning and destroying actors on client is an issue is the fact that when you get off their relevance area and come back, the player's pawn class instance changes.

            Say you just joined the game and all your teammates are next to you, relevant. Their pawn classes have names kfpawn_human_0, 1... kfpawn_human_4...

            But when you get away and come back their names change and now they are kf_pawn_human_5, 6... 8 and so on.

            Not just airborne agent. Every template ever used by explosion actor that is a long time goner stays loaded.
            That is interesting and unexpected (to me). I'm not currently in a position to do any rigorous testing or investigation due to other commitments, but at a later date I might do just that.

            I guess the first thing would be to add this in KFPawn_Human.Destroyed:
            Code:
            if(PerkFXEmitterPool != None)
            {
                PerkFXEmitterPool.Destroy();
                PerkFXEmitterPool = None;
            }
            That should fix the KFPerkFXEmitterPool spam, but I'm surprised it's not freed automatically. Then it's a matter of figuring out why the explosion templates aren't cleared. There must be references to them somewhere, otherwise they would be garbage collected since they're Objects.

            Comment


            • #7
              Destroying objects and garbage collection can be discussed in a high level, generalized way or examined in painstaking detail, but it is difficult to do much from between those extremes, in my experience.

              Comment


              • #8
                I vaguely recall some board members having this issue in EA - not sure if it was specific to hardware or what though.

                My rig is very basic and with a somewhat dated gpu (gtx 950) and I have never experienced the issues described :s

                Comment


                • #9
                  Just an observation: just had really long endless game on 32 man server (yeah, i know it is not officially supported). KF2 ended up with 12gb ram used (normally for me it is 4-6). I had 39000 game explosion templates and 4300 instances of KFPerkFXEmitterPool.
                  Killing Floor 2 stats (spreadsheet)
                  http://docs.google.com/spreadsheets/d/1GDpg2mN1l_86U_RaDug0glFx8cZCuErwxZLiBKl9SyY

                  Comment


                  • #10
                    Yes, non-supported modes are not a good way to report this kind of problem. There are reasons for the limits that exist. If you find things, I want to know, but it really helps if it is a thing we can make happen and observe in the vanilla game.

                    Also, simplecat what would the object count look like before and after the cyclic garbage collection routine? I know destroyed but uncleared objects, like full auto shell casings, can lead to memory problems, but have you watched the RAM graph in Task Manager rise over time, or are you just going by object count and if so, when do you count, relative to garbage collection?

                    Comment


                    • #11
                      I haven't really watched over the memory graph with the exception of when i just to started play (~5 gb) and when i decided to stop (~11.5gb) but i assume it had been rising over the play course as my performance had slowly been getting worse.
                      With the exception of 4300 instances of KFPerkFXEmitterPool, actor count hasn't really changed, everything else just comes and goes away staying at the same level. But this and GameExplosion objects have never ever been cleared once and i ended having a lot of them. If i would quit the match and rejoined it again then it could have been reset and game could've start collecting them from the beginning.

                      Yep. 32 players server play worth a lot of data, but the problem (is it?) is there even on regular 6 players games. I think it is only a matter of how fast game accumulates redundand stuff.
                      Last edited by simplecat; 10-25-2018, 06:46 PM.
                      Killing Floor 2 stats (spreadsheet)
                      http://docs.google.com/spreadsheets/d/1GDpg2mN1l_86U_RaDug0glFx8cZCuErwxZLiBKl9SyY

                      Comment


                      • #12
                        Just want to bump this thread. Game still keeps eating more RAM over the play course. Seems like more players there's on the server, the faster it happens. Screenshot was taking middle the match, 1h7m = +2.4gb ram used.

                        Spoiler!
                        Last edited by simplecat; 03-30-2019, 04:24 PM.
                        Killing Floor 2 stats (spreadsheet)
                        http://docs.google.com/spreadsheets/d/1GDpg2mN1l_86U_RaDug0glFx8cZCuErwxZLiBKl9SyY

                        Comment


                        • #13
                          Totally agree! It all started after the Revolt event has ended. And it's getting worse.
                          The game tends to start from mini-freezes to a totally unplayable 5 fps slide-show, after 2 or 3 map loadings.
                          Also, the game crashes much more than ever lately.

                          Inbefore:
                          YES, my pc is capable to run it smoothly on ultra;
                          NO, files verifying doesnt do any good;
                          YES, my internet connection is good;
                          YES, any other game works great on my pc.

                          Dear TWI, please do something about it.

                          Comment


                          • #14
                            The game just still keeps eating more RAM over the play course.
                            Last edited by Kittenmittens; 05-07-2019, 01:50 PM. Reason: removed unrelated link

                            Comment


                            • #15
                              Now I can 120% confirm there is something wrong going on because of the "Pawn_Human" thingy one guy mentioned before.
                              So, I've been playing the game on an empty server and everything was okay.
                              At the wave 2, the red text said that someone is connecting. After about 10 seconds (exactly as the person connected to the server), the game started to freezing and stuttering, although the new player didn't even spawned

                              Comment

                              Working...
                              X