TheGhostOfDefi

Well you dont HAVE to go out of FCR to use guns or rockets. But weapons are slewed by the selected sensor. Be it HMD or FCR.

I admit following my Step by Step list i dont get the issue recreated right away! After i leave the aircraft do the step by step stuff and then go back into the aircraft. Then i can recreate this issue. Track attached. FLIRIssueDefi1.trk

Can basically merge those: Step by Step i needed: 1. Go into combined arms switch a bit around with Flir and First and 3rd person view. And the Q seat switching while in FLIR & back. 2. Go back into any aircraft 3. FLIR only stretched / bugged (Repost since im an Idiot.)

This is Not ment to be rude: Touch some Grass! Every map so far is an interpretation of the region for DCS. It never will be a 100% recreation and it never has to. Not even MSFS is 100%… And it’s their strength! We shall be provided with a German battleground. Because this is a combat flight sim game (yeah I said that).. I’m sure after phase 3 is completed, Ugra media is open about certain improvements for accuracy. But right now we received a Gorgeous map that is great as it is. And many hours of our precious life will be sunken into..

If i remember correctly they said they just immediate lower the collective. But im not to sure about the source of that. To be fair its laborious to use in a situation where seconds matter. But you know what, im not an Pilot soo.. ¯\_(ツ)_/¯

As much as i heard it has been barely used even in reallife so i guess its a fairly low priority.

Yes, and due to the fidelity of those Radars, in an instant. (When scanning for gmt not mapping). This goes for using HRM mapping oder RBM. But Not for searching Ground Moving Targets! (Edit: Ackshually the GMT range of the F15 is 32nm.) I am exclusively talking about detecting moving targets!

It feels weird that the F-16 has 80nm range with GMT. Even though the F-18 & F-15 with more powerfull Radars just get 40 Max. I dont know if this slipped through or the 16 just got an superb Radar.

@YurgonCould you maybe verify that the FMU-152 is the reason for the fault? With the FMU-139 the Lasercodes work. When selected together with the FMU-152 they go back to 1688.

Yeah i know all that and didnt knew why it wasnt working and in this specific scenario it was at least a coincidence..

No clue, can be coincidence but as i flew the track it made me fire the laser. Wasnt sure why it didnt fire it in the first place. As far as i could see everything was set...

I have additional Infos that i could not yet comprehend: 1. Pretty much is the case all the Time (Given: Not testet with x3). 2. Station 4 in my most recent tests did not divert from Code 1688 at all. (All tests are conducted Hot Spawned in Air with Loadout set in editor) Further i have the feeling that i get more problems if i use the lasercode 1567 than 1686. As i used copy to all stations in editor all entered lasercodes are ignored and 1688 is used. I couldnt verify more today. I try tomorrow. ## Update ## It seems to have to do with saved Loadouts. If i select the weapons manually onto the Aircraft the Lasercode mostly works. BUT if i select a saved Loadout and change the lasercode then there. It wont be taken over. Even problem 1. i could eliminate in this very limited Testing-Run i did. (By changing weapons manually) 2. I guess that certain stations are problematic can be traced back to my testing behavior. Now the only interesting thing is, if my saved Loadouts are corrupted (And if more aircraft are affected) or this could be a problem with other users too.

Looked at your track and your laser does not fire at all. I had the problem in your track that the TGP was permanently in INR. Try Area Track. Ps. Ah and you can slew your TGP to where you are looking with DMS right Long. That works smoother and at least in the quick run i did, resulted in a more reliability.

I´ll hope that i can deliver more tracks the coming weekend.

Aged Like milk huh?

I found inconsitencys with the Lasercodes using the GBU-12: 1. If you use the BRU-42 the Lasercode shown in Cockpit is always 1688. 2. If you set a Lasercode by the armament page in Editor for the GBU-12 w/o the 42 Rack (Not tested from Rearm menu) the Lasercode is shown in cockpit as set. But the actual code is sporadic still 1688. Track Attached. P.s. It just dawned on me that i should´ve done that track on Caucasus instead of Sinai for accessibility reasons. A10Lasercodes.trk

+1

For me important, can vehicle still use those Roads as they can be quiet crucial?

@Pikey If you are looking for how certain areas looked back then. There are many websites showing older aerial photos for example: https://luftbilder.geoportal.ruhr/ covering the Ruhrgebiet. Or https://www.kreis-coesfeld.de/ASmobile/?appid=HIST_Luftbilder# for the area of Coesfeld. etc. If you need certain areas let me know.

I dont want to escelate this thread to an "WhatAboutism" one. I agree with you that the extra kinetic energy isnt just gone. Still the kinetic energy of ~10kg of modern explosive, some even packed with frag sleeves, should have a meaningfull impact as well. If not even have the bigger impact. I just think there is an inconsitency with damage. Think of what happens to your helicopter if YOU are hit by an ATGM vs AI. This effect just not carries over to the AI.

The effect of HEAT charges to helicopter seem to differ by weapon type. So for example if a Tank fires a HEAT at a (ai) helicopter it pretty much disintegrates. But if we take a HEAT of a Hellfire for example it limps away. Both warheads have about the same weight. So the result should be the same. Im wasn’t sure if this is rather a weapon “bug” or an Aircraft “bug” but I figured it could remotely be related to the overall damage model situation of ai helicopters. with kind regards Defi

TSD -> Route (RTE) -> on the left side you then click Direct (DIR) -> Select Waypoint from list on the right you want to be directed to

Ehm, is it intended that i have Iraq in the Main Menue as a Module (Not Owning it but can buy [Its there in grey]). @BIGNEWY

As i see it the problem is not the Hellfire not tracking but rather you not lasing... Title is a bit misleading. My wild guess would be wrong button mapping. You do not by accident activated manual laser search? When you dont get the "X" on the Display that indicates an active laser and you range is still the Manual entered Range you do not Lase. A Trackfile would be helpfull to trace your steps and see any mistake. Or maybe even a bug.

Well sounds like the autofill stuff from your browser..