Jump to content

miguelaco

Members
 View Profile  See their activity

  • Posts

    313

  • Joined

  • Last visited

 Content Type 

Everything posted by miguelaco

  1. miguelaco
    I still have long freezes when selecting the slot in MP servers. Several minutes and it eventually works, but didn't experience this before previous version.
  2. miguelaco
    You can't set individual targets to bombs in the same station AFAIK. The next best thing you can do is to set the first 4 targets in PP1 and the other 4 in PP2, release 4 bombs, switch all stations to PP2 and pickle again to release the last 4. With a little practice you can do all this in a single run.
  3. miguelaco
    Not possible AFAIK since a Markpoint works just as a regular waypoint and it’s not shown in either HUD or HMD unless it’s designated as a target, which as already stated, forces AUTO delivery. I usually designate, roll in cueing the diamond and undesignate once in the dive, when I got tally on the target for a CCIP run.
  4. miguelaco
    It would be nice to have confirmation that this is being looked at by the dev team, as it is a pretty obvious issue.
  5. miguelaco
    FWIW I'm using OvGME to replace the dll, nvidiaProfileInspector to apply preset J only to DCS profile and DLSSTweaks to enable the overlay and check everything works as expected. I got the dll from the CP2077 installation, is there a newer version of the dll or the one shipped with it is the latest?
  6. miguelaco
    I also reported and provided evidence in this thread: It seems it's been handed over to the devs for analysis.
  7. miguelaco
    Same thing noticed and screenshots provided below:
  8. miguelaco
    Hi again @Sedlo, Tried the mission once more and got the same result: landing is not acknowledged and therefore, the mission score is not 100 as should be. Find attached the full track of the mission in case you want to take a look. Maybe I'm screwing things up at some point, but honestly I don't know what's going on. One thing that seems strange is that during the mission, the comms dialogue for the CASE III recovery is initiated automatically, even though I'm not in the carrier frequency nor called inbound. I had to request abort a couple of times to reset comms for when I'm actually RTB. I have no mods besides some checklists for the Hornet. https://drive.google.com/file/d/1LtfnNPQt94DGSUnt3PqP4K_ZK-lho8Zg/view?usp=sharing
  9. miguelaco
    Got the same with stock liveries.
  10. miguelaco
    Strange, will try again and post the results. Thanks for the heads up.
  11. miguelaco
    New S-3B refueling lights are broken (missing texture?):
  12. miguelaco
    Hi @Sedlo, thanks again for this awesome campaign. Just finished mission 8 and I'm getting a score of 60 despite having completed all the objectives and returned safely to the carrier. It seems the landing is not getting recognized, I'm not getting the usual message once in the carrier deck. I took a brief look at the mission in the editor and it seems the trigger zones are misplaced. Maybe something was broken when switched from Stennis to George Washington?
  13. 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?
  14. 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!
  15. 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
  16. 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
  17. 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.
  18. 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.
  19. miguelaco
    I've provided a trackfile in another thread showing the issue:
  20. 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
  21. 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.
  22. 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?
  23. 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.
  24. 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.
  25. 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.
×
×
  • Create New...