Jump to content

miguelaco

Members
 View Profile  See their activity

  • Posts

    326

  • Joined

  • Last visited

 Content Type 

Everything posted by miguelaco

  1. miguelaco
    Any updates on this? I originally posted under Bugs & problems in F/A-18C subforum and it was moved here without any notice. I can hardly see it is a problem in the Supercarrier module itself, but anyway, shouldn't it at least be under Bugs & problems in this subforum?
  2. miguelaco
    I would suggest not to enforce the setting, since it not only influence the carrier burble. It also makes AAR and dogfights more challenging among other things. What about leaving the option and adding a designer note saying that the option can cause problems with ACLS in some missions and it is advised to either disable wake turbulence or fly manually on final approach? Just my perspective—it's your campaign, and it'll be awesome no matter what you decide!
  3. miguelaco
    Flying the excellent Bold Cheetah campaign by @Sedlo, I encountered difficulties with Mission 6 due to ACLS's inability to land the aircraft properly in those weather conditions. After some investigation, I found that the "Wake turbulence" setting might be the root cause. According to some sources, this setting affects the carrier burble, making the ACLS system work hard to compensate, leading to frequent bolters, hard traps, and damaged landing gear. These two videos illustrate the issue, both in the same mission and under identical weather conditions: I believe ACLS should handle these situations better, but I might be mistaken, and this could be the intended behavior. It seems odd that this single setting causes such a failure. acls_no_wake_turbulence.trk acls_wake_turbulence.trk
  4. miguelaco
    Just to follow up on this, take a look at these two videos showcasing the issue: Same weather conditions as in Mission 6. I'm also attaching the trackfiles in case anyone is interested. I will also post it in the Bugs and Problems subforum so ED can take a look at it. Thanks everyone for the help. acls_wake_turbulence.trk acls_no_wake_turbulence.trk
  5. miguelaco
    Thank you! I was able to complete the mission a few days ago, just as you suggested, by taking control on final. However, I’ve been curious about why the ACLS failed in that way. I’ve managed to narrow down the issue. As I suspected, it seems related to the "wake turbulence" setting. Despite its name, this also appears to influence the carrier burble. The effect seems to be amplified under the specific weather conditions in Mission 6. I have two tracks from the same mission, one with wake turbulence on and the other off. In the first track, the aircraft sinks rapidly on final, and the ACLS can’t compensate for it. I’ll post the tracks once I’m home and have access to my PC.
  6. miguelaco
    You raised an interesting issue, maybe I'm doing it wrong. I thought it was not possible to set the airspeed once you engage both ATC and CPLD P/R. How do I command a higher speed? Do I have to set the aircraft to that speed prior to engaging ATC and then it will try to maintain it? Thanks again for the assistance.
  7. miguelaco
    I've provided a trackfile in another thread showing the issue:
  8. miguelaco
    As promised, I'm attaching a track that shows the issue. I took mission 6, and edited to start in the air, ready for a Case III approach. I didn't respect the procedures and commenced right away after established. I also removed most of the payload to make sure I was within weight limits for a carrier trap. The following screenshot shows the exact moment of touchdown, and as you can see ATC and AP CPLD P/R are engaged but the rate of descent is 1000 fpm, too much for the Hornet's landing gear: acls.trk acls-test.miz
  9. miguelaco
    No, I have no mods installed apart from some kneeboards. Yesterday after the update I run a slow repair, so I think It's all good. It's weird because I tried other missions and landed a bit short but fine, nonetheless. Do you have wake turbulence enabled? It seems the problem is at the very end, so it could be that the burble is causing it somehow. Did you test with mission 6 specifically? Anyway, I think it's easier if I try to replicate and get evidence. I'll post back as soon as I managed to get a trackfile showing the issue.
  10. miguelaco
    I tried Mission 6 yesterday after updating both DCS and the campaign. Managed to land engaging ACLS, but the gear got damaged too, so I think something is definitely wrong with the implementation. Everything looked smooth from the cockpit until the very end, the system commands throttles to idle and aims too short. It ends with the aircraft bouncing on touchdown and hopefully catching the wire #4 or boltering, while damaging the gear in the process. Not nice. I think I'll try to replicate it in a different mission, same conditions but starting in the air and performing the Case III right away. Any thoughts?
  11. miguelaco
    I’m also getting flickering with certain settings. At the moment, I’m Running DCS with DLSS enabled and it seems to be mitigated by disabling it, if you can take the performance hit. This is in VR, with a Pimax Crystal OG in a 4090.
  12. miguelaco
    I would say it’s normal until just before touchdown. I will try to replicate the same conditions and repeat the recovery in order to have more data. Hopefully I’ll come back with a track too. First time I tried I didn’t realize the aircraft was too heavy and thought that could be the cause, but on a second and third attempts, I dumped fuel and landed at 33000 lbs.
  13. miguelaco
    I also got this recently in Bold Cheetah campaign, mission 6. Tried twice and my gear was damaged on both occasions. I don’t have a track at hand, but I would manage to get one if necessary.
  14. miguelaco
    I just finished mission 6, Iron Hand, and it’s been a blast so far, thank you. I had to repeat mission 6 a couple of times since ACLS seems it’s not correctly handling the weather conditions. Everything seems good until the last moments, as the aircraft is touching down really hard and got its gear damaged. Anyone experienced this? On my third attempt I had to land manually and I passed, but I thought ACLS would be capable of handling this.
  15. miguelaco
  16. miguelaco
  17. miguelaco
    If you order Virpil Ace Pedals with the damper upgrade, I think you can remove the spring and it shouldn't return to center, which I believe is what you're asking for.
  18. miguelaco
    This issue has been around for quite a while. I think it was first reported here:
  19. miguelaco
    You can disable the NVIDIA overlay in the app
  20. miguelaco
    If you're using QuadViewsCompanion, you can check the option "Focus View" to only render the high resolution region. If it works, then you can be sure you're using mbucchia's QVF. The option can also be enabled directly in the config file, but it's easier this way. Another way, less practical is in DCS launcher Options>VR, you have a new option to enable QuadViews. Next to it you should see a warning sign and it will tell you which api layers are enabled in your system.
  21. miguelaco
    As I stated, I noticed more stutter with Pimax Play, which seems weird. Looking at the FPS counter in DCS, I noticed I'm CPU Bound (I run it at 72Hz), but the text is coloured in red, whereas with the old stack is coloured in yellow. i wonder what that means exactly, but the frame times are much less stable too, hence the stutter. What are your hw specs, if I may ask?
  22. miguelaco
    I don't think QVC can be used with Pimax Play's own DFR implementation. I tested it by checking the "Focus View" option in QVC and it has no effect, so I concluded that it does not work with that implementation. Are you seeing something different? Let me know, maybe I'm doing something wrong.
  23. miguelaco
    I'll try, but even with 150% I'm seeing better results using the old stack where I can't hardly notice any stutter. I guess you're still using @mbucchia's QVF along with the OpenXR shipped with new version of Pimax Play. I also tried that and it is much better but still worse than the "old" option in terms of stuttering. BTW, I have a 4090 with an i9 14900K and 64GB of RAM. I think it's not needed, you can actually choose. If you install @mbucchia's QVF you'll be using that, but if you uninstall it and check "OpenXR Quadviews" option in Pimax Play, you'll get dynamic foveated rendering by means of the new OpenXR shipped in Pimax Play. However, the only tweaking you can do in this last case is the three settings below (Performance, Balanced and Quality). Maybe I'm wrong, but these are the conclusions I reached during my tests.
  24. miguelaco
    I'm seeing quite the opposite, frames are ok, locked at 72 most of the time, but I noticed more stutter with native stack. Going back to old trusty PimaxXR + QVF. Maybe it has to do with my QV settings that I cannot replicate with Pimax Play since it only has three presets (Performance, Balanced, Quality):
  25. miguelaco
    Tested this and can confirm is still not resolved in the latest patch
×
×
  • Create New...