Jump to content

Nate--IRL--

Members
 View Profile  See their activity

  • Posts

    11148

  • Joined

  • Last visited

  • Days Won

    13

 Content Type 

Everything posted by Nate--IRL--

  1. Nate--IRL--
    Wow even from just reading the Docs, it looks like you've put a ton of work into this. You've given me the reason I've been looking to finally learn the Hind. Looking forward to this Nate
  2. Nate--IRL--
    I've just pulled the trigger on a 9070 XT - would be very interested to know how you get on with the testing the newer versions. Nate
  3. Nate--IRL--
    Excellent post - addresses precisely what I'd imagined a QAG to be. This is a clear design / high-level view of what should be the Player / QAG interface and feature set. The Current QAG is built very much from the perspective of attempting piece together something from the existing structures. It is incoherent in terms of what it want to achieve and how the player interacts with it. The Design above flows, it leads the player though intuitive simple options, and gets them to the cockpit quickly. The job of the QAG is to take care of the details. The player might then have the option to use the mission editor/planner should they wish. Overall the goal of the QAG should be a Randomised mission, generated though a simple intuitive interface, and not for the player to manually build the mission in a simplified mission editor. I believe the OPs design, while not perfect, illustrates succinctly what could work, and also the minimum of what a Player would expect of a Game interface. Nate
  4. Nate--IRL--
    Fantastic! I'd almost given up hope for a solution! I note on the thread on reddit that AMD are talking to him too, so it may not just be Nvidia only. Nate
  5. Nate--IRL--
    It needs a single "Randomise" button, so no user input is required. It also needs to be quick. For flyers with limited time, it needs to offer a one click jump to cockpit option, random or not. I would also like to see it populate the world in the mission automatically, but that's for the future I guess. EDIT:- as an aside the UI/UX really needs to be improved. Less of a corporate application feel and more of a Game interface. Nate
  6. Nate--IRL--
    Hah - I only learned of the effects of Procession yesterday, and today I learn about P-Factor now too. Why does it all want me in the ditch on the left of the runway? Nate
  7. Nate--IRL--
    How did you think to look at the sound as being the issue? Nate
  8. Nate--IRL--
    Cool Mission - Flying around Belin at low level is great (ate all my RAM though - 64gb )! Nate
  9. Nate--IRL--
    I'm leaning toward the 9070XT myself, while I could afford something like a 5090, I just couldn't stomach it. The 9070XT is the closest thing to "decent" value this time around. My only concern is support for FSR4 in DCS. I rely heavily on DLAA for 2d and DLSS for VR (2070S) and would hope the FSR4 is supported by DCS so any gain isn't wiped away by having to use MSAA and FSR1 or something like that. I don't know enough about FSR in DCS really. Nate
  10. Nate--IRL--
    I went through a painful few months of something similar, DCS crash ing or a full reboot after 10 to 30 mins in DCS. I was ready to splash out on a new GPU as I'd a feeling that was the issue. By chance I noticed in windows that my RAM voltage was 0.1 or 0.2v above what was set in the BIOS. My Motherboard was slightly over-volting my RAM, compared to what was set by SPD. So I manually set the voltage a little below what it should be, and hey presto, my system has been rock solid for over a year. This is not to say this is your issue, but rather a suggestion to double and triple check everything is as it should be with all parts of the system and BIOS Nate
  11. Nate--IRL--
    Yep I've the Super Carrier. Looks like the link for the download hasn't updated on the User files side yet - will re-check once I see the new version. Nate
  12. Nate--IRL--
    I'm pretty sure I have the latest version (new fog etc). For the mission "Bold Cheetah MIssion 12 - Action Reaction_Cold Start" the Player Carrier was not present, had to add it myself to the mission, but I'm sure there were various triggers broken because of that. Also have to concur with the above this campaign is excellent, quite the sales pitch for your other campaigns Nate
  13. Nate--IRL--
    Tried preset K this morning and am very happy with the Improvement in clarity in Balanced mode. It has it's own particular artifacts that I can overlook, overall it's positive for me. Nate
  14. Nate--IRL--
    I'm rediscovering my love for the Shark recently and also want to add my thanks for this mod! Nate
  15. Nate--IRL--
    I've taken the opportunity to add a more fixes/tweaks to both missions, and added A-10C2 versions too. I forgot the insane amount of triggers I'd put in these . Nate The Serpents Head A-10CII.miz The Serpents Tail.miz The Serpents Tail A-10CII.miz The Serpents Head.miz
  16. Nate--IRL--
    I will look at A-10CII missions for both at the weekend. Nate
  17. Nate--IRL--
    Hi There - almost 14 years ago I created the 2 Serpent missions included with the A-10C. I see they have been given some love with new Voice overs which is fantastic, but the New weather system has created issues for one of them. I've edited the Weather and Mission time on the Serpents Head mission to make it actually playable now, while retaining the Claustrophobic vibe originally intended. Attached is the updated mission. The Serpents Head.miz Nate
  18. Nate--IRL--
    Decided to get this up and running today after an unsuccessful attempt a few months ago. Initially I was really disappointed, FPS was terrible, Colour saturation and Sharpness I'd been using in the VRshader mod were gone. Everything looked terrible and Slow/Jerky. OK so, I set the Colour Saturation and FSR in the OpenXR menu, now that is looking better than ever. Still had to fix the FPS, Decided to set the Render scale to 70% in the Open XR settings, et voila FPS is much higher than SteamVR and much much smoother. I can't tell the Difference in image quality between 70% and 100% - but I sure as <profanity> see the improvement in motion. So happy to have finally put the time into getting this working, I can finally enjoy VR again. Nate
  19. Nate--IRL--
    Glad I checked here first before testing it myself. Thanks @Harker ! Nate
  20. Nate--IRL--
    I've not tested this in sim yet, but further reading suggests that it alternates between Bar scans, but doesn't alternate each bar after a sweep. E.g........ Bar 1 in a 2 bar is Med Bar 2 in a 2 bar is High reset Bar 1 in a 2 bar is Med Bar 2 in a 2 bar is High Where it should be Bar 1 in a 2 bar is Med Bar 2 in a 2 bar is High reset Bar 1 in a 2 bar is High Bar 2 in a 2 bar is Med I'll test it at the weekend. Nate
  21. Nate--IRL--
    Fantastic Graph! Thanks. Isn't MED the preferred mode for Cold and Flanking contacts though? Nate
  22. Nate--IRL--
    Yes, apologies I should have included something to show what I was seeing. Here is a quick n dirty track. Co-alt, 4 contacts flying directly away. RWS, MED prf. Left to right F-15, F-16 Mig-29 and Mig-21. There are other Flights, but ignore them. Contact on Mig-21 is lost at approx 20nm, Then Mig-29 at 23nm or so, then at 25nm, the F-15 and F-16 on the left are lostFA-18-Radar-Test.trk Nate
  23. Nate--IRL--
    I've been trying to get to grips with the FA-18 Radar and have been playing about with GrEa5eLiTeNiN's HAFU practice mission https://www.digitalcombatsimulator.com/en/files/3317002/ Something I've noted for the first time is that the Radar detection range for Fighter size Targets in the mission, that are not HOT, is about 20-25nm. This seems to be the same whether Co-altitude, Look-Up, Look-Down, High or Med PRF, RWS or TWS. Is there something I'm missing or is this the intended model for the Radar at present? Nate
  24. Nate--IRL--
    Found this on another thread as I was having the very same issues - now I can control YAW much much easier. i.e. I do much less movement with the pedals now that I understand the logic of the stability system. Basically I was fighting the Automatic Heading Hold - without realising it was there. It is always on under the conditions below, and it is slow to compensate for drift, leading the user to use input, when they should leave the pedals alone. "Heading hold won't engage unless the aircraft yaw is < 3 deg per second and less, < 0.1 inches from the trimmed position, and ground speed is <40 knots. There is some other logic as well based on what, if any, attitude hold mode is engaged, but those are the big ones. Heading hold is a heading hold, not a "stop turn" autopilot mode." Nate
  25. Nate--IRL--
    Anybody have or see an issue where the Main Map in the Liberation GUI is just blank white? same happened to me with 3.0 so I stayed with 2.x, but now 4.0 is having that same problem. Works fine when I try it in a VM I have on the same PC though. Very odd. EDIT:- For others who might encounter this..... Maptiles are loaded from the internet now in v3.0 onward. "Its Always DNS" Simply Toggling my DNS ad-filter (Pi-Hole) brought it to life, can't find what it was actually blocking, but it 's working now regardless. (Thanks to Malakhit for the hint.) Nate
×
×
  • Create New...