Rongor

In my experience so far it does. Releasing the paddle defines the altitude just like the initial AP switching to ALT mode.

You were bringing up the paddle switch. the paddle switch is on your stick. It's not a toggle switch, nor is it 3way.

If the aircraft currently isn't within a certain trimmed limit, let's call it 'unstable', the AP will not engage. This is a safety thing. Your AP has only so much authority to trim your aircraft into stability. It's no different in your A-10C. If your AP Pitch switch centered by itself, effectively disengaging, you are in one of the situations you listed above.

I am Winchester and can use guns. Or maybe I find a single Mk82 under my wing. That is all. So there is no VIS mode.

While fumbling around in the cockpit, I unsuccessfully tried to designate a random location in A-G mode with the HUD, which failed due to undocumented reasons. I got a SPI marker box and slew it to the left, visible in the HMCS. When designating didnt work, I tried again with the TGP, which caused the SPI marker to reset upon the first TDC input. I only had the TGP format in the MFD for this, didn't make it SOI. After making TGP SOI at 04:04:00, I noticed that TMS inputs had no effect. Also creation of a Markpoint was impossible. At 04:05:38 I am switching from Markpoint DED page back to CNI. Still no effect. Giving up. trackfile below OpenBeta 2.7.9.18080 NoTMSonTGPinCCRP.trk

See, this is what I grew up with in the A-10C a decade ago. Apparently this has changed meanwhile and tankers are now providing range. Good.

Since 2 weeks I am on the look out to find a solution for this: Let's assume we are transiting between 2 steerpoints. Now we see some ground targets of opportunity off our flight path - let's say firing artillery in maybe 5 NM in our 10 o'clock. primary task: secure coordinates of the target's location (to report them to other flights or to come back later with suitable loadout) secondary task: engage these targets. Whenever I try this, I run into some showstoppers. The interwoven dependencies of the sensors aren't that well documented in the manual so far and even Wags' videos can't demonstrate every combination. The HMCS suffering from the problem that it simply doesn't work for target designation depending on a diffuse and undocumented set of preconditions is the worst part in this topic. How would you solve the situation I described?

I am currently unable to get a designation box at all in NAV and A-G in the HMCS. When this is only available if you have a weapons loadout offering VIS mode, this whole feature is pretty useless most of the time.

I mean that some readers assume I am looking for precision or how to set a Markpoint by radar or by TGP. Which I am not. The HTS is obviously capable to show data on the DED. So the next logical step would be to expect this data also being available for creating Markpoints, just like the DED is showing an interface to the other sensors providing coordinates, FCR, HUD, TGP... So I asked if this is possible in the F-16C or even already available in the DCS F-16C. My interest clearly shows intentions to learn how it is done, if already implemented. Instead dudes tell me I can do it by slaved TGP and emphasize how very necessary the use of the TGP is to get a pinpoint location. How is this addressing my question? It doesn't. I often see this on the boards. People fail to understand queries because they have tunnel vision on the workflow they use. Any question from outside the box gets bend in a way to enable a reply which is based on their use of the module. They can't see beyond how it is working for them. So any question not matching their way of doing things is basically labeled as a faulty approach, the OP then gets lectured how he should approach the matter correctly. This is not helpful at all. Not only does this not answer a specific question, it even destructively prevents us all - the ones asking and the ones answering - to learn new things, to benefit from viewing stuff from different angles and to get enlightening responses from people who actually have an answer. I don't care for the precision of the coordinates. I know how to create Markpoints by radar and the TGP. Thanks! These answers are off-topic. I wasn't looking how to get any Markpoint by Radar or TGP. Even my line you quoted explicitly repeats what I was asking for: a transfer of coordinates not only into a readout page of the DED but into the Markpoint creation page of the DED. Obviously, this transfer isn't possible or at least nobody participating in this thread so far knows that it is possible. The next question would be if it is possible in the real world F-16. We also didn't receive hints on that. So, assuming there is no such capability, the question remained: What is the DED coord display good for? Answers arriving here suggested that this serves to send these coordinates to wingmen and others by radio. I find this idea not very well thought through, because for all your emphasizing on using the radar and the TGP for creating the Markpoint, why would you then still readout the coordinates from the DED? You could simply read them off your radar and TGP display to tell your wingmen. It's still unclear, what the DED display showing the HTS coordinates is intended to be used for. We can assume those engineers implementing this data to the DED by TMS right had something in mind. I would like to know what this might have been. Shrugging this question off by suggesting "simply use the TGP" doesn't really promote the investigation, don't you agree?

Yes and this doesn't address what I literally said at all. Thanks anyway

Assume you don't have a TGP. Or you are out of HARMs and wanna come back later, recalling these coordinates to navigate there. Please be creative. Btw. if 'there might not be anything', the TGP is not helping much anyways. Guys, please. Just stick to the thread. I know the TGP is convenient. But I was asking for the use of the DED coordinates.

I see nothing wrong

Oh, they totally are, as creating a Markpoint would be the obvious and simply convenient solution.

This also happens on my Virpil collective pitch grip hats and it seems to be a bad design of the mechanical contacts. It's simply hard to not accidently push the center down while moving the hat in one of its directions. As said, the only solution seems to not use (not bind) the depress input.

Yeah well, I am with you with the availability of these workarounds. Yet even more the question comes up then: what is the coords readout in the DED good for?

Maybe I missed something but isn't that accurate and also working like this since the release of the A-10C 10 years or so ago? exactly, isn't that working incorrectly? Should give only bearings...

Since we have the possibility to receive the approximate coordinates of an emitting site in the DED when working with the HARM Targeting Pod and display them in the DED, I wonder what to do with these. It would help to transfer these coordinates into a markpoint for example, yet I don't see how this would be possible right now. So my question for those who know: Might this be a real life feature which is waiting to be implemented in DCS some day? If not, how to put these coordinates to use in any way elsewhere? Using them as a Markpoint would be the obvious benefit...

The setting was a flight at night, where visual cues aren't available as much in target areas. So the idea was to locate the site by radar, set a markpoint there, so I could slew my TGP to that markpoint and start scanning for the targets from there, as the next steerpoint is way distant and there are no known target coordinates. Did this successfully the night before and form my memory I'd say the MAVs were on PRE then. I will try this out what you explained, also regarding the possible ECM interference, when I come home later. no worries. It's ok to bring this up. I didn't notice it so far when switching to TWS. Only in the case of making the HMCS SOI I immediately found it distracting, waiting for symbol to change until I lost patience and released the TMS.

A-G selected. Mavericks are powered on in the SMS format. RF up/NORM, FCR forward/on 1. I selected the ground mode in the FCR MFD. radar screen remained black, although I was flying across landscape, around 15000 ft AGL. Checked ECM XMIT wasn't on 2. switched ECM back to standby to be sure. Didn't cure it. Switched ECM back to OPR. Radar came alive. 2. after slewing around on the GM (radar MFD still as SOI), TMS forward to designate. Wanted to create a Markpoint at this location. So I pressed 7/MARK on the ICP. This switched SOI back to HUD, Markpoint DED page didn't receive any further inputs from TMS up. Displayed source in DED: 'HUD' 3. A-A selected, AMRAAMs selected in SMS. FCR is SOI. RWS mode TMS right long didn't switch to TWS as usual, no matter how often or long I pressed. All this happened while flying online. Any idea what I could have missed in any of these cases?

I agree, though in his two drops from 8000R and 14000B it still worked fine.

The laser will of course put its spot on the very location the TGP is showing in your MFD so what did you expect? It is to be expected that LGB will hit in this case. The laser doesn't care for the misalignment in your HUD and so won't the laser seeker in that LGB. I think we have understood the problem but you didn't really respond to the hints that were given so far. What exactly is 'the procedure' you now tried again? Explain it step by step or even better send a track. What about the Altimeter setting and INS alignment? Frederf asked if you are using some kind of mod. You didn't tell. Also cutting down your screenshots isn't helpful as many possible clues are now outside of the frame.

This isn't really evidence. We see the situation after release, so it doesn't matter if his TGP is tracking the target. As long as the SFW received the correct data at some time before pickle (which it apparently didn't somehow). He would have to tell us if he sent the data from a tracking TGP to the CBU before dropping. If he didn't, why did CCRP release the bomb? Only if the CCRP took the steerpoint or the target was designated with a different method (HUD). The misalignment of the TGP in the HUD is a hint, that even an evidently tracking TGP wouldn't have provided the correct data.

Set your altimeter to the QNH set in the mission. This is an everday procedure in real life aviation, if you aren't sure what this is about, you'll find plenty of stuff on this in the net. Think of QNH as the current meteorological pressure at sea level, calculated for your area. Due to weather, the QNH does change and has to be fetched and set into your altimeter for every flight, even during flights (if they take long or you transit into different regions, because weather may change during an hour and of course might be different in a region 100 NM away). You will find the value in the mission briefing. If you created the mission by yourself and didn't change anything in the weather settings, the standard 29.92 will do it. Take care to flip the little lever at the bottom right of your altimeter to ELEC and keep it there for some seconds until the indicators stop adjusting. At cold start, this lever may be on PNEU, which is kind of a backup solution only. Only then set the QNH value by turning the dial. Ideally do this before engaging INS alignment, or at least during the first two minutes of alignment, if you chose to go NORM alignment. If you don't know where to find your current QNH while sitting on the parking spot, look up your current elevation on the F10 map, then turn the dial until the altimeter shows this elevation. Radar alt and baro alt still will show differences, this is due to terrain of course. So in most cases your baro alt will be higher. On your pic it is the opposite, that is why it's obvious you didn't set it, as there shouldn't be any 1200 ft terrain depressions below sea level on any of the DCS maps.

Have the same problem, files attached I only flew the F-16 in these cases. I was busy with the TGP. dcs.log-20211229-223911.zip dcs.log-20211231-004429.zip