Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DCS World Steam Edition (223750) #1722

Open
2 tasks done
h54 opened this issue Oct 12, 2018 · 483 comments
Open
2 tasks done

DCS World Steam Edition (223750) #1722

h54 opened this issue Oct 12, 2018 · 483 comments
Labels
Game compatibility - Unofficial Games not expected to work without issues

Comments

@h54
Copy link

h54 commented Oct 12, 2018

Compatibility Report

  • Name of the game with compatibility issues: Does not launch
  • Steam AppID of the game: 223750

System Information

  • GPU: GTX 1070
  • Driver/LLVM version: Nvidia 396.54
  • Kernel version: 4.15.0-36
  • Link to full system information report as Gist:
  • Proton version: 3.7-7

I confirm:

  • that I haven't found an existing compatibility report for this game.
  • that I have checked whether there are updates for my system available.

steam-223750.log

Symptoms

While using the most current, stable (non-beta) client (Proton 3.7-7), the game does not launch. The attached report shows errors.

Reproduction

Install DCS World Steam Edition, launch the game and acknowledge play via Steamplay.

@kisak-valve kisak-valve added the Game compatibility - Unofficial Games not expected to work without issues label Oct 12, 2018
@MrMinimal
Copy link

Same here.
System information: gist

@mlassnig
Copy link

mlassnig commented Apr 6, 2019

I got it to start (Proton 4.2-2, Nvidia 418.56) and authenticate by installing corefonts and vcrun2015 via protontricks. It came up in windowed mode, then I set it to fullscreen and all graphics options to the highest I could. So far so good, then I started a mission with A10-C. It loaded ok, but once it reached 100% it didn't continue. I had to SIGKILL the whole thing. It didn't start again after that so I removed the Config directory from the compatdata prefix. More humble in iteration two, I left everything as is (windowed, no graphics change), now the mission loaded fine, but then the whole process crashed when it tried to switch to in-flight.

@kisak-valve kisak-valve changed the title DCS World Steam Edition DCS World Steam Edition (223750) Apr 6, 2019
@h54
Copy link
Author

h54 commented May 18, 2019

@mlassnig I followed your instructions and got it running with proton 4.2-4. Everything is purple/pink (see attached screenshot) and I'm currently messing with the settings to see if I can fix it.

My System:

  • Ubuntu 19.04, kernel 5.0.0-15
  • GTX-1070, driver 418.56

What I did to get it running:

  • installed corefonts and vcrun2015 using winetricks. I used these instructions: https://github.com/redmcg/wine/wiki. DCS-World steam ID is 223750
  • ensured I have the latest release of proton enabled in Steam 4.2-4

Screenshot from 2019-05-18 15-26-21

@h54
Copy link
Author

h54 commented May 19, 2019

I got rid of the pink hue by turning off MSSA but no combination of settings seems to allow this to render correctly. I upgraded to nvidia-drivers-430 with the same results. See screenshots:

Screenshot from 2019-05-18 20-02-00

Screenshot from 2019-05-18 19-39-05

@berniyh
Copy link

berniyh commented Jun 16, 2019

Tried it with proton 4.2-7 mesa/radv and DXVK. Had to manually install corefonts using protontricks.

That did work, even in fullscreen and with MSAA activated. Also the activation and usage of DLC does work.
Performance was ok (35-40 fps on high profile with my RX Vega 64), but a bit worse than on Windows.

Also tried it with WINED3D, but there I get the same visual glitches as @h54.

@h54
Copy link
Author

h54 commented Aug 5, 2019

Using protontricks
protontricks 223750 vcrun2017 corefonts xact d3dcompiler_43
seemed to fix nearly all the issues I was having. Everything renders beautifully at 60fps with very high settings.

The only things I'm unsure about:

  • is the mouse supposed to control the camera inside/outside the aircraft? If so, it doesn't work.
  • Pressing for the map freezes the game. I have to use ALT+F4 and restart Steam but the game restarts just fine.

@berniyh
Copy link

berniyh commented Aug 5, 2019

* is the mouse supposed to control the camera inside/outside the aircraft?  If so, it doesn't work.

Inside the aircraft, no.
The aircraft usually have a clickable cockpit, so moving the mouse moves a cursor you can use to flip switches etc.
Not sure about outside of the cockpit from the top of my head.

@h54
Copy link
Author

h54 commented Aug 6, 2019

It runs really nicely!
Screenshot from 2019-08-02 21-50-35

@Preisschild
Copy link

@h54 did you get TrackIR and HOTAS working?

@h54
Copy link
Author

h54 commented Aug 11, 2019

@Preisschild not as of yet. LinuxTrack recognizes the device and is able to create a working profile for X-Plane but I'm not sure where to go for DCS.

@MrMinimal
Copy link

@h54 What is your joystick setup? Do you have one, if so how well does it work?

@h54
Copy link
Author

h54 commented Aug 11, 2019

@MrMinimal currently using a Gladiator Mk II and it worked out of the box with no issues. I just had to map buttons to where I wanted them.
https://store.x-plane.org/Gladiator-MK-II_p_595.html

@h54 h54 closed this as completed Aug 24, 2019
@h54
Copy link
Author

h54 commented Aug 24, 2019

Anyone have any luck getting the F10 map working? The game freezes (alt + F4 fixes that) and restarting Steam fixes it. To restart Steam, I have to kill 9 a bunch of steam processes.

@Preisschild
Copy link

@h54 reopen the issue please

@h54 h54 reopened this Aug 24, 2019
@berniyh
Copy link

berniyh commented Aug 25, 2019

Anyone have any luck getting the F10 map working? The game freezes (alt + F4 fixes that) and restarting Steam fixes it. To restart Steam, I have to kill 9 a bunch of steam processes.

Actually that works fine for me, no issues. Without applying any additional tricks, just what is mentioned above already.

btw, in my test yesterday I found that the performance is now significantly better and around the same as on Windows 7.
As I mentioned before, I had around 35-40 fps on high profile (just did a short test flight with the T51D and the Huey). Now I get 60-80 fps on high profile in the T51D.
Don't know what caused the improvement, might be a new kernel version, new mesa version, new wine/proton, DXVK or something else, but it's definitely better.

@Termuellinator
Copy link

It still crashes on launch for me :/
Only thing that caught my eye during protontricks installation was a lot of lines like this:
Executing cabextract -q -d /media/data/Spiele/Steam/steamapps/compatdata/223750/pfx/dosdevices/c:/windows/syswow64 -L -F xapofx*.dll /media/data/Spiele/Steam/steamapps/compatdata/223750/pfx/dosdevices/c:/windows/temp/_xact/oct2006_xact_x86.cab /media/data/Spiele/Steam/steamapps/compatdata/223750/pfx/dosdevices/c:/windows/temp/_xact/oct2006_xact_x86.cab: WARNING; possible 5960 extra bytes at end of file.

The Proton-Log states a pagefault, but nothing i can read anything out of. It doesn't create a subfolder "dcs" in "steamapps/compatdata/223750/pfx/dosdevices/c:/users/steamuser/Saved Games/" where the gamelog normaly should be iirc.

steam-223750.log

Happens both with ACO and RADV_PERFTEST=llvm

Maybe someone has any suggestion?

@berniyh
Copy link

berniyh commented Aug 26, 2019

Maybe something went wrong during the installation of the packages?
Did you try with a clean wine prefix?

@Termuellinator
Copy link

i just quit steam, deleted /steamapps/compatdata/223750/ and /steamapps/common/Proton 4.11/, restarted steam and verified proton 4.11 to download it again, started DCS (crash), ran "protontricks 223750 vcrun2013 corefonts xact d3dcompiler_43" and still got a crash :/
Is there any way to make proton "more clean"?

@berniyh
Copy link

berniyh commented Aug 26, 2019

No I think that'll do. I don't think it's proton then.
Maybe drivers or some part of the system or maybe a bad download for DCS or something else.

@h54
Copy link
Author

h54 commented Aug 27, 2019

@Termuellinator
Try adding dxvk
protontricks 223750 dxvk

@berniyh
I started with a clean wine prefix and can't get the F10 map to work. The game still crashes for me. Can you show me the output of the following?
protontricks 223750 list-installed

@Termuellinator
Copy link

Termuellinator commented Aug 27, 2019

@h54 didn't help either.
Seems to still be the same error if i read the log correctly:

1993.470:0033:0034:trace:seh:call_stack_handlers found wine frame 0x22fdf0 rsp 22ffe0 handler 0x7b4c0fe0
1993.470:0033:0034:trace:seh:call_teb_handler calling TEB handler 0x7b4c0fe0 (rec=0x22f7d0, frame=0x22fdf0 context=0x22eca0, dispatch=0x22ea40)
wine: Unhandled page fault on read access to 0x00000004 at address 0x1407024fa (thread 0034), starting debugger...
1993.470:0033:0034:trace:seh:start_debugger Starting debugger "winedbg --auto 51 232"
ERROR: ld.so: object '/home/termy/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

i disabled the steam overlay (because of the gameoverlayrenderer.se error), but still the same

@h54
Copy link
Author

h54 commented Aug 29, 2019

Have you checked out what other AMD users did on ProtonDB?
https://www.protondb.com/app/223750

@h54 didn't help either.
Seems to still be the same error if i read the log correctly:

1993.470:0033:0034:trace:seh:call_stack_handlers found wine frame 0x22fdf0 rsp 22ffe0 handler 0x7b4c0fe0
1993.470:0033:0034:trace:seh:call_teb_handler calling TEB handler 0x7b4c0fe0 (rec=0x22f7d0, frame=0x22fdf0 context=0x22eca0, dispatch=0x22ea40)
wine: Unhandled page fault on read access to 0x00000004 at address 0x1407024fa (thread 0034), starting debugger...
1993.470:0033:0034:trace:seh:start_debugger Starting debugger "winedbg --auto 51 232"
ERROR: ld.so: object '/home/termy/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

i disabled the steam overlay (because of the gameoverlayrenderer.se error), but still the same

@Termuellinator , have you checked out what other AMD users did on ProtonDB?
https://www.protondb.com/app/223750

@berniyh
Copy link

berniyh commented Aug 29, 2019

i disabled the steam overlay (because of the gameoverlayrenderer.se error), but still the same

That error you can ignore, it's just normal on 64bit systems.

Have you checked out what other AMD users did on ProtonDB?

I was the first here to report success with this game and I'm running an AMD CPU (FX 4350) and GPU (RX Vega). ;)

Also on Mesa and RADV.

@h54
Copy link
Author

h54 commented Oct 30, 2019

I upgraded to Ubuntu 19.10 with the packaged Nvidia 435 drivers and was getting frequent freezes. I had to start over with a clean Steam prefix every time afterwards. Downgrading to the 430 drivers (graphics drivers PPA) fixed it. Anyone else experience this? Also, the F10 map still crashes the game.

@TheZoq2
Copy link

TheZoq2 commented Nov 1, 2019

The game runs pretty much flawlessly on 4.11.7 for me. The one annoying issue is the F10 map crash which I don't seem to be alone in experiencing. What makes it even worse is that I have to remove and re-create the whole prefix after it happens.

@berniyh You said the F10 map works fine for you. Would you mind posting more info about your setup?

@TheZoq2
Copy link

TheZoq2 commented Nov 1, 2019

Update: I found a very simple solution to the problem. The map isn't the issue, it's the F10 key itself. Try pressing it in the main menu and it will still crash the game. So, the solution is to just rebind the key to anything else.

Also, I ran a diff of a working and non-working prefix, and it looks like the crash causes two files to appear:

pfx/drive_c/windows/system32/wbemprox.dll
pfx/drive_c/windows/system32/lsteamclient.dll

The latter is the one that is causing the game to not start again, so removing it saves you from having to reset your whole prefix after a crash.

@Fell
Copy link

Fell commented May 8, 2024

I noticed that in Wine scrolling/zooming/panning around the map (F10) too much causes it to leak graphics memory. It was occupying all 12 GB at the end. Can anyone confirm that with Proton?

Arch Linux, NVIDIA RTX 2080 Ti, proprietary drivers, Wine 9.8, DXVK 2.3.2

@SkippTekk
Copy link

Compatibility Report

Name of the game with compatibility issues: DCS world
Steam AppID of the game: 223750 (non steam version)

System Information

GPU: 5700xt
Video driver version: amdgpu (not sure how to properly get the data)
Kernel version: 6.8.9-arch1-2 endeavourOS
Link to full system information report as [Gist](https://gist.github.com/): https://gist.github.com/SkippTekk/ead9f9bb34cef96ffdb51a5372f37a78
Proton version: proton experimental

I confirm:

[x ] that I haven't found an existing compatibility report for this game.
[ x] that I have checked whether there are updates for my system available.

Symptoms
Reproduction

Load DCS, trial the Apache and turn it on, gets Box's instead of text's. Hover over the box's and text shows but doesn't once the curser (monitor mouse in game) leaves it goes back into a black box.

Screenshot from 2024-05-14 17-13-49

@SkippTekk
Copy link

I noticed that in Wine scrolling/zooming/panning around the map (F10) too much causes it to leak graphics memory. It was occupying all 12 GB at the end. Can anyone confirm that with Proton?

Arch Linux, NVIDIA RTX 2080 Ti, proprietary drivers, Wine 9.8, DXVK 2.3.2

Yes the game devs intentionally put the game to take up practically all VRAM resources which is outrages.

@TheZoq2
Copy link

TheZoq2 commented May 16, 2024

Load DCS, trial the Apache and turn it on, gets Box's instead of text's.

This problem is known and caused by weird settings on some textures. I have a script to fix it, remind me to post it tomorrow

@Fell
Copy link

Fell commented May 16, 2024

I noticed that in Wine scrolling/zooming/panning around the map (F10) too much causes it to leak graphics memory. It was occupying all 12 GB at the end. Can anyone confirm that with Proton?
Arch Linux, NVIDIA RTX 2080 Ti, proprietary drivers, Wine 9.8, DXVK 2.3.2

Yes the game devs intentionally put the game to take up practically all VRAM resources which is outrages.

Update: I have even experienced compositor crashes (kwin_wayland) due to failing VRAM allocations because the VRAM is actually full.

Note: Yes, DCS World is actually one of the few games which work nearly flawlessly with Wine's experimental Wayland support.

@SkippTekk
Copy link

Load DCS, trial the Apache and turn it on, gets Box's instead of text's.

This problem is known and caused by weird settings on some textures. I have a script to fix it, remind me to post it tomorrow

Just woken up and i just saw this. Maybe it's tomorrow for you now? xD

@TheZoq2
Copy link

TheZoq2 commented May 16, 2024

Technically no, but I'm at my home PC :D

Here is the script

#!/bin/bash

DCS_INSTALL="/home/frans/.local/share/Steam/steamapps/common/DCSWorld"

BROKEN_FILES="Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/FontMPD_64.tga
Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/FontMPD_64_bold.tga
Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/FontMPD_64_inv.tga
Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/FontMPD_64_inv_bold.tga
Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/indication_MPD.tga
Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/indication_MPD_1024.tga
Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/indication_MPD_WPN.tga
Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/indication_MPD_WPN_fon.tga
Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/MFD_dark_green.dds
Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/MFD_gray.dds
Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/MFD_green.dds
Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/MFD_white.dds
Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/MPD_VideoSymbology.dds
Mods/aircraft/AH-64D/Cockpit/IndicationResources/Displays/MPD/MPD_VideoSymbology_font.dds
Mods/aircraft/Mi-24P/Cockpit/IndicationTextures/9K113_bg.tga
Mods/aircraft/Mi-24P/Cockpit/IndicationTextures/9K113_Fixed_Grid.tga
Mods/aircraft/Mi-24P/Cockpit/IndicationTextures/9K113_Grid_3x.tga
Mods/aircraft/Mi-24P/Cockpit/IndicationTextures/9K113_Grid_3x_backlight.tga
Mods/aircraft/Mi-24P/Cockpit/IndicationTextures/9K113_Grid_10x.tga
Mods/aircraft/Mi-24P/Cockpit/IndicationTextures/9K113_Grid_10x_backlight.tga
Mods/aircraft/Mi-24P/Cockpit/IndicationTextures/9K113_Ready.tga
Mods/aircraft/Mi-24P/Cockpit/IndicationTextures/ASP17_flex_sight.tga
Mods/aircraft/Mi-24P/Cockpit/IndicationTextures/font_arcade.tga
Mods/aircraft/Mi-24P/Cockpit/IndicationTextures/font_general.tga
Mods/aircraft/Mi-24P/Cockpit/IndicationTextures/GOST_BU.TTF
Mods/aircraft/Mi-24P/Cockpit/IndicationTextures/HelperAI_common.dds
Mods/aircraft/Mi-24P/Cockpit/IndicationTextures/PKV_Grid.tga
Mods/aircraft/Ka-50_3/Cockpit/IndicationTextures/SHKVAL_MASK.bmp"

while read -r file; do
    FULL_PATH="$DCS_INSTALL/$file"
    echo "Converting ${FULL_PATH}"
    cp "${FULL_PATH}" "${FULL_PATH}.original"
    convert "${FULL_PATH}" "${FULL_PATH}"
done <<< "$BROKEN_FILES"

You'll need to adjust the first variable to your game install path.

The digits showing the number of chaff and flares is still broken. There is probably another texture in there that can be patched, but I haven't bothered to figure out which one.

Also, this breaks strict integrity check but only if you fly the apache. So don't slot into an apache on a server that requires pure textures, and if you try to join one after flying the apache, you'll need to restart.

It also fixes the mi-24 gunsight and ka-50-II monitor if you're into those. Same deal with IC there

@SkippTekk
Copy link

@TheZoq2 Thank you that has worked! Buuuuut i can't join the servers i like but you did warn about that :P

@SkippTekk
Copy link

Well, it works! Just bitches on 2 files. so gonna try and "fake" it to think it's legit....

@TheZoq2
Copy link

TheZoq2 commented May 17, 2024

If you do manage to fake it, let me know. Would be nice to be able to fly those aircraft on servers with strict IC

@aCeTotal
Copy link

aCeTotal commented May 17, 2024

Hello. Has anyone managed to extract Telemetry data with Linux? Seems like Export.lua has no effect on Linux.

Can u show ur export Lua and log file ? Export Lua should run just fine

Hi, thank you for trying to help me. What I am trying to achieve is that data specified in Export.lua is sent over a TCP connection. I have written a cpp tcp-program that listens to ip and port, but it cannot receive anything and I cannot find any error messages in the log file.

DCS Log file: https://pastebin.com/QcFgk0Lt
Export.lua: https://pastebin.com/iXFVWnQ8

The path: /home/total/.local//share/Steam/steamapps/compatdata/223750/pfx/drive_c/users/steamuser/Saved%20Games/DCS/Export.lua

@gallexme
Copy link

gallexme commented May 17, 2024 via email

@aCeTotal
Copy link

Oh, thank you blush

@Woazboat
Copy link

The new F-4 Phantom module is unfortunately broken and gets stuck in the loading screen when using Proton on Linux.
https://steamcommunity.com/app/223750/discussions/0/4334230222054697344/

@alexeijd
Copy link

The Heatblur F-4E is not working for me - the following is showing up in the proton log:

0134:trace:loaddll:build_module Loaded L"Z:\Steam\steamapps\common\DCSWorld\Mods\aircraft\F-4E\bin\lua51.dll" at 00006FFFD1430000: native
0134:trace:loaddll:build_module Loaded L"C:\windows\system32\MSVCP140_ATOMIC_WAIT.dll" at 00006FFFD02B0000: builtin
0134:trace:loaddll:build_module Loaded L"Z:\Steam\steamapps\common\DCSWorld\Mods\aircraft\F-4E\bin\HeatblurJester.dll" at 00006FFFD02D0000: native
0134:trace:loaddll:build_module Loaded L"Z:\Steam\steamapps\common\DCSWorld\Mods\aircraft\F-4E\bin\HeatblurUiLib.dll" at 00006FFFD0240000: native
0134:err:module:import_dll Library F-4E-Nextgen.dll (which is needed by L"Z:\Steam\steamapps\common\DCSWorld\Mods\aircraft\F-4E\bin\F-4E-FlightModel.dll") not found
0134:trace:loaddll:build_module Loaded L"Z:\Steam\steamapps\common\DCSWorld\Mods\aircraft\F-4E\bin\F-4E-Nextgen.dll" at 00006FFFCD180000: native
0134:trace:loaddll:build_module Loaded L"Z:\Steam\steamapps\common\DCSWorld\Mods\aircraft\F-4E\bin\F-4E-FlightModel.dll" at 00007FFFFEDB0000: native
0134:trace:loaddll:build_module Loaded L"Z:\Steam\steamapps\common\DCSWorld\Mods\aircraft\F-4E\bin\F-4E-Avionics.dll" at 00006FFFCB7C0000: native

Symlinking F-4E-Nextgen.dll into the main DCS directory doesn't work, peldd shows the following libraries linked:

peldd F-4E-Nextgen.dll
Dependencies
HeatblurJester.dll
lua51.dll
HeatblurDCSBase.dll
CockpitBase.dll
edCore.dll
edObjects.dll
Flight.dll
GraphicsVista.dll
Inter.dll
Transport.dll
Weather.dll
WorldGeneral.dll
ImGui.dll
HeatblurComponents.dll
HeatblurCore.dll
MSVCP140.dll
VCRUNTIME140.dll
VCRUNTIME140_1.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
KERNEL32.dll
KERNEL32.dll
KERNEL32.dll

Everything else is working fine,other than the usual glitches

@TheZoq2
Copy link

TheZoq2 commented May 26, 2024

We have some discussion around the broken F4 in https://matrix.to/#/#dcs-on-linux:matrix.org. The working theory there is that it is a subsequent DLL load that is being loaded from the wrong directory

@Woazboat
Copy link

Woazboat commented May 26, 2024

Symlinking the dll file in bin-mt/ does allow F-4E-Nextgen.dll to be loaded, but then there's an exception when loading/initializing F-4E-Avionics.dll.

Click to expand
0184:trace:module:load_dll looking for L"C:/Program Files/Eagle Dynamics/DCS World/Mods/aircraft/F-4E/bin/F-4E-Avionics.dll" in L"C:\\Program Files\\Eagle Dynamics\\DCS World\\bin-mt;C:\\windows\\system32;C:\\windows\\system;C:\\windows;.;C:\\windows\\system32;C:\\windows;C:\\windows\\system32\\wbem;C:\\windows\\system32\\WindowsPowershell\\v1.0"
0184:trace:module:get_load_order looking for L"C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll"
0184:trace:module:get_load_order got hardcoded default for L"C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll"
0184:warn:module:find_builtin_dll cannot find builtin library for L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll"
0184:trace:module:map_image_into_view mapping PE file L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" at 0x90f150000-0x910af5000
0184:trace:module:map_image_into_view mapping L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" section .text at 0x90f151000 off 0 size 0 virt 4b698f flags 68000020
0184:trace:module:map_image_into_view mapping L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" section .rdata at 0x90f608000 off 0 size 0 virt 1bb7c4 flags 48000040
0184:trace:module:map_image_into_view mapping L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" section .data at 0x90f7c4000 off 0 size 0 virt 2e7580 flags c0000040
0184:trace:module:map_image_into_view mapping L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" section .pdata at 0x90faac000 off 0 size 0 virt 1fb6c flags 48000040
0184:trace:module:map_image_into_view mapping L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" section .UPX0 at 0x90facc000 off 0 size 0 virt 1b4 flags 48000040
0184:trace:module:map_image_into_view mapping L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" section .UPX1 at 0x90facd000 off 0 size 0 virt 17c00 flags 48000040
0184:trace:module:map_image_into_view mapping L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" section .UPX2 at 0x90fae5000 off 0 size 0 virt 14d flags 68000020
0184:trace:module:map_image_into_view mapping L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" section .UPX3 at 0x90fae6000 off 0 size 0 virt 50a flags 48000040
0184:trace:module:map_image_into_view mapping L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" section .UPX4 at 0x90fae7000 off 0 size 0 virt 530e84 flags 68000020
0184:trace:module:map_image_into_view mapping L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" section .UPX5 at 0x910018000 off 400 size 3200 virt 30d8 flags c0000040
0184:trace:module:map_image_into_view clearing 0x91001b200 - 0x91001c000
0184:trace:module:map_image_into_view mapping L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" section .UPX6 at 0x91001c000 off 3600 size ad6c00 virt ad6a1c flags 68000060
0184:trace:module:map_image_into_view clearing 0x910af2c00 - 0x910af3000
0184:trace:module:map_image_into_view mapping L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" section .reloc at 0x910af3000 off ada200 size 200 virt 128 flags 40000040
0184:trace:module:map_image_into_view clearing 0x910af3200 - 0x910af4000
0184:trace:module:map_image_into_view mapping L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" section .rsrc at 0x910af4000 off ada400 size 200 virt 1b2 flags 40000040
0184:trace:module:map_image_into_view clearing 0x910af4200 - 0x910af5000
0184:trace:module:perform_relocations relocating from 0000000180000000-00000001819A5000 to 000000090F150000-0000000910AF5000
0184:trace:module:set_security_cookie initializing security cookie 000000090F7C5CA8
0184:trace:module:alloc_tls_slot module 000000090F150000 data 000000091001B0D0-000000091001B0D8 zerofill 0 index 000000090FAAAFA0 callback 0000000000000000 flags 300000 -> slot 82
0184:trace:module:alloc_tls_slot thread 02f4 slot 82: 8/0 bytes at 000000050CCEEC00
0184:trace:module:alloc_tls_slot thread 02f0 slot 82: 8/0 bytes at 000000050CCEEC30
0184:trace:module:alloc_tls_slot thread 02ec slot 82: 8/0 bytes at 000000050CCEEC60
0184:trace:module:alloc_tls_slot thread 02e8 slot 82: 8/0 bytes at 000000050CCEEC90
0184:trace:module:alloc_tls_slot thread 02e4 slot 82: 8/0 bytes at 000000050CCEECC0
0184:trace:module:alloc_tls_slot thread 02e0 slot 82: 8/0 bytes at 000000050CCEECF0
0184:trace:module:alloc_tls_slot thread 02dc slot 82: 8/0 bytes at 000000050CCEED20
0184:trace:module:alloc_tls_slot thread 02d8 slot 82: 8/0 bytes at 000000050CCEED50
0184:trace:module:alloc_tls_slot thread 02d4 slot 82: 8/0 bytes at 000000050CCEED80
0184:trace:module:alloc_tls_slot thread 02d0 slot 82: 8/0 bytes at 000000050CCEEDB0
0184:trace:module:alloc_tls_slot thread 02cc slot 82: 8/0 bytes at 000000050CCEEDE0
0184:trace:module:alloc_tls_slot thread 02c4 slot 82: 8/0 bytes at 000000050CCEEE10
0184:trace:module:alloc_tls_slot thread 02c0 slot 82: 8/0 bytes at 000000050CCEEE40
0184:trace:module:alloc_tls_slot thread 02bc slot 82: 8/0 bytes at 000000050CCEEE70
0184:trace:module:alloc_tls_slot thread 02b8 slot 82: 8/0 bytes at 000000050CCEEEA0
0184:trace:module:alloc_tls_slot thread 02b4 slot 82: 8/0 bytes at 000000050CCEEED0
0184:trace:module:alloc_tls_slot thread 02b0 slot 82: 8/0 bytes at 000000050CCEEF00
0184:trace:module:alloc_tls_slot thread 02ac slot 82: 8/0 bytes at 000000050CCEEF30
0184:trace:module:alloc_tls_slot thread 02a8 slot 82: 8/0 bytes at 000000050CCEEF60
0184:trace:module:alloc_tls_slot thread 02a4 slot 82: 8/0 bytes at 000000050CCEEF90
0184:trace:module:alloc_tls_slot thread 02a0 slot 82: 8/0 bytes at 000000050CCEEFC0
0184:trace:module:alloc_tls_slot thread 029c slot 82: 8/0 bytes at 000000050CCEEFF0
0184:trace:module:alloc_tls_slot thread 0298 slot 82: 8/0 bytes at 000000050CCEF020
0184:trace:module:alloc_tls_slot thread 0294 slot 82: 8/0 bytes at 000000050CCF17D0
0184:trace:module:alloc_tls_slot thread 0288 slot 82: 8/0 bytes at 000000050CCF1800
0184:trace:module:alloc_tls_slot thread 0290 slot 82: 8/0 bytes at 000000050CCF1830
0184:trace:module:alloc_tls_slot thread 028c slot 82: 8/0 bytes at 000000050CCF1860
0184:trace:module:alloc_tls_slot thread 0284 slot 82: 8/0 bytes at 000000050CCF1890
0184:trace:module:alloc_tls_slot thread 0280 slot 82: 8/0 bytes at 000000050CCF18C0
0184:trace:module:alloc_tls_slot thread 027c slot 82: 8/0 bytes at 000000050CCF18F0
0184:trace:module:alloc_tls_slot thread 0278 slot 82: 8/0 bytes at 000000050CCF1920
0184:trace:module:alloc_tls_slot thread 0274 slot 82: 8/0 bytes at 000000050CCF1950
0184:trace:module:alloc_tls_slot thread 0270 slot 82: 8/0 bytes at 000000050CCF1980
0184:trace:module:alloc_tls_slot thread 026c slot 82: 8/0 bytes at 000000050CCF19B0
0184:trace:module:alloc_tls_slot thread 0268 slot 82: 8/0 bytes at 000000050CCF19E0
0184:trace:module:alloc_tls_slot thread 0264 slot 82: 8/0 bytes at 000000050CCF1A10
0184:trace:module:alloc_tls_slot thread 0260 slot 82: 8/0 bytes at 000000050CCF1A40
0184:trace:module:alloc_tls_slot thread 025c slot 82: 8/0 bytes at 000000050CCF1A70
0184:trace:module:alloc_tls_slot thread 0258 slot 82: 8/0 bytes at 000000050CCF1AA0
0184:trace:module:alloc_tls_slot thread 0254 slot 82: 8/0 bytes at 000000050CCF1AD0
0184:trace:module:alloc_tls_slot thread 0248 slot 82: 8/0 bytes at 000000050CCF1B00
0184:trace:module:alloc_tls_slot thread 0240 slot 82: 8/0 bytes at 000000050CCF1B30
0184:trace:module:alloc_tls_slot thread 023c slot 82: 8/0 bytes at 000000050CCF1B60
0184:trace:module:alloc_tls_slot thread 0238 slot 82: 8/0 bytes at 000000050CCF1B90
0184:trace:module:alloc_tls_slot thread 0234 slot 82: 8/0 bytes at 000000050CCF1BC0
0184:trace:module:alloc_tls_slot thread 022c slot 82: 8/0 bytes at 000000050CCF1BF0
0184:trace:module:alloc_tls_slot thread 01e0 slot 82: 8/0 bytes at 000000050CCF1C20
0184:trace:module:alloc_tls_slot thread 01dc slot 82: 8/0 bytes at 000000050CCF1C50
0184:trace:module:alloc_tls_slot thread 01d8 slot 82: 8/0 bytes at 000000050CCF1C80
0184:trace:module:alloc_tls_slot thread 01d4 slot 82: 8/0 bytes at 000000050CCF1CB0
0184:trace:module:alloc_tls_slot thread 01d0 slot 82: 8/0 bytes at 000000050CCF1CE0
0184:trace:module:alloc_tls_slot thread 01cc slot 82: 8/0 bytes at 000000050CCF1D10
0184:trace:module:alloc_tls_slot thread 01c8 slot 82: 8/0 bytes at 000000050CCF1D40
0184:trace:module:alloc_tls_slot thread 01c4 slot 82: 8/0 bytes at 000000050CCF1D70
0184:trace:module:alloc_tls_slot thread 01c0 slot 82: 8/0 bytes at 000000050CCF1DC0
0184:trace:module:alloc_tls_slot thread 01bc slot 82: 8/0 bytes at 000000050CCF1DF0
0184:trace:module:alloc_tls_slot thread 01b8 slot 82: 8/0 bytes at 000000050CCF1E20
0184:trace:module:alloc_tls_slot thread 01b4 slot 82: 8/0 bytes at 000000050CCF1E50
0184:trace:module:alloc_tls_slot thread 01b0 slot 82: 8/0 bytes at 000000050CCF1E80
0184:trace:module:alloc_tls_slot thread 01ac slot 82: 8/0 bytes at 000000050CCF1EB0
0184:trace:module:alloc_tls_slot thread 01a8 slot 82: 8/0 bytes at 000000050CCF1EE0
0184:trace:module:alloc_tls_slot thread 01a4 slot 82: 8/0 bytes at 000000050CCF1F10
0184:trace:module:alloc_tls_slot thread 01a0 slot 82: 8/0 bytes at 000000050CCF1F40
0184:trace:module:alloc_tls_slot thread 019c slot 82: 8/0 bytes at 000000050CCF1F70
0184:trace:module:alloc_tls_slot thread 018c slot 82: 8/0 bytes at 000000050CCF1FA0
0184:trace:module:alloc_tls_slot thread 0188 slot 82: 8/0 bytes at 000000050CCF1FD0
0184:trace:module:alloc_tls_slot thread 0184 slot 82: 8/0 bytes at 000000050CCF2000

...

0184:trace:module:build_module loaded L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" 0000000A3F792EA0 000000090F150000
0184:trace:loaddll:build_module Loaded L"C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" at 000000090F150000: native
0184:trace:module:load_dll Loaded module L"\\??\\C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" at 000000090F150000
0184:trace:module:process_attach (L"F-4E-Avionics.dll",0000000000000000) - START
0184:trace:module:MODULE_InitDLL (000000090F150000 L"F-4E-Avionics.dll",PROCESS_ATTACH,0000000000000000) - CALL
0184:warn:seh:dispatch_exception backtrace: --- Exception 0x80000004.
0184:trace:seh:dispatch_exception code=80000004 flags=0 addr=0000000910896DB0 ip=910896db0
0184:warn:seh:dispatch_exception EXCEPTION_SINGLE_STEP exception (code=80000004) raised
0184:trace:seh:dispatch_exception  rax=00000000dccfc378 rbx=0000000000000000 rcx=00000000deadc0de rdx=000000000000184c
0184:trace:seh:dispatch_exception  rsi=0000000000000000 rdi=0000000000000000 rbp=000000000011cec0 rsp=000000000011ce70
0184:trace:seh:dispatch_exception   r8=000000000000003c  r9=000000000003e000 r10=000000000000df48 r11=00000009100a0286
0184:trace:seh:dispatch_exception  r12=00000000ff17c09c r13=0000000000000000 r14=0000000000000040 r15=000000090f150000
0184:trace:seh:call_vectored_handlers calling handler at 000000021B4407B0 code=80000004 flags=0
0184:trace:seh:call_vectored_handlers handler at 000000021B4407B0 returned 0
0184:trace:seh:call_vectored_handlers calling handler at 000000035917ADF0 code=80000004 flags=0
0184:trace:seh:call_vectored_handlers handler at 000000035917ADF0 returned 0
0184:trace:seh:call_vectored_handlers calling handler at 000000027109CF20 code=80000004 flags=0
0184:trace:seh:call_vectored_handlers handler at 000000027109CF20 returned 0
0184:trace:seh:call_vectored_handlers calling handler at 00000002EDFCCAD0 code=80000004 flags=0
0184:trace:seh:call_vectored_handlers handler at 00000002EDFCCAD0 returned 0
0184:trace:seh:call_vectored_handlers calling handler at 0000000180007320 code=80000004 flags=0
0184:trace:seh:call_vectored_handlers handler at 0000000180007320 returned 0
0184:warn:seh:virtual_unwind backtrace: 0000000910896DB0: L"F-4E-Avionics.dll" + 0000000001746DB0.
0184:trace:unwind:RtlVirtualUnwind type 1 rip 910896db0 rsp 11ce70
0184:trace:unwind:dump_unwind_info **** func 1746b9b-1746f18
0184:trace:unwind:dump_unwind_info unwind info at 000000091002FF9C flags 1 prolog 0x19 bytes function 0000000910896B9B-0000000910896F18
0184:trace:unwind:dump_unwind_info     frame register rbp offset 0x50(%rsp)
0184:trace:unwind:dump_unwind_info     0x19: leaq 0x50(%rsp),rbp
0184:trace:unwind:dump_unwind_info     0x14: subq $0xa88,%rsp
0184:trace:unwind:dump_unwind_info     0xd: pushq %r15
0184:trace:unwind:dump_unwind_info     0xb: pushq %r14
0184:trace:unwind:dump_unwind_info     0x9: pushq %r13
0184:trace:unwind:dump_unwind_info     0x7: pushq %r12
0184:trace:unwind:dump_unwind_info     0x5: pushq %rdi
0184:trace:unwind:dump_unwind_info     0x4: pushq %rsi
0184:trace:unwind:dump_unwind_info     0x3: pushq %rbx
0184:trace:unwind:dump_unwind_info     0x2: pushq %rbp
0184:trace:unwind:dump_unwind_info     handler 000000090FB061B0 data at 000000091002FFBC
0184:trace:seh:call_handler calling handler 000000090FB061B0 (rec=000000000011CC30, frame=000000000011CE70 context=000000000011C190, dispatch=000000000011C060)
0184:trace:unwind:RtlUnwindEx code=80000004 flags=2 end_frame=000000000011CE70 target_ip=0000000910896DCB rip=000000017005c988
0184:trace:unwind:RtlUnwindEx  rax=000000007fee0000 rbx=000000091002ffd8 rcx=000000000011c190 rdx=0000000910896dcb
0184:trace:unwind:RtlUnwindEx  rsi=000000000011c190 rdi=000000000011ba30 rbp=000000000011ba30 rsp=000000000011b8d0
0184:trace:unwind:RtlUnwindEx   r8=000000000011cc30  r9=ffffffff80000004 r10=00007f0acbc37620 r11=0000000000000202
0184:trace:unwind:RtlUnwindEx  r12=000000000011cc30 r13=000000000011c190 r14=000000000011c060 r15=000000000011dac0
0184:trace:unwind:RtlVirtualUnwind type 2 rip 17005c988 rsp 11b8d0
0184:trace:unwind:dump_unwind_info **** func 5c930-5d0d6
0184:trace:unwind:dump_unwind_info unwind info at 000000017008AAA8 flags 0 prolog 0x13 bytes function 000000017005C930-000000017005D0D6
0184:trace:unwind:dump_unwind_info     0x13: subq $0x638,%rsp
0184:trace:unwind:dump_unwind_info     0xc: pushq %rbx
0184:trace:unwind:dump_unwind_info     0xb: pushq %rsi
0184:trace:unwind:dump_unwind_info     0xa: pushq %rdi
0184:trace:unwind:dump_unwind_info     0x9: pushq %rbp
0184:trace:unwind:dump_unwind_info     0x8: pushq %r12
0184:trace:unwind:dump_unwind_info     0x6: pushq %r13
0184:trace:unwind:dump_unwind_info     0x4: pushq %r14
0184:trace:unwind:dump_unwind_info     0x2: pushq %r15
0184:trace:unwind:RtlVirtualUnwind type 2 rip 90fb062b5 rsp 11bf50
0184:trace:unwind:dump_unwind_info **** func 9b61b0-9b6351
0184:trace:unwind:dump_unwind_info unwind info at 000000090FB155E8 flags 0 prolog 0x20 bytes function 000000090FB061B0-000000090FB06351
0184:trace:unwind:dump_unwind_info     0x20: movq %rsi,0x88(%rsp)
0184:trace:unwind:dump_unwind_info     0x20: movq %rbp,0x80(%rsp)
0184:trace:unwind:dump_unwind_info     0x20: movq %rbx,0x70(%rsp)
0184:trace:unwind:dump_unwind_info     0x20: subq $0x40,%rsp
0184:trace:unwind:dump_unwind_info     0x1c: pushq %r15
0184:trace:unwind:dump_unwind_info     0x1a: pushq %r14
0184:trace:unwind:dump_unwind_info     0x18: pushq %r13
0184:trace:unwind:dump_unwind_info     0x16: pushq %r12
0184:trace:unwind:dump_unwind_info     0x14: pushq %rdi
0184:trace:unwind:RtlVirtualUnwind type 2 rip 170059854 rsp 11bfc0
0184:trace:unwind:dump_unwind_info **** func 5984c-5985a
0184:trace:unwind:dump_unwind_info unwind info at 000000017008A8F0 flags 1 prolog 0x0 bytes function 000000017005984C-000000017005985A
0184:trace:unwind:dump_unwind_info     0x4: subq $0x28,%rsp
0184:trace:unwind:dump_unwind_info     handler 000000017005A010 data at 000000017008A8FC
0184:trace:unwind:RtlVirtualUnwind type 2 rip 17005bac5 rsp 11bff0
0184:trace:unwind:dump_unwind_info **** func 5b9c0-5bec1
0184:trace:unwind:dump_unwind_info unwind info at 000000017008AA50 flags 0 prolog 0x13 bytes function 000000017005B9C0-000000017005BEC1
0184:trace:unwind:dump_unwind_info     0x13: subq $0x678,%rsp
0184:trace:unwind:dump_unwind_info     0xc: pushq %rbx
0184:trace:unwind:dump_unwind_info     0xb: pushq %rsi
0184:trace:unwind:dump_unwind_info     0xa: pushq %rdi
0184:trace:unwind:dump_unwind_info     0x9: pushq %rbp
0184:trace:unwind:dump_unwind_info     0x8: pushq %r12
0184:trace:unwind:dump_unwind_info     0x6: pushq %r13
0184:trace:unwind:dump_unwind_info     0x4: pushq %r14
0184:trace:unwind:dump_unwind_info     0x2: pushq %r15
0184:trace:unwind:RtlVirtualUnwind type 2 rip 17005c1e9 rsp 11c6b0
0184:trace:unwind:dump_unwind_info **** func 5bed0-5c49e
0184:trace:unwind:dump_unwind_info unwind info at 000000017008AA68 flags 0 prolog 0x10 bytes function 000000017005BED0-000000017005C49E
0184:trace:unwind:dump_unwind_info     0x10: subq $0x48,%rsp
0184:trace:unwind:dump_unwind_info     0xc: pushq %rbx
0184:trace:unwind:dump_unwind_info     0xb: pushq %rsi
0184:trace:unwind:dump_unwind_info     0xa: pushq %rdi
0184:trace:unwind:dump_unwind_info     0x9: pushq %rbp
0184:trace:unwind:dump_unwind_info     0x8: pushq %r12
0184:trace:unwind:dump_unwind_info     0x6: pushq %r13
0184:trace:unwind:dump_unwind_info     0x4: pushq %r14
0184:trace:unwind:dump_unwind_info     0x2: pushq %r15
0184:trace:unwind:RtlVirtualUnwind type 2 rip 170059886 rsp 11c740
0184:trace:unwind:dump_unwind_info **** func 5985c-59887
0184:trace:unwind:dump_unwind_info unwind info at 000000017008A8FC flags 0 prolog 0x0 bytes function 000000017005985C-0000000170059887
0184:trace:unwind:dump_unwind_info     0x0: movq %r15,0xf0(%rsp)
0184:trace:unwind:dump_unwind_info     0x0: movq %r14,0xe8(%rsp)
0184:trace:unwind:dump_unwind_info     0x0: movq %r13,0xe0(%rsp)
0184:trace:unwind:dump_unwind_info     0x0: movq %r12,0xd8(%rsp)
0184:trace:unwind:dump_unwind_info     0x0: movq %rdi,0xb0(%rsp)
0184:trace:unwind:dump_unwind_info     0x0: movq %rsi,0xa8(%rsp)
0184:trace:unwind:dump_unwind_info     0x0: movq %rbp,0xa0(%rsp)
0184:trace:unwind:dump_unwind_info     0x0: movq %rbx,0x90(%rsp)
0184:trace:unwind:dump_unwind_info     0x0: subq $0x590,%rsp
0184:trace:unwind:dump_unwind_info     0x0: PUSH_MACHFRAME 0
0184:trace:unwind:RtlVirtualUnwind type 2 rip 910896db0 rsp 11ce70
0184:trace:unwind:dump_unwind_info **** func 1746b9b-1746f18
0184:trace:unwind:dump_unwind_info unwind info at 000000091002FF9C flags 1 prolog 0x19 bytes function 0000000910896B9B-0000000910896F18
0184:trace:unwind:dump_unwind_info     frame register rbp offset 0x50(%rsp)
0184:trace:unwind:dump_unwind_info     0x19: leaq 0x50(%rsp),rbp
0184:trace:unwind:dump_unwind_info     0x14: subq $0xa88,%rsp
0184:trace:unwind:dump_unwind_info     0xd: pushq %r15
0184:trace:unwind:dump_unwind_info     0xb: pushq %r14
0184:trace:unwind:dump_unwind_info     0x9: pushq %r13
0184:trace:unwind:dump_unwind_info     0x7: pushq %r12
0184:trace:unwind:dump_unwind_info     0x5: pushq %rdi
0184:trace:unwind:dump_unwind_info     0x4: pushq %rsi
0184:trace:unwind:dump_unwind_info     0x3: pushq %rbx
0184:trace:unwind:dump_unwind_info     0x2: pushq %rbp
0184:trace:unwind:dump_unwind_info     handler 000000090FB061B0 data at 000000091002FFBC
0184:trace:seh:RtlRestoreContext returning to 0000000910896DCB stack 000000000011CE70
0184:trace:module:LdrGetDllFullName module 0000000000000000, name 000000000011C9E0.
0184:trace:module:GetModuleFileNameW L"C:\\Program Files\\Eagle Dynamics\\DCS World\\bin-mt\\DCS.exe"
0184:trace:module:LdrGetDllHandleEx flags 0x1, load_path 0000000000000000, dll_characteristics 0000000000000000, name 000000000011D870, base 000000000011D868.
0184:trace:module:LdrGetDllHandleEx L"World" -> 0000000001F40000 (load path (null))
0184:trace:module:LdrGetDllHandleEx flags 0x1, load_path 0000000000000000, dll_characteristics 0000000000000000, name 000000000011D7E0, base 000000000011D7D8.
0184:trace:module:find_dll_file found L"C:\\windows\\system32\\kernelbase.dll" for L"api-ms-win-core-synch-l1-2-0.dll"
0184:trace:module:LdrGetDllHandleEx L"api-ms-win-core-synch-l1-2-0.dll" -> 000000007B000000 (load path (null))
0184:trace:module:MODULE_InitDLL (000000090F150000,PROCESS_ATTACH,0000000000000000) - RETURN 1
0184:trace:module:process_attach (L"F-4E-Avionics.dll",0000000000000000) - END
0184:trace:module:load_dll looking for L"F-4E-Avionics.dll" in L"C:/Program Files/Eagle Dynamics/DCS World/Mods/aircraft/F-4E/bin/"
0184:trace:module:load_dll Found L"C:\\Program Files\\Eagle Dynamics\\DCS World\\Mods\\aircraft\\F-4E\\bin\\F-4E-Avionics.dll" for L"F-4E-Avionics.dll" at 000000090F150000, count=2
0184:trace:module:LdrGetDllHandleEx flags 0x1, load_path 0000000000000000, dll_characteristics 0000000000000000, name 000000000011DD50, base 000000000011DD48.
0184:trace:module:LdrGetDllHandleEx L"F-4E-Avionics.dll" -> 000000090F150000 (load path (null))

@cymax95
Copy link

cymax95 commented May 27, 2024

Good day.
I hope this is the correct place to ask. I have searched and found an old discussion about it being a Linux issue. But this is from 2021 and was curious if this was still an issue as I am also experiencing the odd smoke trails as below.

image

Thank you for any help.

@TheZoq2
Copy link

TheZoq2 commented May 27, 2024

@cymax95 yep, that is a known issue that I don't think anyone has found a fix for. Last time I investigated it, it seemed to be related to tesselation

@bonkzwonil
Copy link

bonkzwonil commented May 27, 2024

runs great for me
Getting smooth ~170 fps (all default) / ~ 120 fps (all High) in the Huey (Free flight Caucasus) (way smoother than under windooze)

System:

  • guix / kernel 6.1.86
  • RTX 3070
  • nvda 535.54.03
  • Res 2560x1440
  • unbound back to steam version (steam via flatpak)
  • proton experimental
  • protontricks 223750 vcrun2019 xact d3dcompiler_43 dxvk
  • No special startup options
  • running the MT starter

Quite happy with it.

image

@cymax95
Copy link

cymax95 commented May 27, 2024

@cymax95 yep, that is a known issue that I don't think anyone has found a fix for. Last time I investigated it, it seemed to be related to tesselation

Thank you @TheZoq2 for your reply.
Do we know if it is being looked into? I am very happy I am able to play in Linux. This is thus far the only visual issue i have noticed since I started playing months ago. I guess I am curious if it will be resolved or if it is just one of those things.

@TheZoq2
Copy link

TheZoq2 commented May 27, 2024

I'm not aware of anyone looking into it. I think ED doesn't care but it might be worth reporting to the dxvk devs I guess.

Though with vulkan coming to dcs in """"two weeks ™️ """, i'm hoping it'll be resolved eventually

@kisak-valve
Copy link
Member

[BUG] xrCreateInstance failed in DCS

Issue transferred from ValveSoftware/SteamVR-for-Linux#734.
@makerio90 posted on 2024-08-20T21:19:58:

Describe the bug
when trying to open dcs in vr mode, the game crashed instantly. viewing log files shows a xrCreateInstance failed error

To Reproduce
Steps to reproduce the behavior:

  1. dcs latest version,
  2. steamvr any beta (im using beta but still occurs on main release)
  3. launch dcs
  4. nothing happens, game crashes seconds later.

Expected behavior
game should open normally

System Information (please complete the following information):
Please use the latest Steam beta client and SteamVR beta for your bug reports!

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context

  • The game worked before, its only recently that it broke.
  • other vr games work
  • if the logs for dcs arent in one of those tarballs lmk i can copy-paste

@DrymarchonShaun
Copy link

I've followed https://github.com/deleterium/dcs_on_linux trying to get the open beta version of the game (on Steam) to work but no matter what I try I'm getting a black screen on launch, with

ALERT   Dispatcher (Main): Error starting Game GUI: [string "./MissionEditor/modules/Options/optionsDb.lua"]:119: attempt to call field 'getVoiceChatDevices' (a nil value)

in my dcs.log.

I have webrtc_plugin.dll symlinked as suggested,

❯ l /home/shaun/.local/share/Steam/steamapps/common/DCSWorld
Permissions Size User  Date Modified Name
...
lrwxrwxrwx     - shaun 31 Aug 17:23  webrtc_plugin.dll -> /home/shaun/.local/share/Steam/steamapps/common/DCSWorld/bin/webrtc_plugin.dll

but that doesn't seem to be working.

@SkippTekk
Copy link

SkippTekk commented Sep 1, 2024

Replying to #1722 (comment)

Is that the launcher or the game giving you a black pop up?

Do you have wbemprox=n in your DLL override? Once you get the launcher working, don't sign in. Just start the game as normal, have the original login pop up, login, load the game fully then the configs will be generated. Once your past that let me know

@DrymarchonShaun
Copy link

DrymarchonShaun commented Sep 1, 2024

Is that the launcher or the game giving you a black pop up?

It's the game, with ["launcher"] = false, in options.lua there's a "getting steam authorization data" popup before the game window opens to the black screen. Removing it, I get a different black screen, immediately.

Do you have wbemprox=n in your DLL override?

Yeah, I have WINEDLLOVERRIDES='wbemprox=n;msdmo=n' %command% for my steam launch options.

@SkippTekk
Copy link

No need to keep the msdmo=n on. But i would honestly switch over to the Official launcher and use Lutris. Easier to work with AND you get to do Trails. With steam you can't do any Trail. Plus it's really easy to swap over

@marengohue
Copy link

No need to keep the msdmo=n on. But i would honestly switch over to the Official launcher and use Lutris. Easier to work with AND you get to do Trails. With steam you can't do any Trail. Plus it's really easy to swap over

Had the same issue - failed to start into main menu, but removing "msdmo=n" from DLLOVERRIDES helped.
Using Lutris installer from Eagle Dynamics.

Othwerise following the guide helped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Game compatibility - Unofficial Games not expected to work without issues
Projects
None yet
Development

No branches or pull requests