RogueSpecterGaming

If it fails on the first alignment process just realign the cross and press the ENABLE switch again. No need to do anything fancy.

If you are using a HOTAS make sure your throttle is out of the OFF position and in an IDLE or somewhere between IDLE and MIL.

This was pointed out by Cowboy 307 on Discord. Not sure if aircraft specific, but when doing the F16 Air Refueling Instant Actions on Caucasus and PG the AI F16s continue to get in line for refueling even if you call Intent to Refuel far out like in the PG instant action. Weird part continues when you abort refueling, the AI F16s will also abort but stay with the tanker. When calling for Intent to refuel again the AI F16s will go right back to refueling. The only way to stop this loop so you can refuel is to get in line right behind the AI and as soon as they get done call for Ready Precontact. Attached are the two tracks and should be around 5 minutes each give or take. Caucasus AAR F16.trk PG AAR F16.trk

This is what I am seeing, when not zoomed in I get this weird graphic thing going on with the HUD. When I zoom in it goes away, when I turn MSAA OFF it goes away, and when using anything other than MSAA 2x/4x it goes away and doesn't appear. I've checked drivers, redownloaded drivers, repaired DCS, reinstalled DCS, clean install of Windows, and just about everything else you can imagine including going through each graphics settings and turning them off/on both in game and in the AMD software side. This is happening with the F-16, F15E, F18, and AH-64. It does not happen with the A-10CII however. I am running a new PC build with a 9070XT, 9800X3D, MOBO: AsRock Phantom Gaming X870E NOVA WIFI, 32GB DDR5 TEAMGROUP T-FORCE @6400 (I have tried various speeds as well from 5200-6400). Yes, DCS is installed on a M.2 NVME. dcs.log DxDiag.txt NOT ZOOMED JUST CROPPED ZOOMED null

Havent watched the track yet but make sure you dont have the Markpoint page up on the DED. I will watch the track when I get home from work.

Because I worked on the F16 and use to mess around with the TGP. And that is how it works. I can promise you it works as advertised. Because the TGP needs an image to go into regular INR in order to stabilize on. Inertial rate requires an image or it doesnt know what it needs to stabilize on. When you switch STPTs it will stabilize on a set of coords and doesnt need an image on that case. But once you have slewed the TGP you created slew errors and therefore it needs something to stabilize on. This is why it briefly goes into INR AREA/POINT before actually going into AREA/POINT. It is essentially saving the image in the image correlator. It keeps the CZ on the MFD anytime there is a slew error and pressing the MFD CZ is always treated as the "master" CZ essentially and tells the TGP/SPI to go back to the coords; whereas the HOTAS command is treated as a secondary option and is moreso telling the TGP to go back to the first image in the memory which can only do so if it can see (unmasked). Similar to how when you close your eyes and then spin yourself, and without opening your eyes try to face towards the last thing you were looking at before you closed your eyes. You can only correlate when you open your eyes.

Bump

Alright, I did some testing by taking control of your trk. - TMS AFT is not functioning correctly when masked. In the trk I uploaded you will see I mask the TGP, and I am actively pressing TMS AFT and it does not CZ or going into regular INR. HOWEVER, as the trk plays you will see that I do manage to CZ and even go into INR while masked. I am only able to do this because I am slewing the TGP ever so slightly to bring it out of INR AREA/POINT and pressing TMS AFT at the same time. Final conclusion: This is accurate and works as intended and here is why. You cannot CZ when the TGP is in: AREA, POINT, or INR Tracks (INR AREA/INR POINT). When in AREA or POINT notice you have to TMS AFT in order to bring it into INR first (not INR AREA or INR POINT just plain INR) in order to TMS AFT again to CZ. The reason you cannot TMS AFT 2x while in INR AREA/POINT is because that is the TGP correlating the image. You can test this out for yourself by having the TGP in front of you at the first stpt and slewing the TGP in order to have INR AREA/POINT appear and pressing TMS AFT twice to try to CZ, it will not work. So, if you have the TGP masked or it is about to be masked before you enter INR yourself, it will go into INR AREA/POINT, and that means it is attempting to correlate the image to what was stored in the memory but cannot do so. INR AREA/POINT goes away the minute you unmask. Now, if you have one stpt in view and switch to put the other stpt behind you; you will notice that it automatically goes into INR mode. That is because it is going straight to the coords in the memory and doesn't need to correlate the image because no slews were made. But the minute you slew it, it will enter INR AREA, and you will not be able to CZ or enter INR. The only reason I am able to enter INR or CZ while being masked is because I am triggering it between the time it takes the image correlator in the TGP to correlate the image and the time I stop slewing. It happens very fast, so you have to TMS AFT 2x very quickly. no TMS aft to INR - Rogue.trk

I've just tested and if you look at the Radar Scanning (bottom of the FCR) when you TMS up long it will allow you to move the radar with your JHMCS. You are expecting to see the oval symbology, but you won't see that in NAV mode.

The wings on the tail package of the GBU12/10/24 do not "ignite". The wire that attaches to the wing release latch gets safety wired directly to the sway brace of the MAU-12 or sway brace on the TER (there is no arming loop that goes into a solenoid). In the case of the MAU-12 with a GBU12 on it, you have two arming loops that go into the solenoids: one for the initiator that goes into the center solenoid, and one for the BFD on the CCG that goes into the nose solenoid which is slid onto the wire for the BFD. If you have a GBU12 on the TER, both BFD and wing release latch wires get safety wired to the sway braces of the station that the bomb is on, while the initiator goes into the nose solenoid on that station. So, in the case of the GBU12/10/24 on a MAU-12 the choice of NOSE is for the BFD arming loop and the initiator arming loop. This is considering the fuze you are using is either the FMU-139 or FMU-152. You can equip a M905 but it is not a typical configuration in real life. If you have GBU12s on a TER the choice of NOSE is for the initiator only. MAU-12 Selecting (GBU-12 with FMU-139/152): NOSE = Bomb will arm and guide (will DUD if using M905) NOSE/TAIL = Bomb will arm and guide TAIL = Bomb will DUD and not guide (will go unguided but will still explode if using M905) Just gotta remember what fuzes you put in the bomb. But you are always safe going with the N/T option.

JDAMs are currently only using "Relative Targeting" at the moment. In other words, the JDAMs on the F16 do not have the GPS enabled just yet. This has been talked about to death in a few other forums if you just search "JDAM". You are doing everything correctly though by the looks of it. In relative targeting mode the accuracy for JDAMs is a 30m CEP. Your bomb is falling within that 30m CEP judging by the pictures. Make sure you lase at the base of the target though before dropping and lase as you press & hold the pickle button. The reason why you want to hold the laser down is to ensure the coords (including the correct altitude) are correct. You will notice this if you were to lase the top of the tank you will get a different elevation compared to lasing at the base of the tank. As far as impact angles those are going to be relative to distance. See above as to why you lase. It is common practice to lase before dropping a JDAM in the F16. Being in Area or Point track doesn't matter as the SPI is controlled by the TGP either way. MAN/AUTO is specifically for AGM-65s for Handoffs. Not related to this at all.

Why not just save the loadout you made, give it a name, and then all you have to do is just select it from the drop down menu? That saves more time than anything honestly. I get the idea but the saving loadouts options is pretty good.

Not everything is fully modelled like the A-10. The A-10 is much much older and has had plenty of time to be worked on and outside the A-10C II, the regular A-10C is a fully finished product.

I would get rid of the way and DICE, unless you fly the A10C, A10C2, AV8B, M2000C then keep those, but this program works better for the F16C, Strike Eagle, Hornet, and Apache, and incorporates both those programs into it. And you can also share your settings with others if you play in a small/large group, and with the new update they added a kneeboard function. And you said the DiCE program doesn't work anymore so for countermeasure settings DCS-DTC is the next best option for you.

Release Version 8.1.0 · the-paid-actor/dcs-dtc · GitHub Use this. It is literally the best thing out there right now for the F16 and a few other aircraft and it DOES NOT break IC at all as it doesn't mess with LUAs. You're welcome.