Corrigan

I use a mini-joystick on my throttle, with two axes, to control the RDR CURSOR. In the FCR, this works fine -- the slew rate is normal. However, for other sensors (like HARM and the HSD), the slew rate is much too high when the movement is diagonal. In other words: when moving the cursor along either single axis, it moves as intended. When movement is diagonal, it moves many times too fast. This is shown in this short video. https://youtu.be/GwBM-HUgdBU First, I move the cursor on the FCR. Speed is normal. Diagonal is a bit faster (probably sqrt(2) times faster). Next, I make the HSD SOI and slew the cursor there, using the exact same joystick. Now, the slew rate is normal when moving only on one axis, but much too high when moving diagonally. This issue does not occur (on any sensor/page) when buttons are used to slew instead of joystick axes. It seems to have been known for many years (https://forum.dcs.world/topic/281024-can-i-adjust-harm-page-curser-speeds) although it seems that the connection to diagonal movement was not made before. This really deserves a fix.

Yeah, the performance is way off. https://forums.eagle.ru/showthread.php?t=181927 EDIT: feel free to post in that thread if you have good evidence that the performance is lacking, and in what way.

You don't get to have opinions about facts. You're just wrong here, sorry.

Nu jävlar!

Great post, thanks for this. As most people probably know by now, Flygvapnet did not mess around when exercising attack missions, neither with Viggen nor with Lansen. They'd often fly exercises in pitch darkness (heard once per week at some point during the '80s or '90s), and some of those times they'd be in complete radio silence for the entire flight, so that really great idea about a light hidden by the speed brakes definitely wasn't for show. Here's a fantastic video showing some low-level Lansen flying. Watch the whole thing, not just at my timestamp. Crazy.

Looks great! Love the bloom, very '80s.

Flappie, you're a warrior!

Okay, so I can see two issues here. First, the suddenness with which the plane is willing to rotate, which I can kinda see as plausible now as per Pocket Sized's post. The second issue is that the plane does not rotate when it should according to the SFI, as outbaxx has found.

Yeah, and this is because the engine is used to circulate coolant, and ground idle is not enough to cool the systems outside of BER mode. If you need NAV earlier than 2 mins before take-off, you can kick the throttle into flight idle and that should be fine (according to SFI).

Are radar alts even modelled as emitters in DCS?

Yeah, the RM8B of the JA had an extra compression stage that took care of that problem. Remember, the AJS is not a fighter. It did many things well, but not dogfighting.

Do we know how far the elevons should deflect?

Okay, well, fair enough. I should perhaps add that my experience is limited to simulated aircraft (and common sense + physics degrees). It's just that I've not seen anything mentioned in the SFI about this being an issue.

This is wrong, then. Surface authority should turn-on smoothly with airspeed obviously.

Where are you getting this from? The flaps should not move.

I've seen this too. I assumed it was because I might have bound some switches to my throttle and have "synch controls on start-up" on.

I don't know it it's realistic, but that's chromatic aberration and it looks great!

Nope. Countermeasures, Rb-24 and AKAN pods are the only things you can mix with other ordnance.

I fully agree with both of these.

Fair enough!

Is it possible that they can't see/lock them while sea-skimming?

Looks great!

Good thought, but yeah, actual climb according to the variometer as well. Besides, TVV above horizon does mean I'm climbing, not that the nose is pointing there. Am I the only one seeing this? If so I'll make a quick video.

Excuse me?

Well first of all I agree that there seems to be a problem here. If the manual recommends a rotation speed that's not achievable in-game that's obviously a problem. I was just saying that in that specific scenario there probably IS a limit on how heavy you can be for an MS takeoff being safe. Maybe this needs a bug thread? "Manual says I should be able to rotate at v = V with w = W, but I can't." Seems like a pretty obvious bug to me.