Jump to content

diamond26

Members
 View Profile  See their activity

  • Posts

    399

  • Joined

  • Last visited

 Content Type 

Everything posted by diamond26

  1. diamond26
    According to Mbucchia's guidance the QuadViews can disabled through STEAMVR settings https://github.com/mbucchia/Quad-Views-Foveated/wiki#temporarily-disabling
  2. diamond26
    In M06 everything worked as designed. ILS was present from start to finish (also in the yellow kneeboard page unlike the previous times) . And indeed we were talking in all three missions to CVN-71. Not sure where the problem was.
  3. diamond26
    @Jenson in the last two missions that had Case III recovery (M03 and M04) we didn't have ILS available. When you join the mission you can see in the kneeboard for a moment the ILS 11 but then it dissapears. Is there something I can do to make sure ILS is working or it's part of the trigger issue? We are planning M06 tonight which is also CASE III recovery.
  4. diamond26
    Yes we were on CH 11, but nothing seems to work for all 4 of us. I noticed that the usual yellow kneeboard page didn't have ILS noted. we had the same question regarding triggers but it seems that the system sorts itself out after passing a trigger or two. For example both in M02 and M03 while on carrier we were receiving information not relevant to our stage but for M02 as soon as we were out of 10nm (the trigger for AI launch) and after Rock in M03 things became normal and we had all he info that usually provided in the different stages like the tasking or the shot down of Colt 1-2 etc. In M03 we were not given Other options until return to WP5, 6 for enabling tanker. (I don't know if you had more earlier)
  5. diamond26
    Hi @Jenson we are enjoying your missions and we plan to complete the full campaign. Tonight we flew M03 which was really good fun. One comment in the remastered version is that despite ILS was mentioned in the briefing, that wasn’t available in the mission which made our CASE III recovery challenging.
  6. diamond26
    Hi @Jenson thanks for this nice work. I have a small comment regarding the remastered Mission 02. We flew it in my Squadron with 4 guys flying the Hawk 1 and we let Hawk 2 on AI. We received the updated F10 for the AI and I ordered them to launch TALDS. We got the response in the menu about launching phantom planes but the AI fired HARMs instead. Additional tasking worked nicely.
  7. diamond26
    I'm using as a backup a laptop with RTX 2060 6Gb and I was able to enjoy Q2 with some limitations. First you have to reduce Textures and Terrain textures. MSAA 2x is taxing on old systems but if you can't use DLAA then you have to bear the cost. You can also try the OpenXR toolkit options for upscaling (NIS, FSR) to reduce the total pixel load. You can also try reducing FoV setting in ODT or OTT if you use that. A figure of 0.75 will help a lot without sacrificing too much of actual view. In any case don't expect high FPS when you aim for clarity. The max I got with the laptop is 50-55 FPS in multiplayer using Quad Views and Quest Pro. Normal figures are around 30-35 FPS
  8. diamond26
    Problem solved by deleting the DCS.openbeta_server folder in Saved Games! Thanks to Yoyo from Discord
  9. diamond26
    Since the last update I cannot see through GUI the dedicated server. Something is wrong with port 8088 or something else. I have tried full repair, checking port forwardings, firewall settings (although I had no issues in the past) to no avail. I've seen the same issue was mentioned in the forums back in 2019 but no solution was given. Any ideas? dcs.log
  10. diamond26
    I can confirm the same. Coming from my laptop back to my PC I noticed a difference in the level of gosting ( max 50 fps on laptop, steady 72 on PC)
  11. diamond26
    Completely agree for Globular kit
  12. diamond26
    Here
  13. diamond26
    I don’t know what ED has done under the hood with the last patch but I was able to run on my backup laptop a mission with frames from 35 to 55 in SA and use of carrier. Previously my frames on carrier were 5-8 and max frames at high altitude were 40-45. The mission uses a lot of static units on carrier and in target area.
  14. diamond26
    I’m more fan of Link cable as it seems to provide better clarity for the same or better FPS. But it also depends on your rig. With my laptop I have cases (Mirage F1) where VD rules due to better VRAM management. QPro can work fine with a good quality USB-C cable
  15. diamond26
    QVFR implementation in VD must be different to the one through Link as the results shown in the QVFR log differ a lot in terms of Quad Views pixel count. I tried close resolutions in Link and VD, same settings in the config file and the relatively close initial stereo pixel count. It seems that VD's implementation reduces a lot more the Quad Views Pixel count which in result provides more FPS but less clarity. Still using the laptop the only way to fly Mirage F1 is with VD as the FPS through Link are below 10
  16. diamond26
    I have mixed feelings about VD. I use it with Wi-Fi 6 (2400 mbps connection) and while it helps when I use it with my gaming laptop ( less use of VRAM), I still can’t understand its resolution output. I use it with VDXR at Medium with H264+ auto bitrate and while on paper the resolution is higher than the one I use with Link the output is not as crisp as in Link. In both case QVFR is enabled. Turbo is ON by default in both cases only in QVFR settings.
  17. diamond26
    No I’m on the latest version and haven’t seen that.
  18. diamond26
  19. diamond26
    In my case is a combination of module and settings. With F-15E I always get a VRAM issue which can be resolved with switching to F-10, Alt-Tab and back. No issues with other modules (with Oculus Link) And now that I'm using the laptop, the F-15 is unplayable no matter the settings or tricks. Other modules are above 36 FPS (no ASW) with my laptop and moderate DCS settings. Only case I get it working is with Virtual Desktop
  20. diamond26
    Don’t forget that QVFR already uses CAS sharpening I just noticed you have a non eye tracking headset (G2), so keep in mind that in your case the foveated area is fixed. You have to move your head to the area you want the focus But this thread is not about sorting out QVFR usage. So let’s keep it for what the OP asked for.
  21. diamond26
    You are actually defeating the purpose of QV with these settings. The idea is to have small number in the peripheral (less than 1) and higher number in the focus (greater than 1) so you can actually see the benefit of sharp image where your eyes are looking while performance is better because of the lower resolution in the periphery.
  22. diamond26
    You can take the example he provided in a text editor (notepad++), save it as settings.cfg and put it into the folder Quad Views you will create under Users/“your name”/ Appdata/local. I’m not in my PC to give you a screenshot but somebody else can help
  23. diamond26
    What exactly you mean? The custom cfg is not actually needed for QVFR to work. It's only needed if you want to change the default values. For the custom file Mbucchia has provided detailed explanation in advanced configuration part of his github.
  24. diamond26
    Quad Views is a really important improvement for VR users either with eye tracking capable headset of in fixed mode for non eye-tracking capable headsets. It will be great to have it integrated in DCS .
  25. diamond26
    @LOW_Hitman my experience so far with DLSS is that it works relatively well in combination with Quad Views in Quality mode. Anything more is sacrificing (as mentioned above) quality over performance. It has its artifacts like trailing lights from other planes or not quite straight line of radar sweep in F-18 but seem smoother to no upscaling at all. Using DLSS, clarity in my case is a tad lower compared to using only DLAA. But I guess that's the benefit of using Quad Views with high multiplier in focus resolution.
×
×
  • Create New...