Jump to content

Flappie

ED Beta Testers
 View Profile  See their activity

  • Posts

    17395

  • Joined

  • Last visited

  • Days Won

    11

 Content Type 

Everything posted by Flappie

  1. Flappie
    At first, I was all alone, so I didn't think about reporting this issue. I'll report it.
  2. Flappie
    It could, yes. According to what I read, this setting has various results depending on the game and the PC. I had a brain fart about parking/unparking cores. Simply ensure you let Windows run your CPU as usual, especially if you had to tweak Windows when that messy MT bug was around. You are right: High Performance power plan means no core-parking. Anyway, now that your DCS runs fine, don't touch anything. Come back here if the issue returns.
  3. Flappie
    A dev says the Combattante II smoke thickness cannot be tuned because of a bug in the code which enforces max smoke thickness. Hopefully, the reason for the Kilo smoke thickness is the same, which means it would smoke less once the Combattante II bug is fixed. I've just bumped the Combattante II internal report. We'll see. About the smoking/non-smoking matter, I have a proposition: maybe we can ask devs to make the Kilo stop emitting smoke whenever its depth is less than 0 feet. This way, mission designers and Combined Arms users will be able to choose whether the sub emits smoke or not. Would it work for you, gents?
  4. Flappie
    I don't see anything obvious in your DCS log, but this: 2025-01-25 04:49:33.113 WARNING EDCORE (Main): hypervisor is active ... 2025-01-25 04:49:33.113 WARNING EDCORE (Main): CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores) Warning 1#: Check this thread (and don't forget the second page). Warning #2: Try unparking all of your CPU cores The former MT bug with modern CPUs is no more. If you had tweaked your CPU because of this bug, try the previous, normal, setting. Your DxDiag log shows several blue screens. You might want to check your RAM.
  5. Flappie
    Please attach a DCS track, a screenshot or two, and your custom board so we can give it a try.
  6. Flappie
    A fix is coming. I'll check if it helps with the helo bug.
  7. Flappie
    I'm on 24H2 as well. And I only get the issue when I keep my old .diff.lua files in the Input subfolders. Have you checked your Input subfolders?
  8. Flappie
    I did in another thread, and the AI had no issue to refuel. I don't even know which tanker you used, its speed, its altitude... which is why we ask for tracks.
  9. Flappie
    The pixelated effect is about to get fixed internally, by the way (different issue).
  10. Flappie
    I eventually understood why NineLine and I couldn't reproduce the yellow page issue: it does not happen when "Show pilot body" is disabled in DCS settings. That means there's a workaround for now: disable this option, then, once in the cockpit, manually enable the pilot body. I'll edit the internal report so this issue can be tackled.
  11. Flappie
    Reproduced and reported. Thanks for the heads up.
  12. Flappie
    I can't find anything relevant. You should open a support ticket: Log into DCS website. Click Support, then click "Create a new ticket". Say "Hello" from me.
  13. Flappie
    This will be fixed with the next update.
  14. Flappie
    That's exactly what I thought when I read the book yesterday evening, only the document is not very clear. There's already an internal request to get back to 15°, but devs want concrete proof, not interpretations, for they don't want to be mislead every 15 days and redo the work all over again. If you can provide an official doc saying tankers shouldn't exceed a 15° angle while refueling, that would be great.
  15. Flappie
    I know, which is why I try to reproduce the issue. Thanks for the track, I'll check. A user rightfully reported that NATO's ATP-56 document states tankers can roll with a 25 degree angle, which is why the modification was made. But, it didn't go well apparently. If you have more reliable and public information, please bring it on.
  16. Flappie
    The S-3 is already reported, and the light issue internal report is still open. This was an error in the changelog, indeed.
  17. Flappie
    No issue for me. KC-135MPRS with two AI hornets_OK.trk
  18. Flappie
    The issue with the S-3 is reported already. Can we have a short KC-135 track, please?
  19. Flappie
    Issue reported.
  20. Flappie
    Can we have a track, please?
  21. Flappie
    I suggest we resume this conversation in this other thread:
  22. Flappie
    A fix is in the making for what looks like the same issue (reproduced in the Apache). Could someone provide a F-15C track?
  23. Flappie
    It's the same thing for DCS website: there's no more French translations for news (same thing for Spain, Italy and China). I'll ask devs if they can either revive news translations or hide this panel for "forgotten" languages.
  24. Flappie
    A fix is being made for what looks like a squelch issue. Maybe it's the same issue, but I'm not sure since this thread lacks a fresh track. I cannot reproduce the issue in release with the OP track. Can someone please provide a track demonstrating the issue?
  25. Flappie
    It still looks like the module Input folder issue.
×
×
  • Create New...