RogueSpecterGaming

Alright so a quick breakdown of fuzes and what to select and the bomb will still work: MK82/84 GP on a MAU-12/TER with M904/905: NOSE, TAIL, or NSTL selected = bomb explodes MK82/84 GP on a MAU-12/TER(82 only) with FMU-139/152/DSU33: NOSE or NSTL selected = bomb explodes TAIL selected = DUD MK82/84 GP on a MAU-12 with FMU-139/152/M904 NOSE or NSTL selected = bomb explodes TAIL selected = DUD MK82 GP on a TER with FMU-139/152/M904 NOSE, TAIL, or NSTL selected = bomb explodes GBU-10E/B and GBU-12B/B on MAU-12 with FMU-139, FMU-152 tail fuze only NOSE or NSTL selected = bomb guides and explodes TAIL selected = DUD: Bomb is unguided and fails to explode GBU-10E/B and GBU-12B/B on MAU-12 with M905 tail fuze only NOSE selected = DUD Bomb guides but fails to explode TAIL selected = DUD: Bomb is unguided but explodes NSTL selected = bomb guides and explodes GBU-12B/B on TER with M905 tail fuze only NOSE selected = DUD bomb is guided but fails to explode TAIL selected = bomb guides and explodes NSTL selected = bomb guides and explodes GBU-12B/B on TER with FMU-139, FMU-152 tail fuze only NOSE or NSTL selected = bomb guides and explodes TAIL selected = DUD bomb is guided but fails to explode Who knows maybe the hotfix fixed the problem with bombs going DUD. I havent tried yet but I will soon. I did not have a tracking problem. The bomb guided down to where I was pointing (stationary target), but it didn't explode despite having NSTL selected. Will do some testing this weekend and see if they magically tossed a fix in.

He said route tool though. And ngl I've never used the route tool, so does it function the same way as the ME? Where if you put 0 it will auto adjust to MSL?? And correct. The JDAMs on the F-16 only uses Relative Mode (which the HUD should indicate but there is no indication currently). It also only uses the INS portion and not GPS. Hopefully sometime this year or next year we will see it get that. When we do get that we should get absolute mode at the same time. But this is also why we should not bring other aircraft into this discussion as the JDAMs on the other jets do not suffer from the same thing as the F-16 does. This is also a topic that has been brought up and talked about countless times. A quick search would get OP all his answers about this.

https://www.af.mil/About-Us/Fact-Sheets/Display/Article/104527/sniper-pod/#:~:text=General characteristics,Point of Contact The 446lbs is the pod weight itself. The pylon it attaches to is only around 50lbs. Total weight should be about 496lbs. I will send BN/NL evidence later. Upon looking at my official sources with more info. That 446lbs includes the pylon weight. So the Sniper ATP is 425lbs, and the pylon is only 21lbs for a total weight of 446lbs.

If you are putting 0 for the elevation then that is your problem. I also think you are misunderstanding what AGL means and how to use it. If you set the altitude for a Stpt in the F16 to 0 that is completely wrong. Say you have a tgt and coords X, Y, and the ground is 1850 MSL. You wouldn't put 0 into the DED, because if you did then you are telling the system that at X,Y the elevation of the ground is at sea level. Doing this will move your stpt "under" the ground which would translate to your bombs hitting far away. The number you should put into your DED is the MSL of the ground, so in this case 1850. Now you are telling the system that at X,Y the ground is 1850 above MSL. I've never had a problem with GBU falling that far from a target. 50-100 meters pretty far outside the CEP. Go ahead and place a stpt and put the number you see for Altitude on the F10 map into the DED and try again. And don't compare the Hornet's system with the Viper's. You will just further confuse yourself and others.

Thats just you not holding the nose at 13 degrees AoA. I've consistently gotten to 95-100 kts with 2xtanks, 2x 120s, 2x9, 2x WWPs. With a slick jet I can get all the way to 70-75 knots.

Yes this is correct behavior. Been like this for a while now.

Are you sure you are calculating the speeds correctly, i.e. accounting for winds (headwind/crosswinds), AB vs non-AB speeds, if you have any roll trim? And do you know what speed the Viper was going and what the winds were across the runway in the real-world video you posted? Side note - Real world maximum allowable takeoff GW (48000lbs) based on MLG tire limit speed is 225kts with no winds. But this number changes based on a few things like runway temp and altitude. Could go more into it but not the topic of course, just extra info. If you are still wheels on the ground at 200kts then that could mean you either pulling too early or pulling too late. Pulling too late means you need to use more runway in order to be at a speed to gain lift backb because of ground effect essentially sucking you towards the ground. Pulling too early and the horizontal stabs create drag that will again require you to be at a higher speed to compensate for the increase drag. I typically takeoff with a standard AG loadout (2x 120s, 2x 9s, 2x tanks, 4x 12s, TGP, HTS, ECM long) and depending on the winds on the server my rotate speed with AB ranges from 167-176, meaning my speed at which the main landing gear is off the ground is around 180ish close to 190ish. And thats with aiming for a 10 degree pitch. You would increase takeoff speed 8 percent for an 8 degree pitch. Im not at my computer right now cuz Im mid shift so Im at work and cant watch your track right now. If you can post your weight, winds, and if you used roll trim what your DOT of trim was, that would be helpful as I can do some math while Im waiting and when I get home I will look at your track. I haven't really noticed anything wrong but Ive been busy focusing on the Sniper so maybe I just havent noticed it lol.

If using a FMU-139, 143, or 152 and no fuze in the nose (plugged), keeping it on NSTL is fine as you need the NOSE option in order to have the center solenoid hold the arming loop on the initiator which activates those fuzes. You could select the NOSE only, as the initiator is the only loop since those are electrical fuzes (will double check my work notes but 99% sure you can do that). Mechanical fuzes like the M905 requires the TAIL option as the loop for that goes into the tail solenoid on the MAU-12. Default MK82s in DCS usually always come with both nose and tail fuzes (M904 and M905) so NSTL should've activated the fuses. If you can, can you please post a track. I did have a GBU-10 appear to DUD on me as well the other day, but didn't think too much of it as I was focused on something else.

Mmmm that's weird ain't it. You can find that little note on page 414 of the manual by the way. Oh and again on page 403. And some people are new to DCS and he didn't give too much info either. It could've really well have been that he was too far don't you think? Or are you just high and mighty and feel need to make a comment on everything and think you are right? And I've definitely fired the Litening pod laser well out of 8nm and gotten the L for range. I think the farthest I got was like 20nm or so cuz I would always lase the target before dropping GBU-38s. So no, in DCS they do not have the same range. And where did I say he was flying at an altitude of 50K? 8nm Slant range not freaking altitude dude dang. Like who refers to altitude in NM??? lmao Cool I must've missed it in all the nonsense ya'll are talking about. But he never specified which T soooooooo there is that. How am I confusing two things? We have a Sniper pod that is actually a sniper pod and not two pods mixed into one. So really the Sniper is the benchmark now, and there is no vice versa about it. Lantirn and Litening into one pod isn't a good comparison to make against a pod that is actually being simulated now. You literally can't compare the "Litening" on the F16 to the sniper because it isn't actually a litening. If it was it would be a Gen I or at best Gen II. But both Litening and Lantirn would have much worse clarity due to the constant need for contrast/brightness adjustments and the fact that the old Litening and especially the Lantirn are horrible at image recovery after a bright flash like that from an explosion, if you consider the year ED would be modelling. The current Litening on the F16 needs to be removed completely and never seen again. And I'm not talking other aircraft, just the F16. Do other aircraft sensors need to meet the standard as well, of course they do. But this thread is not about other aircraft at all. And the whole "We either choose one path – game mode, or realistic. not both in the same title." comment is literally what I am talking about. But you, for some reason, are trying to go another direction. You cannot deny the fact that there are people currently complaining about the two pods and wanting something done to the sniper to make it clearer like the litening. Which again in DCS are completely different altogether. The real-world litening Gen IV and the sniper are more comparable than the sniper and the lantirn are if they were compared together. The "problem" isn't really hard to fix. Just remove the current Litening on the F16 and problem solved.

Did you happen to hit ICP 7 for markpoints? If so, you cannot be on the markpoint page of the DED as the Markpoint page takes priority of the sensors and you cannot use the HAD to create markpoints.

Ive been following it and ya'll still comparing a pod that isn't really Litening pod but a mix of two pods. You either get realism or you dont. You cant really have it both ways unless you ask for a setting where it makes your pod look better than others. That is something I dont think will happen. The Sniper works, looks fantastic, and this is coming from real world experience seeing it in the jet. How you gonna reference old material? You do realize the manual was updated with the Sniper pod info right? It is literally noted multiple times that the laser will not work outside of 8nm. The only other things that can effect that range is clouds and dust/fog. And in my tested in the sim the T will not change to L until you are within 8nm of the target. Again, it will change from T to L. And the person asking never got an answer. That is why I answered him. Dont refer to forum posts from literal years ago and not even about the same dang pod. That doesnt make sense to do my guy. This.

You do realize a vast majority of that footage the pod is under 10nm when looking at stuff, right? Here is a better video for you skip the intro go to 0:10. They even talk about how they are only 13n aways. And when they are tracking the F16 they are about 14nm. Im getting pretty good image quality in DCS when using the Sniper and Im using MSAA 2x. Im sure msaa 4x would be even more clear. But I bet a lot of the people in here are using DLSS or FSR or something which just isnt that good and blurs the image a lot. I would stay away from DLSS/FSR usage imo but i know that isnt much of an option for most. Later I will post images of what I am seeing. All the way out to 40nm.

The laser only works under 8nm. If you fire it outside of that the range will not display the L. Read the manual.

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.