darkman222

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.

As a workaround you can use GM radar. You will see the cross on the HSD move accordingly. You can create a mark point from that. Works especially well when you have a thread ring of a SAM site you need for a mark point. Although I think thats a feature the F16 actually has. But selecting a thread ring center as a markpoint / waypoint could also be a feature our F16 does not have due to its time frame.

What do you mean? I tried it and it works. If you have lets say, 4 waypoints close to each other, you cursor slew one, all the others are moved accordingly. CZ and they are all moved back to the initial position. No issue here. If you use FIX, it does the same. But you can not CZ to the initial position any more obviously. So can you be more precise what you are referring to?

I also had "blackouts". But playing in VR. Especially when holding my head still for air to air refueling. I never figured out how to fix it. Could be a placebo, but I never had it again when Tacview was uninstalled. So every time I knew there was AAR involved I uninstalled Tacview. You might want to give it a try as well. At least if it helps it would have been an easy fix for now.