dlder

Will try! So, I've now tested with a "clean" Beta install (non-steam) and comparing 1:1 to my steam-stable version. Doesn't seem much difference: (all without Mirrors) 02-08-2023, 11:38:27 DCS.exe benchmark completed, 9535 frames rendered in 109.438 s dcs beta MT "default dcs vr settings" (no mirrors) Average framerate : 87.1 FPS Minimum framerate : 3.9 FPS Maximum framerate : 91.2 FPS 1% low framerate : 44.2 FPS 0.1% low framerate : 1.0 FPS 02-08-2023, 12:06:04 DCS.exe benchmark completed, 4855 frames rendered in 108.641 s dcs beta MT "all maximum w/o motion blur" (no mirrors) -> does Beta currently have a problem with MotionBlur? I figured that out through trial&error, that if this is activated, the screen is blank and only blurry MFD-green-text is visible... Average framerate : 44.6 FPS Minimum framerate : 9.9 FPS Maximum framerate : 52.4 FPS 1% low framerate : 29.8 FPS 0.1% low framerate : 1.2 FPS 02-08-2023, 12:22:08 DCS.exe benchmark completed, 4675 frames rendered in 107.313 s dcs stable mt "2d w/o motion blur" (no mirrors) Average framerate : 43.5 FPS Minimum framerate : 32.6 FPS Maximum framerate : 50.4 FPS 1% low framerate : 29.8 FPS 0.1% low framerate : 4.6 FPS 02-08-2023, 13:05:30 DCS.exe benchmark completed, 9311 frames rendered in 109.672 s dcs stable mt "default dcs vr settings" (no mirrors) Average framerate : 84.8 FPS Minimum framerate : 0.4 FPS Maximum framerate : 90.5 FPS 1% low framerate : 0.4 FPS 0.1% low framerate : 0.4 FPS I've also tested my Marianas flight and it too is the same FPS. So it doesn't seem to be a problem with Tacview or Texture-Mods. Just for comparison's sake, I'll keep using your Track file in DCS beta.

Thanks all! I'll do some more testing; I'm thinking about doing a clean Windows install on a different SSD (don't wanna ruin my current installation^^), but I doubt it would help (only if something critical is out of tune with Windows - Settings). I'll try Caucassus next; I wanted to use Marianas because if it runs here (those trees are very taxing for whatever reason), then it will run Caucasus and all the other maps too. Just for completeness sake, here are my settings: nVidia Pimax (needs to be open for the headset to start?) OpenXR (not much to set up)null

Thanks for True; the resolution is different, but the amount of pixels is apparently the same. Really weird. Yes, as I've stated in my post, I have it set to 100% everywhere. Maybe some Upsampling can work, but if it's not dynamic foveated rendering, then it's a pretty big clarity loss. Can I ask: does your Crystal support eye-tracking & auto-ipd? I don't see those options in the Pimax app anywhere... (as can be seen here: https://github.com/mbucchia/Quad-Views-Foveated/wiki/Pimax-Crystal) The biggest problem I have: even if I fine-tune the graphics and nVidia driver settings, nothing get's me to that level: Sure, I don't know his Pixel Density setting in every middle-wear, but lowering that is like a last-ditch effort. And the 4090 can handle the amount of pixels; in 2D. But that shouldn't make that much different then in VR, one would think.

Hi, I've literally tried every setting in DCS (Stable, MT) so far and checked it in a 1500ft flight over Marianas. I'm running OpenXR + PimaxXR and DCS forced to OpenXR. I've set pixel density in PimaxPlay, OpenXR and DCS all to 1.0. Here are my specs: Here are my findings: So, with that out of the way: how is that possible? From 66 to 20 FPS? There are dozens of posts of people running an older i5 with an 1060ti playing in VR... I just don't get how!? Do you have any tips on what else I could check? "Windows Game Mode" is on (should help with Win-AntiVirus which isn't power hungry in the first place) "Windows Graphics preference for DCS" is set to High performance "Hardware-accelerated GPU scheduling" = on Thanks for "hearing me out"^^ I'm truly baffled tbh. I've only tried "Serious Sam VR" (SteamVR, not OpenXR) and it ran flawlessly with max settings. Sure, that's an older title (to be fair: so is DCS), but it shows, that there doesn't seem to be anything "generally wrong" with drivers, APIs and such. DCS Settings for VR.pdf Custom2.lua Custom3.lua Custom1.lua

The fuselage tank can hold 85ga of fuel and the gauge goes up to 85 What I am not sure about: are the right/left wing fuel gauges non-linear? Because the 75ga is pretty much at the maximum on those gauges, even though it holds 92 gallons: null So ist the very last, 100% mark actually 92 gallons? Or is 75 not gallons, but the percentage (what I doubt)? I just can't find that answer in either the DCS manual, nor Army FlightOps, nor Dr. Google... Cheers!

Ok... small update: I'm mildly optimistic that it works, just the way I've configured in the VPC Config. Seems I just had to restart DCS: null I'm gonna continue to configure this Hotas, but I might just finally have figured out how to do it... (fingers crossed) Thanks anyway

I've been playing around with those stupid 4-way HATs that Virpil uses for literally hours now. If used as default, you only have 4 physical and thus 4 logical buttons. Diagonal are just 2 directional keys combined; that doesn't work in DCS. There is NO WAY to set them to 8-way; you can use "Toggles Decoding" to create 4 virtual buttons for the diagonal, which does work somewhat (you get a new logical button which can be assigned in DCS), but because both the directional keys + the diagonal key get activated, it can happen that DCS doesn't activate the diagonal, but one of the directional keys. Very frustrating that. So, the only other way I thought might be possible: create a POV; it doesn't use buttons and thus there is no... "cross talk" between the directional and diagonal keys. The problem here though is: DCS doesn't see POVs? Windows does: But I can find now way to bind the POV to anything... null Any idea what could be wrong? Or does anyone know how to use a Virpil 4-physical-button-HAT as a 8-button-HAT? Thanks, dlder PS: for completeness sakes, here's the Virpil forum post: https://forum.virpil.com/index.php?/topic/16977-hatspovs-with-8-buttons/

just to add my 2c: I've always been playing at native resolution (3440x1440) and the highest graphical setting. I NEED to use barebones labels and or finding targets is impossible! Not all pixels are the same; clearly. PPI of displays just changes things and having a higher density / smaller pixels is visually better. But not in DCS, where you get punished for going beyond 19", 1280x1024 it seems. That may not have been a problem in 2008, but it is now!

What you're doing is an awesome idea! Especially the liveries; nobody needs dozens of GB just for that. The F-14 alone has 11.5GB of liveries...; the F-1 has 7.1GB. AH-64 are 5.1GB, etc, etc. I hope you'll downsize all of the default ones. Cheers!

Thanks; I did do that:

Here's the related topic where I asked about this problem: The gist of it is this: the manual states so, to tell if you are in range to launch your AGM-65, you watch the seeker's crosshair in the TV and if it starts to blink, you can fire the missile But that's not what happens. The crosshair starts to blink as soon as you lock onto a target! Doesn't matter if it's in range or not! Here's a video showcasing the problem: I've also included the track file. Thanks! A10A_MAV-in-range-bug.trk

So, I'm pretty sure I cannot post a Trk for that, as it's input related, so let me explain what I mean: when using the MAV, I can move the targeting circle around with my mouse. Up, down, left right, just as expected. but it doesn't work for bombs for some reason I can only move it left and right with the mouse to move it up/down, I have to use the keyboard Here's my mouse view/tdc setup: Cheers!

Thanks for that hint; I did go through pretty much all nVidia settings and now I know: it's not Reshade, or Auto-HDR. Nor is it GSync and Ambient Occlusion. it's MFAA I never expedted this to be a problem; for me, it was just a newer, better way to do old-school MultiSampling AntiAliasing. Seems it can actually cause artifacts in some games (DCS is the first tbh though)...

So, I read a bit more in the manual and on page 95 it really does state, that the flashing crosshair indicates "in range":

Will do and report back asap; ty!

This is not a new, DCS 2.8 issue (I'm on latest stable), as this has been an issue in 2.7 too; I hoped it would've been resolved by now, but I guess not a lot of people are experiencing that, so it never came up? It's a kind of shimmering, which isn't always there; I guess it depends on the time of day? Its apparent in the first two missions in the A-10A campaign; it's gone by the 3rd though... but it is at least reproduce able, which is always good to find bugs^^! Makes me wonder, what special settings I use for that to happen... I'm on max graphical settings in DCS. I had that problem with my previous computer (Ryzen 9 3900X + 1080Ti) and with my new PC (i7-13700KF + 4900), so it's not the hardware. Would be awesome if other people could try those two missions (you start right next to the water, so it only takes a few minutes to get into the air and the bug is visible)! But here is a track file nonetheless; hope it helps! Thanks WaterRenderingBug.trk

Just to add: I have these issues too, especially visible with clouds

We already have attack planes and multi-role jets, but especially with the coming F-15E, this quote from the book "Flying the F-15E in the Gulf War", the "AWACS for the ground" would be immensely valuable! Especially with datalink and hopefully some more integrated/better communications, because the controller has to "paint a picture" for the pilot to look for the target (like outlined in the book), this would bring so much immersion to the game! So, the question shouldn't be IF, but WHEN. Thanks for the consideration, dlder

But aren't track files inherently unreliable and "shifting" (in what is happening when/where/what? It's been said all the time that you can't watch track files as things shift out of place, especially in multiplayer track files, to be fair, but happens in SP too).

Thanks for your help and opinion. Gonna consider posting a bug report; don't know what a track file or a logfile would be good for though. Anyone can just try the Jet and see for themselfs...

Unfortunately, no. It starts flashing as soon as you lock a target; even if it's beyond range. From the manual: A valid lock is any hard lock on a target (not the ground itself). I too read it at first like you mentioned:" within firing parameters", but that alas is wrong. So I guess at least with the "A", there is only eye-balling it.

Is there any indication anywhere (which I'm not seeing), that tells you that the target is in range and can be shot? Stationary and more importantly moving targets? On another note, the manual is wrong with this statement: Both can lock onto truck sized targets from 20.700m (11.2nm) slant range. Or this one: But both have 6x magnification!?

Thanks!!

Ok, now that we've concluded that this is normal behavior for the airbrake-toggle in the A-10, there are some other things that might be wrong / not working: The "TDC Slew Vertical (mouse)" doesn't work for the CCRP "depressible piper" (it works with MAVs though!). The piper can only be moved horizontally with the mouse, not vertically. Only with the keys, it can be moved vertically! Pretty weird... I've found a post explaining what EAC does stand for and what it does, but when pressing the default keybinds (LAlt 4 / 5), the EAC-switch (behind the throttle) doesn't move and I'm too inexperienced in the A-10 to know if it's just the switch not moving or if that function won't de-/activate

Oh... I haven't read anything about that in the manual; good to know then! Yep, tried it: you'r right! Thanks again!