Gizzy

The keypad is a logitec g13.... now redundant as I only use VR (Rift). I have the original plastic extension in a spares box if you want it... PM an address and I'll post it across... I'm in NI and it's light so N/C if you want it.. :)

Food for thought... IMAGE 1: I used a simple plastic pipe extension cable clipped to the TMWH throttle... worked a treat with perfect precision control for several years.... IMAGE 2: A friend then made this up for me, I asked for 'loads' of switches and Hats... It is on a bracket that slides between the 2 throttles and held in place by the TMWH locking slide bolt. An elastic cord at the rear balances the weight without using the TMWH friction rotary..... hands off at any position with no slip and instant movement up or down smooth as silk.......

Hate to get involved in this but I when I originally purchased the NS340 on first release for the Mi8 there was an option displayed for using it with the L39. This disappeared soon after on an update. There was much speculation as to what modules this unit will be used with and many many wishlists for various models appeared as is normal for these forums. I never had the impression that it was for all aircraft and once the L39 option disappeared I'm positive it was affirmed by someone from ED that the purchase related to the Mi8 only. I never use 2D now and for the record I and all my 'squad' use the the Garmin extensively in MP scenarios - I have no quibble about the price.... in fact ED hurry up and put the BUY IT link for the L39 3D upgrade on the website please.... for 6 dollars it's a steal...

Just a note... ED mention that the NS 430 is fully wired into the electrical and radio systems of the Mi-8MTV2 and the L39... so that is a good positive.. looking forward to exploring this avenue... On the 2D side there is no mention of full electrical integration...

Don't tell him that please....! (even if it is true :)) His head is big enough as it is ....

Here you go :) https://forums.eagle.ru/showthread.php?t=187726

This is unusual with Cypher. I have had several dealing with Virpli over the last year and no issues whatsoever.... I would rate Virpil service very good albeit a bit slow in response times. Your last about shorting 2 pins, I presume you have 'bricked' the device somehow ... there are 2 pins that you short out on boot that resets the the device to its initial state then you simply recalibrate as normal... a simple process. Cypher sent me a simple document of the process a long time ago but unfortunately I have binned it. I have had my device apart several times and see no issues whatsoever with the build or wiring, it is a solid unit.

It comes down to your settings and that depends on your PC and GPU. Running a OC 980ti and a OC i76700 I use a PD of 1.6, most setting max'ed, no MSAA and cockpit display set at 1024 (not every frame) and as a guide I have no difficulty reading the main instruments / MFDs / HUDs in ALL aircraft. I fly mainly all rotary wings and the 8AVNA & LC39L MP using airframe navigation (as in game all F10 map options are turned off) in VR with no issues..... so I use all the instruments all of the time.... Apart from the normal set-up alignment and adjustment of the rift / face angle to ensure 'sweet spot' sharpness, these options may help... 1. Map a HOTAS momentary button to your VR zoom. 2. Using your camera view controls, set 'your seat' at the correct distance from the cockpit panel. Most A/C defaults the seat is too far back, away from the instruments... with VR bring 'your self' forward. Look at the top of the in game joystick and naturally rest your hand on the top... if you 'feel' the real joystick top you are positioned correctly. 3. With some airframes the MFD displays are enhanced and larger in HUD view 'ALT F1' - A10C and Ka50 for example. This makes it easier to identify targets. Map 'ALT + F1' to a momentary button, it acts as a view on/off toggle 4. Use 'a couple of 'snapviews'. In VR you can assign different zoom and positioning of the 'pilot' view to snapviews. It is NOT like 2D, the screen is NOT frozen or static, you still have full head movement it is just the camera or pilot head position that is changed. Map these to a latching toggle switch.... just change your positioning for task.... i.e. for the Mi8 I have a view that is leaning outside of the pilots window and another for the side gunner to lean out of the side door.... helps in very tight landing spaces etc.... For the Ka50 I use one to get closer to the abris for configuration and another which sets me little closer to the Garmin in the Mi8, again for configuring... in use normal view as in 2 above, the positioning is just fine...

Again, sorry mate, that video is not a truly representative of what you see, in fact it give a completely false sense of what is achievable. You cannot take a video outside one of the lens and attempt to portray that is what you see in game. What you actually see and the definition or clarity is dependent on your camera view and your DCS settings which are dependent on your equipment. OC980ti and an OC i76700 in a correctly set up in cockpit view gives to me perfectively readable gauges and HUD. Sure the small text on small gauges requires a lean in to read but normal position allows reading of all graduations in most aircraft.

Sorry mate, totally disagree with you on this one.

Cib, all mappings are fine my end so it may be local. Rename this folder as a backup and remap your bindings.... should fix it :) ...Saved Games\DCS.openbeta\Config\input\UH-1H\

If the top plate axis adjusting screws are loosened beyond a certain point slack can cause noise or a clunk. Tighten both axis some and see if this helps.

I'm having no issues at all, but like I said my process worked fine for me. After axis PCB swap and software calibration the centre was way off, windows calibration solved it, but hey, whatever works for you.

T-50 has 8 POV inputs and 19 Buttons, all DX direct inputs seen by the Windows / DCS in the same manner as the TMWH. As I understand it, Virpil software calibration is stored within the device. You may also need to calibrate the device in Windows AFTER calibrating in the software - this depends on settings current within Windows OS for that device. After calibrating and saving the profile within the software, I had to additionally calibrate in Windows before the pinky axis worked correctly and, on another occasion, after replacing an axis PCB both calibrations were needed. Use the Virpil software as described in their video. Flashing wrong firmware may brick the device which then requires a dismantle and a pin short to reset. I use multiple input devices and T-50 is the best yet.... and support is solid, sure slow at times but good. Thrustmaster support over the years I have found to be very good and just as slow ha ha ha.... I think we just exoect more... :)

Docs, Lessons, intuitive FM, great cockpit, graphics and systems and no nasty surprises... Beyond expectations ED for an Early Access.... thank you and well done. An Early Access DONE RIGHT! Nice....:thumbup:

That made me go back and check the MODS.... not all had been removed by GME... Ranger Pack was still in situ... hence 'Insurgent MANPAD' causes a crash and Igla MANPAD does not... Should have physically checked the actual SG MODS folder before testing & posting.... :doh: Sorry for making you test it, it wasn't necessary... :poster_oops:

Confirmed.... DCS v2.5.2.17559 No MODs New Miz file 'Insurgent MANPAD' placeable and viewable in the object view tab New hot start helo placed. Run Miz, DCS Crash. Repeatable. Igla MANPADS work fine....

It comes down to your settings and that depends on your PC and GPU. Running a OC 980ti and a OC i76700 I use a PD of 1.6, most setting max'ed, no MSAA and cockpit display set at 1024 (not every frame) and as a guide I have no difficulty reading the main instruments / MFDs in all aircraft. I fly mainly all rotary wings and the 8AVNA & LC39L MP using airframe navigation (as in game all F10 map options are turned off) in VR with no issues..... so I use all the instruments all of the time.... Apart from the normal set-up alignment and adjustment of the rift / face angle to ensure 'sweet spot' sharpness, these options may help... 1. Map a HOTAS momentary button to your VR zoom. 2. Using your camera view controls, set 'your seat' at the correct distance from the cockpit panel. Most A/C defaults the seat is too far back, away from the instruments... with VR bring 'your self' forward. Look at the top of the in game joystick and naturally rest your hand on the top... if you 'feel' the real joystick top you are positioned correctly. 3. With some airframes the MFD displays are enhanced and larger in HUD view 'ALT F1' - A10C and Ka50 for example. This makes it easier to identify targets. Map 'ALT + F1' to a momentary button, it acts as a view on/off toggle 4. Use 'a couple of 'snapviews'. In VR you can assign different zoom and positioning of the 'pilot' view to snapviews. It is NOT like 2D, the screen is NOT frozen or static, you still have full head movement it is just the camera or pilot head position that is changed. Map these to a latching toggle switch.... just change your positioning for task.... i.e. for the Mi8 I have a view that is leaning outside of the pilots window and another for the side gunner to lean out of the side door.... helps in very tight landing spaces etc.... For the Ka50 I use one to get closer to the abris for configuration and another which sets me little closer to the Garmin in the Mi8, again for configuring... in use normal view as in 2 above, the positioning is just fine... 5. If you use spectacles for driving or distance work you need them in the rift. Keep them clean, if they have coating they attract muck like iron filings to a magnet. Clean them daily. For me, spectacles are uncomfortable in the rift but these are great......

[deleted] Not relevant

Absolutely fantastic Avantar.... Over the years I have used most things extensively from 'target script' joy2key, VoiceAttack code direct on the controllers etc and this is great.... especially if you manage to incorporate DX codes and sequences.... brilliant - thank you Sir.. :)

Use your ADF volume control rotary and you are good. Ciribob mapped it to this rotary on request as a fix. It works well..... Hope this helps...

Have a look at 229th AHB http://1stcavdiv.conceptbb.com/ Everything you ask and more is in place, you just need enthusiasm to acces it.

I believe it is soft centre cam and medium spring... give it a good rattle before changing.... for me after trying the others I came back to default even with 2 extensions :) Enjoy..

Tacca Mod is good and working just fine in VR. Yes, left and right eyes do not synch to form 1 circle as in a perfectly formed binocular view but I think you will find this is down to DCS VR implementation. You can change the width, height and position to some degree by editing MOD_nvg.hlsl found in the MOD in Bazar\shaders\common\... and also whether you want a ring / thickness etc.. Personally I use no ring and these settings static const float2 EYE_CENTER = float2(0.5f, 0.75) & static const float2 EYE_SIZE = float2(0.8f, 0.7f); Works well for me for long periods.... no headaches. Suggest move your head a lot and always look through the center of the NVG view. (as in RL) Do not 'look' at the edges of the NVG area use the center portion. Should help some...

Hey BG, VoiceAttack will work fine, use one for a toggle or use 2 separate commands for on / off... just a thought :)