NEVER EVER!
I want FDev to add a take-off permission procedure!
... and docking fees.
... and a button to boot up your ship.
Last edited:
Do away with request for landing.
- Thread starter dunno
- Start date
NEVER EVER!
I want FDev to add a take-off permission procedure!
... and docking fees.
... and a button to boot up your ship.
With that I agree.
Yes please.
There are a lot of really really bad ideas that are frequently suggested in this forum. This is one of those.
This^
Or a message 2 km from the station - "You've forgotten again, haven't you? You muppet."
Nope Seldom happens as in my previous life I had to ask for landing clearance all the time. Should it occur it's no big deal as my final approach is stable and the vector is straight ahead, On the rare occasion (T9) that I've forgotten I hit max reverse and slide out no problem, easy as pie.
I'm thinking that it would be simpler and elegant to remove the docking request altogether, as one enters the aperture get "PAD Allocation". and at 7.5k's get "docking denied Pad Occupied" if the station is busy.
But never mind, "nothing to see here move on"
)
Last edited:
Nope Seldom happens as in my previous life I had to ask for landing clearance all the time. Should it occur it's no big deal as my final approach is stable and the vector is straight ahead, On the rare occasion (T9) that I've forgotten I hit max reverse and slide out no problem, easy as pie.
I'm thinking that it would be simpler and elegant to remove the docking request altogether, as one enters the aperture get "PAD Allocation". and at 7.5k's get "docking denied Pad Occupied" if the station is busy.
But never mind, "nothing to see here move on"
This is the weirdest backpedal I've ever seen
I haven't retracted anything. Weird ?, because I've conceded that most don't want the change, merely a idea I thought I'd put out there. Shyte idea no problem, "I'll move along nothing to see here".
Last edited:
That's not the correct response. You're supposed to go down in noble flames to the bitter end, holding your idea aloft like a beacon to the next generation of idea posters. Did you not get the protocol memo?
EDIT: Because I had a real thought about the idea. >__>
Autorequest would constantly mess with people like myself who like to bomb around the station exteriors practicing hi-speed maneuvering amongst the solar panels and such. I'm ambivalent about a hotkey since my docking request takes all of 1.5 seconds even adjusting muscle memory to the new button arrangement.
Last edited:
Lol we need to see if burke has a copy of that memo he can fax over to the OP. I'm on ps4 and requesting docking takes about the same time and is super easy. A key bind as others said sounds cool though and would drop that down to less than .5sec but the system as is works fine.
Last edited:
Please ensure that the cover page is a black page
)Now *that* would be helpful.
That actually makes more sense than how I understood your first post. It wouldn't work for outposts or planetary bases though and might be counterproductive if it breaks the habit of asking.
Combining these ideas though, you could get a message at 7.5 km if there are no pads available and one at 2 km or so if you haven't asked permission. That would be a lot more useful than telling me to continue on my current vector when I'm headed in completely the wrong direction.
Actually the idiot NPC pilots put lives at risk anyway. They make no effort whatsoever to avoid collisions and when there is an 'incident' the player character gets the blame and the fine.
And in RL, I have personally flown in busy aerodrome circuits where there is no ATC. I dunno if you have those kinds of airfields in the US; likely you do. But as long as all the pilots keep a running commentary as to their positions in the circuit, to maintain situational awareness (SA), it all runs smoothly. I once flew in a circuit where it was like the Battle of Britain with aircraft all over the place, but because the pilots kept their SA up to date it all was all kosher.
Last edited:
yeah NPC behaviour could use a bit of fixing near the station and in actally recognizing that a corvette can make your adder go poof
I love requesting landing permission.
I also love the blind panic when I forget.
Please don't take that away.
I also love the blind panic when I forget.
Please don't take that away.
Add another no to removing the request.
Definitely "no" to removing the request.
However, there shoudl be a "no fly zone" on the approach to the docking slot which extends further out than at present and has 2 zones; the first zone (further out) is where you'd get notified of trespassing (but no fine) if you don't have docking authorization, the second zone is where you get fined for trespassing.
Having the "trespasss-and-fine" notification within the mailslot allows very limited room for maneuvering to exit within the time limit.
More realistically a "no fly zone" would extend all around a station, but that would stop people from being able to race around the superstructure of stations which is "fun".
However, there shoudl be a "no fly zone" on the approach to the docking slot which extends further out than at present and has 2 zones; the first zone (further out) is where you'd get notified of trespassing (but no fine) if you don't have docking authorization, the second zone is where you get fined for trespassing.
Having the "trespasss-and-fine" notification within the mailslot allows very limited room for maneuvering to exit within the time limit.
More realistically a "no fly zone" would extend all around a station, but that would stop people from being able to race around the superstructure of stations which is "fun".
Only if you speed.
Yeah, a Type 9 or 10 does a pretty good job of ramming those Belugas out of the way. Just do it at a sensible speed and the station will tell you off without fining you.