N206LG

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

I have 2 different computers with two different setups. I originally got this so my wife and I could fly together but now I use the first for VR and the second for the A-10C. This is because I consider the A-10C unusable in VR, due to the head positioning issue and not being able to see the entire HUD. In my opinion, the entire HUD is critical for navigation (especially at night and in bad weather) and for tactical engagement. The VR system is used for maximum immersion in all of the other modules that I own. I assume that ED will eventually fix the A-10 for VR but until then, this is my solution for max enjoyment of that module. P.S. As a consequence, I have begun to build out a cockpit around the A-10 system with 8” LDC monitors and a custom UFC. This is not necessary for VR. Sent from my iPad using Tapatalk

Dear DCS, Please publish the web interface so we can create our own Android and iOS clients. :helpsmilie:

I’ve been considering a button box or two. Please share some info regarding what you use and how you use it (or them). Also a picture or link to the boxes would be handy. Thanks.

I use a trackball next to my throttle and I find that the regular mouse, which remains plugged-in, also works simultaneously. Unfortunately, Microsoft wasn’t clever enough to have a separate configuration for each mouse so I have to use the same primary button on both pointing devices. The natural preference for me would be to have the primary and secondary buttons reversed on the track ball. But I digress.

Viggen for Steam dropped today. Better late than never. I’ll catch it on the next Steam sale. Sent from my iPhone using Tapatalk

Today or tomorrow is the last day of the sale on Steam and I'd love to pickup the Viggen for a discount. Why is it not currently available with other relatively recent modules such as the F-5 and M2KC?

Sounds like fun. Sent from my iPhone using Tapatalk

Apples and oranges (rudder and stick). Not sure what kind of comparison you'd like me to make. I don't have a VKB joystick and, as far as I know, Virpil doesn't make rudder pedals. Both well constructed and solid. Installed the lighter springs in the Virpil and found it to be intuitively easy to take apart and reassemble. Earlier, I planned to try the VKB stick when it is ready, but, unless it is all metal construction, like the Thrust Master, I won't bother. I'm very satisfied with my new joystick. Sent from my iPad using Tapatalk

How does one know when a fired AIM-120 has gone pitbull?

Mine just showed up! Talk about a happy Friday. I can't play with it yet because my workday hasn't ended (I have coding deadlines to meet). But, here it is and just in time for the new SU-33 module. I did a quick-mount but still have to tighten everything and move the bottom bracket up for structural reinforcement. I'll write back if there are any issues. :pilotfly:

That worked. Thanks for you help. Sent from my iPad using Tapatalk

Here is the output from the 'npm install' command:

I did, or at least I thought I did. I will start over from the top of the instructions. Thanks. Sent from my iPad using Tapatalk

Getting an error on the last step (npm start) in the dcs-stream-deck-ka50 directory. The output follows. Perhaps you can translate?

It's not that I can't, it is that I prefer not to. With my TM-HOTAS, A10-C is a natural in VR. But, I really like using my physical MFDs. Also, accessing some of the other buttons and switches to the rear-left and the rear-right can be a little difficult in VR. Also, I can't use zoom the way I like, both when accessing controls and when flying. I have the track-ball (stated earlier) and I have Voice Attack but use it (I know I need to integrate that in but haven't gotten round to it yet). These are not big issues but since I have a choice I go with my preferences. And, while I am proficient with the A-10C in and out of VR, the same cannot be said for the KA-50 and the M2KC. I suck on these two platforms and need to practice them a lot more. Maybe then I'll make the switch but not now.