Tiger-II

The real units don't support that kind of customization.

I think you can ignore this report - I have flown several times since and all seems to be operating as expected. Not sure what caused the glitch previously.

This. It's by far the single biggest design flaw of the avionics.

I think the 200 is all. We already have all the other weapon types carried. A-A: PL-5II SD-10 A-G: Mk-82 Mk-83 Mk-84 Mk-82 high-drag GBU-16 GBU-12 GBU-10 Guided rockets Unguided rockets Cluster munitions 4 versions of GBU-6 glide bomb 2 anti-ship missiles (one autonomous, one MITL) Optical guided missiles (similar to Maverick) Anti-Radiation missiles Illumination pods Smoke pods What did I miss?!

Uhh... I'll check the status of NAV and try it again.

If it's a feature and not a bug - awesome! 8)

It's verrry subtle. I seem to be very sensitive to things that aren't parallel, so when the aircraft starts to roll I notice it quickly. Try this: load up a clean jet, takeoff, climb to 8000 ft and 300 kts, level the aircraft, reduce power to hold speed, and just watch the roll pointer on the HUD. The thing that drew my attention to it at first was the roll issue but also the fact I kept having problems maintaining heading. I then realized what was going on. You'll need to fly for maybe 5 minutes to really see it. Make sure there is no wind or turbulence in the mission.

It would make most sense if it was reset/new charges installed with re-arming.

Hi, I thought it was my hardware, so I set huge null zones to try and eliminate it. It made no difference. It's hard to describe, but I'll try... Regardless of whether symmetric stores are loaded or the aircraft is clean, the aircraft exhibits a tiny bit of yaw to the left and left roll tendency. It's as if there is some kind of gyroscopic precession being modeled as the result of torque from the engine? Engine torque yaws the aircraft, then roll-yaw coupling rolls the aircraft. It's strange.

I was a bit rushed earlier! Here are some notes from the flights. The AKG track: this was initially just a mess-around with the smoke pods. There is a delay after the first landing as I consult the manual for how to get the smoke pods to work. Seems I needed to assign a key. I then decided to go fly with the AKG for a bit and try the MITL again as I had low success with it (I keep losing signal despite being in good parameters). The first AKG fired was in DIR mode. It just kept flying in circles over the target. The second missile was fired too close to the target so by the time I realized I was meant to control it, it had flown past it. Oh well! As part of those flights you will see some oddities with the waypoints, even though I use the same procedure as in the track attached to this post. I appreciate the first track is rather long, but it shows some issues that are encountered when flying. The track in the first post is hard to replicate without trying to do something. It just...malfunctions. The track attached to this post is rather shorter, but appears to operate as expected throughout the flight. I don't do much except to fly a bit, get some distance as fast as possible and turn back to the field. I do some hard maneuvers that would upset any alignment (I assume this is modeled) but equally I wouldn't expect it to be upset much on this short flight if INS alignment is part of the problem. I did discover during this flight that it is sensitive to roll. The nav box moves very large distances proportional to roll angle, whereas the caret only moves with bearing/heading changes. In the first track I end up with an interesting problem in that the caret is permanently deflected to one side, regardless of where I'm heading, and for some reason there is a tiny short line between the alignment waypoint and the WPT1, even though it was copied. I hope this provides enough for you to figure out what is going on. JF-17 Nav.trk

Please see the attached. JF-17 Nav and AKG.trk

Will a screenshot suffice?

Hi, I've noticed some inconsistencies with the RADAR and target locks. NAV MODE. RADAR in RWS. Target bugged. Triangle for bugged target; still showing other contacts as squares. Switch to AA mode. RADAR acts like nothing is locked in TWS mode. Bug more targets (or not). Return to NAV mode. Original target is still bugged. Dogfight RADAR: Unable to unlock locked target sometimes. Once it gets stuck, it won't unlock. NAV MODE: Using the HOTAS to switch RADAR modes cycles thus: RWS - TWS - VS - MAP - EXP - DBS1 - DSB2 - MAP - EXP - etc.. It gets stuck in AG Map submodes and will not return to AA RADAR modes without entering the MFD menu to switch back to RWS.

I hope this is a priority bug to fix. It makes it pretty hard to use for BVR or searching for targets that you don't know are there.

There are a couple of things to consider when discussing RedFor: 1) Sheer numbers of aircraft. We are trying to operate single-aircraft airforces. Reality is in a war situation it comes down to attrition rates. 2) Different doctrines. US doctrine is air superiority backed by precision long-range strike capability. Even SEAD is less important than it used to be. Other country's doctrine is different: for every fighter they oppose, launch two or three to attack it. It's purely a numbers game. They're not always looking at rolling into another country, but defending their own, so less emphasis on ability to support ground troops or carry out large scale aerial bombing of ground targets. Light attack works for many things except full-scale war. That's why most but the biggest airforces lack heavy bombers, etc. They're mostly about engaging hostile enemy aircraft.

I flew around for a couple of hours and everything looked OK. I have discovered why some RWR targets such as AWACS disappear momentarily: the AWACS has a problem in that the scan area tilts with the aircraft in roll. This might explain why AWACS periodically calls CLEAN when called for hostile information because in a turn it can't see anything.

I don't think so - the bearing pointer remains accurate; the box doesn't align with the pointer. This is true from takeoff, so no time for drift to be an issue.

Chinese New Year is two weeks (generally) so I guess mid-February is when they'll be back.

Will the board be plug'n'play? i.e. show as a standard game controller with buttons, or will it require some additional hardware/software?

The basic model should be available, so if one crew member has it and the other doesn't, the aircraft and sim still works without issues. The guy who bought it will then see everything they paid for. Win-win.

I'm not saying that loaded the F-5 won't suffer, but taking just a clean aircraft and performing idle descents shows something's not right (descent distance is measurably less than it should be). This manifests also in top-end all-out speed, and affects other parts of the flight envelope as well. +1 for manual flaps! Yes... the more interesting aircraft as you mention are unflyable without FBW. A major limitation of simulations are they are inherently stable, which causes problems when trying to model the edges (or beyond) of the handling characteristics.

Other aircraft in DCS exhibit too much drag from what I can see. The F-5 is by far the worst. As the video I linked shows, the pilot is modulating the speedbrakes as he comes around the corner to final. She's sleek for sure. An often overlooked part of the equation is residual thrust; as Jeff is light then even idle thrust will be relatively high, and with a light/clean jet could be significant.

@tweet: Sir, you rock! I'm sorry about your friend. Your posts sum up why I get annoyed reading these "sore loser" posts by everyone saying the Jeff is "wrong" because it's eating their favorite "Blue" jet for breakfast. There are so many facets to ACM yet they want to dive into dissimilar combat as if it proves anything. As for your comments on FCS, AFAIK the only axis that requires it is in pitch, which Jeff has. On the F-16 I think it only has a complete FCS because it can, and helps with control, but isn't necessarily required. I'd wager the F-16 only needs pitch stability as well. Doesn't the F-16 maintain TEF UP even at high alpha? As I understood it the FCS blends in TEF for roll control with gear up, and auto flaperons with gear down (again to aid with roll control at low speed). Jeff has auto LEF which is far more critical, and something F-5 doesn't have (it has auto flaps which camber the whole wing; if the flaps are up so too are the LEF). This comment nailed the whole discussion though: Jeff is a decades newer design.

Great question.

It's been doing some weird things for me. It works, but with some serious glitches.