Open KynikossDragonn opened 3 years ago
Very strange bug. And I really can't reproduce it even with fresh version or with old one from november. If you more lucky in it - it would be great to catch it one more time or find conditions when it appear.
I'm not sure how I could reproduce it, if I ever decide to replay this campaign again and get to this mission and start using Serp's to snipe powerstations with, I can give it another shot.
Hopefully it's not the compiler producing weird code.
Seems I reproduce it on debug map with "2 level" aggr and placing new units in same squad while they attacking something But still no idea why it's happening and why it's not in squad manager, but on map.
пт, 22 янв. 2021 г. в 17:07, KynikossDragonn notifications@github.com:
I'm not sure how I could reproduce it, if I ever decide to replay this campaign again and get to this mission and start using Serp's to snipe powerstations with, I can give it another shot.
Hopefully it's not the compiler producing weird code.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Marisa-Chan/UA_source/issues/22#issuecomment-765294381, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADJLFL75SKP2JNOTIPF6STS3FE6ZANCNFSM4ULBDDDQ .
Oh, seems I found why it's rendered and does not function. Seems it's only in sector units list and somehow lost from units list.
пт, 22 янв. 2021 г. в 17:44, Zidane Sama llancelot7@gmail.com:
Seems I reproduce it on debug map with "2 level" aggr and placing new units in same squad while they attacking something But still no idea why it's happening and why it's not in squad manager, but on map.
пт, 22 янв. 2021 г. в 17:07, KynikossDragonn notifications@github.com:
I'm not sure how I could reproduce it, if I ever decide to replay this campaign again and get to this mission and start using Serp's to snipe powerstations with, I can give it another shot.
Hopefully it's not the compiler producing weird code.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Marisa-Chan/UA_source/issues/22#issuecomment-765294381, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADJLFL75SKP2JNOTIPF6STS3FE6ZANCNFSM4ULBDDDQ .
Finally I catch what's going wrong. And seems it's vanilla bug too. Well, steps what's going on:
I hope it was fixed with this commit https://github.com/Marisa-Chan/UA_source/commit/5995fab88cca85051de60f4e4e9279d70e49e2d9 User's unit management things was moved before update loop.
And hope it will not generate new bugs.
I'm not fully sure how to describe the situation that just happened but:
While I was streaming the Taerkasten campaign I came across this situation: https://www.twitch.tv/videos/823464137
All I can think of what happened was, somehow while rapidly adding more Serps into that squad, somehow I guess one got fully created at nearly the same exact time one of them fired upon the power station and somehow made one of the newly created ones get stuck in a "zombified" state where I can't move or order it, it doesn't show up in the Squadron Manager, and destroying it permanently leaves a wreck that isn't affected by physics nor collides with anything.
The game didn't crash after this and I was able to complete the mission successfully and return to the shell after beaming out.