spiddx

There is weird stuff happening across multiple modules (Viggen, WW2 birds, F-5,...) after the latest 2.0 update. This might be related. Not everybody seems to be affected though.

In case you didn't see it in your other thread:

You can read up on TACAN navigation in this thread: https://forums.eagle.ru/showthread.php?t=175448 Have fun!

Won't help. Look at Mirage: the limitation warning is in the manual since beta release and 15 months later people are still creating bug reports about it. ^^

Ja Nav Fixes in der Mirage funktionieren im Moment (noch?) nicht richtig. Die Updates korrigieren den Drift immer zu 100% korrekt, egal, wann und wo man den Fix auslöst. Man kann somit auch nicht absichtlich einen "falschen" Fix machen... Ist also zur Zeit mehr ein Cheat als ein realistisches Verfahren. ;) Ich hoffe mal, die Devs verbessern das System irgendwann.

Well they told you to get 8 gigs of RAM, not 32. Just sayin'.

Half true. It's fixed in 1.5 for quite some time now, axis are fully customizable. Not in 2.0 though as that hasn't been patched in ages. Afaik there is a Nevada update planned for tomorrow, so we should get the fix there soon.

+1

Nah they simulated the harness your pilot is strapped into.

Low priority stuff: I taxied out without disconnecting ground power (mad crew chief and everything!). Finished the mission, started a new one => Ground power was already connected when I entered the cockpit. Pretty handy, but probably not supposed to happen. :D

Well we should have a margin of at least 15° off so we'd end up in the dirt long before the NAV SYST failure appears. ;)

Awesome, thanks a lot!

Afaik it's a DCS wide problem, other modules are affected as well.

Same here, pages are empty.

Right. That got me confused at first too, it's a little bit unintuitive. It is. ;)

Nope, that's not an actual position of the dial, it's just the descripton of what the following line refers to. So inner line => bombs, outer line => RB05. What you need is the position (mark) in my picture. ;)

You are talking about this position, right?

https://forums.eagle.ru/showpost.php?p=3029987&postcount=6

Don't watch that!!! Damn song is so catchy, couldn't get it out of my head for the last couple of hours... :poster_ban:;)

You are using the latest Open Beta, right?

Let's say your starting airfield is at 120 meters ASL. So your starting position is 100m above the tank. Now before takeoff set your altimeter so that it displays 100 and dadaa! Target QFE aquired! :) Obviously doesn't work with air start... Or you could just add a waypoint at the target location (in the Mission Editor) and its QFE will be generated automatically in the kneeboard. ;)

Well Viggen is out for one day, so expect people getting a lot more efficient with it with practice and after a few bugs and missing features are resolved. Remember when M2000 came out and people were slaughtered by Mig-21s left and right. That situation changed rather quickly after a few days of practice... :)

There seem to be a couple of issues. See here: https://forums.eagle.ru/showthread.php?t=181637

Well it's pretty obvious that ED worked on 1.5.6 since at least the end of the holidays. When it became clear that it would be ready for release on the 27th in your opinion what should have happened? 1) Release 1.5.6 in stable and risk bringing major bugs and problems for all DCS players. (In fact there are major visual and performance issues in the beta right now) 2) Pull resources away from DCS development to update the now obsolete 1.5.5 to bring Viggen to 1.5.5 stable (also risking bugs of course) for the - according to this thread what? -15-20 people who have a problem using the beta or can't wait a week. I'm really curious what you think the best course of action was.

You are really not doing yourself a favor with that ridiculous insinuation that this was done on purpose.