Jump to content

Panny

ED Closed Beta Testers Team
  • Posts

    333
  • Joined

  • Last visited

3 Followers

About Panny

  • Birthday September 17

Personal Information

  • Flight Simulators
    DCS
  • Location
    United Kingdom
  • Interests
    Aviation, getting more people to join our community!
  • Website
    https://dcafoc.wixsite.com/home

Recent Profile Visitors

2716 profile views
  1. I think you need to be much more specific than anecdotal evidence such as just 'Masada , University of Haifa , unifil helipad near naqoura'. The title 'add the lack of details' is useful to no one
  2. Truthfully, some of the largest gains I got is from dynamic foveated rendering. If you're using a Pimax Crystal Light you're missing out on some pretty massive performance gains and have to settle for lower FPS due to the lack of DFR to be honest. It's what I found oxymoronic about the headset - yes it's much cheaper to get but to run it properly you need an extremely expensive GPU and for the likes of DCS it still struggles even with the best hardware
  3. Hi Thorns - what other information are you looking for specifically?
  4. Yes you are right - I completely forgot about that. Then that would likely suggest with my adjusted values having render quality set to high would have a higher total render resolution. I think, in context of @Peedee's correction what you suggest could well be the case. For what it's worth I have generally tried to not get too engrossed with VR optimisation and maybe double check it once a year so I generally try to stay away getting too bogged down in FPS overlays and frametimes. I will check to see what they are presently as and when I have the time. It's a shame that the DCS fps overlay isn't the most useful. Either way, the tinkering has made for a much more enjoyable experience in which the visual experience is much improved and significantly smoother. Sounds dumb on my end to have missed this, but still an interesting note Yes you are right - I completely forgot about that. Then that would likely suggest with my adjusted values having render quality set to high would have a higher total render resolution. I think, in context of @Peedee's correction what you suggest could well be the case. For what it's worth I have generally tried to not get too engrossed with VR optimisation and maybe double check it once a year so I generally try to stay away getting too bogged down in FPS overlays and frametimes. I will check to see what they are presently as and when I have the time. It's a shame that the DCS fps overlay isn't the most useful. Either way, the tinkering has made for a much more enjoyable experience in which the visual experience is much improved and significantly smoother. Sounds dumb on my end to have missed this, but still an interesting note. My performance in dogfighting has definitely vastly improved. Because of the near constant juddering it was much harder to track the aspect of the hostile and react accordingly. I did notice quite abruptly that against the AI it suddenly became trivial again
  5. OK so when opening Pimax Play, device settings, and then games, you have the option to set render quality. Basically this is how many pixels the GPU has to render. So with OG Crystal that's 2880x2880 for each eye. So with render quality at high - the headset is asking for a pixel for each, meaning 16,128,000 need to be rendered. However, by using Tallymouse's Quadviews Companion tool we can adjust that. So for the foveated area I have 170% (so let's say that covers 1/3 of what has to be rendered by the GPU), that section alone is now asking for 8,225,280. However, I have set the peripheral resolution to 15%, which covers the remaining 2/3 of my view, I need to render 1,596,672 there, making a total count of 9,821,952 that have to be rendered in my headset. null Before when I had render quality set to medium, the headset asks for fewer pixels to be rendered than what the headset actually has, at 75% - so by default it is asking 12,096,000. I used to have foveate resolution at 200%, and peripheral at 30% to make up for this. Foveated asked for 7,983,360, while peripheral resulted in 2,431,296, for a grand total of 10,414,656. So ironically with my new settings my pixel count is slightly lower, but because the base resolution the headset is asking for is the same, it feels clearer. Why my stutters largely disappeared changing from medium to high - I have no idea. The GPU workload according to MSI afterburner is largely the same. null
  6. Very strangely setting Pimax quality to high and then adjusting pixel count to a similar average value as before(when in medium) made the game vastly smoother. Very strange
  7. Went from DK2 to Rift S to Reverb G2 to Pimax 8KX and now to Crystal. Subjectively the first two headsets weren't usable for DCS. Reverb G2 was, 8KX was like the G2 but with a much bigger FOV and vastly better sweetspot. With those headsets I could read the gauges I needed to read but ultimately that's because I knew what it roughly meant. I couldn't read small text on the right and left side consoles. Pimax Crystal put all of that two bed and I can clearly read anything I directly look at, regardless of how small the text is. There's no interpretation of a smudge on my part. Out of all times of upgrading headset this one felt the most profound to me where I could immediately tell how much better it was. With previous headsets you only came to appreciate it when you put your old headset back on and realised how bad you had it. Don't get me wrong I'm sure the Super is much better. But I'm happy with the crystal as I can clearly see what I need to see and what I really appreciated when they launched the headset was that I could trial it before buying. I know I have a 14 day return window with the Super but it's still a hassle versus walking in to a VR shop and trying first for free. So I'm happy with the Crystal and not willing to push £1k+ until the next headset comes FWIW, as I understand this is a subjective exercise, my eyesight is better than 20/20 so there's no factor of my eyes being the 'problem'
  8. And this is a nice simple guide alongside! https://flyandwire.com/2022/04/12/the-basics-the-detailed-data-display-in-pulse-and-pulse-doppler-search/
  9. I'm an OG Crystal user, and I'm so pleased with the quality that I haven't felt it justified enough to go for the Super. Still holding out for when we get 8KX FOV with at least Crystal PPD and then I'll jump
  10. The select stations is very useful. In an air to air sortie I'll typically have stations 2 & 7 selected through Jester. That means if I'm going to have to do any heavy manoeuvring I can raise the ACM guard, press ACM jettision and tanks are off straight away. Very useful having it prepped instead of telling Jester just before a merge.
  11. You're getting two things confused - In the mission maker you can force settings that override the client's dot spotting. This is much the same as labels. So if you play SP missions with labels on but then go onto a server that is running a mission that disables it, you don't get the labels. This is the same with dot spotting. So what you're describing in MP servers is that there are no dots being visible because it's not being rendered. Just because your friend is using a Reverb G2 doesn't mean he's getting a dot. He isn't. It's just because the pixel density is much lower in the Reverb G2 meaning the target is being rendered from a further distance (even if it looks like a dot). Try a different MP server which is not enforcing dot spotting to be off and you'll find it should be the same as singleplayer
  12. Reverb G2 in general has incredibly permissive spotting of aircraft, even if they disable spotting dots. High res headsets don't have the same gameplay benefit and consequently are more reliant on an artificial spotting dot being superimposed over the aircraft itself.
  13. Hi @rosteven1, Am away from my desktop so can't share settings, but also have same headset and very similar specs to you. Multiplayer server hosts can force spotting dots to be off for clients, so it's best to do your testing in singeplayer first and I suspect this is the issue you're facting. In my experience your anti-aliasing affects spotting dots the most. MSAA is the best by far, while others such as DLAA or TAA can smudge them and even make them seem invisible. Other settings don't seem to factor as much. Hope that helps.
  14. Mirage III would be an excellent addition. Considering the Arab-Israeli conflict we are rapidly reaching the point in which all modules are featured. Syria, Sinai, F-4 Phantom, MiG-19, MiG-21, soonish MiG-17. Having the Mirage III would be the real icing on the cake to fill out that theatre
  15. Probably something to do with how Jester works than anything else
×
×
  • Create New...