Tiramisu

Here is a summary of how to install DCS on Linux (Steam version): 1. Install protontricks with flatpak: https://github.com/flathub/com.github.Matoking.protontricks?tab=readme-ov-file#protontricks-for-flatpak This means you should install flatpak as described on the webpage before you install protontricks with the Linux terminal: flatpak install flathub com.github.Matoking.protontricks (It is recommended to use flatpak, because some Linux distros may not support newer protontricks versions required for the steam client.) 2. Add a few command prompt aliases: https://github.com/Matoking/protontricks?tab=readme-ov-file#flatpak-recommended echo "alias protontricks='flatpak run com.github.Matoking.protontricks'" >> ~/.bashrc echo "alias protontricks-launch='flatpak run --command=protontricks-launch com.github.Matoking.protontricks'" >> ~/.bashrc 3. Now you can follow the hoggit guide by running the command protontricks 223750 d3dcompiler_47 in the Linux terminal. In the launch option of the DCS steam properties you should add WINEDLLOVERRIDES='wbemprox=n' %command% or else DCS is not going to launch at all. 4. The DCS launcher does not run properly in Linux (you will see a black box on startup). In order to disable the launcher you need an editor to open the file "options.lua" in the install folder "Steam/steamapps/common/DCSWorld/MissionEditor/data/scripts" of DCS. Then you replace ["launcher"] = true with ["launcher"] = false 5. Start DCS in Steam. It should now run without getting stuck in an infinite loading loop.

If I understand it correctly, then we will never have a Mig-19 again even from another developer.

I would do it, but I do not know the source code. What exactly the input data is and so on. Maybe I should ask in the modding section, if there is anything available.

If only ED could patch it as quickly as the Soviets did.

Probably this has been asked a lot, but the missile guidance logic needs to be improved. I don´t think (SAM) missiles should be so easily fooled by driving them into the ground, i.e. using their lead pursuit logic against them until they hit the ground.

There is no aircraft with similar vibes like the ones abandoned by Razbam. Especially the Harrier feels unique. Sometimes you need to accept the grim reality.

The image says it all.

We need to be able to pick up soldiers like this for transport and evac missions. It is not important to have a graphical representation of the outside passenger in the sim. The only things that needs to be simulated is an adjusted (center of) mass of the Apache and the possibility to accidentally drop the passenger during abrupt maneuvers.

On a more serious note it would add to the realism, if enemy missile attacks could have an impact on the operability of the crew. I guess enemy fire is not capable of killing parts of the crew. This means the immersion of the Supercarrier module is rather limited.

I had already tried verifying my game files with Steam several times, but it did not find any problems. So reinstalling was my last option. However, I did not know about the shader folders. Next time I get this kind of problem, I will try it.

Loading missions took a long time for me, especially during the "world preload 1/60" message. It took more than 3-5 minutes before that message went away each time I reloaded the same mission. So I have decided to delete and reinstall DCS, which made loading missions much faster now. It also removed the horrible lag I had in the mission editor. E.g. opening the payload screen always took more than 1 minute the first time I opened it. Now it behaves normal again. I believe reinstalling also increased my FPS a bit. My question is whether I have to frequently reinstall DCS to ensure a good performance, because I suspect that DCS updates create issues for the file system that are not detected by the file validation function in Steam. This time I had to download "only" 188 GB for the reinstallation, because I disabled some of the modules. Otherwise it would take almost 500GB for all the modules I own.

The Christen Eagle is pretty good for some weird stunts in Dubai like flying through one of those metro stations simply because of its small wingspan. Or land on small surfaces like helipads. I have not tried it myself, but it seems to be possible in real life. https://www.youtube.com/watch?v=B-brmk1ua1g

Once the Flir screen is on, my performance goes down. I think the updated new Flir images are much more demanding now.

Thanks for your hard work! I have also found a few minor mistakes in the Apache guide. Page 335: Step 11 - Press VAB next to Freq instead of the one next to Code. Page 509: Description numbers are not correct.

Thanks @sunski34! Your example worked well for me.

That is it. Thank you!

How do you do that?

In addition to this suggestion can we have bindable radio options (F1-F10)?

Unfortunately, I will not be able to proceed with the rest of the campaign as long as this bug is not fixed. If I may guess, then I would say that the AI is not attacking because it has not detected the targets. So maybe that might be worth investigating. There are some Lua functions that can help detecting units or check whether the AI can see a unit. So maybe it would help if you let Monster-flight fly towards the SAMs and start the attack task once they have detected the SA-15s.

Sorry, the link should work for everyone now. The same taxi-bug happened to me on my 2nd and 3rd attempt as well btw. So it should be easily reproducible. It seems like the AI unit blocking the runway is my own wingman.

Yes, of course, but I hope you can fix those issues when the mission is stuck without a warning. In the end all AI aircraft managed to take off with 5 minutes delay, and imo the mission should have been able to carry on or at least I should have got a warning what to do in those situations (e.g. orbit before WP2 until all aircraft have reached me).

Currently the possible AI tasks depend on a fixed mission type (e.g. CAS, CAP, Runway bombing, etc.), but I would like to see a mission type that includes all AI tasks for multipurpose missions. It was a great idea adding the blue/red combined arms coalitions to unlock all units for a side, so if something similar could be done for AI tasks, it would allow mission designers and scripters to add more complexity to their missions. Another restriction that should be removed is that ground units cannot be assigned to attack designated aerial targets. This would be very helpful especially for Lua script designers, who could tell AI SAM units to engage only specific targets (like e.g. only attack bombers with a Sa-2 group, or attack only aircraft above a certain altitude, or attack only HARM missiles with a Sa-10 site, etc.). Currently ground units can only be assigned to attack other ground units. I hope ED considers to add these simple changes. Imo it would open up a lot of opportunities.

I have done all the radio commands correctly and followed the correct timing, but from the Tacview file I could see that due to an AI bug one of the aircraft was stuck on the runway threshold for 5 minutes after I took off. This caused the AI flights to rejoin with me very late on the Sally corridor and therefore the rejoin took place when we have reached WP2 already. This caused the following triggers to not work correctly and I was stuck in the mission for a very long time without knowing it at first. So it would be great if those frustrating trigger-bugs could be avoided. In the end it was not my fault that the AI got stuck. The tacview file is too big, so I had to upload it somewhere else. https://drive.google.com/file/d/1CbuBgPUqq_Q9DRFcsAZBk4bzb7K-LU_z/view?usp=sharing

I could not see this bug in the linked replay. Iirc there was a patch that significantly reduced the likelihood of this bug for me, but it still occurred afterwards sometimes. So I will keep an eye on it. For now I can show you a three months old screenshot from my PC. DxDiag.txt

Thanks. My computer has a Nvidia graphics card btw. So it does not just happen on AMD cards.