TED

Master arm was on. I'd just dropped jdams previously. All the indications showed they'd dropped, which wouldn't have if not armed, so a real mystery! I did another run yesterday and this time they dropped although the impact point was well off as was the 200' interval I'd set.

I’m not sure if this is a bug or user error and these days the user base seems to be posting less and less. Anyway, I’ve been away from the f15 for a while and the last days getting back into it to see how it is. I was trying to use blu 107 on an airfield runway. Set to CDIP, R.SGL, N/T. I am carrying 12 bombs and dropping 6 at a time with intervals of 150’ set in the PACS. As far as I can see I’m following the manual and used to do this quite a bit. I fly a low level pass, pipper on the runway, it designates and appears to release. I see on the armament page 6 bombs have gone, I get the relevant hud release symbology and get a little kick in the haptic seat. As I bank around and check there are no explosions. I then checked the f2 view and lo and behold all bombs are still on the rack! I checked the track replay and see that they don’t actually drop. I don’t have the track file at hand right now so can’t attach it. Just wondering if anyone else has seen this, if it’s any known issue or if I’m missing something in the setup?

This just happened to me today. Also Afghanistan map. Straight and level trimmed out transiting back to Kandahar, a sudden nose down. Short finals to landing sudden pitch up. I've flown hundreds of hours on the a10, albeit not many in Afghanistan, and this is the first time I've experienced this. Quite noticeable.

To be perfectly honest, I just don't understand anymore why people use quest link when virtual desktop is so good. In my experience its just better in every way. Certainly worth a little effort to get it all running, then just uninstall all meta rubbish. Its a constant lottery with every new meta update as to what it will have broken this time. I've had almost non issues since i started using VD a couple of years ago. Any issues i have had, have been due to my own configuration mistakes. Once it's working, it just works. It seen like the developers actually test it thoroughly with multiple headsets and multiple games, including dcs, before they release updates. Its pretty rare if ever an update breaks anything and it just keeps getting better and better.

I’d love to get metalink to work properly just to see if it really compares, but alas - meta says no!

I gave up on Link almost immediately after I got my quest pro and stuck with VD. No matter what I do with link it looks like a mess and none of the settings seem to adjust the graphics and resolution. No idea why. I reinstalled last week and tried again out of interest and its still a blocky mess compared to VD. The difference is huge. I know it’s not supposed to be like this, but to be honest when VD just works, I can’t be bothered messing with link trying to work out which bizarre setting is conflicting with what and why none of the sliders make any difference whatsoever. For such a big company Meta really have messed up on the software side for vr.

Managed to get hold of a globular cluster for the QP. Totally different experience now and solved all comfort issues. Very comfy to use now, so thanks to all those who suggested this as the solution.

Yep. Forgot to check other Amazon stores. Ordered now and hopefully that makes it a bit better.

Tried switching the rear pad around and that is definitely worse for me. Globular cluster seems like the go-to recommendation but they don't seem to sell anymore here on euroland!

After getting my new quest pro, do far really enjoy it except for the comfort issue after playing for a while. Especially noticeable on the forehead with a lot of the pressure building up there. Does anyone have any good recommendations for improving the comfort for longer sessions?

+1 for quest pro. It’s a fantastic headset for dcs. Don’t even bother downloading the meta software on your pc. Just use virtual desktop and leave it at that. Just to throw another option in, I’d seriously consider the pico 4 as well. Much cheaper, but a very good headset and often overlooked as it seems pico hasn’t really hired very many YouTube reviewers as the competition. I have both pico 4 and quest pro and the difference is really not as much as the price indicates. The pico is also much more comfortable. With both headsets, if battery is a worry, they can be plugged in while u play and keep charging. The lenses are better in the quest pro and it is noticeable but the pico does look very nice with a very small amount of adjustment. Use fixed foviated rendering and the performance is good. I still use my pico from time to time and it is much better than I ever expected.

Just downloaded and tested today. Just echo what others are saying and what a great job ugra have done indeed. A really beautiful map and lots of interesting possibilities. Having spent 5 wonderful years myself based in Germany and flying low level around the landscape it really brought me back. A few noticeable landmarks obviously missing but the general feeling is very good and i was able to use my (aging) memory to navigate around quite nicely through the terrain.

Yes. That s what i had read and was doing but for some reason above about 28000' the coolant temp was still getting too low. The engine would just then seize with now warning. The prop just stops and a was never able to do a restart on the long way down.

I re-did the sortie and tried to pay closer attention and it seems to be the rad temp that gets too cold when up high. I alternated between having the radiator flap in on and off (auto) and manages to keep the engine running on the third attempt.

I'm doing beware beware campaign and in sortie 5 at 28000' I've gone over to the main tank, the fuel pu.p/pressure switch on the lower left is on, the fuel pressure warning light has come on so I've switched the pressure lever on the right to on and a few minutes later, in almost exactly the same point, twice the engine just stopped. No warning, just stops. I can't for the life of me work out why. All the temperatures and pressure appear normal. Anyone have any ideas what I'm missing here?

Strange. I do t get any of that latency using VD, even moving my head, it's very smooth. Flying low level in the spitfire from bigin Hill in the Normandy 2 map with a formation and looking out the side, all is still very smooth. Definitely had the same resolution in meta. But definitely worse visually and in terms of performance.

I get very solid bit rate. I've found HEVC to be best and set it to 150. If I use h264+ I easily manage 350. Might be worth checking your router. I replaced mine last year and made a big difference. Also I use a separate 5ghz router only for DCS.

I had a other play around with both today and my experience is just very different from yours. The image quality of meta is way worse than that of vd. I've found vd to be mostly smoother but probably very little difference. The killer though is just the silly set up process and procedures with link. I also cannot get h265 to work without it freaking out totally. HEVC works perfectly in vd. Honestly if it wasn't for VD I'd have returned my quest pro as to me the meta software is a disaster compared to VD. I have my pc connected via ethernet to my router and a fast wifi6 network so wireless VD works really well and that will be my only used method.

I'm really not sure what's going on. To be honest I'm very happy with VD and it was more our of curiosity to try link. I have OXRTK disabled so theoretically I'm running the same resolution, however it looks very different. I think if nothing else this just kind of proves the power of vd as an amazing product in that it just works with minimal fuss. I may have another look later at link and try to see where its going wrong. I noticed as well that I can't seem to get dynamic foviated rendering working properly in link. No problem at all with VD. This shouldn't affect the difference I'm seeing anyway as the fixed foviated render is working in link. I'm even starting to wonder if the oculus debug tool is actually doing anything. If I adjust the resolution up and down in link it is a clear difference but when I set default resolution in link, the 1.73 in oculus debug it looked like very low res.

Thanks again. Tested the cable. All is good. Used the exact same settings as you and still just looks terrible compared to vd. Looks very low resolution too. Something is not right somewhere in my settings. Probably i will just stick to vd as it just seems to work without any messing about.

I have an aftermarket usb c cable I bought that is good quality. Im not sure what else could be accounting for such a large discrepancy in quality. The main difference is in smoothness. Link just seems very choppy compared to vd. Would u mind posting your odt settings?

Yep. I found it. Thanks. Had a good test of link and in my opinion VD is just way better. It seems much clearer, much better performance and more user friendly. Not sure why this is. When I set and compare both like for like - 72fps no asw, HEVC/H265, godlike resolution and 1.0 in oculus debug - VD is very smooth, with a much better image and no stutters. Link just is not. It looks worse with less clarity and quite stuttery.

Stupid question, but where the hell is the oculus debug too?

Im currently using a quest pro and have always used VD as my previous Pico 4 worked great with vd. Considering trying quest link out of curiosity. Will QVFR and DFR still work with link?

I've just picked up a quest pro and no issues for me with eye tracking. I do not have developer mode enabled. It seems like that's not required anymore.