Flagrum

The CMWS panel is a later addition to the aircraft, probably using a standard component. They probably had to tie in the audio into an existing channel - but then having two volume knobs for the same audio channel would make no sense. So they did not use the one on the panel. But if you find this already weired, then you must have never flown the FA-18 or even the Harrier ...

Where is this? The Falklands don't have glaciers, right?? Big Ass Glacier!

I might be missing something here, but what has this discussion to do with Controller Profiles?

I can't remember the details or the exact issue, but changing your loadout in the mission planner confused the DSMS as the jet would spawn with the original INV settings but the new loadout or vice versa. Iirc, you had to reload the INV then, but that would not always help. Your DSMS would then be sprinkled with red text everywhere Or something like that.

It caused more confusion than it was usefull back in the days. If you were not very carefull and knew exactly what you did, it would just mess up your A-10C DSMS / INV, rendering your aircraft virtually useless in that mission. Maybe other aircraft nowadays are not that sensitive in that regard, but I know that 10 years ago, I ran into this issue 3 or 4 times with the Warthog and also read a couple of posts of ppl with the same issue. Then I just ignored this feature. ¯\_(ツ)_/¯

Well, we probably have the eyesight comparable to elderly people when we stare through the monitor (or worse, a VR headset), trying to figure out the labels ... I.e. it probably actually helps the readability - what does 101% accuracy help, if you can't read it? ^^

Georgiens Stromversorger sind vermutlich an bis zu 10 % aller Verluste auf dem Gefechtsfeld verantwortlich!

Hi @BIGNEWY! This is still in status "investigating" - do you need more input to get it "reported"? How can I help?

The new feature of the ME that allows to add own symbology to the F10 map is great - I really love it. But when I tried it out, I noticed a bug: I used the drawing feature in one of my own test missions (Syria) and everything looked and worked as expected when I flew it (started directly from the ME). A bit later, I quit the mission, returned to the ME and also returned to the DCS main page. There I started an instant mission (Marianas). While flying that mission, the F10 map still showed the drawings I created earlier, probably at the same coordinates (DCS World internal map coords) on the Marianas map, where I placed them on the Syria map. It seems, that the list of draw objects is not initialized properly when changing missions.

No. A GPU is a complex part of electronics with many components, which can break - with varying end results. Similar to a car (which is also "hardware" ;). If something breaks in your car, you may still be able to drive. But depending on what part broke, you might not even notice at first. But it could lead to a fatal crash in certain situations.

Yes, that is understood. But I am talking about the difference between the cruise phase and the sea skimming phase between cruise phase and terminal attack phase. At it is now, in R/BL mode the weapon never really has a chance to execute a proper TERM maneuvre as it is still at cruise altitude when the terminal phase begins. It never gets close enough to the water to sea skim or even to pop up. I think we agree, that the flight profile should basically consist of three distinct phases: Cruise, to initially cover the distance to the target Sea Skim, as low as possible without getting wet, something between 15 - 150 ft AGL Terminal, to perform the SKIM or POP maneuvre in order to hit the target It also seems, that all three exists as distinct flight phases in DCS:W, just not merged into one flight profile. When you look at the BOL TacView screenshot: the weapon sea skims at ~150 ft and only a few seconds before the impact, it drops to 15 ft to perform the configured TERM attack (SKIM in that case - but I could also provide a POP example, where the maneuvre is clearly visible). The whole goal of the sea skimming phase is to make the detection (radar horizon!) of, and the defense against the weapon (late detection = short reaction time) as difficult as possible for the opponent. If the weapon enters the sea skim phase too late (or not at all in our R/BL case at hand), this phase is virtually pointless. If it enters this phase too early, it's range is serverly limited. https://navalpost.com/anti-ship-missiles-what-is-sea-skimming/ If the point, when the weapon enters the sea skimming phase, has any direct relation to when either ... a) ... the weapon starts actively searching for a target, or b) ... the weapon has eventually aquired a lock, I can't say. There are probably arguments for both: target aquisition is easier at cruise altitude, but on the other hand, the weapon already knows more or less where the target is anyways and only needs a final lock a few miles out (s. the linked article which also elaborates a bit on that aspect).

Can I create a regular waypoint without having to input the coordinates manually? I.e. can I copy the coordinates from another waypoint or markpoint - or even from a target designation?

Today I saw (for the first time?) the DDI advisory "ADV-A/P". I had enabled baro hold by colonizing BARO and "ADV-BARO" appeared on the LDDI. A bit later, I disabled BARO by deselecting the is UFC option, but then "ADV-A/P" appeared. Th aircrafts attitude remained quite stabilized and even firing a Harpoon did not bother it (slight shudder, but no banking). To me, it seems that the aircraft reacted very similar/identical as if ATTH was enabled (but it wasn't!) and also maneuvering within the A/P limits was still possible. I could only completely disable the A/P by using the paddle switch, but I can enable this mystery mode directly by just pressing "A/P" and "ON" on the UFC. So, what is this semi-secret A/P mode exactly supposed to do - and what is the difference to the ATTH mode?

The bottom left PROG label is missing, although the OSB itself is still functional and allows stepping through the different HPD programs per station:

The flight profile of the Harpoon consists of 3 different phases: 1. cruise 2. sea skim 3. final The DCS manual, and other sources I found, are not very specific about when the transistion from cruise to sea skim is supposed to happen. "Common sense" (yuck, bad word in DCS:W, I know!) suggests, that his should happen way outside of the typical air defense envelope of a war ship. My assumption: the transistion should happen, when the weapon either enters search mode or at least, after aquiring a radar lock. The Harpoon in DCS does not show such behaviour. Instead this happens: R/BL, cruise alt = high: the weapon cruises at 10 000 ft AGL up to almost directly over the designated target. Then it dives towards the target. The terminal mode SKIM or POP is then obviously useless and makes not much of a difference in the flight profile. My assumption is here, that the search mode is only enabled when entering the SEEK distance - which is too small to allow an early enough descent to a sea skimming profile. BOL, cruise alt = high: the weapon dives straight down to ~160 ft AGL and cruises at this altitude until it gets a radar lock a few nm before the target. There it then goes down to ~50 feet and performs the correct TERM maneuvre. The problem here is, that the Harpoon does neither respect the FLT setting (high!), and also a set SRCH distance has no influence on the flight profile (see my assumption in the beginning). R/BL FLT=high vs. BOL FLT=high I have not yet looked into which influence a HPTP has on the flight profile in R/BL or BOL - it is already difficult enough to try to make sense of what the Harpoon does without it. HPD BOL HIGH vs RBL HIGH.trk Tacview-20211003-005418-DCS-HPD BOL HIGH vs RBL HIGH.trk.zip.acmi

@BIGNEWY, this has not happened, yet, correct? The flight phases just make no sense. In RB/L the missile cruises all the way to the designated target. Then it either "sees" the ship and tries to dive at ~90° at it and therefore completely ignoring the TERM settings, or it just overflys it. Seems, the missile only enters search mode just right on top of the target point. And in BOL, it always goes down to 150... ish ft right away and sea skims acording to the BRG to the target and thus ignoring the set cruise altitude altogether. Then it often actually does perform the TERM maneuver. If you then combine all this with HTPT ... and it only gets more complicated. Experimented with all this for several hours now, but I am still not yet able to tell, what effects different settings then have to the flight profile. It's not fun.

Yes, as also someone else mentioned above, it's probably because ED want's to wrap up some loose ends as preparation for the next bigger update. Therefore they wanted only hotfixes in todays patch and not new potential bugs.

Thanks, Snoopy! Well, I guess that makes a lot of sense - so you can configure the weapon on ground and basically any aircraft capable of dropping MK-82s can employ it. And on the other hand, a more modern platform, can used it in a more flexible way.

Hrmm ... what are those three pins at the top of the seeker, labeled 1 - 2 - 3? Some sort of rotary dials? But there are now windows to display the actual value that you have "dialled in"?

"It is related to waypoint editind via EHSD and TDC, it may be related to TDC in INS mode so it does affect also TPOD when in INS... " I agree. In my case, when I thought I would move the IRMAV reticle, I had to undesignate my TPOD target and thus was in EHSD INS mode (which I failed to recognise). Instead of slewing the IRMAV seeker, I was slewing the INS cursor and the IRMAV was just slaved to it. The culprit is the EHSD.

For conventional LGBs, the laser code is set mechanically on the ground directly at the guidance kit. The setting of the code in the A-10C SMS is only meant to be "informational" for the system - it would in reality not change the code of the bomb itself. But for practical reasons, in DCS it actually does change the code the bomb will look for. But how about the GBU-54 LJDAM? As it is also a JDAM and as such it already has a data connection to the aircraft to receive the target coordinates. But will that also allow it to change the laser code electronically "on the fly" (literally)? I.e. will changing the code in the SMS actually change the code of the bomb in RL? Or is that, too, just a "gamification" like it is done for the conventional LGBs?

I was made aware that I made an error here - instead of slewing the IRMAV, I was in INS mode and was moving the INS cursor on the EHSD. Seems to have nothing to do with the IRMAV, but rather seems to be just another manifestation of the bug that Kappa reported here:

Yes, thank you very much, that work for me as well. It's been a while since I more seriously fiddled around with the Harrier - so yes, this was an user error. The IRMAV seems to be ok! But regarding INS - then the behaviour I observed was more likely a direct result of the bug that @Kappa had reported, right? Something with the TDC and the EHDS/INS seems off.

I would not be surprised, if these bugs might be related: @Hornet81, maybe you can have a look at those as well? ty!

(deleted - made no sense)