Registered Users
  • Content count

  • Joined

  • Last visited

  • Days Won


OLDZEKE last won the day on December 2

OLDZEKE had the most liked content!

Community Reputation

279 Salty



  • Rank
  • Birthday 09/20/1954

Profile Information

  • Preferred Side
  • Preferred Branch
  • Preferred Unit
    River Boat
  1. I use 2 pc and a mac. I can run multiple accounts on the pc's. Mac there is a way but not worth the effort. I use software on one pc to induce lag (high ping) or packet loss, or both by percentage. I can do this inbound/outbound or both, TCP or UDP packets. This leaves the other pc and mac operating under normal network conditions. I can use the ping command to verify what its doing or wireshark which is a connection diagnostic tool.
  2. I try to be very careful in all my responses on these forums, discord, facebook as well as ingame. These capitol letters are heavy at times, I can no longer joke or act silly in chat, game or forum because every word is weighed against possible leverage to discredit. I don't go onto discord when ingame anymore for the same reason. I try to be informative and helpful as best as I can. Written text is never a good substitute for face to face conversation, too easy for wrong assumptions simply due to differences in writing styles and or difference in the ways we compose thoughts in writing them. I'm a volunteer, I don't get paid for any of this. I do testing, I search through the game itself to figure out/reverse engineer how parts of it work as well as assist art, dev and production in whatever ways I can because it gives me a means of satisfying my curious nature as well as keeping my mind active. I'm not a coder, have no formal computer type education. I'm a 65 year old former coal miner, disabled due to a mining injury many years ago. What I've learned computer, code, art wise has been self taught due to a insatiable curiosity about how things work. Now as to the issues discussed. Part of testing involves discovery as to how to replicate a issue. This gives the devs a definitive starting point. That's not to say dev does not look at issues without replication but that having defined replication steps greatly speeds the process up. "I can clearly see the player in question, clearly see I shot first, clearly see I hit him (multiple times) and yet he still manages to fire on me (after getting shot) and we both die. " The auto despawn was added to help reduce this, it's still being refined. Netcode3 is also a step in reducing this, you'll notice it's disabled currently as it's causing far too many autodespawns and needs refined some more. It's greatly improved, it still needs to be better. Feet sticking through buildings.... Yea it's not a good thing that we desperately want to have fixed and have had several folks attempt. Vehicles, buildings, terrain all use the same type model. Their colliders are created with the model, to put it in a very basic way you simply select the pollys of the wall or vehicle to be the collider (that's from my layman's view of what I've been shown while watching art work). Vehicles are more involved as each collider has a armor value. Infantry though are a different type model, use a different collision deal that is not as adaptable. The speedtrees are also a different type model and use a capsule type collider. this is why some trees seem to have a "forcefield" coming out of them. they are broadbase and taper but the collision capsule does not give the option to taper it. Some have a bend in the trunk, the capsule does not have that ability, it will only expand by width and length. These are limitations that we hope to grow past soon.
  3. I wonder if y'all have read this? http://forums.wwiionline.com/forums/topic/419864-posted-this-in-the-support-page-though-id-put-it-here-to/ May not apply but sometimes strange things happen.
  4. Best I can tell you is what I've seen in testing the auto despawn limits on a dev server. I could run a high ping without issue. My normal ping is in the 50s. With significant packet loss or packet fragmentation my ping would climb into the 1000s and I'd auto despawn. Our devs are still checking the net code to see if they can make changes to improve this.
  5. Man you used to drive me nuts, you must know every crack and crevice that gives just enough view into a cp window. I spent hours hunting down some of those to see how you got me but it was always ligit
  6. The invisible shooters was a example. And I have played the game, if you check the stats wall of fame I'm on the 75k kill list on this account. I've played the game, ranked up several others, each with 5k or so kills. I've guarded, I've seen bad lag in the past but for me with 1.36 I've not seen it so bad it's not playable. That's my experience. As said I will try to observe some who regularly bug report this to see if I can see it same as y'all do. I'm in the southern WV coal fields, I realy doubt my internet is that much better than the rest of the US so if I can get a idea of how to experience it 1st hand that'll give me info to pas to dev.
  7. I've did a lot of guarding. When I still had time to play and my eyes could stand hours in front of a monitor I guarded a lot. Back when we had the offset issue that came in with 1.35 I saw a lot of "got shot and only saw shooter in the death cam" as well as shot through walls, shot him and he didn't die etc. We found issues, coders fixed issues. I've not seen this issue, I've used the buzzard to observe players that were reporting invisible killers and every time it was a player well hidden but with LoS to the reporter. Clearly some are seeing a issue, we are trying to also find a way to experience that issue so we can replicate it for DEV so they know what to look for and or at. I'm replying as straightforward and clearly as I know how. I try to answer questions to the best of my knowledge and abilities as I feel players need to at least know we are listening. But, when it get to the point my posts are ill received then I'm done.
  8. Changing the capture system is not going to be a light task. I don't know exactly all the intimate details but I do remember testing capture was changed from touching the table to being inside the building. Early on you could cap from on the roof of the building and that had to be adjusted which leads me to assume it involved editing the capture polly in the building model itself in creator. If that's the case, and mixing in what little I know as to strat linkage in the terrain editor I think to change to a area type capture the flag pole deal would require new models (needs some sort of placeable terrain piece with the capture call/code/polly) plus changing existing models (removing the capture bit from flag buildings). Then that would need be recoded into the terrain editor (I assume) and if it cant just be a mater of trading the existing cap building for another terrain object or blank polly model then it would mean redoing every town, every capture point in the game..... Not saying it can't be done, but I think it would likely take a good chunk of time dedicated to a artist, coder or coders and terrain folks doing nothing else but this task.
  9. Yes there will be fractional lag at times, that's a part of online gaming. I watch my grandson play heros and generals and hear him complain about it as well as the games on xbox. Die then seeing the other guy appear around the corner in death cam though is part of what the auto despawn is meant to help with. Squash the blatantly horrible laggy connections. With all that's been said though we are still investigating connection issues and still working to refine the netcode so as to get smoother gameplay with the least amount of lag possible without cutting off a huge chunk of our player base.
  10. I answered you as to the best of my knowledge. I can't play the game from your address so I can only relate as to how it plays from mine. That said, in testing over the last few years I've tested using 3 machines, 2 pc and a MacBook, tested organic as well as through steam. I've tested with induced packet loss as well as with induced ping up to 1000ms as reported by the game logs and ping bar as well as checking via cmd prompt to verify both ping and loss using the ping command. I shoot a player it records in the aar. Same ingame. Now admittedly while ingame playing I don't always check the aar so it's possible it's happened and I missed it. Being you are one this seems to happen too I'll try to determine if you play at times convenient for me and if so I will shadow you and observe to see what it looks like from my perspective.
  11. I've never been able to replicate that. I know this, when we can fix it, it will be fixed. Best guess as to what's happening? I'm not a network engineer so I can only guess. The game you play is on your machine. You get "state" updates that tell you this building is destroyed or the depot has been captured and then the game on your machine updates to that state. The player you shoot is rendered on your machine according to updates the player sends to the server and then is sent to you. When you shoot a player you are shooting where the player is rendered on your machine, the xyz co-ordinates you have for that player at that moment. It's not "I'm sending you fire data to xyz, did I hit you but rather I see you at xyz and I fired at you and hit you. You send the data as to where you hit the player so movement or positional lag are not a thing. Now, if I shoot a player I see the hit sprites and send that I hit you here, with this round, at this angle, with this velocity, I penitrated this far, If I hit armor then I made this much spall and it then tracks each piece of spall against each component that takes damage. If I fired a round that creates shrapnel then each piece of that is tracked and all penitration data is also sent to the person I shot. Only guess I have as to seeing hits that do not register as to dropping/immediately killing the player is that I'm not getting the packets telling me who that player is. If I know who that player is then I know (my machine) that I sent the "I hit you" packet. The only other guess I can give is that that "I hit you" packet got lost going to the server. Either case would, best as I can guess, cause a no stat record of that instance. But best as I know lost packets would be the only likelihood. Again, I'm not a network person. I take the bug reports as do the rest of QA and try to replicate the issue and then give dev the replication steps.
  12. As SCKING said, GM/RAT superpowers as to invulnerability are not a live server thing. Dev servers we have tools to use to test with but live tools are very different and restricted vrs dev server. When you see a hit that does not take down the other guy immediately, he/she continues on for a bit on the same vector then likely that player has lost packet flow and is on the way to auto despawn. You hit a player and see them fall dead but get a damage, most all of us have got hit hard enough to not be able to run, can't change range on weapon (scored dead) but still just enough "life" left to keep walking shooting. Tanks/atg/aa/planes, kill the driver that's a kill. Vehicle can still shoot. Kill break main guns, kill, vehicle can still move and tank wise, secondary mg can still fire. Main gun broke awarded the kill so it's a "dead" tank stats wise. Tanks, both tracks broken or engine dead is a kill award. Tank can still fire all guns but stats wise it's a dead tank. There can only be 1 kill award against a player per sortie. So I kill the driver of a tank I get the kill, someone else blows that tank up they only get a damage. We need better visual feedback as to damage. We need a better scoring system where as you receive credit for disabling as well as total kill. Assist points or whatever. Still loads of things that need be or would be neat to have. All require time, keeping this grand old game alive and the talented folks needed to get there.
  13. We do not use dev/rat powers on live.
  14. I set the essen/dusseldorf corner area axis so there are also fairly close opposing AFs if needed.
  15. It's in testing still. We've created tickets on the latest found issues for the Devs to work off of.