Rant/Plea to fix Wing Beacon issues present since 2.1

Mr_Foxhound

M
ElectricZ said:
I play ED almost exclusively co-operatively in a wing.

I have come to grips that co-op missions weren’t a part of ED even with the introduction of Wings in 1.2 in March of 2015.

I have accepted that there is no built in way to share mission rewards with friends when helping with a mission, and that if I want to give payment to someone I have to buy 50 tons of platinum and eject it for them to pick up, or vice versa, and that it’s such a pain in the butt it’s not worth doing.

I have accepted, over time, that sometimes the internet just hates you and getting in the same instance with a friend won’t happen, or that even if you do you may not see the exact same enemies.

But for the love of Braben, I can’t accept that Wing Beacons/Nav Lock has been broken since 2.1 and has still not been fixed in 2.2. It's been five months since a primary multi-player feature has been broken in this multiplayer game.

The issue: when a wingmate activates a wing beacon, other pilots are supposed to be able to engage wingman Nav Lock to lock in on the wingman’s position so CMDRs can link up for navigation, salvage, sightseeing or combat purposes. This worked fine, most of the time. Your buddy gets interdicted? You can drop in to help. Your buddy has the same assassination target as you? You can drop into the instance and work together to take it out. You want to get together outside of a RES to mine? No problem, the first one in drops a beacon and the rest of the wing can join in.

Except now, you can’t. Ever since 2.1.0.X, released back in May, the using the Wing Beacon is useless at best, and can get you killed at worst.

1. Dropping connections/crash to main menu from wings during high/low wakes
2. Dropping to wing beacons in current position rather than the beacon position, often millions of meters away.
3. Rubber-band snapping back to the beacon location if the nav lock is not turned off and you low-wake away
4. Positional drifting caused by a wingmate's location changing, most evident when trying to dock at a station in an instance where a wingmate has already docked, resulting in a pilot's ship moving like rotational correction is off, making docking nearly impossible without relogging.
5. Wingmate does not appear on scanner, only the wing beacon, which skips around the scanner as the wingmate's position updates every few seconds.

According to this response in this thread, at least the connection issue is resolved:



After playing for 3-4 hours in a wing last night, issue 1 may actually be fixed (hallelujia!), but I can confirm issues 2-4 are alive and well and frustrating as hell. #4 in particular can get you killed in a hurry from scraping you into the walls of the station, or getting you blown out of the sky for loitering.

https://youtu.be/gs_eIlmws3c?t=70

Bug reports have been filed since May. Port forwarding/firewall config isn’t the cause as these issues did not happen until the release of 2.1. Something got broken and needs to be fixed.

https://forums.frontier.co.uk/showt...out-of-supercruise-unexpectedly-while-in-wing
https://forums.frontier.co.uk/showt...ips-appearing-Offset-from-their-True-Location
https://forums.frontier.co.uk/showthread.php/256026-Inside-Station-has-low-LOD
https://forums.frontier.co.uk/showthread.php/267405-Landing-rotational-correction-bug
https://forums.frontier.co.uk/showthread.php/267392-bugged-station-drop-with-nav-lock-(wing)
https://forums.frontier.co.uk/showt...on-doesn-t-work-inside-stations-while-in-wing
https://forums.frontier.co.uk/showt...on-bug-collision-Texture-bugs-(Claim-request)

Please, FD, look into these issues, and if you as a CMDR have run into these issues post in this thread, file a bug report, make some noise about it while Frontier is still putting out patches for 2.2.

Otherwise it may not get fixed until 2.3, or ever. :(
Click to expand...

the rational correction bug has been broken for 8/10 months and reported nothing has been done about it

- - - Updated - - -

ElectricZ said:
You're right, there are several existing threads on this issue. Like this one, for example.

http://i.imgur.com/OPP3ji8.png



Notice the date, 13 June 2016. Not even the first report and certainly not the last one. It hasn't been fixed, along with the other wing issues in the OP, for almost six months. If Frontier needs more info on it, we should give it to them. But just in case the issue isn't a lack of enough information to troubleshoot, I think it's perfectly appropriate to create new threads so that FD is aware this affects more than a couple commanders.

That's my real concern, that these wing issues have lingered as long as they have because they're viewed as low priority. Multiplayer has been jacked up since the game launched in 2014. Most people who play multiplayer have probably long given up and moved on to games that don't make them pull their hair out. It's probably affecting a very small segment of the playing population at this point... but I'm still trying to get the word out.



Hey Spore, presume NOTHING. Post your video and logs and anything else you can. If you ran into this bug, that means you fly with friends and if you give up it'll never get fixed! You're fighting the good fight, my man! Keep it up! o7

Click to expand...

i've been trying to get this fixed since the first bug but have been facing incompetence at every step https://forums.frontier.co.uk/showt...-low-LOD-when-in-a-wing?p=5409769#post5409769
 

ElectricZ

ElectricZ
ElectricZ said:
Please, FD, look into these issues, and if you as a CMDR have run into these issues post in this thread, file a bug report, make some noise about it while Frontier is still putting out patches for 2.2.

Otherwise it may not get fixed until 2.3, or ever. :(
Click to expand...


ElectricZ said:
Please, anybody who's encountered this problem, speak up about it. To reiterate, it's been around since at least May with the release of 2.1.0.3 and has not been fixed for seven months. If it doesn't get fixed with the next hotfix release, it probably won't get fixed until 2.3 in 2017.
Click to expand...

ElectricZ said:
Well, huzzah! A minor victory at least... Thanks to IPL Victim's bug report in the 2.2.03 forum, we finally have acknowledgement from support that this is an issue and it's being looked at!

Unfortunately, in the same message: "2.2.3 beta is specifically focused on changes made to Engineers, powerplay and combat."

Does this mean that they're not looking at patching to existing problems as well? 2.2.03's patch notes seems to cover some issues unrelated to Engineers, powerplay OR combat. Certainly they could get this on the list.

If not, and it is put off until 2.3 or beyond, it will be quite vexing.
Click to expand...

ElectricZ said:
I guess I'm going to. Wait for 2.3, that is, but how far away is that? "Playing my way" means flying in a wing with a friend, and it doesn't work for me. Missions are also a huge source of fun, and have been effectively borked for months now as well. Reading all of the bug reports and threads on that, they're not getting fixed anytime soon either.

http://images.clipartpanda.com/famous-american-history-pictures-whiteflag-300x180.png

See y'all after 2.3, maybe.
Click to expand...

ElectricZ said:
Well this is disappointing. So this is an issue that originally appeared with the 2.1.0.1 or 2.1.0.2 patch way back in May of last year... one year ago, and it is still a problem. My last response to this thread was a plea to try and get someone at Frontier to look at this before the next major patch hit in January. Here it is May, after 2.3.0.01 and it's still a problem. One year after it was first reported.

Bear in mind that this issue did not exist in 2.0. These issues with wings were introduced with the 2.1 patch and still exist today.
Click to expand...

So this thread is now 11 months old for a problem that was reported in May 2016, Introduced in 2.1 and unpached through 2.1.X, 2.2, 2.2.X, 2.3, 2.3.X... and is still unfixed in Beta 2.4.

I know I'm repeating myself here, but if you are facing this issue, please update the tickets in the support forum for it, and if you're in Beta, update the one I put in the Beta Bug forum.

Otherwise this won't get fixed until 3.0 (or later.) :(

This is a recording.
 
Last edited:

bennysheen

B
All I can do is reply and hopefully provide some kind of "bump"idge to this thread.

I agree with everything being said here ever since the first patch post Wings seemed to break everything.

I admit that it has significantly improved, but I still occasionally get dropped out of SC many LS from where my Wing buddy dropped and the rotational bug I thought had been fixed has (infrequently) reappeared.

I can also remember spending a number of days using the new extended network logging feature and collating all the information from two of my Wing buddies and submitting it as a ticket through the official channels - never really got much of a response from it though.

Happy to keep this thread updated until this is fixed :)

Cheers and fly safe (leave your Wing beacons off though!)
 
Last edited:

Alec Turner

Alec Turner
bumpsahead250.gif
 

StevieG

StevieG
Oh the days of 1.4 when wing beacons worked.

Wing m8 at station.... doesnt use wing beacon as it bugs out.

Wing m8 in RES.... doesnt use wing beacon as several bugs makes you not drop on wing m8.

I think most of Delta Squadron would have preferred wing beacons to be fixed rather than what was delivered in 2.3.
 

ElectricZ

ElectricZ
Fighting for a lost cause at this point, I guess. 2.4 Beta 3 has been released and it sounds like they're getting ready to go live. So I suppose that this thread will go dormant, into hibernation until the next update rolls around in 3 months? 6 months? A year? and we try again.

The number of people playing cooperatively in wings is probably a very small percentage of the entire playerbase, which makes this low priority. Of course it's a vicious circle in that regard, and a self-fulfilling prophecy for Frontier Dev akin to CQC and Multicrew where they've said "we'll expand on it if people use it." People who want to use it will participate enthusiastically until issues take the fun away. People stop participating. The devs look at the numbers, see participation is low, then de-priortiize development in that area, justifying letting it wither on the vine because there's so little user activity.

Sad to say, but I take some consolation looking at the mega Beige Plague thread with all of its pages and supporters through the community. They've been railing for a fix to that issue for almost as long and have gotten nowhere, other than an admission from FD that what happened to the graphics was an attempt to improve performance. That's at least an explanation. Maybe the same thing happened with Wings. Maybe by attempting to fix connectivity issues they changed the core netcode which improved performance for most players but broke wing nav lock functions and it will take a massive re-write to correct.

Maybe. Sure would be nice to hear it from the people who can actually fix it beyond "Thanks for the report. We're aware of the issue."

I shouldn't say it won't be fixed until 2.4 is actually released. Maybe they'll pull a rabbit out of the hat, get in a last-minute miracle fix and nav lock will be fully functional and useful again, but the track record thus far is not so good. So I'm gonna go ahead and get this posted so I can add this to the self-quote block a few months down the road:

Guess we'll have to wait for 3.0. :(
 

Chrysophylax

Chrysophylax
ElectricZ said:
So this thread is now 11 months old for a problem that was reported in May 2016, Introduced in 2.1 and unpached through 2.1.X, 2.2, 2.2.X, 2.3, 2.3.X... and is still unfixed in Beta 2.4.
Click to expand...

Quite sobering. I've never kept track of my favorite bugs, but 11 months holy moly. I don't think I want to start now
 

ElectricZ

ElectricZ
hnCFsqm.gif


Wow! Look who's back in 2.4!

Source Video with Bonus Scan & Ram (another fan favorite) at the start. Nice to see our Xbox cousins enjoy the gameplay parity as us PC types.
http://xboxdvr.com/gamer/fude poof/video/37455730

Anyway, for those of you keeping score at home, we're like 0 for 6 in getting this fixed via update since 2.1 way back in May 2016. I know in this day and age of Thargoid Adaptation and Mission Payout scandals this is not a big deal to most people, and it certainly doesn't hold a candle to the Beige Plague as far as severity, but this will always be near and dear to my heart, because it will apparently never be fixed.

As usual, report it if you see it yada yada yada or else we'll be singing this same sad song after the next update blah blah blah.

This is a recordin- skip
This is a recordin- skip
This is a recordin- skip
This is a recordin- skip
This is a recordin- skip
 
Last edited:

Kizbot

Kizbot
I'd love to be proven wrong on this but to me it seems that they have looked at the report, looked at the code for 30 mins, not found the problem and then just chalked it up as 'too expensive to fix' then carried on current task of nerfing something.
 

Azmuth Divarchchron

Azmuth Divarchchron
A friend of mine told me you mentioned my post, and I can confirm that the wing beacon issue is still present in 2.4, navlocking a beacon will almost always prevent rotational correction in a station among other issues.
 

ElectricZ

ElectricZ
I know this will come as a complete shock to everyone who is tired of seeing this thread pop up after every update from over a year ago, but nav lock issues are still not fixed in 2.4.08, including my favorite, the Docking Swirlie.

If it's any consolation, I'm tired of posting about it. But here we are again.

Broken-record.jpg


See you all in Beyond, I guess.
 

Kaocraft

Kaocraft
Hey Frontier I still want to be able to play your multiplayer game with other players too. How about giving this issue the attention it deserves?
 

Susanna

Susanna
ElectricZ said:
I play ED almost exclusively co-operatively in a wing.

I have come to grips that co-op missions weren’t a part of ED even with the introduction of Wings in 1.2 in March of 2015.

I have accepted that there is no built in way to share mission rewards with friends when helping with a mission, and that if I want to give payment to someone I have to buy 50 tons of platinum and eject it for them to pick up, or vice versa, and that it’s such a pain in the butt it’s not worth doing.

I have accepted, over time, that sometimes the internet just hates you and getting in the same instance with a friend won’t happen, or that even if you do you may not see the exact same enemies.

But for the love of Braben, I can’t accept that Wing Beacons/Nav Lock has been broken since 2.1 and has still not been fixed in 2.2. It's been five months since a primary multi-player feature has been broken in this multiplayer game.

The issue: when a wingmate activates a wing beacon, other pilots are supposed to be able to engage wingman Nav Lock to lock in on the wingman’s position so CMDRs can link up for navigation, salvage, sightseeing or combat purposes. This worked fine, most of the time. Your buddy gets interdicted? You can drop in to help. Your buddy has the same assassination target as you? You can drop into the instance and work together to take it out. You want to get together outside of a RES to mine? No problem, the first one in drops a beacon and the rest of the wing can join in.

Except now, you can’t. Ever since 2.1.0.X, released back in May, the using the Wing Beacon is useless at best, and can get you killed at worst.

1. Dropping connections/crash to main menu from wings during high/low wakes
2. Dropping to wing beacons in current position rather than the beacon position, often millions of meters away.
3. Rubber-band snapping back to the beacon location if the nav lock is not turned off and you low-wake away
4. Positional drifting caused by a wingmate's location changing, most evident when trying to dock at a station in an instance where a wingmate has already docked, resulting in a pilot's ship moving like rotational correction is off, making docking nearly impossible without relogging.
5. Wingmate does not appear on scanner, only the wing beacon, which skips around the scanner as the wingmate's position updates every few seconds.

According to this response in this thread, at least the connection issue is resolved:



After playing for 3-4 hours in a wing last night, issue 1 may actually be fixed (hallelujia!), but I can confirm issues 2-4 are alive and well and frustrating as hell. #4 in particular can get you killed in a hurry from scraping you into the walls of the station, or getting you blown out of the sky for loitering.

https://youtu.be/gs_eIlmws3c?t=70

Bug reports have been filed since May. Port forwarding/firewall config isn’t the cause as these issues did not happen until the release of 2.1. Something got broken and needs to be fixed.

https://forums.frontier.co.uk/showt...out-of-supercruise-unexpectedly-while-in-wing
https://forums.frontier.co.uk/showt...ips-appearing-Offset-from-their-True-Location
https://forums.frontier.co.uk/showthread.php/256026-Inside-Station-has-low-LOD
https://forums.frontier.co.uk/showthread.php/267405-Landing-rotational-correction-bug
https://forums.frontier.co.uk/showthread.php/267392-bugged-station-drop-with-nav-lock-(wing)
https://forums.frontier.co.uk/showt...on-doesn-t-work-inside-stations-while-in-wing
https://forums.frontier.co.uk/showt...on-bug-collision-Texture-bugs-(Claim-request)

Please, FD, look into these issues, and if you as a CMDR have run into these issues post in this thread, file a bug report, make some noise about it while Frontier is still putting out patches for 2.2.

Otherwise it may not get fixed until 2.3, or ever. :(
Click to expand...

OH MY GOD!

It wasn't until I got to the end of the first post (when ElectricZ refers to not getting fixed until 2.3), that I realised this wasn't a recent post... It's over a year old! :eek:

I thought that this was a very good summary of the mess that is Wings! Repped.

I hope that making enough noise will get this finally fixed (worked for me with the DC thanks to AJS). Filing a Bug report clearly does 'Bug'ger all...:x
 
You must log in or register to reply here.
Back
Top Bottom