darkman222

Here is the original thread I created in 2023.

I reported that the F16 switches to radar ranging when a mountain is blocking line of sight to the target area measuring the radar distance (F) to the hill thats in between instead of measuring the distance to the waypoint (B). You can work around if you make a mark point for the target, then use this steerpoint while looking down to the HSI to see the real distance to target to coordinate your pop up. HSI does not switch the ranging method. My report was marked as "investigating" and disappeared quietly over time. If you want to make another report feel free to do so, together with track replay.

"that mission requires activation" never seen that message, thus cant replay your file. But what you describe sounds weird and reminds of when I am too excited slewing the Maverick seeker around to find ground targets, but accidentally pressing the RDR Cursor button while slewing, which intentionally puts the Maverick to VIS. Press the RDR Cursor wich is called "cursor enable" and it will cycle through VIS, BORE, PRE and so on. To be sure remove all the keybinds for"ENABLE switch- depress" and try again, see if it happens again.

I would like to give it a try. Can you be more specific which Lua and the corresponding value are?

The trim rate ( polling rate ) of the DCS F16 is way to fast to hit the perfect trim setting. I woul be glad if it could be reduced in future updates. Or if there was a setting implemented. Just one click of trim always overshoots the perfect trim position.

From chucks guide: NORM: all electronic signals for the aircraft are enabled • QUIET: radar, TACAN, and data link transmit but all other emissions are inhibited. • SILENT: all electronic signals for the aircraft are disabled, and include the radar, radar altimeter, data link, TACAN transmit, and ECM.

Everybody who is flying the F16 on a more proficient level has his own MFD layout, which tends to be often very similar between people doing the same task in the F16 though. For example AA: Right MFD (in Nav, MSL, DGFT mode) : HSI, TGP, SMS For example AG: Left MFD: HAD, TGP, FCR. Right MFD: HSI, WPN, SMS That creates the recurring task of setting the MFDs up every mission, especially repetitive on public servers, when you'd respawn often during a session. NAV, MSL, DGFT, AG are 4 separate MFD main modes, that remember their own setting, you have to set up 3 MFD sub modes each for every of the 4 main modes. Which means setting up 12 screens in total, worst case. In the real jet this will be set up via the DTC with one button press. At the moment we only have the option to use the external DTC mod. I attached a screenshot of the DTC mod functionality that covers most of what would be needed for EDs native DTC. As we dont have a roadmap for the ED DTC I can not check if this is already in the planning or if it probably will be missed, which would be very sad.

The amount of trim you get with one click on the trim button is way too fast. Thats why you cant get the F16 trimmed out perfectly, nor can you bring the trim back to neutral, because of the sensitivity of the input you just overshoot the perfect trim value. A trim reset is a good workaround, and or reducing the speed of the trim input per click would be the realistic way to approach it.

Thanks. I did not expect that. But what youre saying is, as the TGP is not replaced, it would stay on then. Which confirms that the behavior of the current rearming process is correct.

Thanks a lot. I was asking for a roadmap to get an idea which features are still in the planning and which ones are probably not, although they might be highly anticipated by users already using the external DTC app. If there was a "MFD configuration" drop down or a greyed out button showing that its in the planning for that feature, me and probably many other users would be glad to know its in the making

Asking especially for the F16 because its pretty hard to tell whats coming or whats not. Pre-configuring the MFDs is such a powerful and handy thing ( and probably comparably simple to implement). Its the only reason I still use the external DTC app that remote controls the ICP to setup the jet, which breaks track replays and is already bugged because the order of button presses is not correct any more after some DCS updates. We already have custom CMDs and radio channels in the DCS DTC. Bein able to set up what page in what sub-mode is shown on a particular MFD would be so helpful. Any statement on that? @BIGNEWY Many people using the external DTC app would be very sad if that was overlooked.

What do you mean? I guess in real life you would never rearm a jet with the engine running, would you? Yeah I think that was the issue too. It was how the rearmarment process was programmed which lead to the behavior that is luckily fixed now for everybody who flies on servers with quick landing, refueling and take off turn around gameplay.

I am wondering the same. While the flight model of the DCS F16 has been improved over the past years a lot, why does it not affect the take off behavior too. Probably a separate look up table for take off behavior that was not changed according to the other flight model adjustments.

If you fire your first Maverick using the ATP, Litening, GMT or even VIS mode, the seeker of the second Maverick is stuck in the middle of the HUD. Which obviously does not make any sense. As you probably want to do a follow up shot. You can bring it back to move to the target area using TMS Down. So it goes back to where ATP, Litening, Ground moving target radar GMT or even the VIS designator is looking. Tracks for each method attached. atp.trk GMT.trk litening.trk vis.trk

I did not think of that. But whats the difference if it loads your default.dtc on cold start, or if it loads none? If you will change your settings for that particular mission you would do it anyway, no matter what was loaded before.

In general it is questionable while you rearm with the engine running in a few minutes in DCS then need to wait for the old TGP to reboot is a realistic combination at all. If the rearming procedure was realistic ( 45 minutes incl engine shutdown and restart ) a TGP boot would be required anyway because ground power does not power any of the TGP. Considering DCS rearming being a game mechanic that way, the need to reboot the litening TGP is not a realistic logic or addition to realism anyway. So its good we dont need to with the ATP.

And thats the reason why I created this thread in Wishlists. Wouldnt it be awesome to create a custom DTC comfortably with the DTC Menus ED is working on, then just click for example "make default DTC" and it will be either loaded into the jet already or at least ready for you to start the loading process via the MFD buttons? Imagine to go to servers like DCS Dogfighters BVR arena, where you can practice many BVR engagements in very little time respawning in a short time and have your CMDS and MFDs already set up each time you spawn.

If you do a trackfile, try to do a short one with only the issue isolated. Airspawn for example. Then dont use Mods. There is the eurofighter mod needed to be installed. I went through it fast forward and saw in the first engagement the TGP was NOT SOI. That could be the issue. In the second engagement the Mavericks were set to Boresight aka BORE. They wont slave to the TGP in BORE. Switching to BORE happens when you accidentally press the cursor enable switch on the hotas, or when its bound with some other key you press together with it. Make sure to stay in PRE mode all the time and that the TGP is SOI before you press TMS up on it.

Thanks. Although I dont fly the F18 it seems to work the same in the F16. Well it does not to break IC. Thats basically the same way we had years ago, when we modified the old CMDS.lua ... before it started to break IC. I would not wonder if it starts breaking IC at some point again. It works for me, and just brings back what we already had, back then. I hope we get the functionality to set up MFD pages next. I dont mind to go through different LUA files to set stuff up. But thats clearly not desireable, and also not user friendly. Especially not because thats the reason we got the DTC. 99% of the time you want to have the same CMDS and MFD setup. That could be in the default DTC for a standard quick action public server sortie. I was quickly looking through the lua files if I could find something to change the default MFD setup- but that does not seem to be integrated yet. Not even in the LUA files. EDIT: It is the EXACT same thing like the old CMDS.lua trick. You edit it, but as soon as a DCS update is rolled out it is being overwritten. I think thats not the proper way to edit a default DTC.

As title says. It would be very helpful on servers where you respawn a lot to have it already loaded. So you'd only have to press the MFD buttons once in the jet instead of browsing through files on th HDD via the DTC menu. As soon as DCS sees a default.dtc file it loads it. If it does not find it the behavior stays as we already have it. For people who like to browse through menus

But what would you do then, if FIX is overridden by GPS. When the accuracy is really 300 ft only instead of 131 ft, which has not been answered yet? 300 ft of INS drift that GPS does not fully correct but that can not be corrected by FIX taking either?

From what I understand is that our (pre EGI) DCS F16 will always have an induced INS drift, that will be corrected via GPS within the limits, which is happening now after the patch has been released. So what was fixed is not that it does not drift anymore, because this is not realistic. What has been fixed is that the drift stays within the allowable realistic limits. Thats what I tested here, and which is the case. As long as we agree on a altitude drift of 30 ft ( 100ft is allowable) and the lat/ long drift is about 300 ft, the fix is on point. Although 300 ft should be the maximum drift where GPS should start correcting it. If you read through the entire thread discussion which is not too long, 300 ft is the maximum drift, when GPS should be activated to start to correct it to a nominal drift of 131 ft (40 meters) . Which is also the amount of drift that is talked about in the Viper Mini Updates white paper, dealing about Kalman filter. If we want to go on discussing something here then it would be the only thing that still stands out: If it is 300 ft or 131 ft we should be experiencing with GPS corrections active.

In general the F16 has had 2 radar updates. 3rd one is still missing. But this should address ACM modes as far as I know, which will not address RWS or TWS. Better do a bug report as it seems like the general F16 section here is seen more as a place for discussion.

Was fixed and mentioned in : en/news/changelog/release/2.9.17.11733/ ->Fixed: INS drift is not GPS corrected and INS drift adds up to more than 1000 ft over time. Which is the exact title of the bug report that I submitted about it in the bugs section. Its now in the allowable limits. Under some circumstances the drift seems higher though. But the reasons will remain a mystery, I guess... Thats why I did the additional test of the drifting in altitude. Which is also in the allowable limits.

Yeah in that case you are right. If the CGI or wingman gives you the bearing and distance from a waypoint to the target, the easiest way actually is to use offset aimpoints. I was just imagining the original poster to move the cross on the HSD around, trying to create a mark point, so I wanted to bring the option to use GM radar up too.