Jump to content

diamond26

Members
  • Posts

    333
  • Joined

  • Last visited

Everything posted by diamond26

  1. Thanks for the update. The Tanker topic is a matter of reality vs game play. If people want an easier play then I understand the slight disortion of reality. At least we managed to get refuelled without being shot down!
  2. @Jenson last night we flew the remastered M10 (thanks again for keeping this campaign updated). We noticed an issue with AI DCA. They followed us in our return till the carrier and actually we had to enable one of them as he got too close. Carrier group then took care of them while we were performing our CASE III recovery. Note: Texaco 1-1 seems to be too close to enemy forces ( there was a point that the tanker was 45 nm from the enemy)
  3. The guidance was only to block Oculus PC app to go to V63. For the headset, apart from what you suggest (which I haven't tried) the only option is to keep wifi off In addition the headest updates if you have SW updates off are enforced after some time. For example v62 in my case has a mandatory enforcement by 28/3. So I guess you are safe in headset with SW updates set to OFF even with wifi on for some period of time which will be mentioned by META.
  4. I only created a bak.staging (actually renamed an existing folder) and a bak.tmp folders and it worked as suggested by @Lange_666
  5. I have also mentioned the issue to META in their support page (not that it matters too much as they use AI for response! )
  6. I'm coming back on this topic of low VR performance. F1 on a low spec machine (like my laptop with an RTX2060 6GB) is definetely not playable in VR compared to other models. Using Link (Quest Pro) and the same settings the difference between F-15E (heavy also in VR) and F1 is 15-20 fps which brings the F1 down to 9-10 FPS Using Virtual Desktop F1 is a bit better with 20-30 FPS. This means that F1 is making more aggressive use of VRAM. And to give you a more startling comparison, F-18 free flight in the same map is averaging 50-60FPS!
  7. Same problem as OP witnessed today. Map is functional but getting the message to install it.
  8. Me too, Oculus Link provides better quality and stability and ASW is miles better that SSW from VD. VD seems to help when I use my laptop as the VRAM is limited and the VD's VRAM use is better compared to Link. That's a requirement for eye tracking to work for VD and Qpro. I imagine won't do anything for Q3
  9. According to Mbucchia's guidance the QuadViews can disabled through STEAMVR settings https://github.com/mbucchia/Quad-Views-Foveated/wiki#temporarily-disabling
  10. 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.
  11. @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.
  12. 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)
  13. 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.
  14. 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.
  15. 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
  16. Problem solved by deleting the DCS.openbeta_server folder in Saved Games! Thanks to Yoyo from Discord
  17. 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
  18. diamond26

    DLSS "update"

    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)
  19. 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.
  20. 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
  21. 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
×
×
  • Create New...