Newcomer / Intro What are you up to?

Well, that Mig (according to Wikipedia - and that means unless the specs there aren't the real specs) tops out at 670 m/s.
Which is 200 miles per hour quicker. The Mig 29 would literally go past the Mamba like the Mamba was sitting still.

And we're talking about an additional 2,000 years of advancement in technology in a zero gravity environment with no atmosphere in the Mamba's favor.
 
It was behaving oddly earlier, pressing F10 was taking high res screenshots as though things had gotten stuck with a toggle (alt) on... But other keybindings are as normal, just I swear Z is not what I had flight assist set to. I think that is the default, and I possibly touched it instinctively on the way down because the landing computer was stuck and I haven't used FA-off since running some CZs in January...

Which does make me feel that had the landing computer worked I wouldn't be in this state 😾



Yeah, I have submitted a ticket explaining that I had an unexpected loss of control resulting in losing weeks of scan data and asking if they can maybe put me back where I was. For now, my rebuy is parked in Jameson and I'll just not touch anything.

--

The worst part is I had just turned around to head back and hand it all in. Just 30 mins previously I'd hit the "deepest" star I could reach, with the next one being ~220ly away. Job done, mission complete, black sky seen. But for some reason, 32 jumps from home, I just wanted to go land on that really hot metal rich planet and see if it had any needle crystals 😾

I'm very demoralised right. I know none of it "matters", it's all numbers on a screen, I was only going to turn the data in for faction rep in my weird quest to get an ally in most of the bubble systems. None of it's real; but it's just suddenly having weeks of investment towards those numbers get erased in such a way. Crashed my mood something rotten.

Tell you what though, it has reminded me again that exploration is the riskiest part of the game. It's not CZs or PvP, it's the ability to lose weeks-months of your time with a single event. It doesn't feel right to me that we can lose all that with no checkpoints. Why do we get first landing tags immediately but scanning and discoveries need handing in?
FWIW, I spent 2.5 months out in the black, died, went right back at it for another 3 weeks, died, went right back at it for another 3 weeks and when I was on my way back, died again...4 months with nothing to show, I've found other things to do in the game, well I do pretty much everything...now that I have a carrier, I'm back to exploring...

In all three cases it was my fault:
  1. Accidentally hit boost while looking at a ground feature and scraped to death up the side of the canyon...

  2. Parked too close to a neutron star while I was repairing my ship priort to jumping...

  3. Got distracted by real life, when I got back to the PC the next morning, I had died 30 minutes prior...assuming I ran out of fuel...
Exploration is the most rigorously demanding game-play in ED...one little mistake is all it takes to lose everything.

Maybe Support will help you out...but I doubt it...

My condolences...
 
B92
6pc7dHkh.jpg

The aptly named B92, the jewel of B92 Sector, is one of those you have to hold up against the durn Milky Way to see. 3308-09-04


I'm concerned that you may be right...

But I think if that's the case, my question is: why can you launch with FA off? Under what circumstances is launching with FA off not much more dangerous than with FA on? Why does it not reset on landing as common sense might expect?

Well, It's more dangerous than with FA on when you stop thrusting upwards (and gravity takes over), I reckon :).

You may recognize it now since it's just doing what you say but carries the velocities.

Hats off for your loss CMDR Nekoszi. May you saddle back up and make many more discoveries! Perhaps after a return to port for some retrofits after your time in the black. Good luck!
 
why can you launch with FA off?
One would assume that the choice is there for those who fly exclusively FAOFF.

I unbound the FAOFF key entirely, because I never use it. If I need it sometime, I'll rebind it :)

But perhaps the real problem here is the longstanding one of the game not warning you when it can't find an input device, or the device is interrupted, etc., and then silently changing you to one of the default binding schemes.

I've had this happen before. In my case, my normal bindings are nothing like any of the default schemes, so I noticed right away.
 
As far as I know, it's on press-and-hold mode so it should have been hard to have on by accident. At 10km altitude I even tried to zero the throttle, go to menu, lower mouse sensitivity and return; I got back just before it hit the deck, but I still had no control. How did it hit the deck with zero throttle set? 😾
I just remembered something, they put out a tiny update a couple of days ago. I remember because I had left Steam and the Odessey launcher open and started playing and it wouldn't exit the FSD tunnel, so I went to the Steam app to check the game files for corruption and noticed the update queued.

After letting the update install by closing the launcher and manually updating Odessey, I started playing again. Some (not all) of my bindings had been reset to stock and in game my plot had disappeared and the system that I already scanned I had to do again in the FSS scanner. I was going to ask if anyone else had issues but took a day off and didn't play.
 
One would assume that the choice is there for those who fly exclusively FAOFF.
I recently changed mine from hold to toggle...it makes some things easier...like cutting a line across the mail slot and engaging auto-dock and zeroing the throttle at just the right moment...not having to hold that button is helpful.

I unbound the FAOFF key entirely, because I never use it. If I need it sometime, I'll rebind it :)

But perhaps the real problem here is the longstanding one of the game not warning you when it can't find an input device, or the device is interrupted, etc., and then silently changing you to one of the default binding schemes.

I've had this happen before. In my case, my normal bindings are nothing like any of the default schemes, so I noticed right away.
(y)
 
Some (not all) of my bindings had been reset to stock and in game my plot had disappeared and the system that I already scanned I had to do again in the FSS scanner. I was going to ask if anyone else had issues but took a day off and didn't play.

Interesting... There was a point not long ago where I had a similar rollback. Disconnected, then was 2 systems further back and had to re-do my scans. I didn't notice any keybinds out of place, but now I wonder...

I unbound the FAOFF key entirely, because I never use it.

For me, it would literally be only trying to land on a 1+ G planet. You don't thrust down, you just tap FA off for a fraction of a second to lose a few metres.

Except it looks like it didn't tap, it toggled. Which I absolutely swear I have never intentionally set to happen because it is certain death. It wasn't even on that key last I knew 😾
 
Last edited:
Interesting... There was a point not long ago where I had a similar rollback. Disconnected, then was 2 systems further back and had to re-do my scans. I didn't notice any keybinds out of place, but now I wonder...



For me, it would literally be only trying to land on a 1+ G planet. You don't thrust down, you just tap FA off for a fraction of a second to lose a few metres.

Except it looks like it didn't tap, it toggled. Which I absolutely swear I have never intentionally set to happen because it is certain death. It wasn't even on that key last I knew 😾
Z, AAFAIK is the default key for FA Off, at least on my client...
 
~9 hours after losing about 2 months worth of expedition data to a freak planetary lithobraking event, I've been through disbelief (that did not just happen!), anger (how dare it! happen!), bargaining (hey support any chance you could...) and depression (that's it I'm done with this game forever).

I haven't quite given up on the bargaining part, I'll see if support responds, because I do feel pretty hard done by after a landing computer screw up (it completely froze and didn't move or let me move the ship until I disabled the module) left me taking manual control, during which I thought I was tapping FA off and instead of it was fully toggled off, a state which persisted until launch and... well. Yes, FA was set to toggle mode. No, I would never have chosen to set it to toggle because I know that this mode is certain death. Something is amiss here.

OTOH, if I remember right, the first destination on this trip was a system I got dibs on ~3 years ago, and which had still not been fully scanned, and in which is now a hexa-bio ammonia world. I'll probably still have first footfall, but it probably won't be scanned. One way or the other, I'm claiming that thing properly. It's bookmarked, it's about 40 minutes out in a fast ship; I'm not giving up on it.

Don't get me wrong - I'm salty. I still don't know for sure it was a flight assist issue, but that is currently a strong candidate. I do not like that you can launch with FA off because I feel like that is 99% harmful and 1% useful, and as a professional software dev I personally would always flip the default state on that kind of weighting!

But I shall not throw in the towel yet. At least I get to keep all those materials I harvested. Because scan data doesn't transmit, but polonium does.

This game is weird.
 
As far as I know, it's on press-and-hold mode so it should have been hard to have on by accident. At 10km altitude I even tried to zero the throttle, go to menu, lower mouse sensitivity and return; I got back just before it hit the deck, but I still had no control. How did it hit the deck with zero throttle set? 😾
Gravity.
The Planetary Landing Suite allows the thrusters under the ship to compensate for local gravity but the higher the gravity the more they struggle, if your ship isn’t level above the surface so that the thrusters underneath the ship aren’t doing most of the work your ship will fall.
If flight assist is off the gravity compensation is also off and your ship will start to fall, this can be used to land in tricky locations and on high gravity worlds to avoid having to thrust down which can lead to too high a descent speed.

I had disabled my docking computer because it had gotten completely stuck trying to land and was just hovering for over a minute without moving. Landed manually, hadn't turned it back on - but it's a docking computer, not a take off computer. As far as I know, I hadn't just disabled flight assist that way.

Maybe I should have done the old immediate exit and relog Horizons trick, idk.

Submitted a ticket, asked if they could reset me. I will happily jump back in if they can sort me out, but I'm not sure I've got the will to start with all that again after such a loss. If FDev support doesn't help with things like this, I never want to explore again, and that's 90% of my gameplay.

--

Edit oh god... I checked the game settings. Flight Assist is on toggle and on Z... that's not the button I set! I have it on Mouse 4 as press and hold! Why are my bloody keybinds not how I set them? I must have clipped it by accident :mad:
If some controller, mouse?, was plugged into the wrong port the game wouldn’t fully recognise it so would load the generic bindings.
Arguably I have nobody to blame but myself. Although I would say, if FA stays off between landing and launch, that's a noob trap. You should never get a launch with FA off by accident.

I'm concerned that you may be right...

But I think if that's the case, my question is: why can you launch with FA off? Under what circumstances is launching with FA off not much more dangerous than with FA on? Why does it not reset on landing as common sense might expect?
There are some who fly FA off all the time, their complaint used to be that when the game starts it defaults to FA on, I don’t know if this is still the case for ships.
 
On my way back to my carrier in my new Miner T9'er carrying 576 units of Tritium. I'm 10% of the way there, only 190 more jumps to go....

View attachment 320614

I shoulda fit a bigger fuel scoop...

Oh my darlin
Oh my darlin

Hey that's brilliant did you name it Clementine, and take it to planet Clementine, and paint it orange? That where that line's from?

I have a T-9 usually idle, disguised as a banana transport. It's a right fruit salad shapin gup

sorry I didn't fill out both replies originally. SURPRISE!!

One way or the other, I'm claiming that thing properly. It's bookmarked, it's about 40 minutes out in a fast ship; I'm not giving up on it.

Yeah!! Hey you know about the time I started letting myself read these forums, for not wanting to spoil the game really, was about the time of the demise of rupee noon the 25th. I felt similar, no doubt of my own fault though; but thanks to having bookmarked my most exciting find, mollusks, I returned there recently and reported it. Felt great!! And, what I was even more recently talking about above, is I'm going back there to look at it some more, at this very time, going to see "my" stellar phenomenae in Smojai. :)

Hurts huh!!! Yours was farther I know.

Go get em Nekozji!!
 
Last edited:
If some controller, mouse?, was plugged into the wrong port the game wouldn’t fully recognise it so would load the generic bindings.

I can say absolutely nothing changed in hardware between that planet and the previous one less than an hour earlier. It is possible that the error was I toggled FA off without meaning to.

But I don't know for a fact that that was the problem; last I knew the FA toggle was on the mouse and in hold mode, but checking control options it was on Z, which is absolutely tappable by accident when trying for a vertical descent (for me, S is thrust down so adjacent keys). Or maybe the game just screwed the heck up and multiplied mouse sensitivity by 10 for no reason. It had been messing me around with F10 deciding to do high res screenshots instead of requiring alt-F10, and it hurtles around the galaxy and system maps in hard-to-control ways already. Doesn't seem implausible that it just messed up in the cockpit today.

I'll bounce back from this, but I will remain angry for a while. If it's a FA issue, then I feel like the ship should be screaming at me that it's in "you'll probably die mode" unless I go to a panel menu and turn that warning off. Most people do not mean to launch without FA. I respect that there are those who do, they should have an option to turn off the warning, but that becomes a double step check because it's incredibly dangerous to do this. It's up there with instant, permanent file deletion without confirmation prompts 😾

I just don't feel like exploration should be the highest risk activity in this game. It's already the lowest reward...
 
Back
Top Bottom