slughead

There has been one for a while...

It seems that turning off Bloom Effect has solved the darker rectangle. Thanks for poking me / giving me a slap

Bloom effect. Missed that one. I'll turn it off and retest.

Mine is configured as per the instructions. It has been that way for a long time before the tool was released. Yet I am seeing this darker rectangle. It isn't present all the time. There are scenes where you can't see it and others where you can. I will experiment and try to pinpoint a scene where it can be seen and if possible I will capture it. For the time being though, I'm just having fun with it. I've only had a couple of short flights so far and also want to demonstrate some absolutely bizarre AI pilot behaviour to ED. Lot's to do! And no, your performance is fubar. I have the same spec system 72Hz, 4x MSAA, 1.3x (ish) PD, all DCS settings maxed out and it's pretty darn good. Moreso with the ETFR. Have to admit that I notice the FR. I'll just have to get used to it. Sacrifices and compromises. It is what it is.

Yes, with lower numbers you should be seeing a smaller image and black borders. So it doesn't appear to be activated for you.

Or just have other business-driven priorities at this time. Let's face it, it's not something they're probably going to make a lot of money doing so they go for the best bang for the buck first. For us it is personal, for them, it's business. By the way, thanks @mbucchia I appreciate your efforts.

It would seem that just opening and resaving the mission also solves the problem for me. I am on the latest open beta.

I wouldn't know where to start with the editor which is why I popped the question up. But never mind, I'm an engineer so don't mind having a fiddle and found that the speed was set to 270kts. I set it to zero and solved it. Retested with your original mission and that one still opens up the throttle when the mission starts. I watched the rpm needle go from 60 upwards without touching anything. With my change, it doesn't move. I went to and from mine and yours a couple of times with the same result.

I have. It doesn’t

It's not in the "home" GUI, i.e. within the headset. It's in the Oculus PC app.

Thanks for this. I've not had much of a chance to fly with this and give it a proper test. My first observation though is that I can see the rectangle as my eyes move around. The image drawn within it is slightly darker so it's quite apparent to me.

AI pilots. Are they the most useless things in this simulator? They crash into hillsides. Can't maintain level flight without wildly increasing or decreasing altitude like a yoyo. They crash on landing and if they don't taxi right off the end of the runway, through fences and off into the sunset. Never mind their ability to stop the aircraft (F-16) yards from touchdown.

I don't know if I have narrowed this down as I have to do more testing. I recently turned off OpenXR Toolkit for preparation for ETFR (eye-tracked foveated rendering). I don't actually use any of the features of the OpenXR Toolkit anymore other than the in-game performance metrics. So far, the problem is significantly improved. The only other change I did at about the same time (yeah, I know, I should only make one change at a time) is to set the Dynamic Bit Rate Offset in ODT to 50. I run with Encode Dynamic Bitrate "Enabled" and everything else at default.

I find that this starts with the throttle open and so the F-16 starts rolling straight away. If I push my throttle forward then back it will only then return to idle. Can you check the script to see if there’ is a bug for the F-16 please?

No worries fella

Indeed my dear Watson lol. Anyway, word has it that it might be released later today! Hold my beer!

No sh!t Sherlock

Perhaps you meant that as a reply to something else?

I am on v54 with no problems over link cable. I’ve not seen any reports of problems with v54 and link cable on the atmeta forum (the official meta/oculus) forum. Anyway, no problem. Good luck.

Yikes. v55 is beta code and Meta/Oculus has a really bad beta reputation. I would turn off PTC / remove yourself from it and factory reset again so it removes all development code and installs released code and configuration. Same with the Oculus app on the PC. If you still have problems return it and get another.

Have you factory reset the headset?

The page was up 3 days ago. It’s just an edit to the contents that he’s done today.

Rarely I think. Sometimes the app and the headset get a bit "confused" so a restart of one or the other or both is in order. Not sure if that is one wake from sleep though as I've never really thought about it too hard. I think it's usually after messing about in the OTT or ODT. I'll keep it in mind though and let you know if I have more info. I read your post on atmeta. Hilarious support response as usual... an utterly useless lot. Just like the bunch on Microsoft support forums. Pretty sure these people are utter amateurs and have no clue about the device and software.

Excellent! When I asked about this I got the distinct impression he was very passed off with meta and wouldn’t waste any more time on the Quest. I wonder what changed

I can't concur. I don't see a difference in the shimmer of the roofs of buildings with the sun on them at distance with the render resolution maxed out. Are you running with MSAA at all? I am running with MSAAx4.