simo1000rr

i had a warthog that i used to mount on an air force one play seat , by default the play seat comes with all the holes in place to mount any thrustmaster or Saitek product , However when i bought the Gladiator Pro the holes position didnt match any of the Supplied Steel plate with the Play seat " it comes with 3 steel plate " So i drilled my own holes using a vertical drill holder from amazon . it is better when the holes comes pre configured however its very easy to drill your own holes.

https://forums.oculus.com/community/discussion/58850/rift-1-20-release-notes#latest

its a very nice idea but i would like to hint to you that you can use the mouse while in VR , although your idea is better but for right now using the mouse to click the radio menu is possible . I have a Razor Naga mouse and it has 12 side button on it , i assigned all the F1 >F10 on it that way i can click anything in the menu right away while in VR

I know what you talking about and no it doesn't affect the precise control of the speed . i fly the F15 and i have each throttle assigned to left and right engine control . when they are both locked by the pin and moved together i get the same precise engine rpm reading on both .

i use VKB mkiii no words i say will do it justice , 3 years now and its rock solid like day one , everything in is hard steel so no matter how much force u will use on it it will suck it up . the axis is deadly accurate with a very solid feeling to it and the center is accurate as well. the only thing ppl complain about is that it doesnt have a toe brake which i dont have a problem with since i have a Thrustmaster Warthoh set i use the extra axis ( the small lever on the right side i dont know what its called ) on the throttle as a brake axis. I also use a rift so no problem there

Also do you by any chance upgraded to Win 10 gaming ? this i heard has stuttering issues in DCS

set your preload radius to the maximum

i believe that will increase their production cost because they will need 2 line of production one with labels and one with out . im just assuming .

i vote without labels as well as i will be using this for every plane assignment so " No labels please "

If you are interested , i have my warthog joystick up for sale ( only the joystick ) its bought from amazon in February 2017 ( have receipt ) . i just got my Gladiator pro so im putting the warthog up for sale. ( price is very good PM if you interested )

its in stock already . https://flightsimcontrols.com/store/joysticks/vkb-gladiator-pro-joystick/

If you ordered the Gunfighter it comes with the dry clutch ability which gives you control over the movement of the stick , in another word you can dial in some friction to the metal gimbal and it will give you that effect you are asking for

Guys If you are running Runtime 1.14 now The Oculus Debug Tool moved from the SDK to the runtime. The new location is Program Files\Oculus\Support\oculus-diagnostics\OculusDebugTool.exe. you should be able to run the debug tool 1.14 from there

download one of the GPU software such as " MSI afterburner " or " EVGA percsion" i personally use EVGA since my card is EVGA . anyway . in those software there is a button called turbo boost. it will keep your card working on the highest clocks all the time. also i you know how to overclock your GPU " its very easy " go for it it will make a big difference . i have mine overclocked +100 for gpu clocks +350 for memory clocks.

i run dcs 1.5 on oculus cv1 . my supersampling is at 1.6 and i force ASW to disabled by the oculus debug tool . i only play online on the 104th and i always get smooth performance . if the mission has clouds then the performance drops but still very playable like 40 to 60 fps. bottom line is if you want good performance in VR turn all shadows off turn mirrors off keep trees and grass to minimum you should see the difference

first , you have to open the radio menu by clicking (\) in the radio menu click others. there you will find what airframe you want to go gun vs gun against . choose whatever you like , for example Su27, once you click it will re-spawn right away at your 12 oclock about 5 miles from you . be ready to lock him on radar right away or he will get on your six and shoot you down .

from what you saying i strongly doubt that you tried VR. i've been flying now the F15 in VR for 8 months . and i never had a problem identifying friend or Foe for the simple reason is that i use the radar to identify Friend or foe . even without VR and with my 4k monitor i could never identify friend or Foe visually no matter what .

Have you tried it yet ? or your statement comes form reading the forums ??

The order of which you should run it us , debug tool first then the oculus run time then what ever game you like, you should notice right away that the runtime looks more crisp

You have the wrong Debug tool version . the SDK from Oculus website should be 1.13.0 there is no 1.3.2 also if you are refering to the .exe file version it also reads 1.13.xxx. did you get the debug tool from this website https://developer.oculus.com/downloads/package/oculus-sdk-for-windows/ this should be the one you get if you are running the latest oculus home 1.13.0

Ya im running the same file version as the one you mentioned above ( 1.13.0.34162) which is the latest debug tool from Oculus website ( 1.13.0) . once you run the debug tool you have to leave it running in the background , doesn't matter minimized or maximized as long as you keep it running. Of course the debug tool override the game setting but still you have to keep the in-game setting at 1.0 since they will both try to run. i tried bumping the in-game one and it caused the performance to drop that's how i know they both try to run . Edit : Also if you go in he oculus home , under settings >beta . make sure that the beta channel thing is on off . meaning that you are not participating in any beta test. for the ASW i set it to disabled, i dont like the way it acts plus if your graphics card is VR capable this ASW should't be kicking off.

will this work in multiplayer ? or the IC will deny it ?

Ok i tried this Debug tool last night . i can confirm its no a placebo thing , there is definitely a noticeable sharpness in the cockpit text . on top of that i can read the some of the stuff better like the Radar screen in the F15. i dont know how is it possible but it does. also i noticed that the game performance is better. another thing, there is an option in the debug tool regarding GPU adaptive performance. what you guys set it to? i set mine to disable.

How do i know if im Running Oculus Home Beta from Not ? i want to try this out but the OP said that it wont work with the Beta driver .

Thank you so much mustang , that HSI bug was holding me back from this mod .