Opps - miss wrote one thing. As velocity away from the surface increases, both X and Z DECREASE.
.
The more I look at it, the more X seem to be very much attached to velocity toward and away from the surface, but Z is a little weird and seems to get a slight boost/decrease with vertical velocity....which I'm not sure how to deal with.
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.
(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.
Opps - miss wrote one thing. As velocity away from the surface increases, both X and Z DECREASE.
.
4.7 years agoThe more I look at it, the more X seem to be very much attached to velocity toward and away from the surface, but Z is a little weird and seems to get a slight boost/decrease with vertical velocity....which I'm not sure how to deal with.
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!
4.7 years ago(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.
.
4.7 years agoI 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.