Feared_1 wrote:The video doesn't show much, to be honest. It seemed like the person recording was either trying to exaggerate the (wrong) effects of the bug or could not focus their ship on what should have been focused on. The bug is much worse than what is being shown. It is certainly a problem. Not sure what Cyber is talking about there...
Red Spot, read your PMs.
Are you joking, or blind? The test showed someone blinking into my face. The Fulmen Method (described earlier) has him doing that, repeatedly as part of his weapon cycle, compounded by collision warp (thankfully that is confirmed fixed).
I thought the video would be perfect evidence and it was for the testing team. If you get blinked at, the omegakick will give you a fun little direction, but the prediction code takes place before that can be relayed. As soon as the actual results come in, which almost always differed from the prediction, your position and vector are reset in the next world swap. That's what you saw in the video. If you think there was lag or poor video quality, note the histogram scrolling in the background. That is what it is for. Find a program convenient to you and scroll through it frame by frame if you would like. You can find the exact moment in game time where the prediction and the actual result are compared and synced, and then reference the histogram to see that the world swap was at that exact time.
I don't know how it could be exaggerated or downplayed in any form. You are blinked at, that happens. Always.
---
edit: Caught me after a bad day at work
When you say it is worse than shown, it usually is because that guy is driving into you headfirst and blink spamming, in conjunction with arc and stuff, which gives its own kick. The video was exclusively for testing purposes: show the bug happening, period. Having all the other factors like driving headfirst and using arc introduces multiple variables, which is catastrophic to testing a single bug.