As of now, the only potential oddities I can find are a notable lack of collision detection on planets (even with working cameras and sensors and proper settings enabled in the Custom Data), and that the script seems to hate the idea of having a minimum altitude set in the Custom Data. Every time I have the altitude set to 0, everything works correctly. However, changing that number causes the navigation systems to become wonky. This could be an issue of correlation and not causation, but it seems to be worth mentioning. Beyond that, the script is working extremely well, and I greatly appreciate your hard work in creating it.

Parameter in CustomData is MaxWorldMps

Written, minor testing and updated.

You'll need to change the SpeedMax parameter in CustomData and also specify the higher speed in the nav commands

@Wicorel I'm using Configurable Parameters, but I'll also do a test or two with a different speed mod. I suspect part of the issue is some stubborn memory storage that doesn't want to be modified after the first run. Some of the issues I have will get resolved by removing and rebuilding the programmable block itself. I'll do further testing and update you.

hmm. which mod are you using to increase speed? I'll test with that.

So far, no major issues with navigation within or outside of gravity. The script is doing an excellent job, and I'm excited to work with it further.

One odd thing, though, is the apparent inability to set the maximum travel speed to a number higher than 100 m/s. Also, running "S 0" apparently enforces the max speed to in fact be 0 m/s instead of removing the limit.

Updated yesterday to fix the issues with navigating in gravity.

Let me know if anybody finds any more problems or has feature requests.

@Wicorel Sorry to hear that it's being a problem. I'm greatly looking forward to using this script as a drone autopilot whenever it gets fixed. Outside of the glitchiness, your script is, I believe, the best autopilot I've found to date.

some luck, yes. but I found more issues.

Seems like I hadn't tested in gravity for a while.. :(

(and I have busy work schedule recently)

@Wicorel Have you had any luck with the script weirdness? If not, that's totally fine. I was just curious.

@Wicorel Yes it had wheels, that comment was before I relished remote control block don’t work with wheels.

@Wicorel Here is a test save to show you what's happening:

https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2796084049

I added what information I could into the description.

@death3574 what kind of rover are you making?

This script does not do wheel propulsion (yet); only frictionless wheels with thrusters.

It should. 155 is the initial alignment towards the waypoint. It tries to keep gravity and target alignment.

Can you send me the world where you're having the problem? Or the ship blueprint and which planet you're on?

Is this script capable of functioning on planets? If so, I seem to be having major problems getting the navigation to work. Space navigation runs like a dream, but when even the slightest bit of gravity comes into play, the autopilot gets stuck at state 155 and cannot do anything except jitter back and forth. Any assistance you could provide would be greatly appreciated.

Hello Wicorel Could you make a tutorial for this I can't seem to get this working for my rover?

D is arrival distance. it's the distance from the waypoint that is considered 'good enough' to stop navigating. Very low numbers (like 1) can cause seeking behavior especially on large grid ships.

I'll have to check code for the align distance. I thought it took ship size into account...

hi Wicorel, is it possible to change height before drone starts aligning with connector, it seem to be fixed at 10m. i want to increase it, since large ship collides with connectors.
Also what is the role of D argument? i tried changing it but i did not see any changes.
Thanks

Thanks. I've updated the published script and that error should be fixed.

Nav is crashing with , UNKNOWN COMMAND and then index out of range