Tiramisu

Thanks. I do not know what to do about the hardware ID, but I will look out for it. My system has become old indeed. DCS used to have 4 (or maybe just 2) GB VRAM as minimum requirements in older versions.

Here is what I get when I close the login window, enter the main menu and start an instant mission.

Thanks, but it did not work. I also tried deleting Saved Games/DCS/network.vault and most of the other files in the Saved Games folder, but DCS still behaves erratically. The simulator does not even care whether I am logged into my account or not. I can simply cancel the login window after startup and play all the modules that are in my Steam DLCs.

I checked the autologin tickbox every time, but the login window appears every time I restart DCS. This was not the case in the past, when everything went smoothly. However recently I had to restart DCS several times in a row and since then I have this annoying problem. What is even worse is that somehow my performance has dropped in some missions (from 40 to 10 FPS). I have not added any mods nor did I change any settings. DCS seems to behave very erratically now. I remember that DCS had account authentication problems in the past. My guess is that it is still causing problems. I use the Steam version btw.

Now it is working. In addition to the previous steps I had to disable the Vulkan shader preprocessing in Linux Steam. Steam -> Settings -> Downloads -> Enable Shader Pre-Caching -> Disabled Somehow this caused lots of bugs.

I did increase my pagefile to 32GB, changed my GPU driver to the more stable 535 driver, deleted the Saved Games folder and reinstalled d3dcompiler_47 for protontricks 223750. Now I get this log. The crash log can be found below the line DX11BACKEND (488): DX11Renderer initialization (w:1920 h:1080 fullscrn:0 vsync:0 adapter:0 monitor:0 shaderErrors:1) This means the shaders have not been initialized correctly. Interestingly DCS does start if I replace Proton Experimental with Proton 9. However, even Proton 9 is not capable of running a mission because of other errors related to the voice chat and other things. I get the feeling that this patch introduced a lot of bugs for linux users like me.

I have deleted the whole DCS folder in Saved Games and restarted DCS, but I get the same problem.

Never mind. I just found out that there is anoter Saved Games folder, where the actual logs are located at. /home/myname/.local/share/Steam/steamapps/compatdata/223750/pfx/drive_c/users/steamuser/Saved Games/DCS/Logs So the last error message is E5020: The 'fx_5_0' target profile is only compatible with the 'fx' target type.

Nope. Alt Tab, Win D, Win Tab, Win arrows do not work. The splash screen is extremely resistant.

Do you have the same problem Max? For me the old 2.5.6 version is working, so it is definitely because of the patch.

I feel the same. Does anyone know how to disable or at least shrink it down? Btw. I needed to post something to get rid of my triple six post count.

So you are referring to Proton being enabled. Yes, I have tried Proton Experimental and Proton 9.04. I have already figured out that it has probably something to do with the new shader introduced by the patch.

Yes, I deleted the DCS folder in /home/name/.wine/drive_c/users/name/Saved Games. Then I ran DCS again, but the Saved Games folder remained empty. I believe the reason is that it is only populated once you get past the point when the splash screen goes away, but in my case it gets stuck.

Yes, I even pasted the backup of the saved games folder to the empty one, but the startup problem with DCS remained. I also tried to delete the whole folder and then run DCS. Until the devs have fixed this issue I will be forced to use the DCS 2.5.6 version from 2020, which is the only backup version of DCS available on Steam right now. Here are my system specs for reference:

After the recent update I cannot run DCS, because I get stuck in the splash screen. The splash screen prevents me from viewing the error window behind it, but I could see its miniature image in Ubuntu: I could decipher it. Apparently shaders/enlight/separateTransparent.fx is not compatible with something. This shader has been introduced in the recent patch according to https://steamdb.info/patchnotes/20499928/. I could not get the DCS error logs, because for some reason my Saved Games/DCS folder is empty now. This was not the case before the patch and I was able to launch DCS back then. At least I could get the steam log: Btw. is there a way to disable the annoying splash screen? It blocks my entire sight. It still appears even after I set ["launcher"] = false in options.lua.

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.