Vizzy - Controlling multiple separate crafts at once?

@sflanker now more people can see it and make use of it. i'm starting to do so. thanks

@crowxe I've moved my comment to a separate post with some additions.

@sflanker
your comment worth to be in a separate post for more to see

Just to follow up real quick, my issue was that staged parts always get 0 as their current altitude AGL. Once I set my landers to use ASL, they started controlling their throttle as expected.

Unfortunately, like @sflanker pointed out, you cannot lock headings with these separated crafts. Because of that, my landers lose control quickly. For now it looks like my booster landing project will have to wait until that is (hopefully) put in place later.

Plenty more to automate!

(Edit: And now I'm just seeing that my staged parts are displaying messages - however I can only seem to see 1 message at a time, so they were often not displaying because I was displaying too many messages at once. It's been a crazy day of trial-and-error.)
.
Has anyone successfully 'Output to Dev Console' using Vizzy?

.
After trying a few things, I feel like my real issue is that I don't have a way to see output from my 'separated' crafts - and that means I don't have a way to display what their variables are set to or what values they are seeing and my programs are likely misbehaving due to unexpected data as opposed to just not functioning.

.
For example, I thought nothing was working because my lander code wasn't firing the engines, but now I think the issue is that it may not be getting a usable value for altitude AGL or surface velocity.
(update: currently I'm getting Altitude AGL returned as 0 for staged parts)

.
If I switch to some code that just does a simple 'wait 5 seconds, throttle to 1, wait 3 seconds, throttle to 0', it works just fine even after staging.

.
I see a checkbox under Flight Program for 'Output to Dev Console'. It says "If enabled, log messages generated by the program will be redirected to the Dev Console", but I don't see anything named 'log' in Vizzy and messages using 'display message' do not go into the Dev Console that I can see.

.
I think if I'm able to see output from my code running on the staged parts, it'll really help me find out what I'm doing wrong.

I'm about sure the right way to do it is having multiple command chip and making each of them controlling respective crafts.

You can make a subassembly of your rocket and load it with "New Rocket". Then attach a command chip on it and then press "Set Primary". Now your subassembly has a dedicated command chip. Save it a subassembly again and load it on your original rocket. Now you have a part of your rocket controlled by secondary command chip.

Here's the example. This rocket has 3 command chip: Crew Module is controlled by primary command chip, CM Command Pod. Service Module is controlled by another command chip: ESM Flight Control. Booster Rocket is controlled by the last command chip: ACES Flight Command.

Ok, I've been working on coming up with a list of things that do and don't work (in Vizzy programs running on crafts not currently controlled by the player). Not yet complete but here you go:

Works

• Setting Activation Groups
• Reading the status of activation groups
• Setting Inputs (Throttle/Slider)
• Reading Inputs
• Reading changes in orientation (measured by converting fixed PCI to local)

Does Not Work

• Locking Heading (Current, Prograde, Target, etc)
• Having a Target (and by extension getting Target information like position vector)
• Setting Heading/Pitch in Degrees (because you can't Lock Heading)
• Reading Current AGL (reports AGL at the last time the craft was in player control)
  

  ---

Obviously there are more things to test, I will update later if I come up with more. UPDATE: for additional information see this post.