N206LG

Looking for suggestions here on how to not have to download updates three times as I have three different systems, which happen to be using three different accounts but that is not really the issue since even duplicate installations with a single account would have the same problem. I don't have to explain the size issues tied to these modules especially the terrain updates. My question is this, can I safely and legally manually copy data between my three systems? Second question, is there a way to get the installer to copy from one computer to the next using shared/distributed file-system tech or something along those lines? I assume that, as long as all the licensing tech/files are not touched, this will not break anything. In case you are curious, I have two separate accounts for myself and my wife. I have a third Steam account that I barely use anymore because I didn't like how it lagged behind on sales and releases. However, that account, which is installed on my gaming laptop, comes in handy when I want to work on mission building. The fixed desktop stations are VR stations; mission building and other related activities are inconvenient on these as they are optimized for gaming and not for creative work.

The problem just magically went away. It seems that SteamVR is the culprit since the crashes stopped shortly after it was automatically updated.

Out of desperation, I upgraded the memory in both systems from 32 to 64 gigabytes. I did this because it seemed like the systems crash only after a certain period of time. If I can get my sorties in before that happens, I'm hard up enough to live with that, at least for a while. As a bonus the systems loads much faster in multiplayer. One system crashed again but the other seems stable. More testing required. The extra memory probably only delayed or masked the true source of the problem but I'm happy with the improved performance when the systems are running,.

Thank you for the reply. Unfortunately, my work keeps me busy during the week so I only get to fly on or near the weekends. I've removed the modules you suggested but unfortunately, the LUA script is for my force-feedback controller from Brunner. I'll pull it out and experiment when I have time this weekend. Today, I experienced two more crashes. With the first, the app kept running so I assume it was a thread that crashed. Later the second crash took me out (killed the entire app). Log files attached. I wasn't even flying. I was sitting in my F-15E, still in the hanger, watching touch-and-go traffic with a live controller. There were a lot of view changes as I watched planes coming and going on TTI-Syria. I'm starting to wonder if I have a memory problem.dcs.log-20250619-231442.zipdcs.logdcs.log-20250619-232924.zip

"sys1" has been very stable but crashed while trying to get multicrew working with "sys0". First crash in months. "sys0" has been crashing almost every day during the last two weeks. It works fine as long as I am not using multiplayer. I've included logs from both systems. Prior to the last couple of major updates, perhaps during the month of June, I had no problems with either system. Let me know If I need to include anything else. Both systems use different accounts both owned by me and both active for years. sys0 user name is N206LG. sys1 user name is SMJ. dcs_sys0.logdcs_sys1.log

I too find that the brightness of my exported display on the F-15E are far too dim. On the HSI I can't even make out the heading markers on the compass-rose. Is there a way to increase the brightness or improve the drawing for these exported displays? As they are, the exports are not visible enough to be usable (IMO). -N206LG

Pilot error (thankfully). As you say, I was missing step where I press the "Enable" switch. Thanks @skywalker22

I'm experiencing a problem with the HMCS alignment procedure where I can only perform the first of three alignments steps. I can't move the cursor (the two reverse video asterisks) on the DED between the three lines on text. I can only hit M-SEL to end the current step. Here is a short TRK demonstrating the issue. My understanding is that this bug was already fixed once before but appears to be broken again. F16 Broken HMCS Alignment Sequence.trk

I just experienced this bug/issue. I can only carry out the first step of the alignment. I cannot move the cursor down to the 2nd or 3rd option. I just installed the latest patch this morning. Is it supposed to still be broken or did that fix you tested get applied and I'm seeing a regression?

@Ready: What did you end up doing? My understanding is that the 4090 may not benefit you any more than the 3080 due to the CPU not being able to keep it fed. In other words, you may be CPU bound. I was wondering if you had made the switch and if so, how it turned out? I'm considering upgrading my CPU and GPU as I don't think one or the other by itself will do the trick. I have a 3080ti GPU with a 5900x CPU.

The problem has been solved. It appears to have been an issue with a power management driver. I say appears because more than one driver was updated.

Will do. Thanks for the reply.

This exact thing keeps happening to me as well; same symptoms you describe. The difference is I have added another 32GB of RAM (64GB total) and it still crashes. Sometimes silently, sometimes with a prompt to phone-home. I see this in the log file: 2022-09-16 19:26:37.055 INFO EDCORE: # -------------- 20220916-192637 -------------- 2022-09-16 19:26:37.056 INFO EDCORE: DCS/2.7.17.29493 (x86_64; Windows NT 10.0.19044) 2022-09-16 19:26:37.057 INFO EDCORE: C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin\ed_sound.dll 2022-09-16 19:26:37.058 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 0CA32C3F 00:00000000

I've had a number of crashes while running in multiplayer with my new system. It looks like a memory exception. This made we wonder if I had defective RAM but my systems seems to pass the bootable memory tester from Microsoft so I'm not sure what's happening. If I could get confirmation or denial that it is a hardware problem, that would be wonderful. Then I know to replace my RAM or wait for beta software updates. Here are the relevant log files. The actual crash quoted in the title is from `dcs.log.old` . I wasn't sure how much info you wanted so I included all log files in the directory. This is the Steam version of DCS, by the way. dcs.log.old dcs.log-20220916-192637.zip dcs.log

I’d also be interested in the answer on this. I use standard wired earbuds and the dangling wire is kind of troublesome. Sent from my iPad using Tapatalk