hornblower793

Have you tried without loading LotATC, SRS, Tacview and any other addons?

Flappie beat me to it

Glad it is working - enjoy the flight

This issue sounds like you might have PTC selected in the Oculus app as this is known to currently stop DCS working. Unselect PTC and you should be good to go The versions are united now (everyone got the download) but it currently remains showing as OB or stable depending on what you updated. The error implies that GraphicsCore.dll is corrupted, but it could also be something to do with a Windows file. Have you tried running sfc to check for errors https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e Also, have you tried to run a repair of the Steam installation. Right click on DCS in your library and then select properties>installed files>verify integrity of files

A couple of thoughts: 1. Are either of you running Oculus VR as the PTC option in the Oculus software is known to be incompatible at the moment. 2. Please could you post your DCS log file from C:\Users\<your username>\Saved Games\<your DCS install>\Logs (assuming it gets this far). I run standalone version so cannot really help debug Steam, although I do use Steam for other games. Have you tried going to the Steamapps folder for DCS and running the exe directly from the bin (for ST) or bin-mt (for MT) exe folder?

This - imgui.dll should be in the bin and bin-mt folders for the install

I think your log shows you are running ST D:\SteamLibrary\steamapps\common\DCSWorld\bin\DCS.exe --force_enable_VR MT should be in the bin-MT folder

How much space is available on the drive? IIt might be worth clearing out temp / backup files

Single / multi threaded for your CPU. It affects how DCS uses the cores available in your processor (rather than your graphics card).

Are you using VR, in particular an Oculus device (you have an Oculus device listed in audio)? Your log stops at the point where VR loads in. If you are then there is a known issue with the latest PTC Oculus driver and you need to roll it back

Having looked at your log file it looks like it is at the point where it tries to initialise your VR headset so I think you probably need to roll back to the last version of the Oculus software. ['civTraffic'] = ''; ['ScreenshotExt'] = 'jpg'; }; 2024-02-16 16:58:20.403 INFO VISUALIZER (Main): VRG skip, ask for support if you own VRG helmet My log file at the same point is: ['civTraffic'] = 'low'; ['ScreenshotExt'] = 'jpg'; }; 2024-02-15 20:02:47.272 INFO VISUALIZER (Main): LAUNCH IN VR OpenXR: Pimax Crystal2024-02-15 20:02:47.273 INFO VISUALIZER (Main): render thread initialization... 2024-02-15 20:02:47.278 INFO GRAPHICSVISTA (8392): renderer: 'dx11backend.dll' 2024-02-15 20:02:47.352 INFO DX11BACKEND (8392): DX11Renderer initialization (w:1176 h:1392 fullscrn:0 vsync:0 adapter:0 monitor:0 shaderErrors:1) 2024-02-15 20:02:47.422 INFO DX11BACKEND (8392): Driver Concurrent Creates - 1 2024-02-15 20:02:47.422 INFO DX11BACKEND (8392): Driver Command Lists - 1 2024-02-15 20:02:47.549 INFO DX11BACKEND (8392): NVIDIA API init OK 2024-02-15 20:02:47.550 INFO DX11BACKEND (8392): NVIDIA Display Driver Version 55152.r551_06 I know my file is from yesterday, but I have just logged in now to check it works

Is this with VR or without? If with VR are you running an Oculus headset. Please could you also attach your DCS log file

Is this with an Oculus VR headset (log file seems to think so). If so it is an issue with the latest early access software

Please could you post your logfile for an unsuccessful VR attempt. Also, are you using Oculus with the latest release candidate?

I think the problem is that there are probably as many ways people would like to sat it as there are users. I use aliases quite a bit and they allow you to customise to your hearts content. This isn't to say that some commands wouldn't be better have core aliases added (I wouldn't remove the existing commands as you will probably throw long time users who have them in their mental 'muscle memory'.

I am reading the log file and not the crash zips. The best thing to do is to remove the mods, run a repair, try to load again and then post that log file if it crashes

From this log file I think the F-22A mod is giving you issues. The first error in the log is this 2024-02-11 12:12:45.441 WARNING SECURITYCONTROL (1020): IC fail: /textures/ais-pod_t50_diffuse @ c:/users/lorfa/saved games/dcs.openbeta/mods/aircraft/f-22a/textures/weapons.zip This is then followed by a lot of DX11BACKEND errors. 2024-02-11 12:13:49.033 ERROR DX11BACKEND (3380): DX device removed. Reason: 0x887A0006 As @BIGNEWY has recommended, please remove the F-22A and A4 mods, repair DCS and then try again

These are the crash zip files - and have .dmp, .trk and .crash files in. There should be a separate dcs.log file in the same folder

I am now back on my PC so it is a lot easier to read the logs You have a very small Pagefile at 2048MB and this might well be the issue. Follow the instructions found here https://mcci.com/support/guides/how-to-change-the-windows-pagefile-size/ to increase its size and see if that works

Could you also post your dcs.log file (found in c:\<username>\saved games\DCS.openbeta\logs for OB (there will be a similar folder for stable)

The first meaningful error I can see in the first log you posted is: 2024-02-10 20:55:13.086 ALERT EDCORE (5404): Out of memory in ed_malloc for 11184984 bytes. 2024-02-10 20:55:13.088 INFO EDCORE (5404): try to write dump information 2024-02-10 20:55:13.093 INFO EDCORE (5404): # -------------- 20240210-205514 -------------- 2024-02-10 20:55:13.094 INFO EDCORE (5404): DCS/2.9.2.49940 (x86_64; MT; Windows NT 10.0.22631) 2024-02-10 20:55:13.094 INFO EDCORE (5404): C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\edCore.dll 2024-02-10 20:55:13.095 INFO EDCORE (5404): # 80000003 BREAKPOINT at 00007ffbb87d7adb 00:00000000 2024-02-10 20:55:13.096 INFO EDCORE (5404): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'danim' 2024-02-10 20:55:13.097 INFO EDCORE (5404): OS-Version: 10.0.22631 () 0x100-0x1 2024-02-10 20:55:13.098 INFO EDCORE (5404): 0x0000000000027adb (edCore): ed::fatal_out_of_memory + 0x3B It then goes on to have a lot more memory and Integrity Check failures. I am away from my PC at the moment so cannot easily search the forums for similar problems

Thanks - I will give this a go

I have the same issue and have tried the same steps. I don't know if there is a technical limitation on the hand offset in DCS but it would be great if you could offset by up to -20 in the vertical direction rather than the current limit of -10. IIt would be best to start a separate thread as this is in one marked as solved

This definitely makes JoyPro worthwhile - I have just had it happen changing the setup of the AH-64D grip and was able to migrate all the bindings in a matter of seconds

I run the Pimax Leapmotion controller addon integrated to the bottom of my Crystal headset and the adjustment ranges for hand offset in DCS do not go big enough (I would need it to be about -18 in the vertical axis. Is there any technical reason why the X,Y and Z adjustments are limited to -10 to +10?