corvinus

Thanks, I was unaware of this ... I have two monitors, so I wonder what that will do, but I will try anyway.

https://forums.eagle.ru/showthread.php?t=196692 https://forums.eagle.ru/showthread.php?t=224118

I have the same thing. Got the fps maxed at 60. Ignoring explosions I used to reach 60 fps without any problems. Since the latest update it dropped below 50 ... I tuned down mssa a bit to restore performance. What is the deal with lalt+enter? I always run fullscreen ...

At 1 m/s wind I did not notice any drift, but at 4 m/s cross wind it started to get bad enough to miss the target. Not sure if this is a bug or a feature :huh:

Iirc you have to do a 4G pull-up at trigger pull. Are you doing this? Personally I do not have a problem with DYK bombing, but I have to admit that I usually use a steeper dive angle, which is more precise.

Using the MFCD selecting the sidearm works ok now for me. I do have to press the button three times. This is from an in-flight start btw.

Great news! The bug fix and the video are greatly appreciated. :thumbup:

Did you compare the fixed target point coordinates with the actual impact location coordinates? Just to verify if the bk90 is flying to the updated coordinates or not. Note that radar fixes are not very precise, due to radar resolution limitations and the fact that you are flying at high speed with radar updates every few seconds. So your radar fix is likely to be off a bit. For what it is worth, the bk90 is flying to updated coordinates in my test mission. So that part seems to be working.

:lol: Well put (and funny).

Indeed, friendliness goes a long way, especially towards newcomers.

Thanks! :thumbup:

Thanks! I found the rotary the other day, but did not relate it to the sidearm. Will try it out!

Guess so ;). Personally I never got it to work, but of course, that does mean not anything.

The latter statement is an assumption on your part on how the Viggen should work. I tried to show that you can follow a different reasoning just as well. I am not saying you are wrong, I was only suggesting that the Viggen engineers could have made a different choice. Like I said, the wingspan method is a rough method, even with an orientation mismatch you can use it. Of course, for more precision use the radar, especially in a turning dogfight. Anyway if the wingspan is not supposed to be horizontal all the time, then I am sure Heatblur will fix it. They probably have access to documentation explaining the functionality.

How do you change the volume?

I think I understand your reasoning and you bring up an interesting point. I would like to add that the Viggen does not know the orientation of your opponent, i.e. it does not know how that plane is pointing in space. So there is no way for the Viggen to orient the wingspan indicator to match the orientation of the wings of your opponent. The Viggen engineers thus had to make a default choice for the orientation of the wings. They chose a level flight for the opponent, which is what you observed: the wingspan indicator is always horizontal. Now for a turning dogfight against a fighter that is probably not the best choice, but for engaging a slowly turning transport aircraft it probably is. I wonder what rationale the Viggen engineers used when designing the indicator. Does anyone know this? P.S.:The wingspan indicator method is not very precise (the wingspan indicator itself can not be set very precisely and the target aspect leads to foreshortening of the observed size of the target), therefore you can get away with mentally comparing the wingspan indicator size with the observed target size.

Boundary lines are not implemented yet afaik. Besides that everything is there and working.

Is this on the ground or airborne? Never seen this in the air and I am using this all the time. Never touched the buttons on the ground though.

Makes sense, thanks for the clarification!

Do you mean this in the context of multi-target engagements? For a single target engagement STT is sufficient, is it not?

Fyi, SLAMRAAM is used in the NASAMS system, it is operated by a handful of countries. See: https://en.m.wikipedia.org/wiki/NASAMS https://en.m.wikipedia.org/wiki/SLAMRAAM

I'm trying to figure out how to detect if the canopy is closed in the Viggen. Is "X:COCKPIT PARAM EQUAL TO" the way to go? If so, how do I determine the proper values for PARAM and VALUE? I found this in clickabledata.lua: elements["PNT_9"] = default_3_position_tumb(_("Canopy Open/Close"), devices.FLIGHTDATAUNIT, 3406, 9, false, false) elements["PNT_9"].sound={{SOUND_CANOPY},{SOUND_CANOPY}} No clue what to do with it ... :helpsmilie:

Afaik the radar detection algorithm for search radars is pretty basic, it uses a maximum detection range icw terrain masking. The maximum detection range is usually several hundreds of kilometers for AEW (airborne early warning). Also it is flying high, so you really need to use valleys and mountains to hide behind.

I'm more of a "meatball import" kind of guy :megalol:

Ah ok, for a minute I was hoping there was a way to extend the list. I guess that is not possible due to the radio messages. Using the group and unit names is a good alternative, at least they show up in the logs.