Jump to content

zildac

Members
 View Profile  See their activity

  • Posts

    1858

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by zildac

  1. zildac
    I'm out and about. Honestly, start the mission fly up toward clouds.... Done
  2. zildac
    Hi, Have you tried Caucasus, Hornet ready on the ramp? It does appear to be related to weather setup and this mission definitely produces the issue or me. As for settings, they are exactly the same as pre patch. DL AA, but it never created artefacts before the patch.
  3. zildac
    Thanks, this will do as a workaround for the time being!
  4. zildac
    Ideally you should have it as a mod, and yes re-run after each update in case base textures have been added/changed.
  5. zildac
    What preset and time of day are you using in that video, looks fantastic?
  6. zildac
    Yes and Yes
  7. zildac
    Yeah... hopefully ED can find a solution. Would suck having to remove a weapon. Definitely!
  8. zildac
    @BIGNEWY Are the team aware of the issue?
  9. zildac
    Ah OK, understood. Thought I was going mad. Have you raised it with ED so they can sort their GUI out? It's a little frustrating, can do a saved loadout with HOBOs for example and then edit, but it's less than ideal.
  10. zildac
    Odd one, in VR (using a Varjo Aero) and when I bring up the list of "bombs" for a given pylon the list is pretty large and ends up off the bottom of the headset FOV. I don't recall this being an issue the last time I flew the F4, a couple of patches ago. Looks like an ED GUI issue, but wondered if anyone else has seen the same?
  11. zildac
    Hi, Using a Varjo aero here and have just noticed that in the F4 (which has a ton of options in terrms of bombs) if I select a pylon for bombs the resultant list is so large it disappears off the bottom of the headset display and there's no way to scroll down to say the GBU8? I'm sure this wasn't an issue a couple of patches ago when I last flew the F4.
  12. zildac
    I'm sure it will get fixed, just a bit odd it wasn't picked up in testing. It's not game breaking tbh. @BIGNEWY appreciate you're likely fielding a bunch of issues at present, but would be great to know when you’ve managed to reproduce and report to the team?
  13. zildac
    I thought this was fixed in the latest release. The changelog seems to suggest so, I’ve not tried it personally.
  14. zildac
    Bit of an overreaction..unless you’re being sarcastic?
  15. zildac
    Not had a chance to test, but I wonder if cloud quality settings have any bearing? I'm currently running “HIGH”
  16. zildac
    Try the Hornet, Caucasus ready on the ramp, fly toward cloud and it'll be obvious. I'm using DLAA, not sure if that has any relevance.
  17. zildac
    There appears to be some issues even without this great mod:
  18. zildac
    Yup, I am seeing exactly the same. I assumed it was mods so disabled all of them. Was also using Matts Varjo Foveated so also disabled that, issue still persists. I was testing on Caucasus ready on the ramp in the Hornet. This seems to be a base game issue. Related to fog and lighting changes possibly? This is in VR for me, have not tried in 2D. @BIGNEWY
  19. zildac
    Well, TBH my RAM is rated at 6600, but it is still an overclock. Re my Mobo (ASUS Z690 Hero) it was just a case of using the “XMP Tweaked” profiled and selecting 6600.
  20. zildac
    Other than the standard rated OC @6600, no. And on Intel 14th Gen and Z690 it is only 99% stable. DCS runs fine, but some other apps which are more parallelised cause hangs occasionally, so I may actually drop it down to 6000.
  21. zildac
    Turbo mode works fine in VFR too (obviously OXRTK needs to be disabled)
  22. zildac
    Gotcha, OK yeah I do recall that was a limitation. Never tried it, so don't know if it is now possible. The only reason I like QVFR was I could still run OXRTK and have a clock, But the eye tracking issues meant I just went back to VFR and live without a clock.
  23. zildac
    Ah OK. So why don't you just use Varjo Foveated from Matt instead? You have an Aero.
  24. zildac
    Thanks for posting, interesting results. One thing though, you mention you are using an Aero and QVFR (not VFR) there's been an ongoing issue with the Aero and QVFR where eye tracking gets disabled, and the log contains entries to that effect. Are you not seeing this issue, what version of Varjo Base are you running with the Aero 3.x or 4.x?
  25. zildac
    Nice!!! Looking forward to trying it!
×
×
  • Create New...