You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While laser rangefinding for the mortar, a mortar near-direct hit me and blew up my binocs. When patched up I awoke still stuck in binocular zoomed view in one direction. The rangefinder was gone. I adminhelped and was told to relog. I went shipside for surgery and got a new rangefinder, but the sling still thought it had one in it. I got a new rangefinder and sling pouch, and went groundside. When I tried to rangefind then exit again I was stuck in 360 view again. I reported this to admin, and relogged. I tested it a couple more times more, using the rangefinder, then deactivating it, and would be zoomed out until relog again.
I informed the same admin I would just not play like that because it would give me an advantage. I got no reply and just continued the round until capped without using my rangefinder again.
What's the difference with what should have happened?
I expected to wake up from mortar with my rangefinder in my sling pouch and not zoomed in vision like superman and to be able to use them without gaining the farsight superpower unless I relog.
How do we reproduce this bug?
Use laser rangefinder to get coords for mortar
mortar drop an HE directly on top of you instead
your rangefinder blow up in your hand while active
wake up to a synth fixing you, but still zoomed in to the East like you're using binos
Attached logs
Not sure what to paste here that I didn't provide already.
https://live.staticflickr.com/65535/54003705667_180f2e42e6_o.png
Additional details
Author: DyvTheNaga
Admin: X31stOverlord
Note: None
The text was updated successfully, but these errors were encountered:
Testmerges
#6334: 'Xenomorph Endgame' by Git-Nivrak at commit 22dcde564c
#6071: '[V] Sorokyne Strata: Expanded Small corridors, removed 3000 unused tiles, Xenos can now weed everything except LZ's and surrounding of LZ's, allow LAZ for CAS inside structures with light blue Areas on Tacmap (glass ceiling hallways)' by Venuska1117 at commit 300a41768f
#6808: 'Attachments resprite' by Blundir at commit cc4fe40905
#7093: 'ports ipintel subsystem' by harryob at commit 3416fba856
#7106: 'Flexible Job Icons' by realforest2001 at commit a490c79b43
#7061: 'Project ARES: Interface Data Proc' by realforest2001 at commit dfe5291875
#6860: 'Mentor New Player Markers' by realforest2001 at commit 1457cbadfe
#6938: 'SHARP Rifle Revived' by Nomoresolvalou at commit a4970c3e4c
#7165: 'Fax Responders & Paperwork Prefabs hybrid TM' by realforest2001 at commit 0f902eff22
Round ID
23991
Description of the bug
While laser rangefinding for the mortar, a mortar near-direct hit me and blew up my binocs. When patched up I awoke still stuck in binocular zoomed view in one direction. The rangefinder was gone. I adminhelped and was told to relog. I went shipside for surgery and got a new rangefinder, but the sling still thought it had one in it. I got a new rangefinder and sling pouch, and went groundside. When I tried to rangefind then exit again I was stuck in 360 view again. I reported this to admin, and relogged. I tested it a couple more times more, using the rangefinder, then deactivating it, and would be zoomed out until relog again.
https://live.staticflickr.com/65535/54003654367_5720aebcd8_o.jpg
https://live.staticflickr.com/65535/54003705667_180f2e42e6_o.png
https://live.staticflickr.com/65535/54004804283_16001dd093_o.png
I informed the same admin I would just not play like that because it would give me an advantage. I got no reply and just continued the round until capped without using my rangefinder again.
What's the difference with what should have happened?
I expected to wake up from mortar with my rangefinder in my sling pouch and not zoomed in vision like superman and to be able to use them without gaining the farsight superpower unless I relog.
How do we reproduce this bug?
Attached logs
Additional details
The text was updated successfully, but these errors were encountered: