Autopilot to point-on-surface

[fluffyfreak]

Currently Pioneer allows for autopiloting into orbit (low, medium, high), to the vicinity of a planet/object, or into a spaceport/station.How do people feel about the ability to pick a point on the surface of a planet and autopilot right too it?I know there's a skill involved, and risk, from doing manual landings wherever you like on a planets surface but it feels like a gaping whole in the functionality that (within limitations perhaps) you can't just pick a bit of planet and set down on it auto-magically.Andy

[Luomu]

Yes, such a functionality it would be great to have in our arsenal. Go and do it :)It can be an expensive autopilot addon, hired crew feature or just plain always available (if you think it's too easy, don't use it!).

[robn]

To be honest, I'm not sure how much I like the idea of the player being able to autopilot to the surface, but its necessary functionality for the time when we want script-controlled ships to go and pick up their mining machines. So having the functionality in the engine is a worthwhile thing to do - go for it, and best of luck. (But finished the sector view highlight stuff first, ok? That stuff is like crack, I need it now!)

[doomdark64]

If theres supposedly going to be mining on planets this feature will be necassary i think.Besides for people that want to do it manually they dont have to use the autopilot if they dont want to.Regards

[fluffyfreak]

@robnI think I already did a bit.The commit you probably want is this one:[url]https://github.com/fluffyfreak/pioneer/commit/00edc86cfec1b2e587334b3e5dc0ab5f150c1506[/url] it already has some of the other stuff that I'm working on implementing, including profiling and DXTn texture compression stuff.Andy

[robn]

fluffyfreak wrote:
@robnI think I already did a bit.
A bit. The SectorLoc/SysLoc stuff seems to be sorted, but you mentioned some ideas about how to do the StarSystem caching better, and the actual heartbeat effect itself wasn't finalised. I don't see either of those there.
Quote:
However it already has some of the other stuff that I'm working on implementing, including profiling and DXTn texture compression stuff.
You need to learn how to use branches ;)Anyway no pressure from me, the code is there for anyone to pick up on in the future if you don't get back to it. The joys of open development

[fluffyfreak]

robn wrote:


fluffyfreak wrote:
@robnI think I already did a bit.
A bit. The SectorLoc/SysLoc stuff seems to be sorted, but you mentioned some ideas about how to do the StarSystem caching better, and the actual heartbeat effect itself wasn't finalised. I don't see either of those there.
Oh bugger, I think they're further up the branch, no wait, they're on "master" *headdesk*
robn wrote:

Quote:
However it already has some of the other stuff that I'm working on implementing, including profiling and DXTn texture compression stuff.
You need to learn how to use branches ;)Anyway no pressure from me, the code is there for anyone to pick up on in the future if you don't get back to it. The joys of open development
Yeah I am using a branch now for some experimental work for an idea I have. Unfortunately I'm really scatter-brained! So I end up doing 3 or 4 different things simultaneously in one branch because otherwise I get cnofused (see above) about where I've committed stuff...I'll get the hang of it!

[s2odan]

Quote:
Oh bugger, I think they're further up the branch, no wait, they're on "master" *headdesk*
You can easily fix that if you want to... Push your changed master to a new branch on your Git Repo (BranchA), then reset you Master to the official master. Now create a new local branch based on your master (clean master)(BranchB) and now pull or fetch the changes made in the BranchA to get them in Branch B.Now force push branch B onto Branch A.You now have a proper branch that can be easily auto-merged