ZoscheHH

I´ am definetely interested in using your profiles and don´t mind paying a few bucks for them. Where can I get them ?

Got it working ! Thanks for your advice. I presumed, that VA would have made the necessary configuration changes to use the assigned button for "radio communication menu" that I had been using in DCS so far. Didn´t expect to have to configure more. Reading the VA manual proved to be a good idea anyway. @Blacleycole: Do you have PTT already working correctly in VA? Did you assign a button of your Puma flightstick and can you use it with VA to have your commands interpreted correctly? If so, double-check if the assigned flight stick button for PTT is set via the VA joystick icon and if the TX-Key-assignments for the different radios are set correctly. You find them at the very end of the DCS-profile in VA. (Missed out on those in the first place - could have spared me a lot of trouble...) For a start, I defined only a button for TX1 and mapped it in the configuration window [CTRL-ALT-C] to the VHF AM radio. That done, I then jumped into the Huey, switched on the battery, set the ATC-frequency to 138.000 Mhz (@Tbilisi-Lochini) and the radio selector switch to position 3 (VHF). When VA reads your commands correctly, you`ll see your request in written words on top of the cockpit window and ATC will answer your request right away. The next step I want to try, is to assign individual cockpit keys to voice commands, that way I can spare fiddling around with the keyboard for cranking the gas throttle to idle or closing the cockpit doors. ; ) For the future, I hope that ED will further improve radio communication logic, so that requests and clearances are handled the correct way while in the Huey.

Keep getting "PTT Key not in use: check configuration." Hi BlacleyCole, I just read your post with great interest. I love to fly the Huey and installed the VA-Pro-Plugin 2.5.2 yesterday. Did everything "by the book" and have it running by now. I chose a button on my Puma flight trainer for the PTT function. After training the voice recognition system a little more, VA´s recognization of commands is now pretty good. The only thing I just can´t seem to get working, is to get rid of the message "PTT Key not in use: check configuration.". I tried different settings for the TX1 - TX6 mappings in the configuration window (CTRL-ALT-C), but nothing seems to work. In DCS I can hear the static noise and confirmation sound when depressing and releasing the communication switch on my Puma, but nothing happens and the message is still appearing in VA. Since you already managed to get VA working with your Puma in the Huey, I ´m curious what I´m doing wrong here... Thanx !

Thats an issue that has been mentioned in the release notes of the PG map. They are working on it. So, we just have to be patient.

First of all, I must say that the Persion Gulf map is just great ! I love flying between the skyscrapers and settling the Huey on top of all those shiny skyscrapers ! Now to my findings: When taking off with the Huey in rainy weather at around 2 p.m., I noticed these bugs: - Navigation and Position Lights are shining through the cabin, - Cabin Light and Position Lights are being reflected in the glass of the hanger buildings, but not so the Navigation Light - runway and taxiway signs were off (dark), even though it was dark outside due to the bad weather. Might be still a general bug that has already been discussed in a few other threads. - rain drops are not showing on the cockpit windows. Since a feature like that had been announced for the map, I was just too curious to see, if it has indeed been modelled. Hhhhmm...unfortunately not (yet?). At least, it´s not raining through the cabin anymore like it has been before on other maps - thanks for fixing that, ED ! - when requesting permission for starting up the engines and a doing a hover check, you `ll get a clearance from the tower to do so. When you´re done with that and radio in to the ATC for permission to taxi to the runway, there´s no answer coming - no matter how often you try. The communication menu at that point shows "Abort takeoff", which you haven´t even asked for - not yet. I think this bug is related to the PG map and not the Huey model since the communication menu differs from that for the Huey on other maps. ED, keep up the good work and try to fix those issues with the Huey. It´ll make the grade of immersion and realism even greater !

Crossing the holding points has no effect on the communications menu choices. Even if you line up at the given runway, no take-off clearance entry will appear in the menu. Instead, the menu just shows "Inbound" as if you were already airborne and want to radio in for landing. I think they just forgot to set a trigger mark for take-off clearance. In the opposite way, if you radio in for landing ("Inbound"), you 'll get directions for joining the designated traffic circuit. If you follow the traffic pattern as shown on the airport chart on your kneeboard (the correct altitude is important) and get alongside the center of the runway well aside from and above it, ATC will ask you to contact tower in order to make your final approach. You do so in the comm-menu and continue flying crosswind, base and even final, but the tower will remain silent. Only, if you continue on final and are already close down above the runway center, you´ll be contacted by ATC again and given clearance to land. (You might as well be given the order to make a go-around due to an occupied runway (or maybe due to a missing landing clearance ? - who knows...). The comm-menu, by the way, shows at that time "Abort Inbound" again, even though you had been given landing clearance seconds before. Hhhhmmm, looks like ED would have to do a little more work on ATC-communications, I´d say. If anyone of you made a different experience, I´d be glad to hear about it.

Caucasus & NTTR maps: When contacting ATC via comm-radio and requesting clearance for starting up the engines as well as taxiing to one of the runway (holding points), orders are given by ATC in the expected order. So far, so good. BUT: When reaching one of the holding points (hovering right in front of the runway), the communications menu doesn´t show an entry for requesting take-off permission. If in that situation you settle down on the ground and call up the comm-menu, it even shows only "request start-up", as if the clearance for taxiing had never been given before. So, that last step in taking off from an airport doesn´t seem to be modeled correctly (it´s missing in the 1.5 and open alpha version as well). I don´t know if it´s aircraft-specific or a general bug, haven´t tried different situations. Ok, it´s not a big thing, but for making the take-off procedure complete, it´ll be great to have that modelled correctly.

Hey there, I just noticed that the interior light (green or white) is not showing when looking from the outside into the cabin. Haven´t checked with other aircraft yet. Has anybody else ? Greetz, Alex

Can´t make it to the summit of Mt. Elbrus anymore Having flown the Elbrus mission successfully several times quite some time ago, I started it up in the Open Beta again just to see if I can still rescue the stranded soldiers. Everything worked as usual after the take-off, but when reaching 11.300 ft (I think the QFE is wrong from the beginning - in the briefing it says 23.17 mmHg, but you start up with a readng of 28.17 mmHg) suddenly the engine fails. Everything was in the limits except for the exhaust temperature which reads 700° - yellow range. I tried the climb several times going up as slow and close to the ground as possible to keep EGT really low, but on that one plateau in front of Mt. Elbrus the engines simply die with a bang every time. Any suggestions how to accomplish that mission in 2.5 ? What´s the trick now ?

Thanx Gizzy for your screenshot. The confusing thing is the mixed-up usage of the designators "throttle" and "ECLs". With that knowledge in mind, it now makes sense, that there is a "throttle left" and a throttle right". Could not make up, what a function the "corrector" would have since I thought there should be two of them... Hey BelsimTek, it´d be great if you could fix that in one of the next updates ! And please check the international translations as well. Thank you !

I just replaced my ASUS GTX 1070 Turbo 8G with an ASUS GTX 1080 TI OC 11G because I wanted to see how much more level of detail can be set with DCS still running sound and soft. Well, reading all the posts about lags and stutters, I wasn´t too confdent about an improvement, but, what can I say, it just works ! DCS 1.5 set to a quite high level of detail (in-game AF and AA set to max, shadows to flat and low, terrain and traffic to medium, bushes, trees and radius to medium values, everything else to high & pixel density to 2.0) runs smoothly with around 23 fps when close to the ground and a good 45 fps in altitudes higher than 200ft. With the same settings in DCS 2.x, the frame rate stays as low as 23 fps even if you climb a little higher, but, and that´s the difference to my old 1070, there´s no stutter - no matter how close you fly to the buildings nor how much you rotate your head sideways to watch the moving traffic. Great - as far as my configuration is concerned ! By the way, I left the Nvidia control-panel settings to the recommended values in the graphics configuration, that is, most of the settings say "application-controlled". I´m not really sure how much that affects the VR functionality, but it might have an impact on the way DCS handles ASW & ATW.

Gizzy, I gave the key / button assignment another try in order to see if an axis can be assigned to throttle movement. As I said before, I didn´t find a way to do it, which is sad, since I own the Puma Flighttrainer and could use a "real" throttle handle. Talking about the engine controls, I think it´s a bug as far as description and function (key assignments) of "Throttle" and "ECL" are concerned. "PageUp/PageDown" keys are by default key layout assigned to "Correction Lever Up / Down" whereas "Throttle Up / Down" is assigned to "RTCR-POS1/RCTRL-END". Now, if I start-up DCS with a running MI-8 and I press "PageDown", the throttle handle moves to the right, decelerating the engines. That´s strange, because the ECLs should go down when pressing "PageDown", right ? Using RCTRL-POS1/RCTRL-END" sets the ECLs in one of three positions (zero/half/full). There´s no "in-between" for those levers unless you put cursor focus on them and use your mouse wheel function, which is not really useful when flying in VR. Instead, I used "Joytokey" to simulate mouse movement. To make the trick work, map the default key assignment of "Page Up/Down" to, say, Left/Right Coolie Hat directions. Just assign "PageUp / Down" keys to the appropriate hat direction and there you go ! Same as using the mouse but you can keep your hands on the stick ! I know, it´s a lot of fiddling around with key and stick assignments, but it brings the feeling of immersion a little closer to "perfection", right ?! I am really curious to know how you managed to assign axis movement to engine controls.

The problem seems to be that no axis can be mapped for manipulating the throttle. Only way to get it working is to use a tool like 'Joytokey' in order to map the 'PageUp'/'PageDown' key with repetitive action to one of the joystick buttons.

Thanx for your reply.I appreciate your response to my question. Neither I, nor my Co-Pilot or Gunners are able to fire guns or missiles. I didn't take into account, that making changes in the mission configuration would be part of pre-flight preparation. Let me know, if I got your words right or wrong.

Same here I experienced the same: No weapons seem to be deployed when starting up on mission 4. What exactly hast to be done to make them work?

Hey there BelsimTek-Team, when are you guys going to make the WSPS finally work ? The issue has been on the'wishlist' for the Huey from the beginning on. The Huey is equipped with the cutters, but when I purposely fly into a powerline, it makes a flash and the heli goes down. Even the wire is still hanging as if nothing has happened. Please fix that issue soon. Thanx!

I am using a combination of Oculus CV1, a 24" monitor (1920x1080) and an ASUS GTX 1070 8Gb. I found out that you can boost performance for the Rift best by reducing the resolution for the monitor as secondary display. Setting the monitor´s display resolution to a minimal 1280x800 (with the appropriate display ratio of 16:10) leaves most performance to the Rift. So, as long as ED doesn´t explicitely say that DCS will take advantage of Dual-GPU configurations, it´s the only way to minimize load on the graphics card. If someone knows a way (if there is one at all) how to make DCS turn off the secondary display, please let me know.

One more opinion to hardware-related stalls, which is often disregarded: Besides updating your graphics card driver, make sure your BIOS is up-to-date too, so that your Mainboard chipset-drivers (also to be up-to-date !) handling the communications between the various processing units on the board are performing as best as they can. Second thing to check for (as mentioned in one of the posts above):Make sure that no power-saving functions on the mainboard prevent maximum performance. And last, but not least, check the graphics-card-specific settings for AA and AF. I read in some post, that setting the AA to only MSAA shall have a great boost on the performance without a noticable backdraw on graphics quality.

This one seems to be a collision detection problem between aircraft and hangar rooftops: When trying to settle down on the grass-covered aircraft hangars next to Vaziani Airport, the aircarft drops right through the rooftops. The walls and hangar doors don`t allow for passing through,though. Developers, please cross-check for similar behaviour on other airports, too.

Remember to turn the knobs beneath the meter for setting lower and upper altitude limits. If you don't the digits won't lit.

You certainly mean 'Radar Altimeter', which is switched-on on the overhead panel, right ?

> Thanks !

The problem with the rain and snow in the cabin and the not working gas throttle issue seem still not fixed as of may 5th in the latest 1.5.x release.

Noticed this bug when I used my newly bought Puma flight trainer in the new Argo campaign. Bug seems to only appear when using certain analoque hardware input devices. Haven't noticed it before while using the Hotas X Stick. That might be because now I'm not using an additional keyboard-to-stick overlay program such as Joytokey anymore.

Gas throttle not reacting Yes, I checked it. It's not the campaign's fault. It turns out to be the case in every mission when starting up the Huey with a gas throttle. Will report this bug and others (raining/snowing into the cabin for example) that still exist in the newest update in the Huey section.