Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Milling Machine
Lathe
3D Printer
Meassuring Machine
Industrial crane
And so on...
The up and down is the most the Z.
It would be awesome 😁👍
To answer your question, the only other thing you should have to do is add the [factory] tag..... buuut I did notice a bug and just pushed the update for it. I believe this will resolve your issue if your still interested.
Done. In the top of the code you will find a "Custom" section and your name. Set the value to zero and it will behave as requested.
I may convert this to a configuration but that takes a bit more work and is not backwards compatible so I will wait to do that when there is another major update :).
First idea: A faster drill speed means you may not be giving the drill enough time to properly drill out the voxels and it could be getting caught/stuck on them. It may even force it's way past un-removed voxels, but then get stuck when attempting to reverse back over them.
Second idea: My script will happily take whatever number you give it for the drill speed and attempt to apply it to the pistons. However, the pistons have a max/min velocity setting that will override whatever values you give it. So I am not sure that it is even using anything higher than a 5 (or whatever max piston velocity is), but maybe SE is taking a performance hit overriding that variable all the time?
To be continued....
Is there any other "buggy" stop/start behavior you are experiencing outside of server restarts? If so could you explain in more detail what is happening? If you have a blueprint/world save that you could share that would be very beneficial :)
That would be an interesting challenge! I could definitely add it to my list of To-Do's, but I don't get much time these days and I have another script currently in the works that I would like to wrap up before starting another project.
On a positive note, a build for this could be attached to a large ship (using rotors to "put away" the arms when not in use) and could be mobile that way. Would give that "unlimited" range I think you are looking for and would keep some level of automation to free you up while it works :).
On the other hand my new script could help with this print drone..... ;)
You don't want scripters having the ability to write files to your computer ;)
Mind-blown! I never even considered multiple factories running on the same platform *sigh*.
I am beyond impressed that you figured out the naming convention and changing the factory constant without any guidance!
All that said it looks like the factory was getting stuck on the voxels in that corner. After drilling it out a bit it continued on. I am interested into why it didn't drill out the space it needed to operate, but you could add some drills (at one block height higher than that drill but still next to that drill) to help that if necessary.
As an aside, I did update the script to add extra debugging output! In the programming block's CustomData is a "debug: false". Set it to "debug: true" and you will see a bit more into what the script is doing and what it is trying to accomplish :).
Best!
I think I may have found a few more bugs. I have two drills, one drill works fine, but the other seems to get stuck on z iteriation 9/9. It just sits there, the drill is on, but the pistons stop moving. i think it may be a problem with two drills on the platform. The drill that works is labled as [factory], and the drill that stops working is labled as [mag], (and I did edit it in a separate programing block). Also, the skip command does not seem to work properly when one drill is running. It moves it into position, but does not start the drill and the pistons do not move after it is in position. Let me know if you need anything.
Thanks! We made it *sigh of relief*. I made some updates to the script that seem to have resolved your issue. It was a flaw in the logic that totally shredded the script :face-palm:. But it ran very well for me in your world so hopefully it is done right this time!
As an aside I recommend two things:
First - change your PB.CustomData welding_speed variable anywhere between a 1-2. Your drill can go about 8x as fast as it is right now :).
Second - For stability you should have all the pistons set to the "share inertia tensor" setting.
Best!
Everything is set to share with all, you can spawn in the medbay and it will take you right there. I have not changed anything else. If there is specific info you need just let me know. Ignore the button panels, they are not set up properly. If I use "run" it will go as normal, but the Z interval will continue to increment so it never goes down another layer.
Hmm... thats no good. Mind helping me reproduce your error? I see your image, but it is hard to say what could be the cause here. Could you post your build with the command you are using?
Your keeping me honest :). In my case it was the welder factory and it turned on one of my docked ship's welders that just so happened to be right next to me! XD. I resolved this issue.
I was able to reproduce that Z interval lock, but in the process found other minor issues. I attempted to fix them all, but who knows what mayhem the updates could have caused ;). I am hoping the one I found was yours!
Finally, I updated the output a bit to have some more stuffs :).
Huge thanks for the feedback!
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1409377216
Sorry for the delay! This was something I ran into pretty quickly myself, but lack of time and demand forced me to tolerate it
However , I added the feature to skip to a desired iteration. Simply run the "skip" command with your desired y and z iterations.
For example run the script with the following argument:
skip:3,2
Cheers!
It does require a projector to do 3D Printing (weld blueprints) and you setup a projector like you normally would only make sure that the blueprint is in range of the factory's welder. Other than that just follow the normal projector-welding rules like having the blueprint touching a block :)