VirusAM

Exactly, If you don't want to take your headset off its ok....You have just a 2d screen inside your headset. Then when you do enter the mission, everything is in normal VR. But, having the possibility to use mission planner, mission editor, reading the briefing and so on, in 2d would be optimal for many of us

Hi, has this been fixed in the latest build?I guess it's not as it is not in the changelog...but I didn't progress in the campaign just for this (I don't want to move further on without completing this mission)

Balcani impossibile per ora (secondo me), anche perchè le mappe di DCS sono troppo piccole, ci vorrebbe almeno la dimensione di quella di Falcon per poter ricreare qualcosa di interessante Non credo l'Iraq, non avrebbe alcun senso se non come espansione del Persico (la Siria è di 3d-party)

Non è una novità....si sapeva dal video dell'anno scorso...confermato varie volte da Nineline sui vari reddit ed altri social. La novità sarà l'altra mappa che si vedrà nel trailer 2024 e beyond....

If you use it with link, just cable, enable link and enjoy....the account on the PC app should be the one leading

What does that mean? It means that Quad-Views-Foveated does not fill a gap in the application (DCS), but instead it fills a gap in the platform (Oculus, Pimax, etc...). Yes, Eagle Dynamics could pull in the entire quad views on top of stereo emulation framework that I created, but it's way outside of the scope of what any normal game engine should do and I would not expect (or even encourage) any game developer to do that. In addition, there are many challenges linked to eye tracking, because just like Meta, Valve, etc did not implement quad views support in their OpenXR runtimes, they also did not implement eye tracking support in them. Only Varjo implements the proper OpenXR interface for eye tracking (XR_EXT_eye_gaze_interaction). Meta chose to only expose social eye tracking data through a proprietary extension in Developer Mode only and recently Steam Link also only forwards eye tracking via a non-standard OSC interface. This is what a 3rd project of mine, OpenXR-Eye-Trackers, aimed at fixing. This is a complete nightmare for any game developer to have to deal with this mess and they really don't have to put up with it. It's not Eagle Dyamics you need to ask the feature to: it's Meta, Valve, Pimax, etc. instead. They are the ones who need to build support for XR_VARJO_quad_views and XR_VARJO_foveated_rendering into their platforms. On this front, there are 2 noteworthy developments: a) Somnium has announced that their OpenXR runtime will have support for XR_VARJO_quad_views and XR_VARJO_foveated_rendering, which will put them at the same level of support as Varjo I believe. However, due to issues 1) and 2), users will still need the extra Varjo-Foveated mod in order to use dynamic foveated rendering in DCS. b) Khronos (the organization behind OpenXR) is currently pushing quad views to become a core feature in OpenXR 1.1. This is a good news, because it means the name quad views will no longer be associated with Varjo only. However, in itself, it will not directly help the end-users: quad views remains an optional feature that is implemented at the discretion of the platform vendor. So Meta, Valve, etc will still be free to ignore that quad views is a thing and to not implement support for it in their platform. Summary - Eagle Dynamics, please resolve issue 1) and 2) described above in order to offer an implementation of dynamic foveated rendering that can work out-of-the-box on platforms like Varjo and Somnium. Resolving these two issues is a very small matter than could be achieved with little effort. - Meta, Valve and other major platform vendors, please provide support for quad views configuration type out-of-the-box in your PC runtimes. Only by having major vendors with mass volume of users supporting the technology out-of-the-box we will encourage developers like Eagle Dynamics and others to provide support for this great technology that really benefits the end users. Until all vendors align with providing quad views support in their OpenXR runtimes, I am afraid my Quad-Views-Foveated mod is going to remain the only way to do dynamic foveated rendering in DCS for Quest Pro, Reverb G2 Omnicept and Pimax Crystal users, and this is not a problem Eagle Dynamics can fix. Always good info from Mbucchia, I would love if vendors would agree on a common sets of features and APIs

What you are asking is the next level.... What op asking are the basics... Both things have been requested multiple times, let's see what happens. Personally I would like to have all the menu and preparation 2d only, similar to the other f16 simulator, and the mission in VR.

bump, added winwing mfssb and missing pictures. Reduced prices

Oh yes...It could very well be...will check later

thanks. I will try that, and I will also watch your video. Yes the mod should be at its latest version.il I'll update you

I tried stemvr link...but it seems no ASW/Motion smoothing...am I doing something wrong? Also is fovetead encoding active by default?Cannot find any relevant option for it nor in steamvr settings, nor in the headset's app.

Hi, I tried to use the mod to transfer some waypoints into the F-15E. Did something changed since your video? With target points I get just flashing numbers in the UFC, and yes before clicking "load waypoints" I pressed menu to enter menu1 in the UFC.

I am sorry about your experience, I received the NLR Flight Seat last week (bought from Amazon) and no issue at all... I saw other users in this post having a similar experience, so maybe their logistics department needs to step up

Hi, I just bought the military seat, and I am still in the first phases of mounting it (probably will finish during this weekend. Could you please tell me some more details of the holes you had to do in the pedal's plate? I also have an MFG (but with combat pedals) so I would immediately do the holes without first mounting everything, so It would be handy if you could give me some detailed pictures. Thanks

Hi, thanks for this initiative, however I am also not receiving the verification code (spam checked as well)

Do you use Fovetead Rendering with the quad-views fovetead app?if so, disable bloom in dcs vr options.

Yeah same

I sent him also an email, to an address to which I did contact him in the past...so far, no reply...if you have another email address would you please give it to me? Unfortunately I didn't see this post before and I hope he has still some pieces left

Pm sent Having used both FSSB and Winwing MFSSB, I can say that personally I tune down forces a lot. So if there is no way to keep precision it would be better to use a lower force. Winwing also have a 6kg limit on their unit and I use it at 55% Y+, 45% Y-, 33% Xleft, 28% Xright.

That tailpipe can work only with Thrustmaster grips. Winwing ones are totally different and would need a different one designed for the scope.

Hi @curtomic7 I can...no problem...but I don't know if it would be viable for you as I think shipping will be expensive. Send me a PM with your postal code so I can simulate a shipping and get you a quote.

Not possible as the winwing grip structure is quite different.

I had to try....:) It doesn't work for me..but not too interested neither as i don't have special hardware for bms But it would be good if the two softwares would be unified, with yours as a paid addon (or for the aviators as a free add-on for yours)

I would like to get a 7900xtx also, coming from a 3090 and don't want to dump cash on the 4090. But I know that and cards have issues with reprojection, so ASW won't work. Last year I tried a 6900xt and performance was very good, but asw didn't kick in, it worked only with very old drivers. It seems that the few people which use the 7900xtx doesn't use reprojection at all... But without reprojection my VR experience would be really unpleasant

Hi @slughead...I have to check, as I don't have anything from thrustmaster at the moment, and I hope I have the files somewhere. About the DCS export, I am pretty sure I still have it. It basically wrote on a text file some values (module name, gear and lights state etc). Then the target script opened that file (remember target uses C ), and read it and set lights and commands accordingly. EDIT: I found some backup on my onedrive folder: Target script (the main file to load should be DCS_global.tmc don't quite remember) and export lua to put in dcs saved games, script folder. About the online, I never solved it...I read the documentation about the online export, and the lua functions I used should be working also in MP, but it didn't. Maybe it is something time dependant (in MP you need first to select the slot)...but I abandoned the project when I sold my thrustmaster gear. DCS_Global.7z Scripts.7z