i need help with very basic vizzy (real basic)

@TheVizzyLucky it sshould be around 3 am in his country but idk maybe later than 3

@Livingg017 I talked to Lq11 and we got sth that should work. If he hasn't sent you anything yet (I was away for a few hours), I think you can expect results... let's say tomorrow, it's quite late in my timezone (and I think in his too)

also what i think you guys are not understanding is that the doors have only (true) or (false) activation states and the rotators have an "analog" input

if you guys get it working without needig extra AG's then do it like that

@Lq11 @TheVizzyLucky the landing gear part has nothing to be with the program itself, it just needs to change its state when the rotators are being moved. As this part has to move while the program already has started running, it cannot be used to verify the status on the other parts. Lq11 understood what i wanted with the rotators so i explain to you guys for better undestanding: take as an example the Airbus A350, to deploy the landing gear it first opens the doors, when theyre open the gear deploys (rotator output) and then it closes them, as the front gear does not feature this sequence and its a normal default juno gear it is not a thing to worry about. i hve worked on timing each movement needed so you just need to make the program to be usable infinite times and for it not to do strange movements such as opening and closing the doors for no reason

@TheVizzyLucky I have no idea, I made a program that uses the landing gear bay...

Cause otherwise it could be CargoBay.OpenAmount too

@Lq11 The cargo bay properties don't work on landing gear bays, do they?

@TheVizzyLucky Yes, that's exactly it, but there's a line like that in the chassis compartment, but I don't remember the name. I will be very busy for the next 1.5 hours and won’t be able to answer.

@Lq11 Oh, that's what you mean. Would that be SubPartRotator.Data.CurrentEnabledPercent? Cause I can't find a currentEnabledPercent for landing gear bays, only for the gear itself

@TheVizzyLucky I can post an example I made so you can see it for yourself.
By the way, as I understand it, using the funk function will allow us to get rid of possible bugs

@TheVizzyLucky You can monitor the position of the landing gear and open the doors when the value is > 0, or close them when it is less than the required value.

@Lq11 Oh, I really thought I'd had problems with spaces in the name before... good to know. Wait, funk? How would you do that with funk?

@Livingg017
I think it's better not to use timers, it's better to use the Funk function for this... I already have an example ready with two options: one works on a timer and the second on a Funk function, all with an explanation.

@TheVizzyLucky
A little note about what Lq11 said:
I'm not entirely sure, but I think that won't work if the command pod's name has a space. E.g., if the name is Command Pod, I think it will see Command and Pod.VZ.variableName as two separate instructions because of the space. So you'll probably have to rename it (e.g. to Command_Pod) — I initially thought the same thing, but everything is fine and it works if you leave spaces in the command module name... I guess the periods between words act as a delimiter...

I couldn't test it yet, but I think such a program could look like this:

while ( true ) {
wait until ( not(activation group 8) )
Set Activation Group ( 7 ) to ( true )
wait ( 2.5 ) seconds
Set ( Slider 4 ) to ( 1 )
Set Activation Group ( 10 ) to ( false )
wait ( 2 ) seconds
Set Activation Group ( 7 ) to ( false )
wait until ( activation group 8 )
Set Activation Group ( 7 ) to ( true )
wait ( 2.5 ) seconds
Set ( Slider 4 ) to ( 0 )
Set Activation Group ( 10 ) to ( true )
wait ( 2 ) seconds
Set Activation Group ( 7 ) to ( false )
}

If you want to use Lq11's suggestion, simply replace all the set AGs with set variable to true/false and the Set Slider 4s with set variable to 1/0 - the value the variables are set to are the same as with the AGs (e.g. if the AG is set to false, the variable needs to be set to false too).

A little note about what Lq11 said:
I'm not entirely sure, but I think that won't work if the command pod's name has a space. E.g., if the name is Command Pod, I think it will see Command and Pod.VZ.variableName as two separate instructions because of the space. So you'll probably have to rename it (e.g. to Command_Pod)

Edit: Since the website ignores lines starting with spaces even in code blocks: everything in the program above has to be in the while ( true ) loop

@Livingg017 i will try to help, send the craft

@Livingg017 thank you brother

Also, how many landing gear door flaps do you need, I was just confused by the doors closed, wheel extended

I did something similar on the AICS-04 front chassis...
You know, I don't think it's necessary to have multiple activation groups there; just one AG that controls the chassis (yours is the AG10) is enough.
Why so little? Because for me, ""input for vizzy"" is useless, a separate AG for the Chassis doors is the same, since you can use the functions [Current name of the command pod].VZ.[The name assigned to the variable]... Example: Command chip.VZ.LandingDoor... Why do we need an input the rotators? Isn't it the same as an input the doors?

I think I remembered everything correctly, I'll try to put together a working example...

@Yugveergreat

@TheVizzyLucky @TritonAerospace @Lq11