TOViper

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.

Done. I had to remove all WAV files from the missions, thus they might now work. Anyway, you can analyze them in terms of the warehouses. The problem is the programming strategy they used for the EQP tab. Instead of adding new DCS items to the end of the list and show the list sorted alphabetically, they somehow changed indexes of existing items (which is a killer). At least this seems to me when looking at this.

Hello Nealius! From a technical point of view it makes sense to turn the nose into the wind in order to avoid starting problems and overheat of the cowling. Aircraft usually allow for a maximum tailwind component for engine start (e.g. not more than ~5-10 knots). To be honest I am not sure if this is the logic of the game because the programmers took this into consideration, or simply a bug.

Just to make clear what I was talking about: In the "A/C" tab: The strategy to show newly added aircraft to DCS with a value of 100 is a good idea. It is not a problem to change the number, e.g. to zero. This step is - in fact - not really necessary, because during creation of the mission in the past the new aircraft were not available. Fine! In the "EQP" tab: The problem arises in the equipment tab. Once the mission is opened in a newer DCS version, the first lines - depending on which content was added - are emtpy, and with a number of 0. If I want to add the newly created weapons of my new DCS version to this specific mission, I have to first click "Unlimited Munitions", save the mission, and then uncheck this check box. This - of course - kills all settings from the past, and I have to reconfigure all numbers from scratch. These are my two cents on that. I am still not sure if the other guys are talking about the same or have other problems. Flappie: I could send mission via PM, is that OK?

I have to add that it is not required to fly a full loop in order to get the freeze. Today I flew 70° nose up, then rolled half, and went down. After reaching normal flight attitude the sim stopped (was a reverse half cuban eight).

De nada my friend. What would we do without a manual? Loosing our minds sometimes ...

According to manual RC2 - and according to my understanding - the steering orders (bearing & distance) should be as follows: ADI: U point and M point HUD: U point and M point CI: M point only(!) I made a track where you can see my inputs right before take-off: - TAKT - IN - 22506 - B2 (which is M2 because it has a time-on-target TOT defined via the mission editor) - OUT - AKT POS After lift-off and reaching 400km/h, the waypoint B1 is selected automatically, showing the steering orders on CI, ADI, HUD. When passing B1, the next waypoint U2 is selected automatically, showing the steering orders on ADI, HUD. After passing U2, the M2 target point is selected automatically, showing the steering orders on CI, ADI, HUD. Viggen_PupUp-Point_working_on_HUD_and_ADI_as_intended.trk