Quote:
|
Originally Posted by drEaPer
Their subs both had an ESM contact, so they went to PD to exchange their info. Then they wanted to merge them in TMA and found out that it didnt work. I told em that they can make a manual solution and merge that, but they werent really satisfied with that.
What made them also go crazy, was the fact that they couldnt tell the NavMap to merge their ownship contacts with the links data contacts. They just didnt understand why they should have so many stuff on their screen when they exactly knew that a certain Ownship contact was the same contact that is already on the link. They asked for an option to tell the TMA: Take link No.XXXX as a solution for M02. I told them it doesnt work that way but they were just annoyed by having the same ships multiple times on their nav maps and when trying to select a contact that was under another contact (link) they had to scroll in and out alot. They were also confused about the fact that a link contact has a different number for different players, and that made communicating harder.
What they also didnt like was searching the USNI reference for a certain ship, cause the ESM didnt tell em the country origin.
|
My suggestion is if you have have both your own data and link data, use the link data to confirm what your own sensors are saying and then Drop the link data to keep clutter from building. Or alternatively, use the link to refine their own TMA soluations and then chose "Hide Link Data" to free up clutter. Other than that, its up to them to learn their own methods of keeping things clean and organized..... I use link data only when confirming my own data or only when I'm ready to fire.
I agree with XabbasRus, a lot of DW is taking two or three steps to piece together information, whether than just a one button solution. That and dealing with significan fog-of-war and sensor ambuiguity and information clutter, which most people don't like.
The bugs are a little annoying I agree. Hope that they give it a second try.