Hummingbird Posted April 8, 2019 Posted April 8, 2019 (edited) Through a lot of testing my co pilots and I have been able to observe a correlation between wing breakage and ping. As pr. our testing wing breakage becomes more and more frequent the higher the ping is, and at high pings (200+) sometimes the wings break at accelerations as low as 6-7 G's, and that's without any previous accelerations above that. By comparison when the ping is very low or zero (host) wing breakage pretty much never occurs until at very high accelerations, above 12-13 G's. In short there might be a netcode issue here. Edited April 14, 2019 by IronMike
Cobra847 Posted April 8, 2019 Posted April 8, 2019 We're moving the stress behaviour to a moving average to try to account for netcode. Nicholas Dackard Founder & Lead Artist Heatblur Simulations https://www.facebook.com/heatblur/
Sandman1330 Posted April 9, 2019 Posted April 9, 2019 This explains sooo much! Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2
SonofEil Posted April 9, 2019 Posted April 9, 2019 (edited) I wonder if this also causes the snap blackouts I’ll sometimes experience in MP (of which I’m an admitted total noob). It seems much easier to go full G-LOC when pulling low-ish even, consistent g’s. I’ll have the mild peripheral fuzzies then *poof* total blackout. Never happens to me in SP. Edited April 9, 2019 by SonofEil i7 7700K @5.0, 1080Ti, 32GB DDR4, HMD Odyssey, TM WH, Crosswind Rudder...
Hummingbird Posted April 9, 2019 Author Posted April 9, 2019 We're moving the stress behaviour to a moving average to try to account for netcode. Great, looking forward to testing it out :) And thanks for the answer :thumbup:
RangerKarl Posted April 10, 2019 Posted April 10, 2019 I get odd super G behavior when doing an instant pitch up at M1+. Almost always end up breaking my wings in the Caucasus Dogfight instant mission, preceded by a blackout. Tacview never picks up any Gs over 2 or 3.
lunaticfringe Posted April 10, 2019 Posted April 10, 2019 Because Tacview interpolates G from point to point and you already destroyed the aircraft, so between the two frames it captured you ramped the G, were damaged, and the aircraft immediately unloaded- hence an average report of 2-3 Gs based on 12+ G for an instant, and 0 G the rest of that time period.
Tom Kazansky Posted April 10, 2019 Posted April 10, 2019 "Adjustments to structural integrity and wing snap code (hopefully corrects less lenient structural damage with higher network latencies)" said Chizh today: DCS World 2.5 Changelog and Updates of Open Beta https://forums.eagle.ru/showthread.php?t=200724
Recommended Posts