AndreNL

First video, the second will follow. Maybe this one is enough to see what we are doing wrong?

No problems here with the brightness dimming... Works just fine.

We tried as instructed. We still have the NAK message. For the rest, the data link works fine. We're going to make videos of the two of us recorded at the same time. . Step by step to see what we are doing wrong.

@Raptor9 I did as you indicate, and when I press COM and then MAN, I see that the frequency has indeed already changed as I set it in the preset. I'll check tomorrow to see if this was the problem. But at the bottom line, something is not right. We managed it with the wrong way and we didn't encounter any problems in the Syria folder....??? Roger, we gonna try it this afternoon. If we still have the NAK message we gonna make a video from both sides at the same time.

@Raptor9 I did as you indicate, and when I press COM and then MAN, I see that the frequency has indeed already changed as I set it in the preset. I'll check tomorrow to see if this was the problem. But at the bottom line, something is not right. We managed it with the wrong way and we didn't encounter any problems in the Syria folder....???

This story has taken another twist since today. My buddy and I did some testing today and we came up with the following: Inferno Syria server: No problem, everything works as it should. Inferno caucasus server: NAK message. Inferno mariana server: NAK message. We set up the data link on all three servers as follows: We go to the COM page, we always use preset3 FM1 as data link channel. -We press "PRESET EDIT". And change the preset to: -Unit ID> wsl -call sign> wsl Then we press the FM button (at the top) and we change the frequency of FM1 and FM2 to 31,000 both left and right from the preset screen. Then we press "preset edit" again to return to the COM page. We then see that preset 3 has changed to WSL L3 FM1. But the frequency on the radio screen (above the MPD's) is not yet correct. We then press "MAN" --> FM1 FREQ --> and change the frequency to 31,000. For both of us, we enter our own Id's for our own Apache. For me: call sign: wsl11 datalink 1 Buddy: call sign : wsl12 datalink 1 Summary: On the Syra server we have no problems, and on the other 2 we both get NAK message. Maybe it's a server issue or a map issue. If it's really needed, we can make a video of it.

As the title indicates, when I turn on the rotor lights before the start, it works. But as soon as the rotor reaches full speed, the lights go out. Maybe I'm doing something wrong, maybe other pilots are experiencing the same problem?

This one is solved. We noticed that if you have 1 letter or digital wrong in the preset you will get a nak message. However, when the datalink presets are not exact the same the message will be send and recived with the nak message.

Good morning pilots, Is there a way to adjust the hight/possition of the eye sight and or night vission in VR? Because the place it's now is somewhere on my forhead instead in front of my eyes. In the AH64 it's spot on.....

So, this button I selected shouldn't be a option for the pilot seat? If that's the case, than I understand my own confusion.....

So when the FCR is active, I can no longer use the gun with my helmet-sight? Even when I use the TADS-sight switch? If my cpg or myself using the FCR and I see a close groundtarget, I first have to switch off the fcr to enable the gun sight again, feels wrong to me, but okay.

Good morning fellow pilots / DCS team, As the title indicates, my on-board gun no longer works when the FCR is active. I made a short video of it. And maybe that's how it should work, I'm curious about your ideas about this.

Well, thanks anyway! I set my cores as you said. Running dcs as we speak.... fingers crossed.

And I have this "warning core engine is not running".....??

I need a little help with that. I installed process lasso, where do I fing "run physical processors only" ? And, do I run MT or ST?

Yup. Ryzen 9 5900x with a Nvidia 3080ti,

Dear pilots / team, I have a question about VR. Playing DCS in MT gives me a lot of stuttering, see photos of my VR performance meter DCS_MT_1 / DCS_MT_2. I'm not going to complain about that, I'm just happy that the team is working on it. But it's not working for me atm. I prefer to play in ST, which is by far stable and very sharp / clear in my headset, but I see the following in my VR performance meter, see photo DCS_ST_1~. What I'm wondering now is, can this harm my GPU/CPU system If I keep using ST?

So if I understand it correct. How it was before the last update was wrong. And now it works how it should be, correct? Problem solved.

@[RENEGADES] T-Bone I don't have to test it, I get my K-hellfire to a target with a 3rd party lasing. That's not the point. The problem is: When in the back seat and I select SKR for ACQ source it pops back to FXT or TADS or whatever it was accept SKR. You can see this in the youtube clip I made. I press SKR and the ACQ stays on FIX-TADS-previous selection but I can't get it on the SKR. That's all. And for that I had to make a youtube account, made a video-clip upload it. Everybody can see I press SKR right?? Now I have to make a trackfile in singleplayer, WHY? To proof I press the SKR button on my MPD? Before the last update, I pressed the SKR in ACQ and AQS showed that it was on SKR mode......That's it, nothing more.

I don't know why the track file is so important since I made a video in which you can clearly see that I try to enable the skr option several times, I encounter the following problem: my track file is 60 MB and can of course only send 50 MB. Any idea's on that?

"need more information etc..." Well, If you watch the video how much more information do I need to deliver?

2nd point: What I use to do, is when I attacked a target I mark it with a target point on the map. The FRC doesn't know when a target is destroyed or not. So I can see in an eyeblink if the target that's pops up in a new scan is already destroyed. Also handy If you wanna look with the tads to that saved target point on the map.

I would like to apologize right away, this is my first video on YouTube and they are certainly not as perfectly edited as those of Wags from ED to name just an example. I do everything the same as before, but as the video shows, the seeker option no longer works for me.

Sorry, I found my problem. I thought the Searchlight switch down-off-on-up buttons controlled the lamp. But that's what the Position Switch does. My mistake, solved! ( What I find strange is that the lamp turns on and off with key 8 - 7. Well, that's is not strange but Key 6 does nothing and key 5 turns off the lamp in my situation. ) Any idea's on that? I'm one of those people who can't sleep if I don't understand something.

My keybindings are: 8 searchlight on 7 searchlight off 6 searchlight up (when I press that key the searchlight goes off) 5 searchlight down (nothing happends) I gonna make a video of it later today.