fjacobsen

Title says...

STT is mandatory for the AIM-7, while TWS can be used with the AIM-120.

If no target has been locked prior to selecting the AIM-120, it will be in visual mode. If a target has been locked, and then selecting the AIM-120, then it will be in normal mode.

Is it possible to change the range on the MFD radar page when a target is locked ?. Seems the range change arrows are removed once a target has been locked. If not, then I would expect the range to automatically change as the target gets closer or moves away.

Please read my initial post once again. I guess we all can agree on this posted by bbrz: "The point is that you don't set a certain pitch, e.g. 15° with the prop lever, you set a certain RPM!" Only caveat ist that You don´t set a certain RPM, but set a desired RPM, and the prop governor will adjust the prop pitch to achieve that RPM, but it can only achive this within certain limits (low and high stops of the prop pitch). Generally for such constant speed props, You might see rpm drop with low throttle setting and low speed (f.ex during approach, standing still and offcourse with the engine stopped ), cause there is not sufficient airflow to windmill the prop to the set desired rpm. Also on the extreme, going into a steep dive, the govenor will lower prop pitch, but once reaching it´s low stop, prop RPM will start to increase. So in most conditions the prop lever might be refered to as engine rpm lever, cause thats what it will do, but still only within certain limits. A better and also most used name for it is Prop control lever, cause that's universally usable for the different kind of propeller systems i.e Constant speed, variable pitch or two state props (as used on the very early Spitfires f.ex). The BF-109 and FW-190 f.ex did not have constant speed props, but variable pitch props, where the throttle and prop levers where combined into one lever (called Kommandogerät on the FW-190).

And what rpm do You get with prp lever full forward (high rpm / fine pitch) throttle at idle standing still on the ground ? Definitly You don' t get high rpm.

Normally the angle of the propeller blades are also refered to as pitch and the lever simply called prop lever. Calling it Engine RPM is somewhat wrong, since it only sets the engine rpm to a certain value if the propeller governor has something to work with i.e if the throttle is set near idle and the airspeed is low, then engine rpm will drop regardless of the prop lever setting. With the prop lever You essentially tell the prop governor which prop rpm You would like it to spin at, and the governor will adjust the propeller pitch accordingly, though within limits. So the prop lever does not set propeller pitch directly. All this offcourse only holds true for constant speed props. There are also variable pitch propellers, where the prop lever will set propeller pitch directly and thus calling it prop pitch lever is right.

Yes - it´s the same.

Also important for the prop warbirds... Turn off landing set to zero) help in the special tab, cause it won´t help You learn proper landings. As said - just keep practicing,cause there is no substitute. Actually for me, landing the Spitfire, still often ends with a groundloop. You really need to dance the pedals like a Fred Astair, while keeping the stick pulled into Yor chest.

I agree - the Yak-52 is not going to learn You alot about flying high performance proepeller taildraggers. The best recommendation I can give is simply to practice, practice and practice. The hardest one to land is the Spitfire, cause the landing gear is so narrow combined with the tailwheel not being lockable. I find that the P-51D and the FW-190D9 to be the easiest to learn. Best advice is to keep some power on during the ground roll.

Gear and flaps movement is done with airpressure. Once the flaps and/or gear has been moved, there is no need to keep pressurating the actuators. At the same time that would also negate the the control of them from the other cockpit..

With latest update I still see excessive RAM usage and stutters with the AV-8B. Especially o the Persian Gulf map, it stutters alot. I hope they soon start to optimise the module for better performance.

Well - not available in the open beta, but still available in the stable version.

Regardless how You see it.... The stutters are game code related. I have alot of games installed, some with high requirements, but none of them stutter and can easily be adjusted for smooth running, mainly by lowering graphics settings. I find the devs. should put more effort into finding the culprit for these stutters. Instead we are just recommended to buy more RAM or a heftiger PC. Problem is just that even some people with plenty of RAM and powerfull PC's are getting stutters as well.

Thats also my experience. I can fly all other modules with quite smooth performance, but with the AV-8B I get some heavy stutters and often also freezes. This happens especially when the DMT is displayed. Right after EA release I remember there was an issue with all displays being rendered in the background even if not displayed - maybe this is back again.

By "accumulators" are not meant electrical batteries, but hydraulic accumulators. These are pressure bottles with a rubber balloon inside, filled with nitrogen. These balloons are pre-charged with the nitrogen with pressure. When the normal hydraulic pumps operates, hydraulic oil is pumped into these bottle and compresses the nitrogen filled balloon. This way hydralic pressure can be stored. Not sure if the AV-8B has such accumulators though.

On my system I get more stutters in the AV-8B than in any of the other modules. The KA-50, A-10C and F/A-18 runs smooth ans with very few hickups. But with the AV-8B I get some nasty stutters and sometimes freezes for a few seconds. It seems related to the rendering of the TPOD, DMT and Maverick displays.

After some tests, I found that the stuttering mostly occurs with the Razbam AV-8B. Other modules do not stutter very much and the sim runs rather smooth.

I have not checked actual memory use, but when the "texture unloader" was introduced, flying the AV-8B became smooth. But with the latest update(s), for both release and open beta version, it has started stuttering again. So maybe the culprit indeed is that something has been reverted that shouldn´t.

Seems no update for 2.5 beta today...

One of the errors one easily make is comming in too high. Also note that the scale of the VSI is different and more course than for the UH-1D. As You deccelerate, pepare to add collective as You come out of translational lift.

Yes I did - and that did the trick... Thanks for Your feedback :)

In nav mode a caret will indicate PVI-800 waypoint bearing on the HUD. After I have recieved a datalink target from my wingman and locked it through the SHKVAL, the caret changes from a diamond to a circle and now indicates bearing to the target point - all fine... But when finsished attacking and resets the targeting system, the HUD cahnges back to NAV mode, but it still indicates the circle caret and "bearing to target point" instead of reverting to the diamond caret "bearing to PVI-800 waypoint". Is this a bug or must I do something else ? I have tried to center the SHKVAL, delete the datalink on the ABRIS, but cannot get the diamond caret back !

I´m curious too... Seems that progress, or at least updates, has been put on hold since the release of the F/A-18 (not a Razbam module, I know). I just don´t hope that the AV-8B will become the same slow project as seen with the M2000C.

Not to spoil the party.... But I rather want to see the M2000C and AV-8B being finished, rather than get on the hype train towards another lengthy early acces module.