hello, so after the server check that was meant to fix the barrage & demolition macro disconnection issue, somehow im still disconnecting right after i cast transform and my macro (barrage+demo) key. Have uninstalled and reinstalled and tried both img and wz yet the issue is still there. My hero's client however was fine when my bucc's client got disconnected, not sure what other solution there is to try hence posting here. Any help is appreciated!
I crashed again at shao today too, i think its because i spam the transform button when its still blinking whilist spamming the barrage demo combo.
For extra context, this is what i did before i dc-ed (sorry if its a little blur though): Right after i came out of transformation, i transformed again and pressed macro key, which would cancel skill animations as seen in the video above^ creds to Donn1e & onetwotree for the vid *pls let me know if you want the video taken down*
After talking with my bucc friend he stopped using barrage demo macro and stopped d/cing, did an entire krex just fine.
I was recommended to post my experience here, but I really have nothing new to add. Above comments are accurate, I seem to only D/C when using this macro on my Bucc. Have also tried to reinstall. 3x Demo until I hear otherwise, I guess. P.S. To the people working on this, thanks for the work ya'll do keeping this fun going!
Have not dced ever since recent SC. I've used both the macro and macro+transform (to cancel skill animation) and doing bosses such as shao and NT have been fine as of now. Using img file if that helps.
I D/Ced like 4/5 times when I cast barrage+demo right after super transformation It looks like if u cast super transformation+barrage, sometimes the animation of barrage won`t present correctly (the character will just move forward without punching), and cast demo during this broken barrage animation will cause D/C, so I have to wait a sec after S transformation now
There is an upcoming fix in this next patch for the disconnect issues. Hopefully we got to the root of the problem now. Will keep this thread open to see how people are doing once the fix goes live!
