Don't worry. I'm in there too - although that probably just makes things even more scary.
Last edited:
Cannot Comply
- Thread starter Gordon Hartley
- Start date
Don't worry. I'm in there too - although that probably just makes things even more scary.
This guy gets it. If we don't learn from our mistakes, we make more mistakes. We do slowly improve, but we also regress. I remember the time before they started color coding the different ports and uses you could accidentally plug your mouse into the monitor port and vice versa and the computer wouldn't boot and yet nothing would appear obviously wrong.
So you have a big vague message in the top right telling you to look at the smaller information in the bottom right?
This is a minor issue most of the time, and I can understand the where the 'duh' comments are coming from. At least its generating interesting discussion.
However I don't want to mess around remembering if its hardpoints or hardpoints and scoop or just scoop if my shields are rapidly approaching 0%, I just want to jump away with miminal opportunity for any mistakes trying to put the right thing(s) away one at a time whilst freaking out about whether I'm about to die.
Maybe I'm the only pilot who occasionally deploys hardpoints instead of retracting the scoop, or opens the scoop instead of retracting hardpoints before jumping after scooping after combat, but I doubt it. During unexpected combat, this is a lot more of a concern.
Last edited:
Please don't take my previous comment to heart mate, I was just havin' a sarcastic moment.
I completely agree, players need warnings if anything is and what is deployed while trying to initiate an FSD jump.
Just an idea off the top of my head would be to have hard points, etc. automatically stow away when initiating a jump. But that might possibly cause a few problems during combat etc. So maybe a 3 second countdown before stowing hardpoints, landing gear and/or cargo hatch or even a warning like you get when you have an SLF active while initiating a jump.
Sounds good to me, suggest it please
I think we're all saying, they forgot one of the 3 lights, so put the 3rd one in the obvious spot that Greasetrap42 indicated. It's not like they have to rebuild things, or even change the layout. Just put the one in that they forgot. If it were a real ship, with a physical dashboard, modders would be drilling a hole there, and sticking a LED in it, with a tastefully printed label saying "Hardpoints".
As a person that worked in IT fixing home computers I can assure you that for the average user that made no difference at all!
can i have your ... never mind, just joking.
you do have a point. i'm looking forward to your reaction when you discover the sublime nuances of cockpit modes, though. you're going to love that!
I made this suggestion about a year ago.
https://forums.frontier.co.uk/threads/ship-status-for-engaging-fsd.531862/
The hardpoint indicator is the whole hud being covered with lists of weapons available on each trigger, on a ship like an Anaconda it is sort of obvious.
On the original issue, while a more specific message would help, I like the idea I saw a few months back (can't remember who said it now, sorry) of having the option to double-press "activate hyperdrive" and have it automatically retract scoop, gear and weapons.
If you try to enter hyperspace and it doesn't work for reasons other than deployment of modules, the message is not "cannot hyperspace: no target / target obscured / target out of range / drive offline / drive destroyed / insufficent fuel / mass locked", leaving you to figure out which applies - it actually says which one of those things applies.
The UI is:
It's better than it was in 2.4 - where additions for features since 1.0 had been piled up on the original (fairly good) 1.0 design to breaking point - but it still needs a lot of work. It shouldn't be controversial to point that out, even if most experienced players have been using it so much that they just reflexively work around and see through all the various issues.
Sure, and the solution to the "cargo collected" warning overlapping the scoop UI for several seconds is to wait several seconds before scooping the next thing, and the solution to the FSS warning messages being huge is to just ignore them entirely, and the solution to module damage being quietly reported buried in a side panel is to submit tens of bug reports about the Contacts panel not working because it's not at all obvious your sensors have been destroyed. (A simple "Sensors offline" message in the contacts panel, if they are, would do a lot!)
If you try to enter hyperspace and it doesn't work for reasons other than deployment of modules, the message is not "cannot hyperspace: no target / target obscured / target out of range / drive offline / drive destroyed / insufficent fuel / mass locked", leaving you to figure out which applies - it actually says which one of those things applies.
The UI is:
- highly inconsistent about the priority with which it reports messages relative to their actual importance
- fails to set sensible defaults for several things, requiring manual changes each time (from wing beacons to cargo pickup/drop amounts for missions)
- has occasional missing options (e.g. you can't filter by Pirate Attack state on the galaxy map)
It's better than it was in 2.4 - where additions for features since 1.0 had been piled up on the original (fairly good) 1.0 design to breaking point - but it still needs a lot of work. It shouldn't be controversial to point that out, even if most experienced players have been using it so much that they just reflexively work around and see through all the various issues.
Yeah, but for the people that were above the average user level, they understood the value immediately and never wanted to go back. Connect green to green and not green to purple. Win.
Ok, this guy gets filed under people who see the situation similar to me. Woohoo.
Ok, this guy gets filed under people who see the situation similar to me. Woohoo. Except he missed an opportunity to also rant about the trading screens.
To be fair, I do understand that some of these issues are also due to trying to support limited input controllers for the consoles. Some of them are not though.
I ranted about those a couple of weeks ago, though
(Separate buy and sell filters, document what the red and green supply/demand bars actually mean ... actually I'm mostly happy with the market screens nowadays compared with some of the UI which hasn't been touched anywhere near as recently)
I suspect none of you fly ship without weapons installed in the hardpoints...
I have several but I don’t recall using them for anything like Wake Scanning that requires me to operate the hardpoints.
Cobra III set up for racing.
Dolphin used as a Taxi.
Phantom nominally set up for exploration.
T9 unarmed freighter.