Recent content by jevans

Because the Tu-4 was an exact copy of a B-29. I think that picture must be a render - as far as we know, it hasn't started flight tests. It took even the US some years to get the F22 right before it entered service, so the same may well be true here.

Look up MirCorp...:facepalm:

Today I sorted the leak, then worked out how to do tapes for the velocity and so on. You can see the tapes for alpha and H dot are done, now to do the M/V and H ones, which are the ones that are slightly more complex, with scale changes. There is a g-meter in the corner that pops up when in the...

That's what I'm using. It seems slightly enthusiastic about placing icons on files that aren't under svn, but never mind.

Don't worry, I'll make sure there's no leaks before you see it.:) I'll admit I'm not used to working with proper source/version control - I usually work as a solo developer.

At what point of 'completeness' do you think the new PFD and so on should be checked in? Should I just wait until it's completely done to put it up here? I also managed today to write a rather embarrassing memory leak into the module - it leaked a whole bitmap every frame... The clue was when...

So it's like in Orbiter, VR is speed relative to the point on the surface below the ship? And VI has the extra .2 because of the rotation of the Earth.

Well, the Garmin in FS would give 0 if you were traveling vertically. I don't know if this is true for real ones too, but I would imagine it is. It's modeled quite accurately.

I see. I've spent too long on FSX, then... Urwumpe, So which one should I use for the SSU PFD? 'Orbiter' GS or 'True/aviation' GS? (This is for the M/VR mode, I sorted the others out fine).

I don't know if I'm just being stupid, but I'm trying to get ground speed using the formula: GS = TAS * (PR /(PR+A)) Where PR is the radius of the reference body, and a is altitude. While this gets a value that seems correct, it disagrees slightly with the GS readout on the default surface...

That one might be a little difficult to do because of water in Orbiter being somewhat solid...

Aaahhhhh... Of course. It's beginning to make sense now, thank you!

This is SCOM revision OI-33, from 2008. It's the same in the workbook. Mach 4 =4.466 kft/s, according to google, so when the indicator passes over mach 4 does it suddenly switch units and flick up to indicating 4.47 (in kft/s) instantaneously? I just don't understand how the transition from...

Ok, thanks. That seems slightly clearer, I'll have a go at those tomorrow. I must admit I'm still not totally clear on the speed display. I found this in the SCOM: The bit in bold is a bit confusing. So is the number in the box always mach, with the tape in kft/s? Seems odd, or I could be...

I've been using the Orbiter API functions for all the values so far, as I could see that the GPC's and NAV system can't provide them yet. It wouldn't be too difficult to convert them when the GPC code can do this. The thing I haven't been able to work out is how to get the DAP, throttle...