my Drill Align example truck still works, so I guess so. It should be showing a red aligner mark on the PB and my logo, if you look in the PB debug log it should say "RotorAlign by P3st align" if it doesn't say "align" but "stop" or some other text, try Run PB again. It should log any serious errors about not finding needed blocks. No need to name anything.

Does this script still work? Because i tried it. Attached a Remote and the Script block to the "top" part and Ran the script. It doesnt seem to do anything tho. Do i need to rename anything or did i set it up incorrectly?

I seem to have been unsubscribed to some threads, sorry guys, should be fixed now?

You are my Hero.

Ohhh WOW! This is awesome!

Im making a Rollcage inspired rover, where the cockpit is always facing the ground, i tried gyro alligners, i tried anti roll scripts, leveling script, i tried gravity leveling by adding artificial mass. but this! this script was just jackpot

@KeithFromCanada - Its a script m8. you place is in a PB

Hmmm... I just tried to add it but the SE mod browser doesn't see it.

Is there any way to get the display shown in the PB in a screen in a cockpit?

oh never mind, i could add another rotor after the "alignment" rotor and ajust it to 10° :D that was bad :D :D :D

Great skript! works great!
But i do have a suggestion.
Can you add s.th. to build a slope? like aligne rotor and add 10° for building an perfect slope ?

added feature to align toward a waypoint instead of gravity. see description for details.

No luck today. Removing an extra piston extender arm (well, it removed itself, actually) seems to have calmed Clang a bit, enough to where I was able to tune the drill height to the point I was able to bore fairly level tunnels. But now SE and Steam have conspired to prevent my ability to publish the blueprint. idk wtf today.

Well, using it to align two different arms axes works fine, but frustratingly enough, Clang lives in such contraptions, and my simple tests invoked Clang's fury to the point I couldn't even test it out, and after a half hour of fighting the stupid rotor limits and the physics engine, I give up. But yeah, if you can stop Clang from wrecking Havok and wreaking havoc, your idea of using two copies of the script would totally work.

No, not at all. PirateLaserBeam from Twitch was doing the same idea using my Gravity Aligner script. I hadn't really intended this script to control both arms, but it certainly could. I may even make a proof of concept. But I should really work on the other script that faces toward a waypoint, that he wanted, which comes in handy when trying to drill toward a specific point, if that point is higher or lower altitude than your drill truck currently is. That would take an hour or less, I just haven't done it, so lazy.

Thanks for the reply. I'm probably being overly ambitious...

Wasn't designed for that, specifically, but if you are creative with rotating the remote control, you should be able to get it to work. You may need to use two copies of it, on 2 different PB's, on 2 different hinge/rotor blocks, using 2 different remotes, to get it to fully articulate, and I have not tried it fully rigged like that yet. I'm so lazy. I was going to write a whole different script for the 2nd arm though, that had other features. I've had success using my Gravity Aligner script to do the job with one remote, but gyros aren't ideal for the job and the clang factor was very high with that setup, required carefully built robotic arm or the gyro wouldn't drive the joints properly in many cases, got hung up alot. Driving the rotors directly instead of using gyros seems to help.

Can this keep my drills angled so that my rover doesn't angle downwards as it drills, eventually causing the tunnel to angle down until the rover has tipped nose down into a vertical tunnel instead of the horizontal tunnel I wanted causing me to scream in anguish?

PB must be on the arm with the remote, currently; that's how it finds the remote. It complains in the PB console about missing blocks, so if you look in the control panel, on the pb, script should be telling you what it can't find.

I set it up several different ways. But yeah I think the problem was that the rotor was not on the base grid. There was a hinge in between.

What details? Pretty sure I tried advanced rotor, so that should be fine, but the rotor should actually be on the base parent grid, and the remote should be on the moving rotor head part grid.

I have been looking for something like this. Any timeframe on those details? Having some trouble getting it to recognise the advanced rotor thats on the same grid as the remote control.

Found whiplash141's script, not easy, tyvm. This guy scripts everything!

If you want to make a possibly useful script you could consider making rover autopilot script. There are few around but they all are pretty bad.

I think whiplash subgrid wheel control script does that

true, why reinvent the wheel. Speaking of wheels... I may have to write a 'drive using connected grid wheels' script. Like Full Control but for wheels. I couldn't find anything like that the other day.

You can already point a subgrid at turret target with turret slaver scripts tho

I'm supposed to be working on another one that keeps it facing a GPS waypoint. Could adapt that to track facing to target obtained by turret. Hmm. So much to do!

I'm in your head!

I was just thinking i could use a script like this and boom. Look what is on the workshop.

1 tin foil hat please.

WELCOME BACK BRO!