Rufnax

bump. No response from ED unfortunately. It would be such a benefit to copy the trim option from the kiowa. I know they are third party dev but maybe ED could make a deal with them to get the trim option fade in / out transfered to the apache.

I support this request and hope ED will add the trim option to the apache. It's the most optimal trim solution so far imo.

Hi Vader :)George is lasing continuously when you select rockets or hellfires even when he is outside of the shooting range. So the points above do not sound as a plausible argument for me. When you select hellfires george is lasing all the time from a range of 9999m till we get into shooting distance at about 8000m. I like this concept because this helps us as a pilot as we get the range displayed and it makes him fire immediately as soon as we get into range. So my question is, why does he not lase continiously when he is using the gun? From a user perspective this is not quite understandable. I get all the stuff with nose to deep or gun has to have certain angle and all. But just have george lase all the time when gun is selected (similar to hellfires or rockets) would solve the issue and misunderstanding that alot of people have because the range would be displayed all the time on the TADS display. I think this would just be a simple fix for an issue or misunderstanding that obviously alot of other users have (atleast it just seems to me by the amount of posts that we have on this forum atm). I don't wanted to start and argument. Just wanted to provide my 2 cents as a user to give you some feedback to this. Thanks for listening

Hi there. I don't have a specific track file for this behavior but I saw other user having issues with the laser usage of george with the gun as well. Since the last few weeks i found that george is barely usable when he is using the gun. He is lasing so sporadically that you often have to come close to the target before is even trying to shoot. And no it's not an elevation issue. You can use the gun on the same ranges without an issue as pilot but when commanding george to use it he won't shoot because he is not correctly ranging the target because he does not use the laser. I don't know if this is subjective but I found that a while ago he was much more useful and used the laser more often. Again this is only specific when using the GUN. Hellfire and Rockets work correct. I was wondering why he uses the laser not permanentally when using the gun (he does this for the other weapons as well). Atleast he should always ranger range when I command him to shoot the target. Otherwise I would like to request a specific action in the AI Helper to have him lase manually (like you can already when no weapon is selected) or to increase the lase time / frequencys when he is using the gun.

I don't expect and want George to see and identify everything on the ground but I would appreciate the ability for george that he is reacting at least to targets / enemies that are shooting at me. So for example like jester is doing in the f14 back seat. George should call out, identify and mark targets that are threatening or engaging (shooting) at the apache.

Hi! Same issue just happend to me today. INU drift after flying for 30-45 minutes. CAQ and Waypoints where at about 50m offset to the actual target / point. When firing LIMA Hellfires onto the target the hellfires also missed the target at about 50m. So I would assume these two issues are somehow related. A statement from ED would be nice to know if they are working on it already.

I can't speak for other people but for me "no LSS Function, less zoom capability and a much worse image quality" kinda is "loosing a feature" for me. And I understand your points of ongoing development with new informations. But I, as a customer, expect ED as a developer to deliver the features on the modules that they advertise and promise. Everything else is false advertising imho. You can't advertise a red ferrari with 350hp and deliver a green lada niva with 16hp because you don't have the necessary informations available to develop the ferrari. Naturally, you will have to "change" a feature or a function when it is not working as intended or because you recieved "new" informations. I understand this, really. But just "pulling" a (core) feature, like in this case the lightning TGP from the features list completely is not a consumer friendly way of "changing functionalities with new informations". Sorry to say. This damages my trust in ED as a developer and for your early access modules in general. How am I supposed to buy my next module, for example the AH-64 when I can't be sure that you have the necessary informations / documentations to implement the Fire Control Radar as a core feature. Maybe you are pulling this from the feature List when you get "new" informations"? I guess ED has made it's point as a developer here and I have stated my opinion as a customer. I personally would love to see ED to overthink their way of "handling new informations" in this case and in future cases like this. Otherwise I am not sure if and how I will buy further modules in early acces development. Thanks.

@NineLine I understand technological reasons and reasons from a documentation side but from a customer experience I have to say that loosing main capabilities on a module, like the Lightning TGP for example, after they have been advertised as official features on the modules roadmap (for month), kinda feels wrong from a customer service side and throws a bad light on ED as a developer. Can't help myself but see this as a real bummer and makes me more hesitant to buy further modules in early access in the future. What do you want to trust on when the developer is not able to provide the advertised features on a product, which in the end you paid money for based on the details from the roadmap. Just my personal opinion on this topic.

Does it still release even when you are not on the configurated release angle? I always thought that's mandatory. But thanks. Will test it myself next time I am flying in DCS. But one question, what is the advantage of the release angle setting? I could always just let it stay on 45° default value when it's not necessary to have the correct value. Right?

did you configurate the GBU for a 0° loft angle or did you use the basic value for loft angle which is 45° when i remember correctly? When you don't change the loft angle to 0° the bomb won't release from the hardpoint when you fly a "level" attack.

I am wondering if we will ever get a liverie overhaul for the F-16C Viper. A few of the basic liveries are lacking alot of detail tbh and are looking like the liverie is still WIP. So is there a chance we will eventually get updated liveries for the different countries? There is soo much potential and cool liveries available in the Userfile section. Should be a quick and easy win to include some of the best skins that are available.