AndreNL

BeFore the last update I proceeded as follows: Mastar arm on, Hellfire selected. LOAL HI selected. Acquisition SKR selected. All this in the rear pilot seat. Now I can't select SKR as acquisition. Maybe I doing something wrong.... On the moment I select SKR it pops back to fixed.

Can no longer enable the SKR option for the hellfire's (k) in pilot seat. Or should it be so?

So as the title indicates, the Apache searchlight is not working properly. I can turn it on and off but I can't move it up or down.

@ Lord Vader, We are gonna try to make a track from both side's. It can take some time because we both work atm..... The only thing I don't understand is that the datalink works perfect, even with the NAK message.

It's off topic, the topic was att not working. It works a bit better then before. But about MT, it stutters a lot on my machine. I prefere to use ST but my gpu doesn't like that but in-game is much and much smoother. And I noticed that DLSS is not working in ST. I'm using AMD ryzen9 5900X NVidia RTX3080TI and have 64RAM Htc vive pro

Well, Can it be a server problem?? My buddy and I did join a other server. Did exact the same thing and we both didn't get the NAK message. Anyway, on both servers it works just fine. The only thing thats different is that on the first server we still get the NAK message.

What DD_Frair means, If u put a ah64 on the map in de editor, you have tab the box for the fcr on. Otherwise the apache doesn't have a fcr at all.

Dear, Since the update on Tuesday December 19, I am experiencing a problem with the data link. Me and my buddy use the datalink frequently and we are also very happy with it, but after the last update we both get the NAK message after sending something while everything functions normally. We both can send and we recive. Also, tailwheel unlocks always appears after sending a message. Not a big deal, but needs some attention. Keep up the good work!!

Dear all, Dear everyone, I noticed that after the last update att is now working again! Well, it's not fine tuned yet....but better than before...

Dear fellow pilots, I did not start this topic to complain, humiliate or completely criticize someone. I started this topic to see if I am the only pilot who has this problem, and if not, it is a signal to the designers to address these problems in their work. We are talking about the beta version here, it is still Work In Progress. As everyone is slowly used to, an update is always 3 steps forward and 1 step back. A lot of problems have been solved, which I am very grateful for and yes, unfortunately, 1 problem has rised to the surface. Together with the entire community, we are real testers here, we experience the defects and we pass them on so that developers can work on them. In a real Apache, things sometimes break... don't forget that!

Since yesterday's update we have added a bug. If I fly around 100 knots and activate attitude hold, the ah64 banks seriously to the right

Dear all, After yesterday's update I can no longer play on the usual servers as my ping is 2x higher than normal. Is there anyone else having this same problem?

I have the same problem from the day it came out. I always aim a little bit to the right and a little bit down. Works perfect. I'm using htc vive pro btw...

Thank you for your comment, I really appreciate it! I gonna check the right handgrip for the on/off LST.

Dear, After a busy period on the farm (I'm a farmer) I finally had time to pick up the thread again with the AH64. But I see quite a few problems in the meantime. After playing for 30 minutes I come to the following conclusion: 1 I cannot switch between radio presets with the swap button. 2 In the cpg position (also as pilot): the tads goes crazy. It's doing some zigzag pattern continuous which I can't turn off. 3 Laser designator does not work, I cannot turn it on. Not that it matters since the tads keep zigzagging. 4 There are apparently Longbow missles now, cool!. But I can't select RF as a pilot in the weapon page. Tried in MT and without MT. I haven't taken/had the time yet to scour the entire forum for these issues.

That make sense bonesvf103, about the display feed of the rio. Now I have to do some research of how to get a ground point direction in my compass rose. Anyway, Thanks guys for the reply's

Yup, you are right! I was focusing on the HSD. That screen stays black. Like I said, it's been a long time for me that I flew the F14. It's comming back bit by bit. What I never understood is why the radar screen (HSD) is not function anymore when the F14 is switched to Air to ground modus. I always let Jester make an groundpoint where I can fly too. But when you put your aircraft into AG modus, the screen turned black..... Any idea's on that?

Here the same! Fixed, thanks!

It's been a while since I've flown the f14. But since this week I picked up the thread again and notice that a few bugs have been added. The lantern pod has stopped working. When I put the aircraft in air to ground target mode it took a while for the pod to become active. Now the pod won't be active at all. The gbu24 shows up in the jester menu as 2x?? Maybe tis has already been reported, in which case apologies.

Well, I can't complete my profile at all. Gets stuck at 67%..... Press next and then fubar..... "this page doesn't work".

Yup, Thanks for the reply. I'm a steam user so I posted it on the steam forumsand never had a feedback on this topic. The way the radiopresets are working now is for me not logicall but it seems that this is the way how it is working in ah ah64. Thanks!

Dear members of dcs, The next riddle: When the AH64 came out you could set 2 presets per radio channel. This was done as follows: Open the COM page, then you clicked on MAN and then on the radio channel you wanted to change. Once changed the first channel settings you switched the radio channel to the 2nd setting and changed the frequency you wanted aswell. For me, this is logicall. Now: If I change the first preset frequency, and I confirm that and then select 2nd radio channel and also change its frequency, the 1st will jump back to the default frequency. If I change and confirm the first preset frequency, and immediately change the same frequency again, then I have 2 different presets. Is this a bug? Or was the first method wrong?

I read that floyd1212 didn't run into any problems so I tested again yesterday. Of the 16 Hellfire missles, 1 has reached its target. So somewhere I'm doing something wrong. I thought a lot about it and then the penny dropped. (Dutch saying) I started thinking when I tried JTAC for the first time. That was in the Syria map. Open desert, no trees, no houses, no buildings, no shelter. So I have my problem in the caucasus map. With lots of trees, shelter etc. I started firing hellfire from all angles yesterday, and sure enough through one corner the hellfire reached its target. But what I find so strange, and that's where my confusion has arisen: every fired hellfire I get the message in my IHADS "Lase Trgt1". Which I thought the hellfire saw the laser spot. But that is probably not the case. So, I'm glad someone finally responded to my post. And that I was able to find and solve the problem (which is my fault). Floyd1212, thank you so much for trying and helping me! (Ps, I have another challenge for you.) Sincerely, AndréNL

Yup, I got the same problem in VR.

The moment the ah64 came out, I was able to perform a Jtac situation with my buddy who flew f14. For example: My buddy flew the f14 with Jester and instructed him to mark a target with a specific laser code. I made sure to use the same laser code as the f14 and launched a hellfire in a range between 10 and 8 km and used the "seeker" mode for the hellfire (lock after launche high) This worked perfectly then . It felt like a fire and forget missle. This has not worked for a long time, already stated a number of times in the steam forum but never received a reply. So here's the question for every apache pilot here. Try running a jtac situation where you fire a hellfire in "lock after launch high" and the missle in "seeker" mode. I'm very curious if it works for you. Met vriendelijke groet, AndréNL