beelzebub

Hi all, another small request for help with this amazing mod. I'm trying to calculate where two inclined orbits cross (i.e. the ascending node relative to the target) and I'm utterly stuck. I've spent about a week mulling this over and Googling, but to no avail. Certain we've got the necessary information available in the form of ship & target obt:LAN and obt:inclination (relative to the reference plane), but I don't understand how to take these measurements and turn them into a LAN for the target's orbit relative to the ship. I note that the incnode script on the KOS wiki (http://ksp.baldev.de/kos/mtkv3/incnode.txt) solves this using vectors - surely this isn't necessary, and we can just work it out using the reference plane? Any pointers or reading material gratefully received!

Just posting to report complete success with Steve's approach to controlling the pitch and yaw of a rocket independently of its roll. Also the use of the vecdrawargs makes life a lot easier when it comes to debugging. This is a lot more satisfying than lock steering to up!. For the benefit of others... First decide where you want to go: set desiredHeading to heading(90,90). Then get a vector for the directions along your current pitch and yaw axes: lock pitchAxis to ship:facing*R(-90,0,0). lock pitchVector to pitchAxis:Vector. lock yawAxis to ship:facing*R(0,90,0). lock yawVector to yawAxis:Vector. Then get the dot product of this vector and your desired pitch/yaw. The *90 is to convert it to degrees (error of 1 = 90 degrees...) lock pitchError to 90*VDOT(desiredHeading:vector,pitchVector). lock yawError to 90*VDOT(desiredHeading:vector,yawVector). You can get roll error by the obvious way, plus a non-obvious -180: lock rollTarget to desiredHeading:Roll - 180. lock rollError to max(facing:Roll,rTarget) - min(facing:Roll,rollTarget). Feed these into a PID controller and you're good to go!

Thanks, Steve - I'll have a fiddle and report back

Hey gang, first time playing with kOS since 0.6, thanks very much for re-invigorating it! Quick request for some help/advice, since I'm thoroughly stuck. The steering (lock steering to x) is ineffective, as has been discussed, so I've been writing my own PID controller to do ship:control:pitch/yaw/roll. However, I'm experiencing difficulties calculating a pitch/yaw error that is independent of the roll (i.e. it doesn't care which way around the rocket is, just points it in the right direction. Up - ship:facing still wants to correct for roll...). Does anyone have advice, or a sample script, that could help me with this? Alternatively, advice on getting steering working effectively would be grand, but that seems the easy way out

My first challenge, after over a year of playing this game... Good challenge, Death Engineering Mods used - Deadly Re-entry, RemoteTech, Alarm Clock, IonCross, Procedural Farings I reckon 257 points. That's about 10 points per hour Basic mission profile to earn the base of 50 points: Non-asparagus, Saturn 5 style launch vehicle: 3 main stages to LKO, no asparagus-style fuel-tank/engine jettisons on ascent to LKO. Solid rocket boosters ARE permitted, as they were being developed for the Space Shuttle, but there is a penalty for making KSC accelerate their development for this mission. Start with the provided save game persistent file. Single launch mission. No refueling or constructing the vessel in orbit from multiple lauches. The Apollo CSM was not capable of doing a 'direct ascent' mission. You must use a separate command module and lander. Powered descent, parachutes, or a combination will qualify. All stock flight-parts. No mods which provide improved flight performance or flight assistance (auto-pilot) are allowed. Return at least one of the Kerbals that started the mission back safely to Kerbin's surface. Addition points for standard mission goals: 3-kerbal mission +10 2-kerbal lander +10 2-stage lander with separate ascent stage (descent stage stays on Duna) +20 Launch escape system (LES) escape tower +10 Duna lander stored behind the CM during ascent +20 Lander tucked away behind some fairing +5 Perfect landing - no damage to LM +10 Dock with LM's ascent stage prior to leaving Duna's SOI +10 Ascent module de-orbited to burn up in Duna's atmosphere +5 Plant at least one flag +3 Splash-down on Kerbin (water landing) +5 Kerbal fatality -20 each (if any kerbal is left on the Duna surface after the ascent module leaves the surface or the CM leaves Duna orbit, they will die). Flight goals: Launch vehicle should avoid using solid-rocket boosters during its ascent. This *does not* include use of Separatrons that are not used for ascent purposes. If you use a SRB for ascent -10 Complete the mission with only chemical rockets (no nukes). The KSC already has a crate of chemical rockets on hand and you get a bonus for not having to accelerate development on the nuclear engine +15 Aerobrake around Duna to achieve orbit +10 Less than 75 days from game start to Duna orbit? Launching when the game saves starts and performing a standard orbital transfer gets you into a Duna orbit 75 days from when the provided save game starts, day 129 in the game. Find a faster way to get into a Duna orbit using another transfer faster and earn +1 point for every day less than 75 days it takes to get to Duna orbit, from the starting point of day 54, where the provided save game starts (calculated by 129 - day when Duna orbit is reached). Water sample return bonus! Land on either polar icecap AND return a sample to Kerbin (either as part of the kerballed lander or a robotic lander) +10 Rover: At least one rover on board +5 Rovers can seat at least one Kerbal +5 Additional rovers +3 each Distance (score for one only and counts only for a kerballed rover) Drive beyond 100 meters of the lander +2 Drive beyond 2.5 km of the lander +5 Drive beyond 5km of the lander +10 Drive beyond 10km of the lander +15 Orbital Science goals: Deploy orbiting satellite around Duna +5 Deploy orbiting satellite around Ike +10 Duna surface science goals. Each science package must be a powered probecore with at least one scientific instrument: Deploy one science package at landing site (on the LM itself counts, if that part of the LM stays on Duna's surface and remains powered) +5 Deploy a science package at least 2.5km from the landing site +10 (score first one only) Deploy a science package at least 1000m +/- different alititude from LM or any other science package +15 (score first one only) Deploy a science package adjacent (within 100m) to any anomoly +10 (score first one only) Deploy a science package at least 10km from the landing site +10 (score first one only)