- Joined
- Apr 5, 2008
- Messages
- 368
- Reaction score
- 0
- Points
- 0
A tailsitter I am developing works just fine when loaded from a scenario file, sitting and launching properly from a pad. But using the scenario editor to move it to another pad flips it over onto its nose.
The craft is SC3 at this stage of development, and the touchdown points seem to be in order.
LAND_PT1=(3.691974,3.691974,-22.66792)
LAND_PT2=(-3.691974,3.691974,-22.66792)
LAND_PT3=(0,-3.691974,-22.66792)
I'm not using separate LAUNCH_PTs since they should default to the LAND_PTs, but now I think about it that might be the problem, but I can't check it now since I am not at my dev machine. I'm still going to post this now in case anybody knows something else I should be doing differently.
I've searched around and can't find any solution to this. I swear, I should make a book on problems I manage to find that nobody else has ever seen....
:facepalm:
The craft is SC3 at this stage of development, and the touchdown points seem to be in order.
LAND_PT1=(3.691974,3.691974,-22.66792)
LAND_PT2=(-3.691974,3.691974,-22.66792)
LAND_PT3=(0,-3.691974,-22.66792)
I'm not using separate LAUNCH_PTs since they should default to the LAND_PTs, but now I think about it that might be the problem, but I can't check it now since I am not at my dev machine. I'm still going to post this now in case anybody knows something else I should be doing differently.
I've searched around and can't find any solution to this. I swear, I should make a book on problems I manage to find that nobody else has ever seen....
:facepalm: