TOViper

Ok, now we are talking about the same situation. TOM was 17.2 tons Drag is high due to the two pods. I will try to use different loadouts with the same TOM, and see what's happening. Don't forget, the MIL thrust in the Viggen is just 6.5 tons, which is about 38 percent of the weight. This is like an average airliner ...

hm, I have made a track, in which I can find no abnormal behaviour ... If you watch, would you then say it looks abnormal? AJS-37_Viggen_Performance_with_XT_2xRb24_AKAN_at_ISA.trk

I have some of them in the AJS-37 Viggen too, so if its the same problem in the background, it is not specific to F-14. But specific to HB

Erm, guys, what was the OAT and pressure altitude in your test missions? Temperatures over 30 degrees show significant performance degradations, as well as pressure altitude does so. Did you try it at ~ 0m MSL in 15°C? Also, was the gear really retracted and the airbrake?

Must be something like this. I try to avoid such actions, because I have configured Actions very carefully, and I have a lot of them, thus "I have to" import my old configs. Maybe I will try a comparison of the two diff files (the new current one and the older I have imported). Anyway thanks for your quick answer MAXsenna!!

Hi folks! Since the big Viggen update I have a few exclamation marks in my input configuration. They are visible despite the keyboard commands are not used for any other Actions (I cleared them, tried pressing them, no response > fine) and re-assigned them by using the "Default" button. What is wrong?

Having Voicechat in "Push to talk" mode, I have assigned "Transmit Switch - UHF (call radio menu)" command to my F-16. If I press the respective button on the stick, Voicechat does not open the mic. Only the communication menu "UHF Radio AN/ARC-164" opens up. If I manually click on "Mic on", I can hear my voice on the other computer. WTF? Is Voicechat really ready for use or what is this?

Cool, I will keep on monitoring this thread, despite I am not at home much these days.

They seem to communicate to you, but you can hear them only if you have the canopy open. Don't know if this intended or not.

Hey folks! After long time not using it, I noticed this problems with the listening states since a few days. What currently is not working properly is the following: After switching to another profile using the "VoiceAttack Action" called "Switch to profile" the listening state - once the other profile became active AND the other aircraft was already loaded - switches from "not listening" to "listening". The disturbing part for me is then, that once pressing any TX (either on the stick OR on the Viacom Panel) this action just inverts the listening state instead of checking the real state of the TX buttons. I have no other chance to change back to the desktop (put the VR down), completely close Voiceattack, and then start over again. I am using Viacom Pro Licensed 2.5.26.4 Thanks for any hint / work around! Here is the picture which shows how I change profile:

@Mrgone: All the best to you, keep on fighting dude and may your "re-entry" to DCS be the next challenge for you! @Eagle Dynamics: You always say thank you to the comunity. Now its a good time to say: "Thank you ED for you ongoing passion and support for making this simulation so awesome!" It is a pleasure to fly. Period. Happy new year!! Kind regards, TOViper

no, I flew up to 5000m

OB 2.7.9.18080 MP only When re-arming the aircraft with new Rb-75, they dont' work anymore, no picture of the sensor is shown in the EP-13 sight gauge. I can provide TRK if required, but it has 6MB, so too big for this super-limited forum In SP I wasn't able to reproduce this.

OB 2.7.9.18080 SP + MP The HÖJD CI SI switch doesn' switch to LD automatically once passing the "magic" 1000-1400m altitude. This worked before the "big" Viggen Update.

Oh, I thought I was alone ... Now I think I will do a not for @BIGNEWY here ...

I am using CV1 since 2 years, and I will never go back flying on a normal screen, not even when using Track IR. VR is a different world, totally! BTW: I have configured windows firewall to completely block incoming & outgoing traffic for the oculus dash application and its related helper applications (a few have to be blocked). So, no data is transfered anywhere (hopefully). But I agree, FB is p.i.t.a. squared when it comes to privacy.

After having crashes a few seconds afert launching the server, I changed command line to: dcs.exe --norender --server This helped me. Also, the nasty "Authorization failed" messages for some maps disappeared.

1. no, not for me using my 3-separate-button-config; I am using the commands "T0 Fix", "T1 Fix", "TV Fix"; therefore I am not using any of "T0 (three position switch)" or the "T1 Fix Two-stage trigger middle position" or the "TV Three position switch) 2. yep, right 3. yep, right

He Machalot! Yesterday I noticed that normal nav fixes or target fixes (either with or without radar) also require T0 button to be pressed after TV button was released. If T0 is not pressed finally, the fix seems not to complete. HB changed this intentionally or problem here on my machine? I am using Warthog Stick, 3 buttons: one for T0, one for T1, and another one for TV

One quick info from my side: TAKT OUT doesn't show a "1" for pylons carrying weapons/loadout, it always shows "000000"

OB 2.7.9.17830 SP Persian Gulf F-5E-3 with AI wingman Take-off from Shiraz #-key works on ground to trigger the comms menu, menu is working NWS button on joystick in flight does not trigger the comms menu (despite seeing the button pressed on the cockpit-stick). F-5E-3_with_AI_wingman_NWS_not_triggering_COMMS_menu_in_flight.trk

Hello dureiken, I'm using Oculus CV1 and I have same issues. The first activation of the TGP or WPN page creates a massive drop, but then eventually stabilizes, but at lower frame rate. From my understanding: The TGP has a different view at the world, and the sensor of the Maverick has another view at the world. Thus the views have to be calculated separately each on their own due to the different angles. This of course takes CPU/GPU time, ... don't you think? What makes the part really hard is the massive drop in frames when switching ON the pages, because lowest frame rates are really p.i.t.a. Anyway, I have the same issues when switching ON the TCS camera view of the F-14, the frames drop down to 10, then start to stabilize.

I always had the impression that the wings of the F-5 are far too big. So ... this is how they should be ... ?

Yup. The indicator should read FULL. According to the manual page 201 this is the correct procedure. "3. Set flap thumb switch on right engine throttle to AUTO position (press |F|). At the same time flap lever has to be set to THUMB SW position (center position)." "6. ... Control wing flap extension with help of FULL indicator and visually."

Guys at HB, I wish the best to you for getting all the fixes work properly and make every effort you put it worth it! HB rocks.