Jump to content

Wali763

Members
  • Posts

    398
  • Joined

  • Last visited

Everything posted by Wali763

  1. Ok, you might be right to some degree regarding Pico; I did not check this out, since it would be as I said a sidestep, which makes no sense. The other aspect ("the US [ironically] raising concerns") would be a political discussion, that has no place here.
  2. I consider this question to be rethoric. But if you have no problem with Meta, its ok for me. They are offering great products at a even better price.
  3. My G2 is having audiopriblems, most probably to a loose connection. Hopefully the ordered new cable will fix this. Anyway its sad, that people like me, who do not want to use Meta have so limited options. Pico4 would be more or less a sidestep and Im not sure if I can run Dirtrally and AssettoCorsa (that I play much more often than DCS) on OpenXR. In retrospective I should have gotten an Aero at the reduced price. But the tech is still developing rapidly and Im positive my G2 will last until they stop supporting WMR.
  4. At first I saw a about 10% increase in frametimes, but now I think its more than that. No sure yet how much. Anyway, the bigger impact for me is, that the CPU-related occasional stutters (frametimespikes) have gone, which gives me a far better experience. Only yesterday, I was a bit mad at ED, since throwing costly harware at DCS still offered a only mediocre visual experience and today they improve quite a bit!
  5. Doing this on my phone, I was unable to change that yesterday. Now its updated somehow.
  6. Did not read through the thread, only parts. Sry. I dont like DLSS, makes gauges rather hard to read. Also ghosting. DLAA removes all the shimmering but makes the image blurry. Still running lower settings with 2xMSAA to achieve 90fps. No DLxx for me. For me the best compromise.
  7. I got a question: Many have stated, that the Aero´s sweetspot is much higher than on the G2. But when in my G2 I look to the edges of the image, I can see the overlap-edges of the lenses. I very much notice the edge between the part, where only one screens is visible vs the part, where both screens overlap. So it does - at least for me - not matter much, that outer parts of the image are blurrier, since those lens-edges are rather irritating to me and I like to stay focused on the center. Is this the same on the Aero? Or does it have better binocular overlap without those edges visible to a lesser degree?
  8. Sorry for replying so late. Did not see your post earlier. I had this problem on every map I tried. Was not related to PG only. Since I removed the OTK, the problem is gone. Still have to say, that this might only be a few hours, since I dont have too much time for DCS lately.
  9. Hi. I had occasional flickers/flashing with 2.9 until I disabled the Toolkit. Also seems my frametimes went down a bit too. I had only Foved Rendering and the fps-counter on. At first I tried to change other settings like clouds, shadows, etc and also went to general low settings, but nothing changed; still had the occasional white flashes. Only disabling the Toolkit did help. And the problem has not come back yet. Will keep it disabled.
  10. I did not use MSAA up to now, only 75% SS in OpenXR with my G2. Im kind of ok with the shimmering/aliasing I get. DLSS, DLAA and TAA all give me a blurry mess, but all greatly reduce shimmering.. DLAA also reduces perf noticably (~1ms higher frametime). 2x MSAA retains most the the non-AA clarity, but reduces shimmering to a lesser degree than the three above alternatives. Perf impact of 2x MSAA is way too high, so I did not bother testing 4x. As the original poster, for now Im staying with my "old" settings. Will do a retest at a later time.
  11. Hi. Just read the OP and not the rest. forest or trees? Your probably right overall. Still in my case OpenXR is more important than MT, since OpenXR finally made VR usuable for me. Only that made me finally switch over to VR. And I never had real problems with CPU since mine were always fast enough for my flying. Currently have a 5800x3d which works fine. Sill MT gave me some extra headroom to increase some texture settings for a better overall experience.
  12. If you go over to the amd.com support-forum, there are several threads about VR-performance of the 7000-GPUs, this being the longest I think: 7900xtx Low Performance in SteamVR and VR in gene... - AMD Community 7000card dpmt seem to be that good in VR. Some report, that their 7900XRX is as good as 6800XT in VR. I have a 6950XT and its fine. Wanted at first to get a 7900XTX but did not because of the reports of its poor VR-performance. Right now Im very happy with my decision. If my card were 20% faster though, that would be great. I would not bet on AMD getting their issues with the 7000-cards sorted. Its already been 5 months since its release.
  13. Hi. Thx for your input. Unfortunately this did not help and I got a "HMD-crash" again. I did some more testing and Im pretty sure now, that my problem is related to doing changes in the OpenXRTools for WMR, so changing the SS-resolution or checking the frametiming-overlay. Interestingly after unchecking this option, I do not encouter this probelm. Or at least did in my recent test. Only when checking it, which quite relyably can reproduce my HMD going dark (just showing black, not turning the displays off completely).
  14. Hi. Just need to rant some, since I do not understand this. Probably its just my lack of understanding how PC-games work..... Between water quality on low (which I usually have to get max fps) and quality on high, there is a huge perf difference. Its maybe like 15 or 20%, going (in a caucasus mission I tested this) from ~9ms GPUframtime to something like 11 or 12ms. Well thats ok, since you get something for the extra-Perf. But the thing is, this fps-drop is also over land, where there is no water around. I do understand, that water is rendered below the ground textures. But to me this seems like a big waste of GPU-power. Isnt there a way to tell DCS, to not render water, if there is no water visible? I really could use that extra GPU-performance....
  15. Hi. Im pretty happy with MT right now. Since I have a fast CPU (5800x3d) CPU wasnt a problem before, but with MT I get about 10% lower GPU-frametimes, which helps quite a bit. But Ive had this following problem from day one with MT. Sometimes - most often when I change settings - when I start up a mission my headset goes black. To be excat, Im usually jumping into the cockpit, and things start to load for a few secs (like textures etc; didnt have this before MT, when this loading took not time at all) and only when everything seems to have loaded, the headset goes black and does not come back on too. But on the mirror on the monitor all seems ok and I can exit the mission and close DCS. But the headset stays black until I restart DCS. The MixedRealtiyPortal in Windows does work after the shutdown of DCS and does not need to be restarted. About the changing of settings. Today this happened to me, when I turned on the frametimeoverlay in OpenXRDevTools. Usually after some starts this "settles" and no more crashes appear until I change some settings again. options.lua dcs.log
  16. Ok, thx. I was for some time thinking of upgrading to a 4090 or at least a 4080. But since I am already quite used to my lowish settings but 90fps in most situations I fly in on my AMD-GPU, Im not sure, if its worth paying so much for a bit more eyecandy. Anyway, Im not in a rush and Im pretty sure, prices will come down much more. At least for the 4080.
  17. Maybe a stupid question: Are many with a G2 (or other 90-Hz-HMDs) running DCS in 90Hz? Especially with MT and considering 4090-owners for sure have fast CPUs, this should be easily doable. Yet when browsing this thread it seems, many people even with 4090s are below 90fps. Do they prefer to use higher settings instead of fluid 90fps?
  18. I have the same once in a while; maybe 1 out for 4 times. Then I have to restart DCS and usually its ok.
  19. I had it recently, that when there was a call from "Overlord", the correct message was written at the top, but the vocals were those of "request bogey dope"
  20. Hi. I saw you have a 6900XT. The flickering could be a driver-thing. At least I think so. Every driver after 22.5 causes flicker for me having a 6950XT. Maybe give 22.5 a try.
  21. Hi. I have Ryzenmaster. But since I cant oc my 5800x3D, I dont use it. Chipset drivers were updated 1 month ago. Mobo Bios is a bit dated, 03/22. Did not update, since there were no desireable new things to potentially upset a working system. No gamemode, no gamebar. See no use in those. As I wrote above MT brings very little change for me. Maybe 1ms GPU frametime. In CPU-limited scenarios MT helps a bit, but stutters still occur.
  22. I have the strange situation, that in ST (non-MT) in normal (lighter) missions my cpu-frametimes are lower than in MT. At the same time Fps-tracker in MT constantly says "CPU bound rendering thread", whereas in ST there is no message. I get the frametimes from Frame-Timing-Overlay in the OpenXRTools (not toolkit), but the fps-counter in DCS seems to support those numbers. It seems, that CPU-frametimes in MT try to stay around 10,5ms. So, where in ST I get eg 8ms CPU-frametimes in MT I get 10-10,5ms. Thats actually in contrast to what MT should do, meaning lowering CPU-frametimes. At the same time the GPU-frametimes drop a bit by ~1ms, which gives some more headroom for higher video-settings. In larger missions MT is working to some degree. Its lowering the CPU-frametimes in situations where in ST I got 17ms CPU-frametime to 11-12ms in MT. But since (in my case im running my G2 without reprojection to get to full 90fps) this is too high for real 90fps, I get stutters. If those were arount 10ms or lower all would be good. Even those 10,5ms are pretty close to the needed 11,1ms for 90fps, overhead in lighter missions is not that big so I get an almost smooth 90fps ride in lighter missions. But in heavier missions, this overhead might to get too big, so it causes fps to often drop below 90fps which gives visible stutter and spikes in the DCS-framecounter.
  23. Me too. CPU bound (rendering thread). In light missions CPU-frametime (according to frame-timing-overlay in OpenXRTools for WMR) in MT is higher than without MT. Seems wrong to me. 5800X3D, RX6950XT, 32GB, G2, Win10
  24. Just a brief feedback about my findings about MT. This morning I posted, that I dont see any difference MT on or off. I now found some differences for me, but Im not sure, if MT is making it better for me. My settings are directed at getting full 90fps in my G2 since AMD-GPUs and reprojection dont work well together IMO. So I only use 45% OpenXR resolution and most things set to low (except textures and visib range). Its a tradeoff between eyecandy (eg little shimmering) and smoothness. I prefer second. I have a 5800X3D and a RX6950XT. So I guess Im mostly GPU-bound anyway. Usually when frametimes (either CPU or GPU) jump over ~10,5ms fps drop below 90 and I get visible stutter. The difference for me in MT is, that in really CPU-heavy missions CPU-frametimes are better. They are almost the same as in smaller missions and hover around 10ms. Problem is, they often get spikes over 10,5ms, which causes stutter. GPU-frametimes mostly are around 9ms in my tested scenarios and no problem. The problem is, that also in light missions I get those 10ms CPU-frametimes but far lesser spikes to 10,5+ms, whereas in non-MT I have lower CPU-frametimes between around 8ms in comparable situations. So in short it seems that MT in my case seems to level all CPU-frametimes around 10-10,5ms, now matter if a mission is big or light. But since those 10-10,5ms are close to my "stutter-threshold" and those stutters also happen, its not all good for me. On the other side, I do have the feeling, that GPU-frametimes may have dropped by maybe 1ms. I did comparisons back and forth and Im pretty confident saying that. That allowed me to set ground-textures to high again without lowering fps. So my overall finding is, that with my current CPU MT does not add much and differences are rather small. Only in heavy missions, that I usually dont fly anyway. I guess, if current CPU-frametimes would be a bit lower (like 9ms instead of 10ms), so spikes would not let fps drop below 90, Id be very happy with the update. But so my feelings are mixed and Im not sure, if I should go with MT or stay with non-MT.
×
×
  • Create New...