Jump to content

lwalter

Members
  • Posts

    363
  • Joined

  • Last visited

Everything posted by lwalter

  1. As kneeboard bookmarks are not persistent, is there a way to flip the pages as quickly as possible to go back to the last location I was reading before I restarted? I mean without the need to fast click on next page for 100-200 times. At some point I thought that the kneeboard had some kind of scrollbar and that you could use it to do navigate directly to an approximate location, but either I can't find it anymore, either I just dreamt that it existed.
  2. thanks a lot @Flappie and @draconus!
  3. +1 for this requirement
  4. Has anybody ever found a way to workaround this terrible DCS limitation? Flying in VR, I ended up converting Chuck's guides into DCS kneeboards, but without persistent bookmarks, it's a real pain to go the often hundreds of pages they contain.
  5. Good point @Daemoc. I know I have 35% sharpening in OpenXR config. I'll check next weekend if removing this sharpening makes it better. However, I'll probably put it back for the other planes, because else their cockpit texts are not that sharp.
  6. I'm just using the standard Quest 2 AA setting.
  7. I've already seen requests to make persistent: - the size and position (if possible in 3D) of the kneeboard - the bookmarks of the kneeboard but I don't know if these requests have been taken into account. In meantime, and I don't know in which section to post that: is there any way to workaround these limitations with some lua scripting (or other config?), especially for the bookmarks?
  8. any news on that one? I have retried today, May 2024, and FPS drop makes it unplayable.
  9. Using Quest 2 and I have heavy shimmering on the black panels of the cockpit. I have anti-aliasing on and have no such shimmering or very little with any other cockpit, including the very similar dark Mirage 2000 cockpit.
  10. Thanks, I know that Combined Arms is not fully support on VR (which BTW is a pity for a module of a product that itself says it's compatible with VR). Nevertheless, what I'd like to know is whether the selection (lock?) of a target on a SA-8 radar by double-click is not working because I'm doing something wrong or because of a limitation in VR? I didn't see anything in the DCS manual for Combined Arms about using anti-air units with radars.
  11. When in radar view on the SA-8, I would like to select a target by double-clicking it, but it doesn't do anything. I'm in VR. So I don't know if that's the reason it doesn't select the target.
  12. I add new panels on request by users. So if you'd like a CDU, I can work on it. It will come after another request I got about adding a DED to the F-16 ICP. Meanwhile, feel free to use the Android app that @MirabelleBenou suggested if it works for you.
  13. Weird. I suppose you made sure to make the changes I highlighted to the Lua script or that you replaced it with the new version from GitHub, right? (no change needed on the iPad side)
  14. I had this campaign for a while but never managed to get past mission 1. It requires 3 landing in small areas and a hover for the ASW. And if you mess up with one, which always was the case for me, then the mission had to be restarted and it's quite long, because a Huey is not that fast crossing the water from the Argo to Batumi and back. Since then I got better with landings on the Huey and tried again mission 1. It's still very stressful for me to land on this tiny ship area, but this time I made it and for the first time I read: "Mission Accomplished"!!!! Overall nice voice overs and explanations about what you have to do. I can't wait for the next missions.
  15. Was because of a mod. I just disabled all of them, and now I can see again the Tarawa.
  16. I confirm that when I disable my mods (only a few aircraft mods), there's no problem with bombing in the SU 25T.
  17. Ships where you"re supposed to land are not visible, like Tarawa for easy mission. They appear when opening the mission in the mission editor, though.
  18. I tried the same mission replacing the F1 with other planes like M2000, F/A 18 or F 14. I had normal fps. Same with F1 without radar on. As soon as radar is turned on, I lose at least 20 fps, which makes it almost unplayable in VR.
  19. +1 Shimmering very bad for me too (Quest 2). No extra sharpening used.
  20. Today, I was flying and doing some weapon practice with the SU-25T. All weapons worked fine, but using bombs (like FABs) is no longer possible. In the HUD, the CCIP reticle doesn't show on the ground but seems to be mirrored up in the sky. If I manage to put this reticle on the ground with a very steep dive, it turns into a diamond, like for activating post-designate (CCRP-like) and then guidance circle is completely offset to the left. So, neither CCIP or CCRP bombing no longer works for me.
  21. The root cause of the bug related to the UFC line updates after pushing PB10 is still under investigation from my side. However, I found a workaround to fix it. In the iUFCExport.lua script, just comment out these 2 highlighted lines at the bottom of the file (using 2 dashes like I did). I'll post a new version of the lua for those downloading them from GitHub.
  22. I've tried several campaigns in DCS, built-in and paid campaigns. Since the really great paid campaigns I played for the A-10C like The Enemy Within or Operation Piercing Fury, I found most of the other campaigns either too much repetitive, too hard or requiring you to read tons of documents to prepare your mission for hours, until I found Serpent's head campaign. It was number 2 on the store so I decided to look first for #1, which is downloadable for free from the DCS user files. So far, after 3 missions, I enjoy again DCS campaigns. Not overly complex, not overly administrative, but just enough realistic and enough stressful for a weekend F/A-10 "pilot". I bought Serpent's Head 2 campaign right away! Thank you for building these campaigns!
  23. @5ephir0th I'd like to give it a try, but which resolution should be increased by 20%?
  24. After all I read on the forums and saw on YouTube, I was very excited to try the new graphic settings of DCS 2.9, especially DLSS. Note that I use DCS in VR with a Quest 2. In OpenXR, I have no upscaling, only foveated and turbo modes on. I already had some experience with DLSS with the other civilian flight simulator: it helped for the FPS, but because of the blurriness, even with "DLSS quality", was a no-go. It was impossible to read the gauges properly. It shouldn't have been a surprise, but same for DCS, DLSS makes the gauges and other texts blurry in the cockpit. Adding sharpness doesn't help much. The one big improvement for me was DLAA. All shimmering was gone and the clarity was slightly improved, but at the cost of FPS, too much in my case. So, I just gave back on DLSS, DLAA and continued with my older settings, except that there was one good news with DCS 2.9: I could push the sliders quite a lot to the right for the details, clutter, trees, etc settings and without noticeable FPS drop. That was the good news of DCS 2.9 for me. Maybe I didn't leverage DLSS/DLAA settings properly. If anybody has alternative suggestions regarding these settings, please feel free to advise.
  25. Yes, same here. It had nothing to do with "DCS/Steam bindings". It was "just" Steam server problems yesterday. All is running fine again today.
×
×
  • Create New...