Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
I also saw a comment maybe on keen forums about orientation - I may add an offset dealing with that tomorrow so what is considered "UP" on the docking block can be turned
A more recent update was one to use the built in self-trigger thing from keen - they're set to wait the max time between loops until the autopilot is complete, I may need to modify that.
Unfortunately tomorrow evening if not this weekend will be my next chance.
The 2 swarm ships still standing still, so i decided to give them a push with another ship and once i pushed a swarm drone, it began to align shortly and connects to the mothership as it should
But something is causing it to not continue align correctly when they wait the 20 meters??? in front of connector, they just stand still until i push them
Yes this screenshot happens very often ^^ they just fly away then when you try to get them unstuck xD
Sorry off topic a bit. Hm thats not quite right, but I'll look into it - I've actually not tweaked the script for a few versions so its not surprise that its a bit off at the moment, and I'm looking for something to play. Might not bee a bad time to get back into this.
I've got no video/graphic editing skills though, but maybe I can learn a bit to make a thumbnail of some kind.
Lastly can you expand on what you're thinking for the autodock/shuttle script? I'm thinking you mean one sort of like the one ship in the sample world that acts like a shuttle, but already pre-assembled to do just that very thing with a few waypoints?
Would be great if you can rework it a bit ^^ And maybe release it with "Autodock/Shuttle" Script and give it some nice animated thumbnail, so it gets used from more people, it's still the best out there, buit it was very hard for me to find it.
But as i said, it still mostly works. Add me as friend and i will donate you something <3
Alright so the shuttle isn't a script problem, the sensor for it to land on was not configured right. I didn't have it set up to detct large ships and small ships as is required.
Still looking into the autopilot thing. That might be a keen thing rather than a script thing
I cannot recreate the issue with connectors or merge blocks. If anyone out there gets the same issue with these dock types, please let me know.
Looking at that and the autopilot issue next
IMyTerminalBlock passThroughBlock = GridTerminalSystem.GetBlockWithName(passThroughBlockName);
if (passThroughBlock != null) {
IMyProgrammableBlock pTProgBlock = (IMyProgrammableBlock) passThroughBlock;
pTProgBlock.TryRun(inUseArgument);
}
So you'd basically need to do the GetBlockWithName as the name of the childship programmable block, and pass in the arguments in the in use argument. Once i get everything working smooth again, if thats not your cup of tea, I can look into doing something along those lines possibly.
Bad news is with the holiday and the like my time will be limited, I'll have a bit this weekend, but cannot promise anything offhand.
-| Use the ToolShip, press 9 to dock in the Hanger, undock and fly outside, try to dock again with pressing 9, it will fly in front of the Hanger but the autopilot keeps activated, you have to deactivate it manually to continue. The PB-Block says for me 3 Tasks are running.
-| Use the Shuttle, dock at SecondaryBase, fly back to MainBase, then again to SecondaryBase, now you can't fly back to the MainBase cause your docking request gets rejected. When using a Timer-Block to Reinitialize the Bases-PB's this will work fine but the ToolShip AutoPilot problem still exists
I have since started playing around with with applying the program to my own custom miner drones; currently I have simply copied the exact settings of one of the swarm drones onto my miner and deleted said swarm-drone, but as I gradually read and understand your program more I plan to start putting in my own independent settings. I am amazed at how easily the childship program adapted to a new ship, without me having to make any changes to it or even specify where my drone's connector was located. The next test will be for me to try out custom motherships!
PS: It would be great if you can add LCD Infos for the arguments you can't see because they are on Toolbar/Shortcut
Aswell it would be nice if you can redesign the Description So people know and see better which config values they can use for each block (connector, landing gear, merge, remote, pb), i think it would be much helpful for others.
Greez
Believe it or not I do agree, I need to make a better how to and videos would probably help immensely
...And you are correct %action% is totally undocumented. In this case, action will be the action taken -its meant to pass in things like "OnUndock" "OnDock" and "OnAccept" so you can have one programmable block that handles all of the events, simply checking which event name was passed to see what action to take
There was some "patch" today? I had a update and it works now :3 Thank you very much.
I saw the forum post aswell, but i hope somebody will do a nice video since i am not native english speaking and the description is not that clear. Do you even need timer-blocks anymore? I think you can handle this in the script itself now. I love this bc it makes autodocking possible again <3 But a bit better description and How To, step for step would be awesome.
Is there any way to donate you? Greez from Vienna
I was having the same issue too with the rejections, but it seemed to be resolved when I switched to letting the PB block call itself per the new API/updated script. If all else fails, try running the mothership's block with "Reinitialize" as the only parameter. This should be a last resort as it can mess with ongoing docking procedures and queued undocking procedures, but if nothing is currently docked or docking (or all docked ships have no associated "onUndock" config) it should be safe.
I'm glad you're finding the script useful (or at least the concept) - and i know its pretty complex to setup, so thanks for your patience. I wanted it to be very flexible and I'm afraid I may have overdone it to the point of making it a bit hard to use.
The interesting thing is, after that I tried testing one of the other drones to see if it was a mothership problem, by undocking a different drone and flying it away, to then call it back; but instead, *that* drone did not react this time, and instead the modified drone from before flew in and parked in it's place at mothership. I don't know if maybe the program reassigned docking ports, or if the program just decided it didn't want to use the one unused docking port?
And a bit of extra push, I'll probalby have to tweak the "stop distance" calculations a bit.
The come to mothership order should be on the swarm mothership's, or "RequestChildren" if you're setting up a new ship
Tho in my recent testing, one problem I have noticed is that the child swarm ships tend to ram into the already-docked swarm ships or the swarm mothership, appearing to be trying to get to the dock on the opposite side. I did further testing, moving a drone to the opposite side of its mothership connector, and it would again ram the ship.
In your test map it seems the mothership homing stops working after it is first used to dock the drones. How do I reset the drones so they can be called upon again?