William

I've use the VR Shader Mod v2.7 but with the NVG the monocular is on both eyes.

I’m agree if it’s possible it would be a good things, more realistic to

I’m agree with you, plus the use of the VR Shader last update 2.7 (use OVGME for installation, don’t forget to make a recovery folder) ! It improve the experience by adjust shaders and others things (find it on the forum)

The Oculus Link can supply charge to the Quest 2. I think the trouble come from the v.28 of the Oculus Software in conjonction of the 2.7 beta whom have new features for VR like mask for exemple ... the next updates may offer more stability ?!

Hi ! I also have problems which seem to come from the new 2.7 update, it seems that when my Quest 2 is hot it goes into "degraded" mode by swapping the signal to a low resolution version ... Which distorts the view and make the game unplayable. But as soon as I interrupt the Oculus Link connection, and return to the Quest home, the resolution returns to normal. But if I reconnect again same problem. I have to restart the headset. However, I noticed that when this occurs the helmet is hot, not necessarily more than with version 2.5 ... I wrote a request to Oculus support in this direction, I hope that they will be able to bring me some answers on this phenomenon. What do you think ? Side settings I follow more or less the recommendations of the forum see joint piece OculusSetup.log

I just bought myself the Channel map and ... Can't create a quick mission ?! And a priori it's been over a year since the little guys from ED take care of it. Thank you so much !

Good morning all, Being new to DCS, I too encountered some difficulties to properly configure my ThrustMaster Warthog to make the most of my Oculus Quest II and be in total immersion ! And Scoll gives us the best solution here ! Thanks to you ! However his answer is succinct and requires some explanation for the most novices among us. First of all if you are lucky enough to have a Thrustmaster controller I can only advise you to use it through their TARGET configuration software. Why ? Because it will allow you to have total control over your controllers, and therefore will offer you the possibility of using your IDLE trigger as in real life. To begin with, configure all the keys of your controllers, or at least all those you intend to use. In my case for example, for the time being, I only have to map the keys present on the HOTAS, since I use my Oculus Touch to perform all the other actions necessary to be as close as possible to the cockpit of my device, the F/A-18C. So to do this, you carry out a "simple" configuration thanks to TARGET, by creating a profile incorporating your controllers (whether or not they are connected or not, moreover, notice to future buyers pending receipt of their next joystick !). Once this task is carried out, by following the flight manual and by relying on the DCS command settings menu, you should be able to obtain a configuration close to perfection. But if, like me, the idea of doing a round trip on the IDLE detent exasperates you (you paid for it quite expensive like that, it is not to hear you say that it does not do the job !), you will have need to go a little deeper into TARGET. I reassure you now, it will not be very complicated ! The idea is as follows, integrate the lines of code into the script describing the configuration you have just performed on TARGET. To do this nothing complex, go to TARGET, edit your configuration going up to the button parameter setting phase, press the "VIEW SCRIPT" button at the bottom left of the central part entitled "2. ASSIGN PARAMETERS". At this moment the file is opened by the software associated with your operating system (in my case Wordpad, under Win10Pro). There you will find the script version of your "simple" TARGET configuration. Now you will save a copy of this file in a folder created for the occasion in order to find it when editing and using it with TARGET Script Editor. The file will be saved with the addition of a .txt extension, we will remove it afterwards. To modify the file two solutions, either with Wordpad which must still be open at this moment, or, TARGET Script Editor if you wish (remove the .txt extension to keep only the .tmc in this case to succeed in the to open). In both cases, you will need to add the following lines : MapKeyR(&Throttle, IDLERON, PULSE+R_ALT+HOME); MapKey(&Throttle, IDLERON, PULSE+R_ALT+END); MapKeyR(&Throttle, IDLELON, PULSE+R_SHIFT+HOME); MapKey(&Throttle, IDLELON, PULSE+R_SHIFT+END); If you have mapped the IDLERON and IDLELON keys (29, 30) then you will need to replace them with these. The location does not matter a priori, but if in doubt you can map them and then replace them as stated. Don't forget to save the duly modified script using the floppy disk button at the top of TARGET Script Editor. To run the script and generate the Thrustmaster Warthog Combined virtual controller (to which you will need to associate the control axes: rudder, L/R brake, pitch, roll, L/R throttle ...) you just have to compile the script to check that everything is in order and start the script (Play button) ! Check that everything is working in the window at the bottom for order tracking. And there you go ! Now, with your throttles in the OFF position, when you launch a cold start mission, when you put your turbojets in IDLE, the throttles will go from OFF to IDLE and vice versa ! Thanks Scoll for these few lines of code

Yes, but I will to invest in HOTAS in futur, thus for the moment is good for me. I know it, I don't look to much on my "back" ... For the command, the Su 25-T have a non clickable cockpit it's a shame because it forces me to use keyboard now, but with yhe help of VoiceAttack maybe I will fly more intuitively

My sentence about loosing tracking is that : the OT (Oculus Touch) have some inner IR LED on it for tracking those via the 4 camera IR on the google. Thus when I turn my head for look at my back for example, the camera loose sigh on my OT and at the moment the jystick on the game return to that initial position. It's more clear ?

I'm with you, I want an HOTAS at the end, because with some extra support it will be at the exact place like the real plane, more the sensation is real because the joystick is here. No compromise here, for the question of how to map the HOTAS for it's simple if I can buy an Thrustmaster I put the F/A-18 stick on it an fly with the F/A-18. End of story. There is here a point who is problemetic with Quest 2, when I fly with the Su 25 or the TF-51, when I engage a loop for exemple and I look where I want to go the IR google camrea (x4 on the Quest II) loos e tracking of my OT an the aircraft return to initail position thus no more follow my path. +1 point for the HOTAS w/ Quest II and OT. But now I research for fly with only my Oculus, but I know in a near futur a HOTAS will be better. I agree with you. But I haven't yet a HOTAS, but you will sponsorize me ?

Effectively I need to print that, and tick one after one things of that list But I'm not sure to understand how you can go with Quest and keyboard, by definition ypu can view it when you gave the google in you ? I think it's a good news, just for volumetrics clouds implements ! Thanks for your work Good idea, but for more efficiency, add this "detail" in the presentation tet on the purchase page, it seems logical. The PointCTRL hardware is a graet piece of 3D printing and sensor, but for me to much. More cables, more complexity that seems more troubles. And I want to extract as much as possible to my Quest II and Touch Controller before looking at this sort of stuff. You will go read the post about the TouchBinder it can make a good job, but now I think the VoiceAttack is more real feeling. Yes ! And When you crash ... you die. No, anybody here want to be so realistic ? But maybe if you take some fan of your PC ... They can do the tricks

I know, thank you BIGNEWY ! You know maybe when this patch is for ?

Other things, but surely not the subject, all the sentence for crew, wingman etc ... Where are they, in aim to setting up them in my Voice Attack setup ?

Thanks a lot for your experiences return ! I'm very new to DCS, but I want to make a good choice, because I know if I want to fly I need to read about 800 pages of manual, and I'm OK with you the F/A-18 is the greatest value for the bucks. I've a question about your choice for utilize the OT, are you make macro with TouchBinder or/and implement others with VoiceAttack ? Because search the right keyboard for something is a pain in the ass things, don't forget I'm a froggy with an AZERTY keyboard . What you can do if you're in my postion ? I finish to view that vid from Spudknocker DCS: World with VoiceAttack and VIACOM PRO 2.5! It's very cool, but I don't understand all things, it seems to don't use ViaCom ?

Thanks you StevanJ, When I received your message I'm in YT in tutorial by Grim Reaper very interesting things to do with VoiceAttack in VR I think !! The L-39 Albatros is the kind of jet I like to know because is of course a training aircraft as well IRL. The warbird era it's all my child memory with my father at La Ferté-Alais show (You know ?) but fly on a FuckerWolf is not my point of view but on the Spitfire for sure ! But it's not fully VR capable now ... I've think about F-16 more than F/A-18 but your speek make it path, but it's an flyng PC. I want a bird to learn fly for acrobatic movement and some dogfight. So after the F5-E TIger II it seems that the L-39 it's a good option ?!

Hi StevanJ, I don't know who he is, but it seems to be legitime after M. Konstantin "const" Borovik from Eagle Dynamics IT Team (cf. link below). Thus it was without doubt parts of ED. In the F5-E, it possible to manupulate cockpit toogle switch etc. but impossible to catch the joystick and throttle with the Oculus Touch. It's non playable like the TF-51 with Oculus Quest II & Touch.

Hi DutchCoolHand, Thanks for your response, it's interesting things from PointCTRL. But it's not really my question. Let me explain : I don't have a joystick, or throttle control, or rudder. In the planes supplied in the original DCS with the TF51 and the Su 25, with the intermediary of the Oculus Touch, the flight controls can be used (stick and throttle control, the rudder bar remains problematic but not impossible to control on the ground thanks to via a small executable named TouchBinder: Which allows you to map more or less complex keystrokes, preferably by performing a combination with the left trigger, the only key not integrated in the VR mod of DCS) But the problem is that it seems that this interactivity is not yet valid with all the available modules (including those of ED), a list has moreover been made by our friend StevanJ : I have already been reimbursed by ED for my purchase for the F5-E Tiger II, now impatiently awaiting the next update which should according to Mr. Andrey Filin: "Dear William, Just want to inform you that the connectors for the cockpit sticks have already been fixed in the developer build and will be added in the next DCS World update. Thanks" Let's wait and see, and for now I think one of the most practical solutions has to be the VoiceAttck and VaiCom programs !? A fairly exhaustive list of VR apps and enhancements can be found here >> VR Must Have Mod

Hi everyone, It's my first time here, yes I'm a newbie on DCS World and I have a question for you about VR I've buy the F5-E mod after somes hours to fly with my Oculus Quest 2 w/ Touch on the Su25 et TF51 ... And I like the interactivity with the cockpit (joystick and throttle) but when I deicede to invest in the Tiger II because it is an excellent choice for beginning I was disappointed because it don't support Oculus Touch yet Any chance it exist an solution for implement that on my TigerShark ? Thanks by advance, W.