Sergeant_Hamlet

Yes, this is exactly what I'm talking about. Honestly I don't really care if heatblur posts it right now or after they release the module, so long as they tell us their plans eventually. I'm just taking cobra at his word. Right back at'cha chief! :thumbup:

Oh. That’s the module’s ea release day. I’m talking about the roadmap for early access content.

The 18th is a Monday. What calendar?

How ‘bout that roadmap? :)

I know that the literal and functional definitions of trim are different. I was just being pedantic :)

Everything you just said was more or less correct, except for your very first sentence: Read that again. In order to have deviation from a center point, there has to be a center point.

I would also say that if you have a controller with a good throttle response it will definitely be easier to just practice making the adjustments manually.

I've been wondering about the radar screen symbols for a while now. Does the radar in the real airplane display returns as a little box?

pfffft. 747's can't carry AMRAAMs, so they don't count. ;)

Almost all new aircraft are pushed to the open beta branch first, and then to the stable branch the following week. It's a safe bet that the 'cat will be the same.

Well like I said the throttle doesn't have a neutral point that it returns to when you release the controls, so it can't be trimmed like the flight control surfaces can. If you adjust the throttle to set the engines at 90% RPM, they will stay there until you move the throttle again, so you've essentially "trimmed" the engine to 90% RPM. I imagine you're thinking in terms of making small adjustments in airspeed? In that case, the closest you can get is to use the Auto Throttle Control. When you engage the ATC the aircraft will automatically adjust the throttle to maintain its current airspeed. However, because the throttle handle is physically connected to the engine's power lever, moving the throttle manually will override the ATC setting and the ATC will disengage, so it can't really work like cruise control. What I guess you could do is set the ATC, then move the throttle until you get the new airspeed you want, then re-engage the ATC to maintain that new speed. It wouldn't work in real life, but hey, whatever makes life easier. :thumbup:

I usually just let them land first, but I think if you never tell them RTB and just land, they will then break off the formation and enter the landing pattern on their own. The interval won't be realistic, but it should give you enough time to get out of the way.

What do you mean when you say "trim the throttle"? The throttle doesn't center itself, it stays at the setting you give it so trimming it would be redundant. It's possible to set the ATC which will attempt to keep the aircraft at a constant air speed, but that makes the throttle adjust itself forward and backward (you can see it moving in the in-game cockpit), which is like the opposite of trim. You also can't adjust that speed setting up and down like cruise control in a car.

This isn't completely true. The AOA indexer lights tell you that your are either too fast or too slow to maintain correct angle of attack at landing speed. If you drop your flaps and the plane rockets into the air, it's because you are too fast. The way I like to think about it is, don't fly to place the FPM on the E bracket, but instead fly to place the E bracket on the FPM. If you are flying gear out, flaps down with the E bracket above the horizon, and you are constantly pushing the stick forward to keep the FPM on the horizon, the AOA indexer displays will tell you that you are fast. If you take the throttle back and use the speed break as necessary to slow the aircraft down, slowly release forward stick pressure, and then start to slowly apply back stick pressure to keep the FPM from dropping, the E bracket will drop down to meet the horizon. Trim out the back stick pressure, and feed the throttle back up to stabilize pitch. From this point you should not make any pitch changes with the stick, only power adjustments with the throttle. Once you are established in this mode of flight, then you can forget about your speed and pay attention to your throttle instead.

Yeah, I read the wrong acronym. :doh:

http://www.heatblur.se/F-14Manual/general.html#afcs-automatic-flight-control-system edit: :doh: Wrong acronym. My bad.

If any real development issues still exist, then ED would be completely right to tell Heatblur to do more work on it. That's the whole point of QA testing. I don't think that there are any serious bugs holding the module back; I'm pretty sure it's just that the module has a high level of complexity (the damage model apparently has a loooot of failure states) and all the components need to be verified as accurate and not broken, which takes a while. But I'm not a QA tester for ED, so I don't know. Just guesswork here.

I just don't buy that. If ED needs to have their internal QA team review all 3rd party modules before they release, then there has to be either a team dedicated to that task, or people have to be pulled from other tasks to do the testing. Since ED is a small company I think the latter option is more likely. Since Razbam completed their release candidate first, they were first in line. If the Mig delayed the Tomcat at all, it is far more likely that it was an issue of resources, not marketing.

I actually think that the fact that ED is taking their time with it is a very positive sign. To me it seems like ED has finally taken it to heart that they need to step up their quality control. This is good news for us as consumers.

Hot dayumn. You sure haven't been wasting time. Are you planning to just flood the internet with videos during the week before release?

Yes that's correct. The spoilers deploy on the wing that is inside the roll

the long-awaited DCS Cow

Abandon thread? But it was just finally starting to get good!

Hell yeah! Where did you find that?

Cobra is constantly telling us to expect bugs in EA. Also there were a few bugs on display in Jabbers' latest stream. Almost all of them involved jester. There was also a collision detection glitch during his refueling attempts