Your updates the the nav panel throttle and now espesially replacing safe disengage ready with press y to disengage really takes the immersion out of it after 3000 plus hours the games telling me what buttons to press and its frustrating to no end. Make a hint system if you must but give us the option to disable it. Or please make all the updates to the hud optional in hud settings like a smart dev team would. Also would you please add color options to the hud like we've been asking for for literally years instead of hand holding all the noobs why not take the people who kept this game alive into consideration. And while we're at it TEST YOUR GAME BEFORE APPLYING UPDATES
HUD Updates. Many long time players unhappy.
- Thread starter Mccready
- Start date
-
- Tags
- options suggestion
Oh man, they replaced the safe disengage message with a button press in the core gameplay? Thats rather odd, and rather annoying the more I think about it.
I just cringed hard
I dont want to see that in my gameplay
Only very slightly though.As long as we're fixing the HUD, please Frontier, fix this stupid problem! -------v
View attachment 144671
Image slightly exaggerated for effect
As long as we're fixing the HUD, please Frontier, fix this stupid problem! -------v
View attachment 144671
Image slightly exaggerated for effect
That's caused by a module, if you uninstall the module it goes away.
Lame.That's caused by a module, if you uninstall the module it goes away.
Also message about docking is changed. I feel myself lost each time cause it is hard to find landing pad number on it. I used to previous message. I think pad number is important and should be in separate line.
As for subj I think the shortcut is not required. Because couple of loop of shames and pilot will learn the button but the message is crappy forever. Btw, can we have intelligent hints? Like the game sees that the player fails at the same point repeatedly and only in that case show hints. That would be really awesome. I understand development risks though.
As for subj I think the shortcut is not required. Because couple of loop of shames and pilot will learn the button but the message is crappy forever. Btw, can we have intelligent hints? Like the game sees that the player fails at the same point repeatedly and only in that case show hints. That would be really awesome. I understand development risks though.
Last edited:
yes plz; customizing hud colors in game +1
editing .xml is inconsistent / interferes with raster images!
also, would be a nice if the setting was saved to the vehicle uniquely... then i would use the original orange/blue for for mining, reds or green monochrome for fighter, blues/purples for exploration? etc.
i dunno, might be asking for too much.
editing .xml is inconsistent / interferes with raster images!
also, would be a nice if the setting was saved to the vehicle uniquely... then i would use the original orange/blue for for mining, reds or green monochrome for fighter, blues/purples for exploration? etc.
i dunno, might be asking for too much.
based on all the other customizations, engine colour, weapon coulour, I am still suprised that we cannot buy hud colour themes, that would fit with the existing customizations options we have to buy in the shop...
Supercruise disengage changes were super shortsighted on FDev's part. Players use a whole host of custom controllers for this game, its actually a ton of work to get the new "Press key X to disengage" to display correctly for everyone.
I'm using an XBox 360 controller for Windows 10, a standard Microsoft gaming device on Microsoft operating system. A "normal" choice. I'm using a slightly modified version of FDev's normal controller context setup, and have not changed the supercruise controls.
Despite this, the disengage message doesn't display ANYTHING for me. "Press to disengage."
Press what? How much do I have to bench press to disengage? Keep in mind my CMDR's arms are emaciated? When can I stop pumping my arms like this? Oh, right, I remember my controller bindings now.
I'm using an XBox 360 controller for Windows 10, a standard Microsoft gaming device on Microsoft operating system. A "normal" choice. I'm using a slightly modified version of FDev's normal controller context setup, and have not changed the supercruise controls.
Despite this, the disengage message doesn't display ANYTHING for me. "Press to disengage."
Press what? How much do I have to bench press to disengage? Keep in mind my CMDR's arms are emaciated? When can I stop pumping my arms like this? Oh, right, I remember my controller bindings now.
You mean it's a ton of work more than is needed to display this, which I see almost every time I jump?
There are many more of them too scattered here and there in the UI.
Interesting. See, I don't have that when I jump, which kind of makes my point about the difficulty of consistency due to a myriad of input options.
Edit: the controller context setup uses multiple button combos to perform certain actions, which may be why these don't display nicely for me. But it's FDEV's context menu, can't they have it display some meaningful prompt for those of us using it?!
I grabbed that from a bit of footage I took yesterday. Interestingly it didn't happen for the first few jumps. Maybe it only happens outside the bubble or only in Anarchies? That doesn't seem to make sense but there it is.
I don't believe it is input options. It might be PC vs console.
I'll have to pay more attention, maybe it only pops after a certain amount of time charging the FSD.
Then of course there's this, which you have to remember to dismiss every time you get the free camera out.
Ok, so I was mistaken; the FSD charge canceling control DOES show for the context menu setup, and it displays correctly.
So the SC disengage display just needs to be tweaked, and maybe it's not as complex a fix as I thought.
That feels like a bug to me. I thought that they had fixed that blank prompt, but it happens when you don't have a key bound to that function. See the "Ship Controls" prompt on the screenshot above. It can certainly happen with the more "chatty" messages that appear in the HUD, when you do indeed get the "Press <nothing> to do whatever" message.
I note that the SC and Hyperjump buttons can be the same key and are the same key on the default bindings. They are usually moved onto different keys by players who have enough keys because you can do things that you can't do otherwise. There are three keybindings -- both SC and Jump, just SC and just Jump. I suspect that the "Press To Disengage" message is only picking up one of those bindings, when it should be checking for both of them.
So you are correct when you say that it is significant work to do, but it's such a minor thing that I imagine they won't bother. In fact the bugged message is probably more acceptable to more players. If it works for newbies with the default bindings, then it is good enough.
Of course the players on consoles, that don't have enough keys to separate the functions, will not benefit from seeing the message without the immersion breaking binding.
Personally I don't care what that message says because I never read it. The instant I see a flash of blue, I hit the button.