Jump to content

Snake122

Members
  • Content Count

    305
  • Joined

  • Last visited

About Snake122

  • Rank
    Member
  • Birthday 12/26/1979

Personal Information

  • Location
    Indianapolis
  • Occupation
    Aviation teacher/flight instructor

Recent Profile Visitors

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

  1. Thanks for the suggestion. For me though, this works out to be about the same as SVR 78% PT RQ 1.0 which is the resolution that I get almost exactly equal with 50% SVR and PT RQ 1.25. I can also tell that the HUD is slightly less crisp than SVR 100%.
  2. One thing I've noticed is that you have to actively unload the nose when you get in the less than about 250 knots to accelerate with any reasonable amount, I haven't ever looked down to see if I'm at the AOA limiter max. But it will be wallowing around and releasing pressure won't reduce the small amount of Gs, normally 1.4 with neutral stick, you actually have to push over to get it to 1G and start accelerating better and of course a full 0G unload is best when you get the Viper down to where it doesn't like to be.
  3. Plus the Leap Motion seems to have a pretty big performance hit using the two other DCS solutions (VRK for Oculus, SDdraw for SteamVR).
  4. Yes, to me it is smoother at 50-60 fps with my 3090 without motion smoothing than the 37.5 "smoothed"
  5. But even though the parallel projection fix isn't needed anymore in the title, your mod is the only thing that I've found to fix the Pimax NVG not converging issue. Plus I love the label masking, it makes the dot labels feel a little less like a cheat, although I feel like it is needed in VR.
  6. Definitely for me too, it's great to mask the dot labels and make the Pimax NVG tubes converge properly!
  7. Just reporting I'm getting this same crash still on stable 2.5.6.55960 as I cross over APEX.
  8. Yes, it was mentioned earlier in this thread that the parallel projection was no longer needed and it definitely has a performance increase. But I understand how you missed it with this big of tread and now no longer a quick thread search option and it should be mentioned again anyway!
  9. Newer headset Pimax 8k X etc. owners that have the rubberized coating, what are you using to attach your sensor mount? My APBs went on ok reusing the same tape included. I got some 3M VHB double sided tape but it was the clear stuff, not the dark gray MilesD includes and it isn't holding.
  10. I spent a couple hours with the 8k X tonight and the canted lens feeling was no longer noticable. Otherwise, I'm really enjoying it, still playing around with the settings to find the best options. I agree, the upscaling setting seems not worth it at all for the lack of clarity and for very little performance gain. I'm not a person that needs a high refresh rate either. I'm also messing with the SteamVR resolution levels to find the sweet spot. But honestly that 100% setting seems worth it right now, but I haven't flown busy missions or attempted hardly any Supercarrier traps.
  11. Here's my first if impressions on the 8K X. I received it yesterday and only got about 20 minutes in it. I now see what you guys are saying about the cant. It is a weird feeling at first. But my IPD is 63.5mm or so and with the limited time I had last night to try it, both eyes seemed clear. And how clear! First impression was how "glassy" everything looked and that it was more like what I'm used to with a monitor. I was able to see the ball much more clearly on approach and maybe able to turn my custom dot labels off now! After I turned off my 4x MSAA that isn't as needed now, I have just
  12. It should scale through the troposphere if I recall correctly, for a good rule of thumb to make you in the ball park of a simulated DCS dewpoint. And I did make a math error in the original post I'm going to go back and fix. I think your formula is correct though. For some stupid reason, in the U.S. the FAA tends to give us these problems in Fahrenheit on tests despite the aviation weather being in Celsius. For that you divide the spread by 4.4 then to get thousands of feet so the numbers you are shooting me seem a little foreign but correct. I know a typical 10k base is a 44 degree F spread.
  13. Great work again Bailey! It adds one of those missing things that a robust ATC system should have. Just a observation, there is a mathematical way you could get the approximate "real" dewpoint instead of just the 60% humidity constant. I have to dust off some weather theory here with numbers so hopefully I can explain this well enough. The standard lapse rates (amount of degrees lost as altitude increases) of temperature and dewpoint is different. Also at temp/dewpoint matching (100% humidity) is where you would normally get a cloud layer of the other conditions for cloud formation are m
  14. Actually, SteamVR does that on most VR headsets, for instance the 100% setting for my Pimax 5k+ is well over the native at a resolution 3412x2104 for wide FOV. But this SteamVR 100%>native resolution is extra noticeable in the G2 because they apparently set it extra high but is also supposed to go back to native in a future update. I would bet though that what RogueSqdn is seeing in those areas is where DCS is switching from GPU bound to CPU bound. I get similar experiences with my 3090 and my i7-9700kf@5.0ghz, especially close to a Supercarrier or on a lots of aircraft and ground unit
  15. Yes, they are HTC Vive base stations (a.k.a. lighthouses), either 1.0 or 2.0 work with Pimax and the Vive VR stuff obviously, like the knuckles. I know Pimax is working on a "sword" controller, but I don't think they are planning to make their own base stations. I always forget the difference between Valve and Vive these days because at first it was a complete collaboration and they still work together despite different headsets now. I don't know if Valve manufactures base stations too to the same specs or they are all the same source of HTC Vive. You can use more than two 2.0 stations
×
×
  • Create New...