@It'sYuri
Yes. Most PBs only effect the grid they're connected to, so your ship needs to have a PB w/ ExcavOS.

(There are PBs/scripts that can interact with other grids, but they are the exception rather than the norm.)

DO I need to have the programmable block in the ship I wanna use ExcavOs with? I was tyring to run the script from my main base but nothing happens even with editing the custom data of my mining ship's cockpit

Website for documentation seems to be back online !

The pages linked (surge and statichost) are both down. Need the documentation please!

Anyone happen to have the manual? Every link (from other pages as well) to get to the manual is down. Seems like this is a great script based off comments, but I am unable to locate any kind of instructions

The docking tag doesn't seem to work as expected, I have defined the tag and I have put the tag in the connector I use to park the ship but no thrusters turn off.
Currently connected to a space station if that makes any difference..

@Calla, as with all settings they are in the custom data of the script block, clearing it will automatically write back in all the defaults.

Where am I supposed to put the above code to disable the automation features? You did not specify where they go.

cool. if you do I will add it to my mining ships. thanks

after some more in depth inspection of the code i realized there's a lot of legacy code in that just really should be cleaned up. so i'm considering doing a total rewrite of pretty much everything so i can sort out any inconsistencies and duplicate code as well as fix some issues I've ran into today that i can't easily fix without over complicating code needlessly again. this may take a while though.

Thank you for taking this over and updating it! Excited to see it still having a life.

i can't really fix that one easily. i'll have to do some rewriting which i was planning on anyway but it may take a while.

@Unruly, I'm working on that, it shouldn't happen with world loading anymore but it may still happen when copy pasting until i finish rewriting how the initalization phase works.

Same thing, claims it's missing controller.

Thanks very much, but now I'm getting exceptions again when excav was left running and the grid is copied & pasted.

@Unruly, Done and updated. had to push an update anyway as i accidentally left some debug text in the UI that wasn't supposed to be there.

Update seems to have done it. I've just enabled, cut and pasted a ship w/ it running and no glitch. tvm!

I do notice that exavos doesn't remember the gravity alignment setting when pasted/save reloaded, can that be a thing?

cheers; having issues d/loading the new update, so no hurry at this end ...

@PBS-MD @Unruly
If you see this, I've found a solution, turns out this was something caused by a contribution from someone else that i didn't fully read into properly and after taking a closer look i realized now that this change unintentionally caused the script to run twice on certain ticks and if this happened on the load tick that would result in it trying to cache the blocks and immediately try to use that cache in the same frame which was incomplete. will be posting the fixed version tomorrow after i get some time to fix some other issues like rover mode not being detected properly. (using the fan blade thrusters results in the lift thrust not showing up)

on that note. with the new update i plan to pick up the game again so i might have some more time/experience with the issues that script might be having so i might just have a easier time debugging things. o7

will (try to) have a look for an exception, see if it's the same; also see if the gravity align is on / turning off makes it work ...

No rush intended or implied! ;D Sincerely, I've very thankful that people write & share their stuff.

the error is specifically the function that finds a controller that's erroring out so that's not the issue. that said. I've not touched this stuff in ages and i've been quite busy. alongside the fact that majority of this was written by GThoro before he went silent on me. so it might take me a while to figure out what could be causing this.

nm, I see that exception comes after an explicit attempt to find one.

If alignment is on, is there a chance the script goes to service the alignment before updating it's references to the grid?

For me it happens *every* load on every ship w/ the dev branch of excav and, I think, every copy-paste, but only when the program was left w/ gravity alignment enabled. It continues fine if gravity alignment was toggle off before the save or being copied.

@Unruly Thanks for including the exception. that error in particular is it saying that there is no valid cockpit and or ai controller.

If that trips it means the script couldn't find a controller block which is odd if there is a functional cockpit on the ship. I'm not sure how i'd have to go about resolving this. especially since it works fine on my end so i can't even begin debugging it.

@PBS-MD nope, me as well. The exception is says it caught on loading the save is:
"Caught exception during execution of script:Missing Controller!"

Not sure if I've missed something but ... the script is never active when I load up and enter the cockpit; I always have to recompile to get it working/running. Any suggestions ?

@Folx, automatic LCD's is solely for displaying information where ExcavOS also controls various elements of your ship.

What is the advantage of this compared to "Automatic LCDs 2"?

It works btw

Does gravity align work with thruster physics mod?

Is there any way to add a delay before the immersion toggle will trigger again? I like that it boots up the first time I get back in the cockpit, but sometimes I have to bounce in and out a few times and it shouldn't have to boot up each time.

@Brianetta, included your changes and pushed the update, thanks for your contributions!

Your DockTag code doesn't do the shut-off and recharge when docking with a static base, because the static state gets set first, and the connector code's docked state is in an else-clause from that. This was why I thought it was broken - it didn't work on my base.

Weird, but OK. I have event controllers on all my miners that do all of these things anyway.
I'll make a new PR with just the first three commits, since that change is a separate bug fix.

@Brianetta, I've looked through your requests, the automation one seems fine and i'll be merging that one soon.

The other one though actually breaks intended functionality rather then fix it. because i think there's a misunderstanding with how that is supposed to operate.

The DockTag goes on the external connector that you are docking with, not on the ship containing Excav. this is to ensure that the engines only shut off when docked with a ship that you know can handle the extra weight of excav ships.

(i've had it happend where mid-air operations ended catastrophically due to unexpected engine shutoff. so i created this to make it only work with certain connectors on my mothership.)

Also, for faster communication, If anyone wants to just contact me to discuss ideas/changes feel free to add me on discord:
- pokerface_cactus

I have a pull request up already, which might serve your needs, @Melfely

@Brianetta, The source repo is technically up to date. it's the april-2023 branch.
@Melfely, I'll gladly check it if you pull request the dev repo https://github.com/brandonvdongen/ExcavOS

@PF_Cactus well fair enough I presume. IF you want I can do a pull request on your repository with my edits so you can see what I changed in the end.

Ignore that last, I found your fork.

Any chance you'll update the source repository on Github?
https://github.com/kpiatkowski/ExcavOS

@Melfely, Since i'm not the official project owner I can't give permission to post it, that said. I'll have time later today/tomorrow and i'll See if i can do a official implementation for some of the requested things here like disabling the automatic management altogether and a method of excluding only specific objects from the automatic management.

I have made it, was pretty easy to do. Even got the config loader working so its a new field in the custom data. But, If im not allowed to publish it to steam, thats all good. But I am hoping you will allow it.

I don't think there is anyways to currently prevent the script from managing thrusters, tanks and batteries. While neat, it is mildly annoying on some grids.

I am tempted to look into making my own version that has a toggle for that, would you mind if it gets posted to steam, "unlisted" or "public"?

Having modded a couple of games myself in the past I know how time consuming it can get, so thanks for your continued support (i use this on pretty much every atmospheric capable ship)

Rither in manually created groups or single, the script manages thrusters, turning them on at lift off even if manually shut down (which makes a gentle exit from the base amusing.. there's a large industrial on the back for breaking into orbit)

@hangar-8 i don't remember if the entries are made for it in the config automatically but manually creating thruster groups *should* stop it from auto configuring them. tho this could potentially have been lost in the rework. I've not actually worked on this code in over half a year as i've been quite busy. i just kept seeing requests for features that were already in the dev version so i decided to post this to at least help reduce those requests.

Is there a command to exclude certain thrusters and/or groups from auto management? I usually group front facing thrusters with an on/off toggle on the bar to coast, and they keep getting turned on