whitav8

Members
  • Content Count

    390
  • Joined

  • Last visited

Community Reputation

45 Neutral

About whitav8

  • Rank
    Member
  • Birthday 01/03/1947

Profile Information

  • Gender
    Male
  • Location
    Oceanside, CA
  • Interests
    High performance graphics PCs, helicopter flight simulations with three monitors (separate views), photoreal scenery

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

About Me

  • About Me
    Retired from 30 years at the flight simulation department for Boeing Commercial in Seattle and also 10 years with the US Navy at Pt. Mugu, CA in their missile and carrier aircraft flight sim department

Recent Profile Visitors

2,117 profile views
  1. whitav8

    Possible flashlight for VC use in 4.4?

    @Lorby_SI, Sorry to redirect this thread - thanks for the flashlight! Any chance that your scratchpad app would work in VR? We desperately need at least one window for kneeboard help! Thanks much - you are certainly a talented developer! Dave W.
  2. You could try the following CFG setting. I don't remember if it works well in VR: In the configuration file CAMERAS.CFG there is a setting Clipmode in the section for VC. Changing the default setings (=normal) to =minimum can solve this problem, but it causes flickering textures in some cases.
  3. @Brian, You have reason to wonder whether it will be easy to setup - it might be and maybe... Well, I suggest you get a lot of ideas from reddit Reddit - Windows Mixed Reality (which is what you will run with Odyssey+). You don't say what your PC is but if you are getting reasonable frame rates on three screens (separate views, not NvSurround) then you might be OK. I have a brand new PC with a 5Ghz i9 CPU, an Nvidia 2070 GPU, P3D on a fast SSD, and brand new motherboard with USB3.0 ports and running Version 1809 of WIndows 10 - along with my Odyssey+ With all of that, I had a fairly easy time of getting going with P3Dv4.4 (set with Single-pass VR) and I am able to run medium graphics settings (minimal shadows and 2xMSAA) in low density photoreal scenery (no major cities or airports nearby)at 45 fps. This 45 fps requires the forum discussed edit of the following file: XXX:\SteamLibrary\steamapps\common\MixedRealityVRDriver\resources\settings\default.vrsettings to read: // DHW - was 1.0 but 2.0 and SteamVR Manual override SuperSampling set at 200% is much more clear for instrument panels "driver_Holographic" : { "renderTargetScale" : 2.0 }, "driver_Holographic_Experimental" : { // Motion reprojection doubles framerate through motion vector extrapolation // motionvector = force application to always run at half framerate with motion vector reprojection // auto = automatically use motion reprojection when the application can not maintain native framerate // DHW The next line is commented out by default and should be for sims/games other than P3D "motionReprojectionMode" : "motionvector", You will need to install Windows Mixed Reality Portal unless it came with your WIndows 10 update. Then Steam and Steam VR, AND SteamVR Mixed Reality plugin. I start these applications first and make sure that all is well with the image of the Steam VR "Home room". I may have started P3D already and position myself with the scenario of choice in a non-VR mode. I use a HOTAS joystick (mine is the PS4 version of the Thrustmaster HOTAS.X) so I can use buttons for pitch trim, brakes, flaps, gear, speedbrakes, and HMD - Recalibrate Origin. A check of FPS should show above 100 before I go to VR Mode - which I do by using the Virtual Reality Tab of P3D and select SteamVR. The monitor screen should show two images and the FPS should be right at 45 which shows that the SteamVR reprojection mode is on and is providing half of 90fps "sync". Your flight should now be fairly fluid and the view is tremendous (but somewhat less clear than a monitor) - enjoy! As you can see from the Reddit forums, there are many folks having troubles with their headset working right out of the box because of HDMI or USB problems. I suggest getting those solved first before any hope for P3D. Best wishes Dave W.
  4. Does anyone know exactly when the sale begins - example, 12:01am Nov 18th EST??
  5. whitav8

    P3D v4.3 Crash Analysis and final result

    Jim, You list of steps for reinstall are great! I would ask that you copy this to a new topic and then pin it. The only additional comment is that we should make a batch script to make the Documents and etc folders easy and do it after each new major P3D addition maybe. I had to reinstall because I couldn't get Windows 10 to startup at all (repair wouldn't work ). At that point, it is really too late to be backing up since the only way to do that is to get a CMD shell running with installation media, do the copying with DOS-like commands, and then reinstall WIndows 10, and reinstall P3D (what a lot of effort!!). THanks for taking the time to make a great list of what's required! Dave W.
  6. whitav8

    P3D v4.3 Crash Analysis and final result

    @Jim, I am directing this question / comment to you about the steps we should take BEFORE we do a windows 10 reinstall. Maybe this info - after suitable editing by several of us - should be pinned for this forum title. I just had to reinstall Windows 10 and erroneously thought that my scenario files would be left alone but I was wrong - anything that has to do with the "Documents" folders was erased. I would suggest that as much as possible of the control files be backed up. Here is a list for me: Scenarios - "C:\Users\USERNAME\OneDrive\Documents\Prepar3D v4 Files CFG files - "C:\Users\USERNAME\AppData\Roaming\Lockheed Martin\Prepar3D v4" (Only some of these files will be needed or used for reference ) Scenery.cfg and more - "C:\ProgramData\Lockheed Martin\Prepar3D v4" (Only some of these files will be needed or used for reference ) I also recommend each user developing a reinstall_apps folder with each application of interest setup.exe or xxx.msi type files plus website URLs - example for me, Anti-virus, DCS, GIMP, Irfanview, Java, Notepad++, OCCT, Oculus, Prepar3d_Aircraft_Scenery, Printer, Steam, Joystick, USB, Video Card, VisualStudio, WinRAR, etc.. Then reinstall Prepar3D (you won't be able to uninstall Prepar3D if you had to reinstall Windows 10 because you couldn't repair it )
  7. I am a bit confused about Steam (Valve) Motion Smoothing because the Odyssey+ is running with Windows WMR - isn't it? A quote from your article: Valve’s Alex Vlachos tells Road to VR that Motion Smoothing is similar to Oculus’ ASW, but not identical. “We feed the last two frames from the application to the GPU’s video encode chip to generate motion vectors (which are very rough), then [Valve and Oculus each have their own] methods for filtering those vector fields and applying them to the most recent application frame to generate a new frame,” he said. “So ASW, SteamVR Motion Smoothing, and WMR Motion Reprojection are just different implementations of the same high-level tech.” Like I said above - I hope someone can do a great review on the Odyssey+ with a flight sim (maybe SweViver of Pimax 5k+ fame) - even though the Field of View is somewhat less than PiMax 5K+ (150 degrees Normal mode versus 110 degrees for Odyssey+ )
  8. whitav8

    Rift

    First off, you must understand that P3D just doesn't have enough performance even on a single HD monitor to provide a super smooth experience for VR. VR has to generate a slightly different 3D image for each eye (left / right) to get stereo to work and on top of that it is generating the image with a much wider field of view (100 degrees) than usual for a monitor (maybe 60 degrees) - more 3D objects to process. You should definitely use Single Pass Stereo mode for best P3D performance and you will need to make a lot of compromises to get fairly smooth operation. You need to start with a simple aircraft that has steam gauges and a fairly simple scenery area - not a high-end complex airport. You will be lucky to get enough performance to even run with Oculus ASW (half-frame repeat with simple pixel offsets at 45fps). A good rule of thumb is to see that you are getting at least 60 to 70 FPS when using a 2D monitor in the same scenery area, the virtual cockpit, and same settings. VR is the way to really enjoy a flight simulator in my humble opinion! I have P3D (which until recently wasn't much good for VR) and Aerofly FS2 (the best VR performance but missing any third-party aircraft) and even though I have three monitors for wide viewing, I much prefer VR since everything is to real world scale - even with less resolution currently. I was excited to see that the VRS F-18+TacPack bundle released recently would work with P3Dv4.2 and was hoping that it would run smoothly in VR with ASW (45 fps image interpolation). It turned out that I had to craft(tune) some very specific settings in order to fly without stutter - most of the time. My system is a medium performance PC running WIndows 10 - 4.2 GHz 6-core i7, Nvidia 1060 6gb, SSDs - so anything more than that should be able to add back some desirable features like the canopy model and cockpit shadows but I recommend that you start with these settings before you add back. I knew from previous experience that I had to be careful to use a scenery area that should have great performance due to its simplicity and lack of major airports, so I chose to focus on Kaneohe Bay on the northeast side of Oahu - the Marine airbase PHNG. I have the older Megascenery Oahu photoreal but there is a freeware project (that has a FPS reduction) for Oahu from the following: https://hawaii-photoreal.com/downloads-fsx-p3d/ Settings for Oculus Tray Tool: (use Steam VR settings for the Vive and WMR) Prepar3D SS=1.4 ASW Mode = 45fps Normal WMI P3Dv4.3 Settings Virtual Reality Tab On screen display mode = Double View Headset Display Mode = Single-Pass Stereo View Graphic Options DISPLAY FXAA=off, AA = 2XSSAA, Ani=8X, Texture=2Kx2K Frame Rate Target = Unlimited, Vsync=off, Triple=Off MimapVCmode = checked WORLD LOD=Ultra, Tess=High, Mesh=10m, TexRes=7cm Scene Complex = Dense, Autogen Dist = High, Autogen Veg = Normal, Autogen Bldg=Normal Water Detail = Low, No Bathymetry, No reflections SpecEffects = Medium LIGHTING HDR off No dynamic Landing-Lights = checked No lens flare Shadow qual = low, Shadow Dist = low Cast and Receive ONLY for External Vehicle and Receive for Internal (i.e. no cockpit shadows) WEATHER Cloud dist = 80 Cloud Cov = Medium Detailed clouds No more checks TRAFFIC None!! - this is a real performance downer APPLICATION Pause on task switch = unchecked Hope this helps! Dave W
  9. This sounds more like a diffuser that is a simple optical layer (like scotch tape) that was tried by a lot of DK2 users to reduce SDE. Similar to the following:https://www.reddit.com/r/oculus/comments/2dq69k/comparison_of_dk2_screen_door_effect_with_and/If it's not overdone - that is, it becomes blurry - this could be very nice. I like the price and the fact that it doesn't require any more CPU/GPU power. I think some reviews are in order (CV1, Vive Pro, PiMax5k+, Odyssey, Odyssey+) and for me, flight sims as visual benchmarks. I have heard that WMR headsets don't have an ASW (half-frame HMD rate)support really yet - maybe whatever Steam provides but not as good as ASW. Also, is the head-tracking good enough for flight simming?I'd like to see a PiMax 5K+ with a similar SDE reducer.
  10. whitav8

    Quality Wings 787 vs PMDG 747-400 (800)

    The cockpit graphics of the 787 are much more current than the 747 and somewhat similar to the Airbus A350. Just a thought
  11. whitav8

    RTX 2080 ti P3D benchmarks?

    @DylanM, I wonder how many 4KHD large screen HDTVs the 2080ti could drive at a great frame rate?? Sounds great! But maybe just a very large curved 4KHDTV would perform better. I've noticed at Best Buy that I can get real close to a 4K TV - maybe the standard 30 inches for just standard PC work. Dave W.
  12. Make sure your Power Management mode is Prefer maximum performance in the Nvidia Control Panel.
  13. Thanks much - I'll try to make sure all those steps are followed Dave W.
  14. Fellow Quality Wings 787 flyers, I don't always get a switch from LNAV/VNAV to plain LOC/GS at approach even though I push APP on the MCP. What am I doing wrong? Thanks Dave W.
  15. Make sure you are running P3Dv4.3 - fixes were made to those issues in Single Pass with v4.2