some1

I'm off by 3 watts, you're off by 143 watts. As I said, do the math properly, or even better, measure your PC with a power meter.

You're quoting Global System power consumption, it's written right there at the top of the chart. That's total power consumption for the whole test PC they used: motherboard, CPU, RAM, disk, GPU. If motherboard alone used 143 Watts, then it would require a second active cooling solution the same size as the CPU itself. So you've counted CPU twice and did all your math wrong. Do yourself a favor and buy one of these for 10 bucks, you'll be surprised what it shows:

Found this mentioned several times but not as a proper bug report so here goes The initial frequency set in FR24 is plain wrong. This is not a valid VHF frequency. It's like somebody typed "123456" in the code because he didn't have any better idea what to put there.

This is not the issue. Your hardware has nothing to do with it. You load with MRM mode active while the switch on the throttle in game is shown in the middle position.

That still does not add up to 850, not even close, even assuming the worst case scenario where you somehow manage to load all these parts to 100% at the same time. A motherboard does not take 143W on its own, where did you get that number?

After dropping all bombs, the pylon disappears from PACS page, but remains "selected". You can still toggle it by clicking the pushbutton above empty space. In the attached track, I drop all the bombs and then I can't select A2G guns unless I deselect invisible pylon. Also clicking the pylon pushbutton again will deactivate guns mode if it's active. bugPylon.trk

It isn't. A fan is a few watts each, SSD around 5 watts, AIO pump maybe around 10W. The rest of the PC simply does not require much power. Even with a lot of peripherals, there's still much headroom on a decent 850W PSU. Most of the time I don't think so, maybe with some heavy missions or MP.

At the start of a mission, the aircraft system is in MRM mode. But the switch on the throttle is in SRM position. They are not in sync. Pressing the "Weapon switch CNT (SRM)" shortcut has no effect and does not select AIM-9. Because the switch is already in SRM, even though MRM is selected. You have to go to MRM or GUN position, only then the SRM shortcut becomes active and Sidewinder can be selected. bugSRM.trk

I use 850W. It is enough with this CPU.

Added F-15E from Razbam.

It may still be worth doing both. A screen area not rendered by the game at all is better than an area rendered at lower resolution. Larger fov also means more objects inside the screen area to calculate. In 2D just bumping your FOV will reduce FPS even without touching any other settings. The point of that tweak is not to achieve FridgeVision. It's to reduce unusable FOV as long as the change is imperceptible.

Both ends. Pc is obviously busy rendering the whole game, then compressing the video for the headset and sending it through the cable, the headset has to decompress the video using its puny little mobile chip. Momentary freezes may be caused by the headset not being able to decode in real-time and too high bitrate may be an issue. Big freezes and crashes are usually a symptom of something wrong on the pc side.

I did not change any options manually, but the file was still wiped out. Maybe because I start DCS from different shortcuts with command line options (like --force_enable_VR)

Even with Quest Pro, I still have a lot of unused screen area that I can't normally see, which I can disable using OTT FOV multiplier adjustment without any adverse effects. This partially depends on how close to the face you move the lenses, but also on your individual anatomical features. Like how tall is your forehead, how deep are your eyes sockets, etc. FOV tweak is really worth trying, free performance gains.

I don't feel like I'm loosing much detail compared to G2 sweetspot, but I actually like the image sharpening filter that is on by default. Without it there's too much blur. One huge performance trick is to reduce your FOV in OTT. That depends on the shape of your head, but it's possible that you can cut some parts of the display which normally you never see in the headset. I was able to set it to (0,8; 0,85) without any loss in visible FOV, which means there's 30% less pixels to push and less objects to render at the periphery. On top of that I set custom FFR in OpenXR toolkit to 90% area, again reducing the detail at the absolute periphery which I can't even see. That gives another few % of performance. All of that without any visible loss in image quality or FOV, it's only culling the unusable screen area. With the above, I can run in 90Hz mode, 1.5x resolution in Oculus software, 1.2PD and MSAA x2 in DCS, and it maintains 90 FPS most of the time on med-high settings that I used previously with G2.

Yay, again? How many more times do we have to redo this stuff?

But that's the whole point. The game has an offline mode that should let you play for 3 days without online connectivity. Yet with the recent server issues, all authorizations were revoked immediately.

For some reason the current server issues cause the authorization system to treat it not like connection issue (when you still get 3 days to play offline), but an authorization issue (when the licenses are revoked immediately). I launched DCS twice today, the first time I got 3 days counter and could use the modules, but the second time I started the game, the authorization got revoked.

If DCS fails to authorize modules like with today's sever issues, it wipes out all settings from the "Special" tab in DCS Options. These settings are normally saved in "\Saved Games\DCS\Config\options.lua" in the ["plugins"] section. But DCS overwrites this file on every launch, and it does not bother to preserve options for modules that lost authorization. Before: options - Copy (4).lua After: options.lua

Openxr toolkit has a similar feature that works with any headset, you can adjust fov in real time and see how low you can get before you start seeing screen edges. Difference is, IIRC openxr increases pixel density for the visible part instead of simply shutting down pixels, so this setting does not improve fps, but image quality.

I was talking about the original link cable accessory that meta sells for 100 bucks. The one included with the headset is not a data cable, it only carries power. Great that you've found the culprit.

I don't think so, 1.6Gbps is plenty fast, given that the device itself can't decode signal at that speeds. You can try a different cable or pc port, even usb 2.0 should work although at reduced bandwidth. You don't need 20gbs cable, in fact the original cable from meta is still 5gbps.

PF was only a stopgap interceptror until better and more suitable aircraft were developed. Intended to find enemy bombers at night, and not much else. F and its derivatives were the workhorse variant of many armies around the world for many years. And we're getting SRD1 gun radar, that's enough for Dcs combat scenarios.

Your GPU is loaded to 100%, in such scenario CPU can downclock without any loss of performance. It's idling between frames anyway, waiting for GPU to finish its work on the previous frame. CPU can change frequency several hundred times per second. Whatever you see on your OSD, it's just a rough approximation. CPU and GPU frametimes are the primary performance indicators in VR.