Jump to content

frizball

Members
  • Posts

    39
  • Joined

  • Last visited

1 Follower

Personal Information

  • Flight Simulators
    MSFS DLS IL2
  • Location
    USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm new to the P-47 and this campaign. I've read the guidance on climbing with AI and can manage to (mostly) keep up during the initial climb. The problem I'm having is that after reaching cruising altitude, the AI never seems to reduce their unrealistic power settings. Mission 1, which I am still stuck on, the whole AI fleet is balls-to-the-wall all the way until the relief flight shows up. I can climb (mostly) with my flight up to altitude and be within range of catching up, but even if I leave the aircraft at 52/2700, cowl flaps closed, oil/turbo coolers neutral, cruising at 250mph IAS, the AI flights still outpace me. Occasionally I can close some of the distance if I under cut one of their turns, but as soon as I turn back to following, they outpace me once again. I've watched videos that are a couple years old of the flight in this mission where it seems the player is keeping up just fine wile cruising around 200mph IAS. Once the relief flight shows up and our flight heads off to RTB, it seems everyone slows down to a reasonable cruise speed and I am able to catch up. Of course by that time I am so low on fuel that I won't be able to make it home.
  2. Keys are stored in registry.. you can modify most stuff via CLI.. https://mbucchia.github.io/OpenXR-Toolkit/cli.html
  3. IMHO, the focus/peripheral blending is better. And, you have more control over the size and resolutions of each zone. But, unless you want/need to run additional OpenXR layers that conflict with native quad-view (like Toolkit or OBSMirror), or if you want to play other quad-view enabled titles, there is little other reason to migrate over today.
  4. No worries dude. My original message was smart-a**ish in the first place. There’s so many many moving parts it’s hard to keep track of. I also admit that with QVFR being a more generic implementation than Varjo-Foveated, there is far more documentation to look through.
  5. Its not though.. what you are experiencing is the g-force effects interaction with the lens effect... null
  6. Apparently nobody reads anymore... https://github.com/mbucchia/Quad-Views-Foveated/wiki#dcs-world
  7. If you can source a sheet of this microsuction "tape", it works really really well for sticking your pedals to a hard-surface floor. It's not tape at all, rather a microscopic suction cup surface that adheres like tape but is easy to remove/replace/clean and leaves no residue. It's the same stuff that Honeycomb uses on their mounts for the Alpha/Bravo controls, if you are familiar with that.. https://sewelldirect.com/products/airstick-microsuction-tape?variant=15164885270574 Amazon (US at least) has it, or you can try direct from Sewell
  8. How handy are you? G2 speaker adapter: https://www.thingiverse.com/thing:5238887 And a remix of the above for the Index speakers: https://www.thingiverse.com/thing:5634650
  9. Its normal for people not to like things they don't understand. OpenXR is a standard. OpenVR is a standard. SteamVR is an application. SteamVR supports both OpenXR and OpenVR. OpenXR Toolkit is a .... Toolkit. Written by a community member to enable users to tweak and tune and optimize to their hearts content. In no way, shape or form is it required.
  10. @YumaThe issue is that DCS is applying effects to the focus view the same as it is applying them to the peripheral view, and the same as it would if it were applying them to just stereo view. This is a no-no per the Varjo SDK documentation and is the same reason that effects like Bloom and Lens Effects also mess with the focus display. https://developer.varjo.com/docs/get-started/Post-processing You can set Render Mode = 0, which will remove the effect entirely, but you can't only remove it for just the focus area. Just for @tacca's edification.. this has nothing to do with your mod. This is the 'issue' being referenced. null
  11. I think you're over thinking it.. literally just turn the override resolution flag in OpenXR toolkit to OFF... then you're right back to what is set in VB (the next time you launch DCS). If you want to delete the value you have currently set when override is turned on.. delete the following entry from the registry settings for DCS Computer\HKEY_CURRENT_USER\Software\OpenXR_Toolkit\DCS World - 'resolution_height'
  12. nullhttps://varjo.com/use-center/get-to-know-your-headset/getting-the-perfect-image-quality/ That's because you are "overriding it".. it is ignoring what VB is trying to use
  13. Re-reading your message, I think I misunderstood what you're asking.. but I'll leave the below intact as well.. OpenXR Toolkit doesn't care what PPD VB is set to.. Whatever you set in VB is what you are going to get in the headset. *UNLESS* you override the resolution in OpenXR toolkit (this is not enabled by default, in which case OpenXR toolkit plays no part in the final resolution in the headset) Previous reply ~~~~~~~~~~~~~~~~~ Varjo Base still controls the resolution ('High', 'Highest', etc..) and you can see the actual peripheral and focus region resolutions listed in VB when you pick one of those presets. The peripheral and focal multipliers in the configuration file for the DFR layer is exactly that, a multiplier of the listed resolution in VB. If the resolution listed in VB when you set 'Very High' is 1140x1140 1908x1632, and you set both multipliers to 2.0 (dont do that though!). You would see VB report the resolutions as 2280x2280 3816x3264 once you start DCS Leaving the config file at 1 and 1 for peripheral and focal will give you the resolutions shown in VB by default for any given PPD setting
  14. Getting this odd behavior, only in the left eye. You can see in the video the lighting moving around while reflecting off the buildings on the other side of the field. You can also notice the flickering in the hangar lighting in the left eye. No mods installed This issue does not happen in ST Have tried many, but probably not all, permutations of settings. MT Lighting.mp4
  15. +100... I've tried all permutations of settings I can think of.... No mods MT Lighting.mp4
×
×
  • Create New...