Rongor

forget abut this post

To be clear, there are no penguins nor seals at the South pole. You will find them at the coast of the Antarctic though, as they need water, but not at the pole, which is way inland.

any further questions might find answers in this subforum: https://forums.eagle.ru/forum/284-steam-support/

I really don't think Boeing had anything to do with the design of this airplane.

You'll have to chose: To do your first steps in flying helos: Huey To prepare your brain for cockpit management in an attack helo: Ka-50 2 weeks won't do it though

Do we really need a second nonsense thread like this within 5 hours?

You do. So what? Still why reduce the radar screen to not be able to use this one too? Do you want to corellate contacts with your HSD visually all the time? Why not following the datalink target with your radar antenna early instead of constantly crosschecking both MFDs until the target comes within a fixed range of 20? Your radar doesn't have a fixed range, nor does the enemy's. KISS concept applies.

No, absolutely don't do this. Datalink targets visible in the HSD also "carry over" on your radar screen. So regarding airborne threats you can gain and maintain the same situational awareness as with the HSD. This might not be a thing in calm self made SP 'try out something' missions. But it will in campaigns and of course in MP. Reducing the scope to 20 by default can make you lose track of stuff going on way ahead of you. A threat heading towards you, when you both fly with 400kts, only needs 3 minutes to come from 80 NM distance to 40 NM. You don't want to not be aware of this. Below 40 NM, there is a chance to target and get targeted. You will receive RWR warnings and probably be defensive against incoming BVR attacks long before enemy is within 20 NM... If you enjoy datalink contact, leave it at the higher ranges, 40 or 80, consider to keep your RF quiet or silent until you commit to a target closer than 40 NM. Only then reduce scope range accordingly and after adjusting antenna elevation concentrate on catching the target with your own radar emmissions.

Generally your F10 doesn't interact with your cockpit. This is only featured in the DCS Harrier. Yet what you are asking for is available in the DTC for DCS F-16 Viper mod

Firing mode shouldn't affect the targeting. Instead enables Petrovich to launch the missile as soon as conditions are met and not waiting for your consent (trigger). Petrovich silently just moving the crosshair over the assigned point during 'daylight' was a bug, apparently solved in the 2.7.9.18080 patch Fixed Petrovich AI stopping to react at short up command in ATGM sight CMBT mod Also see this from the 2.7.7.15038 changelog Petrovich AI Target acquisition code refactoring (Petrovich now will not acquire targets in the night or dark enough environment. Petrovich will see targets in dark environments if illumination flares are used. Petrovich will see targets behind some obstructions that were blocking acquisition before but geometrically were not covering the target.). Known issue: in some specific relatively good light conditions Petrovich acquiring targets too close. Adjustments WIP.

Wouldn't this carry the current offset over to the next steerpoint?

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.