scaflight

Great work! May I suggest you alter some colours? Either to use a darker colour for the letter 'D', or to make the background white somewhat grey. Bright yellow is very difficult to read against white.

p. 246 of the WIP manual: edit: beaten

Can confirm, as trackIR user who wants to be able to see what the targets are, that there's an immense amount of clipping going on when you lean in.

My initial post in #2 is definitely wrong, and Renhanxue's reading seems more precise. After finding one target, the Rb-04 (realistically) only needs another target behind it to satisfy the conditions of the group mode attack.

(edit: this is wrong) An Rb-04 in GRUPP mode will discriminate against any single or small group of targets, as these could be escort ships. The missile was designed to take on large numbers of landing ships in an invasion fleet. Renhanxue and others on this forum have posted more detailed descriptions of what the radar's looking for, but in brief, you won't find those kinds of numbers outside of enormous formations in invasion-type scenarios. For all your every day scenarios, you need "ENKEL". The manual isn't well written with regards to this. I assume you didn't try a bunch (5-10x) of targets within a small area, but that you were trying with 2x enemies?

Just to point out, "Tid" is just the Swedish word for time. It's not an acronym. :)

Is that also the case for MKR gain? It's stepped in the current release.

Fiskbeddsplinter, ja se det måste vi ha!

Heads must (barrel) roll for this!

Dear anyone, How do you even use the B-Scope? The WIP manual says hardly anything about it. More specifically, when switched to the radar's A2 mode, how do you determine what range and what area is looked at by the B-Scope? And how can you move it around to look elsewhere? Additionally, are there any visual indicators of how far up/down you've set your MKR gain and your antenna elevation? Since the inputs aren't visually modelled (yet?), there's nothing to go by. The manual brags that both of these have a handy snap-to-middle function that works well for ships, but you're left guessing where that is when all you have are up/down keys. Or did I miss something? From experimenting I've discovered that the MKR gain has roughly 10 steps, but I could be mistaken.

Nevermind -- I had to disable trackIR completely, and then had to use numpad to look around and set up my snap views.

According to the manual (p. 130), decidedly no.

I have an affinity for keeping left-handed operations on the throttle, and right-handed on the stick. As such, operating radar modes with the Mode wheel is something I'm iffy about. Right now I just use left coolie. But here's a question! Is there a way I can make the wheels on the throttle correspond to different settings on the master mode and weapon selector wheels?

I was just about to report this as a bug! I discovered it by accident and it had certain catastrophic consequences for my attack run. ;)

I've not been able to get my snap views sorted this way. RAlt+Num0 doesn't seem to save the position properly. Sarge55: how did you do it?

Simon: which airport/runway did you take off from? It might well be that some runways are messed up, improbable though that sounds.

It would make for a neat compilation, but no, they've not released any. I bet there's a ton of easter eggs hidden within the CK.

The manual (p. 130) mentions ONLY a runway direction finding error as causing the NAV SYST warning. It takes into consideration the opposite runway heading, as well as the airport's other listed headings. Therefore most of us can go pretty wild on the runway and still end up with no nav error. The thing you haven't mentioned is waiting for the information to load. I'd advice you to not set IN/OUT switch to OUT until the digit 9 has stopped flashing and displaying 000000. If the 9 stops flashing without showing 000000, that's a sign the data transfer failed (ie, blow the cartridge).

I've since learned that pinkie+trigger is by far preferable. I keep pushing the trigger by mistake, leading to silly new fixes... So now I'm on the T0 mystery. Suppose non-pinkie 2nd trigger will work, just have to make sure fingers don't slip and create bad situations.

In addition to the explanations above... The manual states to "Use the radar to find the target, make a target fix and aim towards the target. (On visual aiming, put the flight path vector on the target)." What I get from this is that a radar target fix is 100% to aid the cognitive aspects of engaging the target. Something more necessary in low-vis situations and in high-traffic ship lanes. If all you have is a lone, unmistakable target, then you have to observe fewer variables and don't have to worry about launching against the wrong target (or worse, civilians).

Yeah, this'd be nice to resolve somehow. :)

I'll give it the 10/10 when the internal loop isn't so noticable ;)

Did you blow the cartridge for dust?

For my X-52, I ended up with pinkie modifier+throttle coolie.

That's not a good way to post. :cry: