GreyStork

Just checking - is it intentional that pages 6/7 and 9/10 are identical?

I've seen footage of Blackhawks resting one wheel on a rooftop while unloading troops in Iraq, so it appears to be done routinely. It is dangerous, though. If the ship experiences an engine failure in a situation like that, the pilot would have a dynamic rollover on his hands before he could say 'boogers.'

If you watch the very end of Producer's note #1, you'll see that the HUD actually is 'ground stabilized' regardless of your viewing angle.

I always thought SLI was supported at the video adapter driver level, so application developers wouldn't have to worry about it. The only concern would be supporting any desired ultra-high resolutions made possible by SLI. I'm not an authority in that area, though, and if I'm wrong, I'd love to hear the real story!

According to Kamov, the Ka-50 armor should withstand a Browning round. Perhaps that's *one* Browning round? ;) I trust the manual will include a few "never exceed" figures, though, so we don't all have to learn the hard way... If it was easy, it wouldn't be very interesting. :)

It would be interesting to see comments on what's actually in the sim, in terms of mission planning tools, at this point, yes.

Tell me they'll be blue LED Christmas lights, please! ;) So no single bullet holes causing a ruptured fuel line or a cut power cable? Looking at the fuel system and electrical power diagrams here, I must admit I was half expecting failures that could be remedied by flipping the right switches. Does this also mean that you don't have to worry about left/right electrical power systems cross-feed if/when you lose an engine (and thus also a generator)? Have you ever fallen out of the sky, simply because your descent rate was too high (vortex ring state), or killed engine RPM by pulling the collective too hard?

Those would be external fuel tanks.

Well, it might actually be fun to watch a compilation of good old pilot error. Perhaps Glowing Amraam could accommodate us in that area. ;)

I can only second that. Where are the edges of the flight envelope, and how do you avoid reaching them? What happens if you do reach them? I imagine that mast bumping isn't a problem due to the fully articulated rotor design, but here are a few other things that could be interesting to explore: - Amount of pedal input leading to blade intersection at hover/forward flight. - Velocity and other conditions attributing to retreating blade stall and blade intersection in forward flight. - Angle of no return for dynamic rollover. - How fast-descent-to-hover attributes to recirculation in ground effect. - Descent rate and other factors contributing to vortex ring state (can it occur during nose-up deceleration). - Parameters for overpitching. - and how to avoid it. Throw in a few suggested procedures for counteracting systems battle damage (e.g. engine, generator, and fuel pump failures) and I'll be a happy camper.

Yep ;)

Thanks, Groove. It would be very interesting to see screenshots, or even movies, of that type of damage modeling. Perhaps that could be the topic of a future producer's note, maybe even in connection with an overview of the electrical power and fuel systems, and how to counteract damage to those. One can hope... ;)

I was just wondering if this phenomenon presents itself in the dynamic rotor model, and if any of you beta testers have run into this. I know that sudden large applications of rudder may lead to blade intersection as a result of the top rotor experiencing a decrease in load and thus downward flapping, while the bottom rotor load increases, resulting in upward flapping. However, I haven't seen any discussions on blade intersections as a result of retreating blade stall. I imagine that at very high speeds, the retreating blade may stall and cause a sudden downward flapping. This would resulting in loss of lift, which might prompt the pilot to apply more collective, causing an exacerbation of the retreating blade stall coinciding with upward flapping of the advancing blade. On the side where the retreating blade is above the advancing blade, this could lead to intersection. This would be even more of a danger in the case where the pilot applies a sharp collective increase, even at moderate speed, leading to inertial over-flapping (as opposed to sudden retreating blade stall), and perhaps be enough to cause an intersection. So do you risk destroying your own rotor blades if you don't go easy on the collective at high speeds?

Weakest link Just remember that the slowest RAM module sets the pace. It won't help buying the latest and greatest if your existing memory is moving through molasses. The paired memory is an advantage, since it has very similar timing, i.e. one stick doesn't have to wait for the other during any of the various operations it performs. Basically, they are equally slow and/or fast at the same things, which means you don't always have to wait for the slowest participant.

Existing terrain Trees that will keep me in the "suspension of disbelief" zone, close up. There's definitely room for added detail levels in this area. Oh, and anacondas. ;)

If I had to choose one from the poll (only 4th generation fighters), I'd say Mirage 2000. On the other hand, if I could pick any aircraft, I'd say Su-35 Flanker-E, with second place going to MiG-35 Fulcrum-F. I'll throw in the Rafale on a third place as well.

F/A-18E!

Wildlife at last? I'm sorry, but as a member of the old Jane's Apache Longbow gang, I have to ask: Will there be wildlife? Will we finally get those anacondas? :smilewink: