corvinus

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.

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:

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.

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.

*Ok, I can't quite wrap my head around it, but here are my observations: 1. In the mission the distance between B1 and B2 is just about 10 km, so a pop-up distance of 10 km won't work (you'd have to instantly jump to a different location). But forget this, if you do 349050, it doesn't work either. 2. Well, doesn't work ... What I have seen is that the switching logic seems ok, but the commanded azimuth does,, not bring you to the correct point. So if you input 349050, the azimuth of the target is not 349o if the distance if 5 km. As a result you don't switch to M2 when you would expect it. However if you keep following the commanded azimuth, then you usually do switch to M2. But you're basically circling back to the target location (it's kind of hilarious). 3. For some combinations of pop-up distance and heading I do get good results, but I can't explain why yet. I seems related to the commanded azimuth. When you hit waypoint B1 and the commanded azimuth is way off your current azimuth, then it is impossible to adhere to the commanded azimuth. As a result you end up in the wrong place. Well, that my hypothesis so far. If you use 340050 at B3 in the attached mission, you'll find it is succesful. Also with 270070, but in that case you see the distance indicator hit 7 km, then it decreases, increases and when it hits 7 km again you get the switch (and correct azimuth). It is probably related to a recent fix, see: https://forums.eagle.ru/showthread.php?t=222415 I can confirm chasing the pop-up point ... __________________ M05 - SB71 LD DYK PRECISION.miz

Dumb question, but how can I change the callsign in the ME? Isn't the predefined list fixed?

It seems I can confirm this bug. I personally fly the Viggen in Caucasus only, there I never experienced problems. Would it matter that you are flying in the Nevada map? You could try setting up a similar mission in the Caucasus and see if that works for you. P.S.: Destroyed the TV tower anyway. :D

I'm using Open Beta and are not experiencing problems with pop-up points. Without more context it is hard to say what is causing your problem (you could post a track or mission file).

At the moment it is not possible to turn off ternav, not explicitly using the computer or implicitly by turning off the rhm. Afaik the rhm is the only source that provides height above terrain info. See also https://forums.eagle.ru/showthread.php?t=194809

That sounds about right to me too. In terms of avionics and weapon systems everything is pretty much there. Of course, there are some issues that have to be ironed out. On the other hand, from a user's perspective, one can value a manual, missions and campaign as 25% of the module. ;)