firefox121

In my rig, I have a folder that has inside the fingersapp.exe and the dll, don't remember if I put the dll inside or it goes with the app, so make a folder and put inside the two files (fingerapp.exe and the .dll and try) - Don't know If you must use a bluetooth mouse, I have one installed with his own receiver (not bluetooth) and works fine, but my system has a bluetooth usb dongle, so I don´t know if fingers app needs a bluetooth device active to work fine or not.... sorry. Think you must use the old method know for all of us : try and error (sorry for the joke) this is how mi folder is :

- Download the last fingers app at github, and run it in administrator mode, think it searchs for bluetooth devices , also if you don't use them, of course you must run before launching fingers the leapmotion app. - When you runs the app you will see the mouse cursor moving where your hands go, starting more or less where your hand is pointing at monitor. If you have a mouse ring you can move the cursor and click it - If fingers is not working, try to put inside the rings folder your leapC.dll the one your device is using, usually inside your leapmotion installation folder.

The only issue you'll find mounting the f15 grips at your "old" orion 1 base is the lost of some axis and buttons (see the winwing page) and also only one of the two grips will vibrate. Plus you wil need a finger lif or a mount extension to attach them to the orion base (see the cheaper one without finger lifts) no needed it only for the inmersion.

Try to disable g-force effects and see if the problem appears again, can't remember if when blackout the external view works. Also , could be a gpu cable conection to monitors that is not well fixed and moves in some way.....

Don't know if this could help , but I think in two other reasons : - 1 :- maybe you have an axis binded to the cockpit lights? .......Dcs some times assign axes to new joys with no reasonable matches....... - 2 : - Did you use enable g-forces at dcs options? could be a black out? - Sorry if this are stupid solutions , but can't figure out other triggers

Think you must calibrate the new axis at simapp before starting tuning dead zones. If you haven't calibrated the new axis base,you will find some troubles.....

Easy, only use both at the same time, and buy a finger mouse ring lime me, so when you move the hand, cursor will move and youll be able to click buttons by clicking at ypur finger mouse.I use this device, only a few bucks at aliexpress. It comes with two buttons and a scroll wheel and is inalambric. has his own rf usb dongle. Search for ring mouse and will find a lot of devices. -P.S. : you dont need nor the leap motion device , nor the fingers app, just uncheck "use mouse" in VR tab and the cursor will stuck at the center, so when you move the head here goes the cursor, only clcik the right or left ring mouse button when the cross is over the cockpit button anf thas all, also you can rotate dials with the center ring mouse's wheel (just where I have my tumb over). Usually I mount the device at my left hand, on my index finger, more usable because does not interfers with the throttle controls. If you not touch any moue button the cursor disappears, in order to make it visible again just click any mouse button and thats all. NOTE . searching at aliexpress I found a bluetooth version of the finger mouse...here you have the link. https://es.aliexpress.com/item/1005005909520469.html?spm=a2g0o.productlist.main.35.7798c376yfq9Qp&algo_pvid=262eeab5-a0e8-4736-9e12-56385cedf546&aem_p4p_detail=2023082413240447328895395100008542119&algo_exp_id=262eeab5-a0e8-4736-9e12-56385cedf546-17&pdp_npi=4%40dis!EUR!20.21!9.9!!!156.30!!%40211b600816929086436172275e54ea!12000034804891829!sea!ES!4218856019!&curPageLogUid=kurrmyH2mDmN&search_p4p_id=2023082413240447328895395100008542119_18 s.

Hello, at low level flight mission in quick missions, when I reach the last waypoint and ascends a little whe "wet feet" while navigating to kobuleti and trying to land, the plane oscilates left and right and I must to compensate all the time with stick, is this normal?, is due to weather conditions? I've checked my bindings an all anre ok (no duplicate controls) . It happened to me flying MT Ob and VR..... Anyone else noticed this? Attached my track, of course is at the end of flight....when exit canno and flying over seavuelo rasante record 2.trk

Using Reverb G2, a question for you, I can see at your signature that you are using a DCS server computer.....after more than 15 years using DCS, what is the function of a dcs server computer? it improves framerates? can you point me in the right path?

Look for keybinds at controls , If I remember well there are option to move the miniature, dearch for DAP in controls, when rebind you can move up down, left right , forward and backwards

I am using DCS DTC aplication that has implemented f15 and saved two or tree configs that I use when needed. Find the app here https://github.com/the-paid-actor/dcs-dtc/releases

nullI have my settings like this in wmr portal, so never have to change mouse behaviour, also at DCS world, in vr tab check use mouse, and uncheck cursor confined to window, This should work for you.

Recently I moved on WIN 11 with my reverb g2 and must say, (could be a placebo) that win11 handles better the processor, for me has ben a good jump.....despite how windows11 manages menus and files that I dislike a lot. MT is present now at DCS release version, but (again placebo effect) I think works better Open beta than release candidate. Just my feelings.

This is a good solution, also this one(cheaper and easiest to find) Also I found at aliexpress the genius, but I think it is expensive. here can you see it https://es.aliexpress.com/item/32780224884.html?gatewayAdapt=glo2esp

AFAIK, and with your rig CPU/GPU , you will not have issues with PICO4 or OCULUS compression issues (none of them have display port), so .... go for the pico4 (better lenses) or wait to meta quest 3.... I Junmped from a firs first gen pico HMD to Rift, later Rift S, and now Reberb G2.... this one is for me the sharpest HMD, only his little sweet spot will force you to move the head more than usual, but if you can live with it is a good start point, and cheapest point ..... I am using the reverb G2 since they went to market, and never har issues with them , so far to trying to achieve best graphics with smooth movements. With my 3080ti and my i9-10850k I must use framerate reprojection, but DCS goes smooth as silk and no need to use x2 or x4 FSAA. See my post here .

Think that all of us are starting to understand the apache, and we fly the beast much much better.......many hours fighting and practising with the helo makes perfection..... For me , now is easier to fly, think because hours and hours taking off and landing.....a lot of fun indeed

Worked, Thanks for helping me.... I owe you a beer or two!!!

Yesterday I found this when trying to use oxr developer tools Nothing seems to work, unistalled and reinstalled wmr portal, open xr developer tools, I am on the latest win 11 build........can anyone help me with this issue? Can be a reg issue?

Also, and it is true, press and release the brakes and disable the parking brake, if not the chopper is "glued" to the floor and will rotate to the left when trying to liftoff.

I moved also to winwing orion hotas 1 two years ago. In my rig, the solution for ghost input was turning off the lights of the two devices.....voilá problem solved.... Just in my rig, don't know if this was a cause-effect solution, but never I have ghost inputs again. But before flying with winwing hotas, never returned to my rhino x56

The finger to button is dependant of the module you are flying. Also you must de-select the finger point laser to be able to push any button. Most of DCS proper modules works with fingers and leap motion, also f-15 and apache works fine, f-5e, f-18 and f-16 works fine too. I use a finger mouse attached to my left hand to use rotarys , because is too hard to rotate knobs because pinch is not binded (AFAIK) In others modules is time to try and error, remember to uncheck use hands in VR options to use leapmotion My advice is to bind some sort of keys to show and hide the hands, you can find them on the ui-layer control page. Feel free to pm if you need more help. Good hunt and happy fly.

Hello , If you have installed the latest drivers found the leapC.dll onto your ultraleap install dir and copy it to the main dcs install bin folder or bin-mt folder...this will solve the issue ad you can use leapmotion as always. hope this works.

For me , working solution is pressing (or assign) one of the keybindings used to move the viviane(.,) and then you can use the axis without problem. If the viviane gets stuck again, same procedure, pres for example (.) key in my bindings and the use the axis again.

You should see this(see picture), the current version is : 113 .2304. 14003.0 If you select use best framerate speed will be able to see the two options below, Disable blah blah nvidia blah RTX" and "prefer fps over latency"....this is likewise turbo mode on in OXR toolkit. So if you chek this, disable turbo mode on at OXR toolkit. If not...shutters will come again

The motion reprojection works linked to OXR toolkit if you have installed it... What Motion Reprojection does is to adjust your framerate to your latency (it should be 10 or less), If the latency goes over 10ms starts working to adjust frames to 1/2, 1/3 your mhz render...so if you are running , for example your HMD (mine is reverb G2) at 90mhz refresh rate, when mr goes on instead of seeing 90fps I am going to see 45 fps (but smooth) if the system still is not capable of reach a steady 45 fps , mr would down to 30fps... There is a lot of info in all the internet...but basically works like that....full fps, 1/2 fps or 1/3 fps.... To control Motion Reprojection from OXR developer tools: Tip : You must set at OXR toolkit the motion reprojection to default in order to use the motion reprojection from oxr tools. Then in oxr tools you have two best using options : -Disabled : no more words....will try to use the best from GPU, if your rig is not powerful enough it will travel from 90 to 45 or less causing spikes , shuttering etc -Use best framerate speed .... it will work as intended... if the gpu are not capable to reach 90fps will use 45 fps...so all will be smooth. If the gpu can't reach 45 fps will drop to 30 fps - check , the option "prefer fps over latency" works like turbo mode on at OXR toolkit, but , for me at least, better. With this options , in my rig, see specs below, I can manage solid 45fps with a great great clarity on graphics and smooth experience. Another way is turning off motion Reprojection at OXR developer tools and play with OXR toolkit options... Personally I find better to use OXR developer tools. But it is your choice. Hope this help you.