trama1983

I 100% agree with your comment and based on my experience. There is still a completely false myth in the simulation community that Quest headsets have worse image quality just because they lack a DisplayPort connection (mentioning compression and lack of image clarity). They keep comparing them to headsets like the G2, claiming its sweet spot is better, and they keep implying that the Quest 3 (or Pro) are the best VR headsets for the masses, but not for demanding simmers. And that is simply NOT true. When properly configured and used with a cable (I run them at 200% super sampling with a 4090), the Quest 3 looks better in absolutely everything—there’s no better sweet spot for the g2 or or anything like that- across the entire lens, in the center, the corner or whatever you look. It looks much much sharper, better coloured and everything thant the g2. Unfortunately, I haven’t been able to compare them with the Crystal, but I have compared them with the G2 (I still have a spare set and have used them for years). But I totally trust your opinion with the crystal as well (quest lenses are just superior and probably that compensates the lack of panel resolution) This myth seriously does a lot of harm... because the Quest 3 is an incredible headset for simulation at an unbeatable price (which makes sense, as Meta is selling it at a loss to gain market share). Even Ismael Jorda ranks the Quest Pro above the Varjo Aero, and honestly, I don’t know anyone more demanding than him—just look at his cockpit and his PC setup. NOT everything is about DisplayPort.

So... We have now native openxr support in DCS (without even mentioning in the change log). But on the other side reproyection with openxr is not working anymore ... Not even with opencomposite now. I wasn't using repro with opencomposite, but for those that did use it, this release is bad news.... At least until ED release a hotfix either for fixing this for good or for disabling openxr support until this is fix... To blow hot and cold....

Just played the 2nd mission.. and I am speechless after that final surprise. An amazing work. Congratulations!

Hi @ChillNG, First of all ... I am really sorry for my previous post. I was totally wrong, and the bad performance was NOT related with the campaign, but on my side... probably the winwing script or the tactivew... Not sure which one of both was the main problem. Or if it was a combination of the two, because I have deactivated both (either way I tend to think it's probably more related with the tacview. more info at the end of the post). Thank you very much for your feedback, because that pointed me in the right direction to check things. Now that I have been able to flight your campaign a little more, and have a look at the incredible documentation attached to it, I must say that you did an ASTONISHING WORK. I haven't seen in other top campaigns this level of detail for example in ground procedures, etc.... Amazing. I will need to study the documentation to make the most of it. Congrats. ------ Let me recap what I did, just in case someone else have the same problem and it can help. What I did is: 1) WINWING: Delete winwing script from exports.lua. I have also removed their application for good. This is the second time I have problems with it.... And there won't be a third one. 2) TACVIEW. I leave the tacview script active in exports.lua (previous screenshot), but I disabled it from menu options. I'am not sure, but maybe the problem was related to having it enabled via export.lua, but not having the "tacview module enlabed" checked in menu options.. Either way it's really strange because I was able to do multiplayer missions, and other missions with no problems... who knows. What I did is: - Check the box "tacview module enabled" - Unchecked the box "enabled" below the "flight data recording" 3) I tried again with these two changes and now the performance is perfect. 45fps in the hangar with my previous high settings for VR. I don't usually get more than 45, because I am using opencomposite (openxr) without reprojection. So this figures are top for me. Best Regards Thank you once again!

Bought the campaign a couple of months ago, and tried it today for the first time. Agree with the OP. It's unplayable in VR. Tried for 15 minutes the first mission (until I took off, just to see if it was way better high in the sky...).. completely stuttering. I tried to lowering my settings with not much benefit. The problem is the scripting... Ctrl+Pause shows almost 50% lua time in 1s mission ground... Little less in the air. But still numbers that shouldn't have been accepted before releasing this campaign. It's unplayable. period. My specs 10700k, 64gb ram, 3080 (Reverb G2). I have paid for some other campaigns (pontus, raven one, serpeants head 2, rising squall, etc), and this is the first time I see something like this...

Hi all! I think we have some good news regarding this topic. Yesterday I was able with great help from @Wingthor to configure and document all the process to have VSCode fully integrated with MOOSE and the DCS ME Debugging. In this document you will see how to: 1) Have Intellisense configured VSCode for MOOSE (this is something already explained by @Costas_Ch in previous post). 2) Debugging MOOSE from VSCode 3) Integration between MOOSE Repo and our Missions. Making it possible to "debug individual .lua files of MOOSE", "check out between branches", "fetching changes from new commits in the repo" and all that really fast having the advantage of Dynamic Links Note that this last step is optional, and something not many people will find it useful. Because they will be good just by dropping the big Moose.lua file into the workspace. Either way, for those that want to have a better integration between MOOSE and their workspace, in order to be able to fetch latest changes, navigate between branches, etc. And are willing to contribute to the project in the future. For those... I find this information really interesting (eventhough it's some more advanced stuff). Happy Flying + Coding! VSCode_Howto_MOOSE_Intellisense_and_Debugging.pdf

+1