Jump to content

Hippo

Members
  • Posts

    1061
  • Joined

  • Last visited

Posts posted by Hippo

  1. I posted the following as a new post, without realising this post already existed so reposting my own doubts and query here.

     

    On paper, the Super with its panels, lenses, eye tracking and audio seems like the ideal headset for Sim VR.  I would probably have ordered one were it not for Pimax's poor historical QC record, and the ridiculous order wait time.  My other concern is performance.  Many YT videos are out stating that the CS can run very well at 72 fps if tweaked e.g.  

    I am currently running my QP, with QV DFR, and am happy that I can finally hold 72 fps at what I consider to be high graphical settings in quite intensive situations (flying low over cities).   Forgive me for being sceptical, but I don't believe that setting a 5% peripheral resolution (as stated @ 10:28 in the video) can possibly provide an acceptable visual experience.  If my numbers are correct, at the Pimax quality setting (5100 x 4312 per eye), this results in a resolution per eye of 255 x 216 (equiv to running 5% over the entire panel).  I am running my Quest Pro at 2704 x 2752 per eye and if I use less that 40% (equivalent 1082 x 1100), the shimmering in the peripheral area becomes too distracting.  Even at the said 40% the shimmering from the F-18's engine gauge in the PA, which seems impossible to remove, irks me.

    I am also very happy with not having to use a face gasket with the QP, and am quite reluctant to go back to the discomfort of using one.

    So, has anyone out there gone from Quest Pro -> Crystal Super?  What's been your experience?  Can you run most scenerios at the Pimax quality setting without having to drop to reprojection?  No regrets?

    • Like 1
    • Thanks 1
  2. 41 minutes ago, draconus said:

    What's your mission then? What exactly you want to achieve apart from annoying all the others who do have a problem?

    My "mission" would be to try and help to identify what might be causing the issue.  My secondary objective would be to inform whoever is looking into it that it isn't happening to everyone.  I am certainly not engaged in a campaign to annoy anyone.

    Over and out.

  3. On 2/21/2025 at 3:38 PM, Rolln said:

    I'll post some screenshots this evening.

    Thanks.  I don't doubt it's happening to you and to others, but it's certainly not happening to me.  Perhaps you could post your DCS settings and I can try them on my system (although I won't be able to for at least two weeks, as I'm away)?

  4. 2 hours ago, Simonster83 said:

    Is there any benefit in upgrading to DLSS4 if I'm using DLAA? Headset Varjo Aero with 1.4 multiplier in focus region and everything looks really sharp as it is.

    I can't say for sure as I haven't tried it, but a quick AI-assisted search gives me:

     

    Quote

    Yes, DLAA under DLSS 4 is considered to be different from DLAA under DLSS 3 because DLSS 4 utilizes a new "transformer" AI model which significantly improves the image quality of DLAA, offering better temporal stability, less ghosting, and higher detail in motion compared to the previous DLSS 3 implementation; essentially providing a more refined anti-aliasing experience with DLSS 4.

    I suspect that the DLAA under DLSS v4 will give a better quality image than DLAA under DLSS v3, but at the cost of a performance hit (and more so on older generation nvidia GPUs).  I did try DLSS under DLSS v4 on my 3080 Ti and I would say that performance was the same or worse than DLAA under DLSS v3, so I didn't even think to try DLSS v4 DLAA.  Also, (any) DLSS + QVFR = too much shimmering in the periphery for me in my Quest Pro; so for now I'm sticking with DLAA, under DLSS v3.

    (And NVIDIA could sure help avoid confusion if they put a bit more thought into the way they name these things).

     

    • Thanks 1
  5. On 2/12/2025 at 1:18 PM, Habu_69 said:

    Tx. Does DLSS-FG (frame generation) provide any benefit to DCS if not using an RTX 50 card?

    the original frame generation (i.e. x2 only) is supported by 40 series (and up I suppose), the new dlss 4 multi frame generation (x2, x3 or x4) is 50 series only.  But neither FG tech is usable in DCS VR (or any VR title) as I understand it (and I assume this is what you mean since this is the VR forum).  I have no idea if it can be made to work in 2D DCS.

     


     

  6. On 2/6/2025 at 2:31 PM, Vakarian said:

    Well, don't mark my post as a solution as this is still not working as I assume it should 🙂 More posts it gets, hopefully more traction it gets with the ED and it gets bumped up in the priority

    Well it was a solution in the sense that you answered my question.  I take your point though and have removed your shiny green badge.

  7. 13 hours ago, Tensorial_Architect said:

    I also tried the obverse, setting the Link slider to 1.5 and then adding on a bit from Pixel Density from within DCS

    My Link slider maxes out at 1.3 (5408 x 2752).   Is that what you meant?  How much is "a bit"?

    I'm sorry if I appear combative, I don't mean to.  I'm just trying to work out what your results would mean for me and the way I like to set things up, and those details matter.  Thank you for your posts, which I believe are genuine, and for your time and patience.

    P.S.

    On 2/5/2025 at 9:46 AM, Tensorial_Architect said:

    or purchasing one for yourself.

    Where, at my local store that also stocks unicorns?  Consider yourself very, very fortunate if you managed to buy a 5090 through normal channels.

  8. 13 hours ago, Tensorial_Architect said:

    If you have the 4090 and were hoping that the 5090 would finally allow enough headroom to run the Somnium, Crystal, or Aero at 90 Hz with all DCS settings maxed, ... you are going to be badly disappointed.

    Alternatively, you can run with reprojection, fly at 30,000 ft over the sea and post YT videos demonstrating how you can a run a Pimax Crystal Super on a 4070 no worries...

    13 hours ago, Tensorial_Architect said:

    I can run the Quest Pro at 72 or 80 Hz with everything in DCS maxed

    Please could you post the QVFR settings you're using for QP, and which AA you're using?

  9. I don't know if it's just me but if I assign some of the newer callsigns, e.g. "squid" or "ragin", to flights, although the name can be seen in the subtitles for radio calls it is not heard, as if the audio file doesn't exist.  E.g.  "squid one" will only be heard as "one", whereas the older callsigns e.g. "enfield one" are played in their entirety.

    • Like 2
  10. 8 minutes ago, Tensorial_Architect said:

    Guys, I teach full time at uni, have a family, and a child. I was fortunate to even get a weekend to myself where my wife and son went off for his fencing regional. I will be lucky to get another weekend like the past during this semester. If the information I listed in the first post of this thread is helpful, ... great. If it is not, ... or you distrust it, ... I suggest either waiting till more DCS VR users acquire 5090s or purchasing one for yourself. You will confirm what I have found.

    I think you might need to reevaluate your priorities.  I would suggest: DCS -> family -> work.

    (😉)

    • Like 3
  11. 8 hours ago, Jimmy8x said:

    attention seeking forum trolling

    Pots, kettles...?  I might more diplomatically suggest that T_A could better support his results by posting his DCS settings and testing methodology.  And I'm rather more concerned about his activities with goats.

    At least he hasn't gone with my own pet peeve of a contextless "that 5090 is awesome, I now get 10 more fps", which is far more common than it should be.

    Selfishly, I might even suggest that he could replicate my test and post graphs of gpu util + frame rate + frame time just for for me.

  12. 17 hours ago, Tensorial_Architect said:

    I do not recommend the RTX 5090 for DCS with VR.

    A bit of a blanket statement there.  I have a 3080Ti, what would you recommend I buy?  4090s are virtually unavailable and extremely expensive.  It'll be two years until the next gen.  5080 or anything below not enough of an increase to be worth bothering with.  I will probably wait around six months and hope for 5090 supply and prices to stabilise.
     

    Quote

     

    "it only beats the 4090 by 21%"

    "it (4090) was in many titles performing at 170% of the rate of the 3090 Ti"

     

    For consistency, shouldn't you say that it beat the 3090 Ti by 70%?  Or that the 5090 performs at 121% the rate of the 4090?  Otherwise you run the risk of appearing to present numbers in a way that supports a particular narrative.

    Thank you for your post and the performance numbers on VR headsets, very informative.  It's nice to finally see 5090 perf numbers for DCS / VR.

     

  13. On 1/28/2025 at 12:51 PM, Foka said:

    Dimm you AoA light, it will be easier to see outside.
    There is a knob for it under the UFC.

    Thank you for your suggestion, and I apologise as I must have failed to explain myself correctly.  The iflols is usable for me in VR and in pancake, but I find the deck lights a bit too dim, however I can use them.  This is entirely different to what others are reporting in this thread (an iflols and deck lights which are far too bright) and I'm puzzled as to why this is.  I am able to trap without issue now in VR or pancake, which I wasn't before the patch, and the last thing I would want is for the brightness to be reduced any further.

    Reducing the brightness of the indexer doesn't make any noticeable difference to my ability to see the iflols or deck lights.

    On 1/29/2025 at 3:46 AM, Micr0 said:

    The irony is that that glow around the AOA indexer is precisely the problem with the ball. Get rid of the glow around these lights. ED is simulating an astigmatism for the pilot.

    I have no problem distinguishing and using the ball in VR from around the ball call.  I get your point, but the glow is trying to replicate a real effect, whether it's overdone is a matter of debate; I suspect that if it were removed there would be just as many complaints.

  14. 8 hours ago, qwksi1 said:

    I recently sold my 4090

     

    8 hours ago, qwksi1 said:

    I do not think I want to buy 5090

    Like you, I sold my 4090 some months ago because of a change in circumstances and I managed to get back a large part of what I paid for it.  I had always intended to go 5090 eventually.  As circumstances changed again I have a stopgap PC based on a 3080Ti.  And boy do I miss the 4090.

    Now, however, I am very likely going to try my luck at getting hold of a 5090 tomorrow, even though the timing isn't ideal.  Why?

    I intend to buy one eventually, so I might as well get it now and make use of it immediately, I don't see prices going down anytime soon.  This may be the only opportunity to grab one for some time.

    It's going to be the most powerful GPU available for at least another two years, and for VR, no matter the headset, you can always use that power.  It'll be the only game in town.

    If I had to choose between the cards you asked about I'd go 5080, but I'd always be regretting not having gone for the 5090.

    8 hours ago, qwksi1 said:

    at 45 fps on multiplayer with no AA

    Having said all that DCS without AA is imho not acceptable, and I can't be doing with reprojection.  No, just no.  😉

     

     

     

  15. And here it is in pancake.  Usable and similar experience to VR.  iflols becomes visible at 1.6, certainly usable at ball call.  Pretty sure that the deck lights have got brighter since the patch, but still very dim - however a trap is perfectly achievable.  I have no idea why I'm not seeing the super bright carrier reported above.

    image.png

    image.png

    image.png

    image.png

    image.png

    CP07.01 Case III Approach DME 10_nofog_tru.miz

  16. 1 hour ago, NAM said:

    This tools enable my 82 yrs father computer with only RTX 2080ti running smoothly ms2020

    Which I presume you set up for him; because, with the greatest of respect, he's surely got better things to do. 😉

    As do I, even though I've still got some way to go before (if) I get to 82!

×
×
  • Create New...