Can't access the documentation on GitHub using the link left at the bottom (404 error). Perhaps you forgot to make it public?

Link fixed! Thanks for letting me know :)

Second part to Hellbent's problem, i cant seem to access the Navigation module on the git. is it not public?

@Birdler, thanks for letting me know! I have some updates to the docs coming tomorrow and will do another pass to verify links! in the meantime, documentation is available here, with the Navigation Module noted second. Cheers

https://github.com/lukejamesmorrison/mother-docs

https://github.com/lukejamesmorrison/mother-docs/blob/main/IngameScript/Modules/Extension/NavigationModule.md

I tried rotor/rotate command and found something odd.
positive values for --speed work nicely.
but negative seem to always put rotor at exactly 2 rpm (positive value not negative).

Originally posted by Liliathe:

I tried rotor/rotate command and found something odd.
positive values for --speed work nicely.
but negative seem to always put rotor at exactly 2 rpm (positive value not negative).

Thanks for letting me know! I have just pushed an update which should have fixed this :)

Hello!. I'm trying use use 0.2.1 and it does not run. Here are the errors in "check code"

Debug window[i.imgur.com]

Originally posted by croxis:

Hello!. I'm trying use use 0.2.1 and it does not run. Here are the errors in "check code"

Debug window[i.imgur.com]

Hi croxis,
You don’t need to “check code” to get the script running :) some of these are warnings caused by the build tool, but they haven’t had a meaningful impact on Mother’s ability to run in my experience. As long as you hit save and see the terminal window ticking then you should be good to go. I hope this helps!

Silly me. I forgot to put in a remote control block

Hey there. The functionality of this script is really cool but I have run into some issues after trying out navigation. Using version 0.2.3

For starters, when using a Command, I have found that there may be some kind of race condition or something with nav/set-flight-plan and fcs/start. When creating a command that first sets the flight plan and then immediately do an fcs/start, I find that it very frequently fails. Sometimes I have to mash it a few times to get it to work properly.

This gets compounded with routines calling other commands. For example, if I have a FlyToLandingSite command which sets nav to above the landing pad and does an fcs/start, then have a routine for the nav that starts a "Land" command which sets nave point to the landing pad itself and does and fcs/start --speed=2, The command line will clearly show both commands being called, that is the nav/set-flight-plan and the fcs/start --speed 2 commands in the output log, but ship won't move suggesting that the nav did not update before fcs/start was called somehow, or some other failure is happening

Also I have a FinishLanding command that is just "connector/lock "Miner Parking Connector";" but for some reason I get an invalid command format error with that and with connector/toggle even when I type in the command manually

Also, not a bug, but I found the navigation sytstem too imprecise for something like landing on a connector, for example.

Thanks for all the hard work.

Howdy! First of all, loving this script, thank you so much for all your hard work!

I found a weird issue were no matter what I set the speed to for a piston, it always moves at 0.1 m/s. Tested in both small and large grid, subgrid and main and eliminated mods to test.

Here's example (running from the command line):
piston/distance Piston 10 --speed=10

Originally posted by Sargon Dragonborn:

Howdy! First of all, loving this script, thank you so much for all your hard work!

I found a weird issue were no matter what I set the speed to for a piston, it always moves at 0.1 m/s. Tested in both small and large grid, subgrid and main and eliminated mods to test.

Here's example (running from the command line):
piston/distance Piston 10 --speed=10

Thanks for letting me know! I’m AFK until Tuesday but can patch this as soon as I’m back! I appreciate the kind words - this has been a large passion project :)

Originally posted by Riiku25:

Hey there. The functionality of this script is really cool but I have run into some issues after trying out navigation. Using version 0.2.3

For starters, when using a Command, I have found that there may be some kind of race condition or something with nav/set-flight-plan and fcs/start. When creating a command that first sets the flight plan and then immediately do an fcs/start, I find that it very frequently fails. Sometimes I have to mash it a few times to get it to work properly.

This gets compounded with routines calling other commands. For example, if I have a FlyToLandingSite command which sets nav to above the landing pad and does an fcs/start, then have a routine for the nav that starts a "Land" command which sets nave point to the landing pad itself and does and fcs/start --speed=2, The command line will clearly show both commands being called, that is the nav/set-flight-plan and the fcs/start --speed 2 commands in the output log, but ship won't move suggesting that the nav did not update before fcs/start was called somehow, or some other failure is happening

Also I have a FinishLanding command that is just "connector/lock "Miner Parking Connector";" but for some reason I get an invalid command format error with that and with connector/toggle even when I type in the command manually

Also, not a bug, but I found the navigation sytstem too imprecise for something like landing on a connector, for example.

Thanks for all the hard work.

Hi Riiku,

Thanks for this extremely robust report! I have noticed that sometimes when activating the remote control autopilot, it sometimes take a moment to execute as the remote control block enters into a path finding mode. I am working on some ways to improve this now and will take your observations into consideration as I troubleshoot and improve.

I will also explore your command formatting issue. Is this command part of the flight plan, or a local command you've defined in CustomData?

As for your note on precision for docking - I completely agree. Sadly precise autopilot is a big challenge and even with the new AI blocks, its still difficult to pull off consistently. I have some ideas on now to address this and have done some experimenting that actually does not use the remote control block or AI blocks for precise manoeuvres. Ideally, you can dock with a ship simply by using a command ie. "dock @Ship". Mother's intergrid comms would allow for the grids to share positional info (of ship and connector location) to determine a safe approach position and then gently guide the grid into position on a connector using thrust vectoring. Early days, but I'm getting there ;)

Originally posted by Agentluke:

I will also explore your command formatting issue. Is this command part of the flight plan, or a local command you've defined in CustomData?

I never put the "connector/lock" command directly into a routine for a flight plan. I tried it as a Command in CustomData, and also tried it with just programmable block arguments. I got the same error no matter what.

Originally posted by Riiku25:

Originally posted by Agentluke:

I will also explore your command formatting issue. Is this command part of the flight plan, or a local command you've defined in CustomData?

I never put the "connector/lock" command directly into a routine for a flight plan. I tried it as a Command in CustomData, and also tried it with just programmable block arguments. I got the same error no matter what.

Awesome, this should be enough to test and I hope to have a patch out soon :) Thanks for the update!