I first subscribed to this script in August of 2020 and still use it today. This is an absolute MUST HAVE script for me. :)

I got a problem with DAS, it keeps setting wheel friction to 100% which causes my vehicle to keep fighting itself when I try to turn. is there a way to stop DAS from adjusting the friction or at least clamp the max value it can set?

Oh, I see that now, thank you. sorry for the stupid question

That's because it goes to standby mode thinking it's docked to a base/carrier. Put "DAS_IGNORE" (w/o quotes) to the connector's Custom Data property.

DAS is not running subgrid wheels as soon as I dock anything to my connector. Anyone have any ideas?

@Amumu the Remote Control block is required for the script to understand where is up & front sides of a vehicle. It won't work without it. DisplayScheduler failure means you don't have LCD screens dedicated for the script, you can ignore it.

i loaded the script in my rover, getting message DAS.DisplaySchedular failure Das GridDynamics Watcher and Critical failure during boot. No remote control block found. i dont have a remote control not planing to so can i turn this all off somehow seens im only after the suspension helping part or am i all wrong into this =D first time trying scripts

After some time (seemingly random) my wheels will just lock up when turning I'm not sure if this is a vanilla issue but I've only ever encountered it when using this script so any input would be appreciated

@fraoud. A work around i have found is to get some armor blocks positions in the right spot so the blocks would make the road you want. then just drive along the blocks and they will keep you level. then grind out the blocks you pass, and replace in the front, so you are continuously moving the armor blocks you drive on. it is a pain but you get a perfectly level road in the end. Just keep in mind the carved road surface will be a bit lower than the top of the blocks... so plan for this in the block positioning.

@Wanderer_308 Okay newbie mistake, I didnt know you had to put LEFT or RIGHT into Custom Data per light. Its not initially present here on the homepage. I had to go to the "Popular Discussions" part and look for the Pinned for the set up. Most guides have a hyperlink on its own guide.

@Fake group naming is correct? "LEFT" and "RIGHT" keywords are put into Custom data? Ownership is same as PB?

Turn lights not working? Tried using on 3 rovers. No luck

I'll second Volg's request. I'm looking for something to level a grader laterally whilst carving a road.

that is how i do it now... but it is a complicated dance as i am tunneling and trying to keep the tunnel level side to side... it is doable i was just hoping for an easier way.

@Volg That would require a bunch of code, which I doubt will fit in character limit. Isn't it easier to just turn of DAS and adjust suspension offset after it? I think you can bind it all to a single timer block.

If you want to see the vehicle I need this for, to understand the needs, i can send you a BP on the work shop.

is it possible to get a mode we can toggle on and off from in the cockpit that will adjust suspension offsets to try and keep the vehicle level? I know it is only a few degrees of motion we will get, but that is all i need. i just need my rover to sit as level as possible, so on gentle slopes it will be level, understanding full well that on steeper slopes it will not be able to reach a level state. I only need this to be done in the roll axis. pitch is not an issue. however the roll adjustment would need all the wheels to be adjusted to reach a level roll state.

No, the RC unit is standing correctly. Shaking and increased vibrations, not flips in place after all.

Could it be that RC block orientation is wrong?

Maybe I don't understand something, but on a rover weighing 14,000 kg, the script sets me 100% friction and a very rigid (almost non-working) suspension. All this leads to the fact that ordinary driving over small bumps turns into a nightmare with jumps and constant twitching. Even on a flat surface it is impossible to drive smoothly, it still pulls back and forth a little bit. Am I missing something?

@Wanderer_308 I seems to have forgotten the camera. Thank you!

@The_Bum_Dave Make sure: a) RC block is properly oriented (up&front axles); b) bottom camera is not obscured by surrounding blocks; c) bottom camera is not a moded full block, aka reinforced, camera one.

GSA seems to think my rover is always flipped. If I turn it on and jump or drive at a steep angle, GSA max rolls me.

Just wanted to drive by and say that this script continues to be an absolute staple, and it runs on every single wheeled vehicle I build. I don't know what I would do without it.

alright, seems like I managed to edit it the way I wanted by replacing:

return block.CustomData.Equals("DAS_IGNORE",StringComparison.OrdinalIgnoreCase);

with

return block.CustomName.Contains("DAS_IGNORE");

absolute love the script but got a problem when using it together with other scripts, in my case SCAM.
Got a large grid rover that I want to use as a mining carrier for drones.
SCAM uses the custom data to handle docking of drones.

so my problem is that I cannot disable Standby mode by using "DAS_IGNORE" on the connectors, or else drones will have dtrouble docking or they will just delete the custom data.

so would it be possible to handle the IGNORE-feature by writing it into the name of the connector like other scripts do, or simply disable it completely?

Well thanks for the help anyway! thats good info to know in the future but now I'm dealing with it happening on vehicles that don't even have connectors or sub-grids so I guess my game might just be fucked our something

Only if your custom turret connected with connector block. Subgrids on rotors, hinges and pistons are totally fine. Also to make the script ignore certain connector blocks just put in said connector block 'Custom Data' property DAS_IGNORE, and it will skip such blosk. Also [2], you can put DAS_IGNORE in any other block Custom Data to make the script ignore it.

Wait... that wouldnt happen to possible include a small custom turret? probaly is we have a custom turret on top, im not surprised as larger rovers i used always had issues with docking so makes sense sub-grids might get a little iffy, if this is that case i would ask if theres any possible fix but if there isnt i completely understand

Do you by chance have anything connected via connector block to your over when it happens? Like drone, or cargo container, or cart/trailer? The script goes into standby mode when it sees the rover is docked to something.

Genuine question, im having problems with DAS in my game randomly just stopping, not completely the script is still running but it stops dealing with friction power anything and only fixes when I either remove the PB block and replace it load the script again and then it works, or if I completely delete the vehicle and respawn it, I've tried the start-stop command and one weird way that fixes it is docking and undocking the vehicle it's a small large rover with 4 wheels when this happens its basically uncontrollable as one side gets more friction then the other, the entire craft starts strafing I cant steer cause the frictions so high that it just forces it to stop as soon as singular wheel turns and my acceleration feels anemic, its probably my fault in some way but just wishing to know if there's a fix

Like to use Wheels Auto Strength, but it picks a too high default value (40%). Tried to set it to -14, -100, -1, but this doesn't seem to make a difference, setting it to 14 works, but turns off automation. Is there a solution?

Volkswagen DAS auto

All remotes facing into the right direction...guess its not about the setup (I used that script like 30 times w/o problems...) has to be something about the wheels being on subgrids

Guess screenshots wont help, its a closed system. I've put remotes onto the wheel subgrids aswell for handbraking. Do they have to face the right direction aswell?

RC block orientation is correct? Maybe some screenshots would shine the light on the problem.

I know that...

" I've edited the Subgrid Wheels Name"
You need to make a group with these subgrid wheel and name the group, not the wheels itself. Maybe that is the issue.

Hi, I've got a huge problem with that script. I've used it many times and it always worked. For a new vehicle, which does have it's wheels on subgrids, this script does not work. It does not control the friction correctly. The vehicle starts to drift very easily and it doesn't break softly. (Yeah, I've edited the Subgrid Wheels Name). What can I do about it?

It's fine. No matter how much hinges, rotors and pistons separates grids, they still considered as a single construct. Only connector block separate constructs.

Having a tough time telling if the script is working on my mobile base rover, so I'm back to ask if anyone knows for sure if the DAS script Subgrid wheels need to be connected via a single connection. I have a 2 part hinge between the 2 segments to allow for better bumpy terrain control, but I wonder if that throws off the Script given the Main Grid is separated from the other wheels by 2 hinges. I would be very appreciative if i could get clarification and if I'm not just being a bit of a Dunce, maybe a fix for the situation.

i must of over looked that. ty

@[I.L]Methidox Script setup

Instructions? all i get is systems frailer

@Goblin Godaky, Something like 1511.

driving on bases feels sticky, what line number was the
baseFriction=100-35*Math.Abs(UserInput.AD);
on?

Unfortunately I'm very low on free time therefore I wouldn't dwell into any development. Maybe one day when things changes a little, but right now it's not even on horizon.

or even potentially a alternative option?

@Wanderer_308, would you open to making a secondary Script that is capable to handle this as an add on maybe?

ok, thx for the info