vsTerminus

You know, we keep telling you guys to stop releasing things on Friday because it deletes people's weekends whenever anything goes wrong. Once again, there are a series of very good reasons why "Patch Tuesday" is an industry standard.

Hi all, I have a sandbox mission which listens for S_EVENT_LAND (event id 4) which just plays a sound file every time anyone lands. That functionality stopped working after updating to DCS 2.9.6.57650 After throwing some extra logging into the listener, the only event I see when landing is S_EVENT_RUNWAY_TOUCH (event id 55). Even in the middle of a field, you can see in the attached screenshot that the only event which fired was 55. Did something change intentionally with S_EVENT_LAND? or is this a bug? Attached is my Syria sandbox miz file, but also the "sandbox.lua" file with the extra logging. You can load that into any mission with a do script file trigger. sandbox.lua Sandbox_Syria.miz

It was shared with me on Discord by quebecd3ltatw0 that there is now a solution for Proton as well! Include WINE_SIMULATE_WRITECOPY=1 in your launch options. I tested on Proton Experimental as well as UMU Proton 9 Beta 16 and it worked! It did not work on system Wine 9.11, but that's fine. WINE_LG from PortProton continues to work if you don't want to use Proton for any reason. Also I tested Proton Experimental in VR and it worked there too, which means as far as I'm concerned this one is "solved via workaround".

Update, another thread was opened about the UI not working and it turned out the author is also on Linux, so same issue. As I posted over in that thread, I have a partial solution now. HeatblurUi is a Chromium Embedded Framework (CEF) app, and those don't seem to play nice with wine. I did find some people claiming success using PortWine (now called PortProton), so I downloaded that and tried launching DCS with it. PortProton ships with its own branded and modified Wine and Proton runners called PROTON_LG and WINE_LG. No luck with Proton, but WINE_LG seems to work fine and is able to load the HBUI. Note: Because it's Wine and not Proton this will only work for the Standalone version (as Steam version requires Proton), and it will not work with SteamVR because seemingly only Proton can bridge apps so that they can see and use the hmd. Using Monado might be an option for VR, I haven't gotten to trying it yet. Original post here

Ok, so. Thanks to riojax for explaining that it's a CEF app, that gave me something to go on. Bit of searching around and some people had reported success with CEF apps using PortWINE, now PortProton. So I installed PortProton and had it launch (standalone) DCS. It lets you pick between PROTON_LG_9-5-1 and WINE_LG_9-10. No luck with PROTON_LG, but WINE_LG actually worked! PortProton is its own launcher but I'll experiment with pulling WINE_LG out of it and having either Steam or Lutris use it and see how that goes. **Quick Edit**: Dropping a copy of WINE_LG into Lutris' runners folder and then using the Prefix that PortProton created, I was able to launch DCS through Lutris and HBUI still works. **Edit 2:** Because it's Wine and not Proton that is working, this will only currently work for the Standalone DCS. For Steam (or SteamVR) to work we're stuck waiting for Proton to start working with CEF apps too. Still, this is better than nothing. I'll just have to stick to licking windows in VR for now.

This is the same issue as After the patch the plane loads on Linux now but HBUI does not work. My guess is that whatever UI framework HB is using doesn't play nice with Wine/Proton, or we're missing some dependency or config option that is required.

After today's update the F-4 is now loading on Linux - At least for me. I have tried wine-ge-8.22, wine-9.9, and proton-experimental, all three can load single player and multiplayer. However, the Heablur UI does not seem to be working. I cannot open the Jester menu or the Crew Chief menu. Attached is a new dcs.log. But hey, one step closer. Again I'm assuming that there's probably a missing dependency for the UI that we just need to install, but without HB's help I'm not sure what that would be. Edit: I can see Wine trying to launch HeatblurUi.exe when I load a mission. Updating my vcruntime to 2022 did change the error popup I get (about wine failing to run the program) but didn't fix the problem. Looks like it tries to start the UI a bunch of times before giving up. Causes some noticeable stuttering in the game when I first load in. Not seeing any helpful errors in my logs though. 2024-06-05_dcs.log

Hi all - I realize that Linux is not officially supported but I'm hoping this can serve as a searchable place (Sorry Discord) for Linux users to maybe figure out how to get this plane working, and maybe Heatblur will be able to chime in with some extra info here and there. Basically: Trying to slot into an F-4 crashes DCS on Linux. Affects single player and multiplayer. It's no trouble when other players fly one on the same server, but trying to load into one myself immediately crashes the game. Attached is a dcs.log file but it doesn't really point me at anything specific. It seems to be loading the Heatblur DLLs OK, and I don't see any unique errors related to it. I'm running DCS Standalone, launching via Lutris, and I've tried Proton 9.0 (and Exerimental), wine 9.9, wine-ge-8.22 and others, in both flatscreen and VR. Same results. I've tried adding WINEDLLOVERRIDES for the Heatblur DLL files, again no results. I've uninstalled and reinstalled the F-4, no results. The F-14 works perfectly, along with every other module I own (which is the vast majority of them). I don't have much for mods, just the two planes (A-4 and Hercules) needed for Greyflag. Anyway, often times when something doesn't work on Linux it's because of either missing dependencies (eg, a specific .NET version) or the UI framework used doesn't play nice with Wine (eg, MSEdge Webview2). I'm wondering if maybe Heatblur can provide some info on the frameworks and dependencies that might be needed by HeatblurUi.exe or other parts of the F4? Might give us something to go on because right now I'm just kind of randomly guessing at stuff. Alternatively, if HB wants to provide files with enhanced logging enabled I'd be happy to give them a go. Would just love to be able to fly this thing because I don't have Windows anymore and I'm not planning to go back any time soon (I know there is a thread on Discord already, but that's not searchable on the web. Anything that gets discovered there I will post here for visibility.) 2024-06-01_dcs.log

So I took the new Gazelle out for about an hour last night and wanted to say thank you for updating the FM. I honestly did not expect it to happen before the Kiowa and I'm thrilled that you decided to do it. Previously my biggest issues were the control hypersensitivity and the way it held bank like a fixed wing aircraft. Both of those have been dealt with; It now flies like a helicopter should, and that's so awesome. For the first time I'm able to fly around the streets of Beirut and keep it between all the light posts without any trouble. I also found myself in VRS by surprise a couple times Nice work on the update, seriously. With that said, there are a couple things I noticed that don't seem quite right to me that you might already be aware of... 1. The Gazelle should require some aft and right cyclic in a hover with calm winds, right? Well, right now it requires aft and left cyclic, but wants to roll right so hard that it still hangs right skid low. Something is generating a lot of right roll that probably shouldn't be. **Edit** Apparently this is correct. It just struck me as unusual for a clockwise rotating helicopter. 2. The engine still seems to be able to spool up and meet any demand I place on it instantaneously. Like, if I'm sitting on the ground and go from 0 to 100% collective in a split second, it should cause a significant drop in rotor RPM while the engine spools up and tries to deal with the increased demand, but instead the rotor RPM is maintained and it just launches straight up. Oh, and unrelated to the FM, but the rotor disc sound seems to have a Flanging Effect that is really clearly audible, at least to my ears. Dunno if there's anything you can do about it but I don't hear it in the other helis. Overall I think it's a really nice update and makes the Gazelle so much more enjoyable to fly, but there are some smaller issues that would be nice to get ironed out in future patches.

Thank you! I'm trying to find time to work on new ones but this summer has been *crazy*. That's funny that the site says 2016 because I purchased it in 2014 and made videos with it that year lol. If you google the mi-8 release date you'll get 2013 so my guess is typo on the site?

The Hip was released in 2013, not 2016. So yea. It will likely be a full 10 years before the Hip gets multicrew, but with the ability to switch seats online finally implemented the way is finally paved for the Mi-8 to get multicrew without killing its usefulness online. So here's hoping!

Hey, glad you found my tutorials. I learned a lot about the module while I was making them, and over the last couple years it seems they have helped a lot of people; That's awesome. The Tactical DCS discord has channels with resources and tutorials for every module, you might have some luck looking through there to see what kinds of content people have shared or recommended.

Controls Indicator mods are breaking IC now also. A couple examples, - Mi-8 https://www.digitalcombatsimulator.com/en/files/3317792/ - Mi-24 https://www.digitalcombatsimulator.com/en/files/3317045/ This kind of mod exists for several other modules too. It makes the background of the controls indicator overlay transparent so it's not so obvious and in your face, plus easier to read in some cases. In the Mi-8 it also hides the autopilot overlay in the other corner, which takes up a lot of space and arguably serves limited purpose. You could make these mods irrelevant by building in some options to customize these overlays, including things like foreground and background color, transparency, position, size, and options to hide things like the AP overlay. This becomes apparently only when trying to slot into an affected module, as IC shield is green until then.

I actually made a video on RBS back in 2014 and noted the same thing back then as well. This has been around for a *long* time. Would be nice to see it get fixed one day.

Yea, that's something I covered in my first impressions video. It sounds like the real hind provides very little feedback during transverse flow, but I still interpret that as "more than nothing at all" which is what we have now. So at the moment yea, you're pretty reliant on your instruments to know when the right time to start feeding collective back in is.