Gizzy

You'll lucky, I gave up a long time ago... you must have plenty of spare time... :) Different terminology, different languages and interpretation can confuse things as does unqualified adamant posts. For what it is worth 'I think' Doc Willy is alluding that if AP and Giro are off and you use the 'trim nose up / down' - 'left / right wing down / up' functions, the control indicator overlay shows the stick moving and holding to the amount allowed by that particular trim function - but of course there is no effect on the airframe, because trim is all off. The trim function 'T' on the other hand does not 'hold' the cyclic in any position within the control indicator overlay as expected. If this is what the Doc is saying, as he should, I would put it at the bottom of the list :) As far as FM issues are concerned I only try and understand points raised by those with good RL experience... more so if it relates to the intended design & role of the Gaz - of which there are a few about :)

I have been puzzling over how to get F10 map co-ordinates into cockpit systems such as the PVI-800 and Mi-8 GARMIN whilst flying in VR using the rift, and as easily as possible... I have difficulty in flying, remembering the Lat / Long from the F10 map and then entering it... Chic (he has a PhD in VA) very kindly investigated for me and came up with a good system involving VoiceAttack dictation mode except I found that for VA to work I have to have the weighting high and often the dictation interprets wrong numbers into gobby-gook... and played them all back simultaneously without any input pauses etc... On digging I came across SOX http://sox.sourceforge.net/ - a respected and well known powerful 'donate ware' command line driven sound utility. A bit of working out the command line references and bolting it into VA gives a good sound recorder that records your mic for a specified duration and plays back whenever you need it.... It works well in the rift... For me... I downloaded and installed the latest version of SOX (14-4-2) - it is not big... I created a folder in the root of 'C' and called it 'c:/rift-sox/' Created a VA command called '10 second record' and in it ran SOX with the correct command line parameters as a VA 'hidden' style... Created a VA command called 'playback' and in it ran SOX with the correct command line parameters as a VA 'hidden' style... SO, with VA listening, '10 second record' records your default mic input for 10 seconds into a wav file in the rift-sox directory. If it is already present, the old file is simply re-written. Playback plays it back into your default speakers.... as many times as you want... simples... You can easily change the recording time... attached is a 3 command VA profile, 10 second record, 20 second record and playback. The command lines for 10 sec reference are... "C:\Program Files (x86)\sox-14-4-2\sox.exe" -t waveaudio -d "c:/rift-sox/test.wav" trim 0 10 "C:\Program Files (x86)\sox-14-4-2\sox.exe" "c:/rift-sox/test.wav" -t waveaudio You can see how it is entered in the VA profile. The first line records and the second plays. The last number group of the first command line controls the recording length... here it is 10 seconds... Works well for me, YMMV.... of course you you dont have to be using VR to use it :) VA Profile

I believe there would only be a need if PC specification is low. Running PD of 2 in 1.5 and 1.5 in 2 and all dashboard dials, markings and controls are perfectly readable... and I wear glasses and the eye's are shot! There is a proviso to that.... make sure your seat (camera view) is correctly positioned fore / aft. I use a centre cyclic mainly flying helo's and adjust so that the VR shown cyclic is 'where my hand is' on the stick. Default view is normally further back so bring it forward. Any of the jets / helos dials and associated markings such as compass divisions are all good for me anyway... For MFD's such as in the A10c or the KA-50 Abris set a snap view.... much better than zoom. Snapviews will hold the camera view adjustments for now anyway.... but not the fixed view as in 2D. i.e. for the Abris adjust your seat to give you the best nearest view - furthest down and as far forward as it will go for example and save that view to a snapview. Bind the LWIN + Snapview number to a switch or button. Allow a good view to read rolling maps, input WP's, define routes etc.... release switch and you're back to flying position. Works for me...

@OP and anyone else deliberating Rift / Vive and waiting for the PIMAX, have a think about your current hardware and the cost of any upgrades (minimum 1080ti or 2 in SLI or even perhaps the unreleased Nvidea VOLT) that might be needed let alone DCS compatibility... Here is a snap of PIMAX's kickstarter page... note the hardware 'possibly' required.

Cockpit resolution and VR experience DCS setting & hardware dependant. For me, in the latest 1.5xx with a pixel density of 2 all cockpits are clear and readable and play smooth with FPS generally 90+ or 45+ in helos low in urban. Alpha is less. (980ti OC & 32RAM) Mapping is not an issue. With a centre mounted cyclic a ball mouse on the knee is perfect. Pimax may or may not be good or better for playability and value for buck as far as DCS is concerned but virtually guaranteed results will be hardware dependent.

Chic's 100%.. To clarify... ENGINE CONDITION LEVERS (ECL). The ECLs vary the N1 control lever (throttle) settings from minimum to maximum power separately for each engine. The normal position of the ECLs is in the centre detents. The engines can be brought to take-off power by moving the engine condition levers to the maximum settings Both ECL's can be mapped to 2 separate axis functions and both can be controlled throughout their range. There is a noticeable centre detent - the normal position. In ENGLISH DCS EGL'S are labelled as THROTTLE LEFT and THROTTLE RIGHT. TWIST GRIP THROTTLE on the COLLECTIVE CONTROL can be mapped to 1 AXIS and can be controlled throughout its range. In ENGLISH DCS this throttle control is labelled CORRECTOR. Yeah I know confusing, not a bug, just the labelling perhaps got 'mixed' in the translation... :) Please see this screenshot of my Mi-8 CONTROLS AXIS SCREEN... Hope this helps...

https://www.howtogeek.com/howto/windows/bring-misplaced-off-screen-windows-back-to-your-desktop-keyboard-trick/

Chic, if you assign these 4 inputs in DCS or VA are the names the same? For what it is worth my end, SR Client recognise TM MFD's, the TMWH and 2 button boxes - one a leo bodnar based and the other a DSD..

My understanding... Initially practise AR's from trimmed stable flight at around 150 KPH and a decent high altitude.. Either reduce throttle to ground idle or cut the fuel :) - your choice as long as you are not paying for the aircrafts... Using cylic and pedals keep the aircraft in trim... The main rotor rpm should not be allowed to fall below 80% at any time during the descent, nor rise above 100%. Optimally, the main rotor RPM should be kept between 93 and 95%, as this gives some cushion to prevent over speeding the rotor, while also providing a lot of potential energy in the rotor system when it comes time to land. Best speed for lowest sink rate is around 110-115kph, depending on the weight of the aircraft Best speed for best glide angle is around 180-190kph, depending on the weight of the aircraft The flight manual talks of 100-130kph as a standard number to use in auto-rotation. For a rolling landing, at 30-40m AGL, decelerate the aircraft by adding about 15 to 20 degrees nose up pitch to arrive at around 9m to 12m AGL and 50 kph. Put the aircraft into a landing attitude, 5 to 10 degrees nose high prior to touchdown. More details in Mi-17 ATM Hope this helps..

No idea about inferno... at all.. The FM radio has 8 channels. Default freq are... 1: 30 2: 31 3: 32 4: 33 5: 34 6: 40 0: 41 RG: 42 and the channels are selected by the left hand rotary as I'm sure you've found out. No other functionality of this radio is modelled. I believe security issues preclude this. Other frequencies for any /all of the channels can be set in the ME - so if none of those default channels match your 'CH23' give the ME designer / Server admin a shout and get a channel changed. Hope this helps.. :)

Not that I am aware. With me full zoom averages under a second so possibly hardware dependent. Snapviews are instantaneous although sometimes unreliable so functionality may be a legacy.

You can use the Camera controls, change forward as much as possible / wanted and save it as a snapview in the normal manner. If you the map a switch or button to the LWIN + NUMPAD ? you can snap in / out of whatever snapviews you set up. Sort of halfway house from the full zoom. For those who use in-cockpit displays or need extra clarity on the gauges this can be handy, especially if you combine the forward position with a lower position... but the LWIN + NUMPAD? needs to be held for constant view.... so a latched toggle switch for long periods (i.e. boat switch on TMWH) or a momentary button for a quick peek... Works for me, YMMV :)

With the Huey, Force centering devices are incorporated in the cyclic controls and directional pedal controls. These devices are installed between the cyclic stick and the hydraulic servo cylinders, and between the anti-torque pedals and the hydraulic servo cylinder. The devices furnish a force gradient or "feel" to the cyclic control stick and anti-torque pedals. A FORCE TRIM ON/OFF switch on the center pedestal turns the system on or off. When ON these forces can be reduced to zero by pressing and holding the force trim push-button switch. Some pilots used Force Trim others did not... DCS mimics this 'trim' function by allowing you to center the stick (no spring forces) whilst maintaining a 'trimmed position'. If your Pro Flight Trainer Puma has no spring acting upon it and is comfortable, switch force trim off, you do not need it!

If you really must, if you have just one free axis you can map one ECL to it and the other as well using a modifier... Not the best arrangement but it works... as does the slider axis in the TMWH. Not quite so Sir, :) you can map both ECL's (called throttles in the axis controls)(RALT+RSHIFT etc....) and the corrector (PAGEUP DWN etc...) to an axis. But as Chic says you really use them... hopefully :)

Yup breaks are important especially until you are well used to it. Different cockpits effect me different, a bright HUD can make it awkward and force double vision, I always adjust mine down.... I always adjust the seat down too if the sight hardware is in your face that helps a lot too... I'm least comfortable 'eye' wise in the Prop cockpits...

I would not advise anyone anything in VR we are all so different .... your opinion is very valid though. I speak from an experience with the rift, similar to yours. Yup, I experienced it and sent my Rift back to Amazon when they first came out. My opinion THEN would be the same as yours NOW. But to put it in perspective, I was using 4 monitors with the main being UHD and 50" and the others all 1920x1080 running HELIOS. I also wear glasses. Later after VR lens brought these out, https://vr-lens-lab.com/product/vr-frames-virtual-reality-glasses/ I purchaseD them and tried again. There was some double vision for the first week or so until the eyes became used to it. What helped is that I would focus at something near in the cockpit and then focus outside at 'infinity' and back close again... I can happily read all gauges and inscriptions without using the zoom on any of the 4 rotary airframes. Very occasionally I sometimes get double vision especially when tired but a couple of focusing exercises normally sorts that. Target spotting with the in cockpit monitor in the KA50 & Gazelle is not the same as having it exported solely to a 32" HD monitor though :) For me, VR is so much more a enjoyable experience than 2D... After 2 months the 50" UHD has been given to the wife for the spare room, 2 monitors put by along with track IR - and the last monitor I only use for DCS ME and the NET. Mostly I fly rotary wings in MP environment. Everyone is different.

Works fine in VR. I personally have camera 6 way positioning mapped to a HAT and in the Co-Pilots seat just bring the seat (camera) in a tadge and down a bit and the display is perfectly readable and usable whilst flying. Just switch seats when you want a wider FOV.. I only use VR zoom to set WP's via the cursor and Map.

Unfortuantly it is a DCS issue / bug in the current build. This post highlights it... https://forums.eagle.ru/showpost.php?p=3203432&postcount=710

Magic...

Realising that it's being looked at but Just for info, setting rotaries pulse rate as low as 8ms, it's still way too sensitive and inoperable (on the rotary switch... screen mouse scroll is fine) ... none the less a great module bolt on...

Thanks very much for the update Pat / PolyChop... Great to know we're moving forward ... Magic!

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\NS430\Doc

This worked for me... Purchased from within 1.5xx BETA Module manager... 1.5xx BETA downloaded the UN430 module in the normal manner.. 1.5xx BETA Activation code requested as normal.. Check Options / Special section for UN430 - ensure Mi-8 ticked. There is no option for the L39. UN430 was present in game, Mi-8 NOT L39... In 1.5xx STABLE / RELEASE Checked Options / Special section for UN430 - Mi-8 ABD L39 were ticked by default. UN430 was present in game, Mi-8 AND L39C YMMV Hope it helps...

Here you go....

Although in the back, you have an option to call it up from the front seat with LALT + B but this probably will not please everyone... in VR as yet it does not display correctly. Here's a screenshot... I'm sure the lua's can be manipulated if you want to move it around and probably with a bit of digging you could 'probably' export it to another monitor if so inclined... EDIT: To be specific, this is in the current release version of 1.5xxx, you have an option in the SPECIAL section to apply the GPS module to the Mi-8 & L39....... In the latest BETA the L39 option is not present and the GPS is not available in the L30... BUT I would not read too much into this... :)