Jump to content
Forum Shutdown 28/7/2023 Read more... ×

diablodbs

Beta Tester
  • Content Сount

    5
  • Joined

  • Last visited

  • Battles

    553

Everything posted by diablodbs

  1. diablodbs

    Client Display Desync Again

    Hallo zusammen, seit ein paar Tagen habe ich wieder ein altes Problem, das um November 2015 herum anscheinend behoben wurde. Für mehr Details zum Problem kann man einen Blick in meinen original Thread oder den von Karck werfen beide sind unten verlinkt. http://forum.worldofwarships.eu/index.php?/topic/24414-wrong-display-of-ship-positions/page__fromsearch__1 http://forum.worldofwarships.eu/index.php?/topic/32573-desync-shells-flying-thru-enemy-ship-whitout-contact-not-over-pen/page__view__findpost__p__631399__fromsearch__1 Um das Problem etwas zu illustrieren etwas Videomaterial seitens ManiacMouse: http://viewsync.net/watch?v=8kUz9a-wH8o&t=9.76&v=Bha2goiKrEw&t=0 Links ist eine Aufzeichnung des Replay und rechts die Liveaufzeichnung. Mit Vergehen der Match-Zeit divergiert die angezeigte und die tatsächliche Position von sich bewegenden Schiffen. Je schneller es sich (durchschnittlich) bewegt, desto größer die Auswirkung auf die Abweichung. Wenn ein Schiff aufhört sich zu bewegen reduziert sich auch die Asynchronität. Ich bin mir nicht sicher ob auch andere Objekte als Schiffe (z.B. Torpedos) ebenso beeinflusst werden, aber da diese grundsätzlich kurze Lebensdauern haben (<120s) hätte die Abweichung hier geringe Auswirkungen. Wie dem auch sei so wie es z.Z. ist, ist es für mich nicht spielbar. Wenn es nur einige Gefechte wären, aber die letzten 5 Tage waren es 100% der Gefechte. Grüße DBS
  2. And i am back again... not that it got better. :-X @Karck good investigation hope it helps them to fix this. CPU: AMD FX-6100 (OC ~4.5GHz) (No change without OC) MB: GigaByte GA-970A-UD3 (still works but need a new one... when i upgrade my CPU :-P) GPU: Sapphire Radeon R9 390 Nitro (Normal settings can only utilize ~85% of 'her' with my current MB) RAM: 2x 8 GB GSkill F3-1600 C9, 2x Crucial Ballistix Tactical 8GB 1600 C8 (C9) OS: Windows 7 Professional 64-Bit Will play something else for a while again. Maybe WoT while i really am getting a bit bitter .. will probably not put more money into either of the games if the support is not even caring about faking interest about major things like this... i mean yeah Bismarck-tan is important but i rather first would like to be able to play the game without looking like an idiot dodging torps 200m of stern and fire my torps right into the next allied BS cause i didn't even know it was there since i had a clear LoS to my target ~.~ About Ghostshells in WoT i see them some times but they're a lot less obvious to notice. Since a lot of players move much less you often still hit them but not where you see the hit which will lead to the "WTF" non-penetrations and ricochets. Like not penning a scout with a 152mm 276 pen gun that was shown to hit in the back of the turret while the scout (LTTB) actually had already turned his turret front towards me. 40mm Turret aft AC -> 3x overmatch -> rico and absorb impossible. 90mm front -> no 3x overmatch, no 2x overmatch -> good angle -> rico. And this also happens with the whole tank model. Since i got my R9 now which has a nice capture software that doesn't drain much performance i might actually start recording some WoT battles and compare them with the replays. My guess is that most of them show signs of desynch, while not as bad as in WoWS and i think the Desync isn't getting worse over time in WoT atm and might even out after movement stopped.. but this is just an assumption Anyways.. i am out again .. will check in again in a week or so.. until then i cannot really care about WoWS.. my day is full of programming work.. want to relax playing some games not think about fixing problems for WG especially when they seem to be as responsive as they are .. or am i missing a blue-post or two? *ah wrong game but at least they ususally blued a post like this in a few hours* Window#44
  3. diablodbs

    Wrong display of ship positions

    Hi everybody, fiirst of all i am sorry if i missed a similar post, the search didn't return anything useful. Since i again have more time at hand i startet playing after nearly half a year. I have played in the close beta some time and never had anything like i experience right now. I experience an extreme divergence of displayed (client side) and actual (server side) position. Overview: Problem: Display postion (client side) of ships != actual position (server side) Manifestation: Shells fly through ship models (even at close range), shells displayed missing my ship damage it etc. Reproducibility: Every battle i life on long enough to notice it (seems to get worse the more time passes) Possible cause: Client server desync / inconsistency I shoot at a ship and the shells pass right through it. And no i don't mean the typical some shells hitting in front (side facing me) and some hitting behind (the far side) but actually shells which pass right through components even in close quarters up to "ramming" right through an enemy ship without any contact at all. On the other hand i can hit them by aiming far in front of them which then shows shells which should just hit the water in front of the ship but damaging it. This usually manifests for me against destroyers as they're much faster than other types but hitting the bow of a BS and disabling the engine also brings up some curiosity. The position is instantly updated when the enemy is sunk which often shows that destroyer or fast cruiser actually were several times their own lenghts away from where i got them displayed. On the other hand i have not noticed, that this inconsistency stops after some time but seems to grow worse with every minute i am in a battle. Additionally i am also often damaged by shots which splash several meters in front or behind me and some times even by shots which hit to my port or starboard side. And some torpedos hit me while i see them passing far away from me and some pass right below me without any reaction. It is really annoying and i can only compensated it to some extent by good guessing the enemies position and then slowly closing in which is not practical with slow loading weaponsystems like torpedos and high cal guns. This is most likely a strangly strong effect of server client inconsistency / desynchronisation like what we also some times see in WoT while there it usually resyncs in a few seconds or tanks just stand long enough. Is this already a known issue with some magical solution on my client side? (other than reinstalling and deleting my WTF folder etc. oh wait wrong game) If i find my Fraps key i might be able to commit some footage of the problem. greetings DBS Edit: Ok today i had some AFK BS for target practice with my torpedos. It seems like my ship is also not where i get it displayed as after 5 min of battle my torps are being launched like 50-100m in front of my ship which also leads to me missing a BS at full stopp while staying still myself. From 350m distance when using the aim indicator (which is pointed exactly on the middle of the BS) my torpedos just go by him (while he as he never moved is actually where i get him displayed and after compensation i even hit him). Reinstalling one last time... :-/
  4. diablodbs

    Wrong display of ship positions

    Don't forget about potential team killing when your torps are being droped into water 1-2 ship lenght in front of the position you think they will :-X When comparing your two videos side by side it looks even more ridiculous -> http://viewsync.net/watch?v=8kUz9a-wH8o&t=9.76&v=Bha2goiKrEw&t=0 Since i got my new graphics card not long ago i gave it a try today again but my old card wasn't the problem.. it really seems the only plausible thing left to have to do with the CPU clocking which would indicate that WG might have some serious trouble resolving this which seems also plausible as they have yet to address this problem at all. I have stopped playing WoWs in august and will stick to it since it is just frustrating 90% of the time .. especially in the destroyers i actually want to play... i mean a cruiser with high rate of fire can somehow compensate.. destroyers with 1:30min+ reload on torps cannot really be effective with this kind of problem and carriers and BS have the same problem.
  5. diablodbs

    Wrong display of ship positions

    I'd love to read something official to this problem since i can't make out anything on my client side which would trigger this nor does the connection seem to have anything to do with it. I tried it on 6 different devices (had some friends over for a small LAN) and 4/6 worked fine with my connection but 2 including my PC had the same problem. I am going to tweak the graphics a lil to see if it might anyhow be connected, since my graphicscard is my systems bottleneck ( still running a HD4000 series heavily overclocked ). It really seems to be just on the display side as the positions of the ships etc. seem to be correctly recieved just not displayed. If i remember correctly something similar happend with the early WoT replay system which was often in desync with what actually happend. Still i have 30-60 FPS and no connection issues .. which makes this very curious.. Edit: So minimal settings result in no better condition :-/ If i keep playing like this i will have problems going back to normal when ever this issue is fixed O_o
×