Pocket Sized

In 1.5.6 update two, I'm still seeing the aileron locking behavior.

None so far, but I don't think it can be too far off at this point. I remember hearing that once the spit FM is done they'll begin work on the Su-33, followed by the MiG-29.

I am currently running 1.5.6 update 2. It's also present in 1.5.5 and 1.5.4. Problem: Ailerons seem to create a tremendous amount of drag when deflected. Replication: Accelerate to 600-800 kmh at low altitude and stabilize your airspeed. Do a full deflection aileron roll and note how much airspeed is lost almost instantly. The amount of drag is comparable to extending the airbrake! Does anyone know of this is accurate behavior? It makes high speed dives difficult as countering uncommanded roll results in severe speed loss. The F-86 has much bigger ailerons that deflect further but they don't have any noticeable effect on airspeed when used, especially not to this degree. I will probably upload a video later today replicating the problem.

I feel like the ailerons move too slowly. Unless the stick in the real aircraft has some VERY serious eddy current dampers, I think it should move a bit quicker when the pilot wrenches it over. Or it could be that the ailerons move at the correct speed and the stick is just moving in unison with them.

No. It has been updated and is now on the latest version of the open beta. This weekend it was down because it wasn't updated on Friday, but that has been resolved.

I often manually retract them after takeoff until 350 kts to reduce drag. As for dogfighting: Auto. The flaps are scheduled to move proportionally with AoA until a certain Mach number (with a small amount of delay) One trick is to structure your maneuvers around the auto flap system. I usually pull just enough to get the flaps moving before really digging into the turn. Airframe buffeting indicates you're pulling too hard for the current flap position and energy bleed will increase significantly. If you need to run away or gain energy in a straight line, putting them up doesn't hurt, but 99% of the time they'll already be up if you're in auto.

Is this the "server update timeout" issue? If so, I cannot wait for the patch! That is the one and only reason I haven't been flying the Viggen 24/7.

There's also "iusedtogomach" This is my favorite video by him, taking a legacy hornet to 1.77 mach in a dive. He has quite a few interesting HUD tapes on his channel. [Youtube]HxFEqYcGrhc

"Ammo pod"?

The server uses Dynamic Weather to allow for stormy conditions over some of the northeastern airfields while the spawn airfields are clear. Only problem is the wind you mentioned (I've gotten killed by VRS thanks to that wind countless times) and the clouds make Sabre Alley unflyable. (The "Race-SA" aircraft spawn just off the coast from it) It seems like the best option would be to get rid of the dyn weather and replace it with a light wind and scattered clouds throughout the map using static weather. Either that or move the weather further north until it no longer blasts the helicopters/obscures sabre alley.

The 1.5 stable server was taken down in favor of the open beta. Both the open beta and alpha servers were down for a few days as they weren't updated with Fridays patch, but they're back up now.

I wouldn't worry about that, as the Huey's FM is EXTREMELY good. But technically it's an External Flight Model, because it comes from a 3rd party developer. But then again BST does work closely with ED so it might be a PFM... the world may never know.

That's the spirit! :thumbup:

Because it's still in beta and not very stable.

Make sure the aircraft is not heavily loaded on approach

Not really. In this case it's related more to the center of gravity and stability margins of the airframe. The Viggen is relatively nose heavy, which grants good stability/departure resistance at the cost of performance and large trim changes with airspeed.

Because the Viggen, like most aircraft, lacks auto trim, you must re trim the aircraft with changes in airspeed. (Also stay below 0.9M, trim gets weird above that) Here's a little trick I figured out to get around the very slow pitch trim hat: When you level off, click the ATT hold autopilot on for a few seconds and center your stick. Once the plane stabilizes, disengage ATT hold and presto! Perfectly trimmed for 1G flight at that airspeed.

At sea level, no. As you go higher the engine throttles back due to a bug in the fuel control code, which can be mitigated by turning on manual fuel control. I probably should have been a bit more specific about what I meant, I was referring solely to the performance in MIL power compared to, say, the Mirage or F-15. Ask any of the guys I fly with and the'll tell you I can't stop bragging about the glory of Zone 3.

Also curious to hear any news about this

On the topic of the engine, the Mirage has a very unconventional thrust curve. The engine reaches nearly full mil thrust at a relatively low throttle setting. The Viggen, like most other a/c, is the other way around. Between 20-60% throttle the engine is basically in flight idle, above that thrust picks up quickly. Also the Viggen is horribly underpowered compare to modern aircraft in full MIL.

The afterburner lights only indicate throttle position. If you engage afterburner in flight (especially noticeable in the mid subsonic range) the acceleration takes about 2-3 seconds to really pick up. So far I think the Viggen has the best afterburner simulation in DCS. I think audible vortex rumble would be a great addition :D

I have gotten the landing fin to work once, but I can't remember the conditions. I usually use landin P/O mode and it always sticks inside the velocity vector regardless of AoA ("speed too low" indication)

The climb performance matches reality pretty much perfectly when in manual mode. Manual mode is only used in emergencies in real life as far as I know.

Whatever it is, it's very intermittent. On Aerobatics Online I've gotten booted off before my canopy closes at least a dozen times now, but I've also had 3 or 4 sessions that lasted 30-120 minutes with no issues. I didn't notice any apparent correlation between timing out and server uptime/client count but I could be wrong.

That's actually a really good idea! I have no idea if it would work in practice, but if you're going to make an accurate Maverick simulation, that's the way to do it. The Mav shouldn't have any insight as to where exactly objects are or if they're alive. Once this script analyzed the image and determined it is within params for a lock, the trouble would be somehow telling the weapon in DCS where it's supposed to go. Edit: Maybe you could simply keep the "lock" command from reaching the missile until the script gives the go ahead for a lock? Ofc this wouldn't allow for locking on to any object that has contrast but it would insure it's not locking on to things it shouldn't be. It would also make bigger objects lockable from much further away.