Jump to content

Zyll

Members
  • Posts

    636
  • Joined

  • Last visited

Posts posted by Zyll

  1. On 8/9/2025 at 3:57 PM, LorenLuke said:

    Make sure the binding for the front seat actually uses the WAS switch on the TEDAC and not on the cyclic grip. COOP rockets will not select if the gunner uses the cyclic grip. I'm no 64 pilot, but I've been lead to believe this is also the case on the real aircraft.

    this is interesting! @HPLsCat I do indeed have my front-seater's keybinds mapped for the cyclic, and not the TEDAC controllers. I will re-map and we can try again.

    • Like 1
  2. this sounds similar, but our experience tonight (and this is on DCS 2.9.18.12899) is that in multiplayer, IAT actually causes LST to lose lock. 

    Specifically, Apache 1 is lasing on laser code Romeo, and Apache 2 and 3 are LST on Romeo, they set LST to auto and their TADS immediately snaps to the laser spot. As soon as Apache 1 turns on his IAT, the LST of both Apache 2 and 3 immediately goes into scan mode, essentially they lost the laser. As soon as Apache 1 IAT is deleted, the LST of both Apache 2 and 3 snaps back on the laser spot again.

    • Like 1
  3. I know its not a high priority, as it doesn't affect functionality, but man, when he says "no inter-visibility/indivisibility on target" it sounds like he's slurring his voice, and there's 2 or 3 extra syllables there that don't sound right. I assume he's saying "no visibility on target", but maybe just say "no visual on target" instead.

    Is it just me? I don't feel like I'm the only one who has noticed.

    Maybe I'll just ask Casmo a small favor and have him send a wav file, then I'll package it up and post it to the ED downloads section as a QOL game enhancement 😉 

    • Like 1
  4. if its a dynamic spawn airport you are trying to put them at, did you make sure that the AI airframes are allowed to spawn there?

    (EDIT: one of my noob squad mates made this mistake)

    • Like 2
  5. On 1/31/2025 at 11:20 AM, Actium said:

    While not exactly what you ask for, you can mute log messages with levels below warning, only for the missions scripting environment (instead of all info messages as above example from Gater):

    log.set_output("dcs", "SCRIPTING", log.WARNING, log.FULL)

    how does that work exactly? is it looking for the word "SCRIPTING" in the log message and suppressing it? 

    On 1/26/2025 at 3:54 AM, LittleNose said:

    Hi Zyll, did you find a suitable way to do this?

    unfortunately not, I just have been getting by with excessively large DCS.log on the dedicated server. tools like klogg have helped to filter the log from a readability point of view, but I'm still concerned about the performance impact

  6. Yep that fixed it! the cleanup/repair identified these files, one/all of them must have been the culprit:

    Scripts/Speech/common.lua

    Scripts/Speech/speech.lua

    Scripts/UI/RadioCommandDialogPanel/RadioCommandDialogsPanel.lua

    Scripts/UI/RadioCommandDialogPanel/TabSheetBar.lua

    Scripts/UI/gameMessages.lua

    I think its Vaicom / VoiceAttack which modified these files. @Livers do you run Vaicom Pro perchance?

    • Thanks 1
  7. I was mistaken actually. When I had a brand new saved games/DCS folder, it still had the issue. I didn't realize that the test message initially appeared completely hidden behind the bar at the top of the screen. Here's a video of what I see. The test message shows eventually lower in the screen because it gets pushed down from the top of the screen by the comms menu, but its still being hidden at the start when the comms menu is not displayed.

    i've tried different screen resolutions, thinking my ultra-wide aspect ratio might be the issue, but 16x9 and 5x4 still showed the issue.

    EDIT: you will notice that the Comms Radio menu appears in the proper location (not cut off), but the "this is a message" text comes up hidden behind the bar at the top of the screen.

    EDIT2: actually upon watching the video again, and seeing Flappie's screenshots in this thread, I think its just because there's extra padding above the Comms Radio menu, that's why it doesn't get cut off

  8. I alt-tab often especially when working on missions (flipping to my scripts, or my DCS.log, or even just Discord). In the past alt-tab worked like... every other application that has ever exists since Windows 95. Now if I have DCS open and alt tab, it will put DCS behind every window that is not minimized on the desktop. What should happen, is the application chooser should appear, and when you release alt-tab, it would only bring focus to the app you chose. 

    I don't even know how DCS can be made to behave in a unique way within Windows, but I'd like it to work like normal. Any other windowed game will work the way I describe above.

    Under DCS System settings, "Full Screen" is unchecked, as it has always been. In fact, the behaviour as it is similar to if "Full Screen" were checked.

    it seems to work normally from load screens within DCS, but once the game, or the Mission Editor has loaded, it acts abnormally

  9. 5 hours ago, BIGNEWY said:

    https://www.digitalcombatsimulator.com/en/news/changelog/stable/2.9.9.2474/

    DCS 2.9.9.2474

    DCS - Core Game

    • Fixed: crash that was induced by some modules using custom effect presets. (This crash was top in our crash reporting track system. Please keep sending crashes when able, it helps us determine and prioritize fixes, Thank you!)

    Fixed: crash that was induced by some modules using custom effect presets.

    Do you have any additional details what modules were impacted or what these "custom effect presets" are? I was trying to troubleshoot excessive crashing last Sunday, and would love to be able to associate them with this fix. My DCS is normally pretty stable, but it crashed 6+ times in an hour span with dxbackend.dll which has not happened in a long time for me.

    Thanks,

    • Like 1
×
×
  • Create New...