_Silens_

Bump - Welcome 2023! Still waiting on a solution for this?

Hi Flappie, thank you for your response. This was precisely the issue! I have shortened the path to the game files and all works as it should now. Thank you very much for your help!

Hi Flappie, thank you for your response. I tried the above but I am given the same error message regarding the same file. What puzzles me is the fact this is with a brand new, fresh install on a new system build. Do you have any other ideas to try? I have attached the autoupdate_log and error message in case they are helpful. Error Message: autoupdate_log.txt

Hello, I am experiencing this same issue when doing a fresh install on a new system build. My error is the same with the same file name/path – the system can not find the path specified. You mention the issue is in the folder structure, do you have any more advice on how to fix this issue? Thank you so much.

Stumbled across this thread and was curious, is there any sort of "Team DCS World" or "Team Eagle Dynamics" for Folding@Home? My systems have been happily folding along, though joining "Team DCS World" would be pretty cool if such a team exists.

How to begin... After reading these past 17 pages, crying to myself, and then weighing my options, I decided to give these new control profiles a go with one module (just one...for now) and I went and deleted my old custom control profile. However, I soon realized my my question is this... Is there a way to figure out what each button/switch/axis does what with this new profile, other than going through and figuring out each one, one by one? I'm afraid there's not a controls mapping "guide" or anything of sorts for these new control profiles, is there? I think at this point I can either just start pressing things to figure out what each one does, OR I can go through the controls and try to figure out what "JOY_BTN2", "JOY_BTN6", "JOY_Z", (etc.) actually correspond to on my stick and throttle. TL;DR: I'm using this new default control profile given to me by ED, and I feel more confused than ever. Would I better off as a new user if someone just gave me a list of recommended/necessary controls and let me decide what button/switch/axis to assign each one to? Would this be easier than someone deciding on those controls for me, mapping them for me, and then letting me figure out what each control is actually mapped to?

Went ahead and gave this a shot and can say that I noticed the same behavior. Does seem a bit odd that the bug only shows up when in an aircraft. I've tried digging through more .lua files hoping to find something significant, but I've not found anything so far. :(

Hello all. First time poster, long time lurker. Just figured I'd speak up and join the cause. I play DCS with my "3+1" setup with 3x 1920x1080 monitors on the bottom and a single 1600x900 monitor centered on the top. I have a 240 pixel bezel-correction offset added to the bottom configuration to give me a total "resolution" of 6000x1080. This setup is all done in Nvidia Control Panel. As I've read on this forum and others, my game is placing the map on one monitor (the left monitor in my case) while still having the clickable-GUI for the map stuck on the middle monitor. I have tried suggestions posted here and elsewhere, in addition to clicking through the .lua's myself and tinkering with various settings. So far I've found nothing that truly works. What I'm currently doing is running a custom version of the "1 Camera" preset and using the resolution of 6000x1080 in the game. I've modified this copy of this "1 Camera" preset to include lines to force the game GUI to occupy my center monitor only, while accounting for the bezel correction (something the normal file doesn't do). Save for this map issue, everything else works just as it should. I tried a suggestion in this thread, but wasn't too fond of having the entire GUI spread out over 3 monitors. In spoiler tags is my version of this "1 Camera" monitor setup file, with the lines that I've added in bold. Here's to hoping we can get this fixed soon!