SpecterDC13

Ok, and like I said, how do you expect me or anyone else to watch a track if we don't have the map? Do whatever tests you want to do on Caucasus and then send me that track so I can see your claim. But I am taking the time to do these tests and as seen above and if you want the tracks to see for yourself, I can send them, and you can see for yourself. The only downside is the track is an hour long so not sure if it will work correctly but I think it will. I have more tests to run which will include doing the test without GPS enabled. So, if you want you can see what those results are.

This one was done prior to the update and the TGP was used and was only done for 30 minutes.

Just finished the first of many tests today. This was done with using the STPT only. No other sensors like TGP or FCR was used. A picture of the HUD is included to show the amount of drift that occurred over the hour of dropping. This was only the GBU-38. The black line circles are every 10ft starting at 20ft. My next test will be done with no GPS available in the mission and again only using the STPT.

just to make sure you aren't using ReShade are you?

@Lord Vader possible merge?

I would watch the track if I had the map. That is why ED suggests you to only do Caucasus IF possible. Not that you have to, but when someone doesn't have the map you are testing then you can't get mad when your track doesn't get watch. So before I watch that first track you mentioned what map is it on? I'm not going to waste my time downloading a track if it is on a map that I don't have. I have every map but Kola and Normandy. The second track you mentioned sounds like it is on Kola so I cannot watch that one. But as I mentioned in another forum about what seems to be a similar problem "In order to perform a FIX/update certain factors must be met, and they can include: SYS ACCUR, GPS ACCUR, and GPS TRK/NOTRK. Now assuming normal GPS values of <50 feet and GPS in track, the Blended KF will have more confidence in GPS-aiding than a 300ft fix/update. But once the SHE exceeds 300ft for whatever reason, then a fix/update on a known stpt may be recommended. The position delta is estimated from the coords of the stpt. That delta is displayed to you on the FIX page." And as well as,"The 38 we currently have on the F16 is not fully "equipped" with the full GPS package so no, it will not update as it should once it is released from the aircraft. So, without it you are going to see some weird behaviors which yes, is normal, but as you can see in the picture it is still accurate." Bottomline is the 38 or 31 currently is not going to be as accurate with a preplanned stpt currently. See this forum to see where I posted a picture of me dropping 47 GBU-38s over a 30-minute period. This was done without a FIX ever being done and with a good amount of drift occurring over that period. Granted I did use a TGP, but my next tests will be done with the TGP again because we just had an update, and I will also run them with a preplanned stpt. I will also increase the time from 30 minutes to an hour if possible. I will also do various distances as well. This first test was done at angels 18, 6NM from the Target at speed of 450kts, bomb impact angle was set to 75 degrees in order to ensure a straight down impact point. Out of 47 bombs 27 hit or came extremely close to the target. But you will see not a single bomb fell outside that 80x60 box. And right now, just with this one test alone the JDAM fell within the 30m CEP and quite a few more fell within the 5m CEP.

I'm not trying to be rude. Just letting you know that what they are going to say is exactly what I have said. I work on the jet and so I know what it should look like. And yeah, it hasn't changed over the years. But they will still ask for a source. If you have one, I highly suggest PMing BigNewy or NineLine. That is best answer you will ever get man. Just trying not to waste peoples' time that's all. A lot of people come to the forums expecting every little thing to get fixed without providing the proper documentation that the team asks you to provide whether that is tracks or public docs. And honestly it isn't as pressing of an issue as a lot of other things right now imo.

It's part of the "canopy reflections". Go to your settings and set the "canopy reflections" slider to like 0.3. That's what I did and it looks way more realistic/better.

Thunderbirds dont fly Block 50s. So that is irrelevant. And you know ED will not accept that. This is from the back of a D model F16 and judging by the electronic altimeter definitely not a blk 50 either Not from a blk 50 though? This guy is the closest. If only the picture wasn't so blurry. Also it would have to be from around 2007. Which reading the video description is from 2018 demo fight. You guys do know ED will shoot all of those down saying the same thing. So, try harder if you want things to change to be accurate/correct.

You still need to put the TGP into a tracking mode either point or area. Per my sources you can do TMS up short to go into point track or you can do TMS Up long to go into PT. This will remain true for the Sniper once we get that as well. Trust me I know the SPI is automatically updated with the TGP when in PRE modes for the F16. It is a bit old but will remain true like I said for the Sniper as well. https://youtu.be/MvQB6tVK-S4?t=562

Did you miss the part where ED has already come out and said that the GPS in the 38s, for the F-16 or any other modern jet, is not fully completed? Or are you choosing to ignore that and gloss over that? You mention other weapon systems but what other weapon systems are affected by this? If you say something give an example don't just make a generalization. Because from my experience I have had no issues whatsoever using any other weapon system to include the JDAM. Just the other night I tested the 38s alone, and once this update drops, I will test them again and include the 31s as well. You can see in the picture it was a good 30 minutes of straight dropping on a single point. Over those 30 minutes I had INS drift on me. 27 out of 47 JDAMs landed on or near the target. Nothing dropped outside of the box as you can see. The next time I test I will do an hour-long session of dropping if needed. This instance was with the TGP. In my next testing runs I will do it with the TGP again AND with preplanned stpts. I'm also not one that just gets into a jet and goes running into an AO nullall willy nilly. I play as close to the realism side as possible as I am an actual F-16 weapons troop, and I like to see how real I can make things. I'm not just getting my info off the internet from a -34 that has nothing to do with our specific model/year of the F-16. I have searched the internet far and wide and the only "-34" is from the other F-16 sim. Granted that does have some things that are shockingly identical to certain things but I won't get into that, it still does not tell you everything you need to know about how a FIX works or when you should do a FIX. Back to the main point though. The 38 we currently have on the F16 is not fully "equipped" with the full GPS package so no, it will not update as it should once it is released from the aircraft. So, without it you are going to see some weird behaviors which yes, is normal, but as you can see in the picture it is still accurate. Also, not every jet has or works with the same set of systems as far as DCS goes. For instance, since you want to bring the F18 into this, the F-18 in DCS is from 2002 and uses EGI, whereas the F16 is from 2007 and uses only INS/GPS and you can tell this by the fact that the NAV knob says INS above it. I promise you the systems between that five-year gap is going to be quite large. But to shed some more light on FIX taking here you go. In order to perform a FIX/update certain factors must be met, and they can include: SYS ACCUR, GPS ACCUR, and GPS TRK/NOTRK. Now assuming normal GPS values of <50 feet and GPS in track, the Blended KF will have more confidence in GPS-aiding than a 300ft fix/update. But once the SHE exceeds 300ft for whatever reason, then a fix/update on a known stpt may be recommended. The position delta is estimated from the coords of the stpt. That delta is displayed to you on the FIX page. And talking to actual pilots who have flown older block 50s which had only INS, yes doing fixes was a pretty common thing, especially under certain scenarios. The newer jets with the EGI it is much less common for them to do so. Which is why you don't see it in the F18 I'm guessing. But I'm not going to speak on the F18 because I have never actually worked on it or talked to those pilots so to compare it with the F16 is just useless really. But I think the biggest problem with all this is everyone is complaining about something that ED has made very clear that it is all a WIP. Which sure gets tiring to hear but it is what it is at the end of the day. The GPS in the 38 and other JDAMs will come I'm sure it is just a matter of waiting. But to sit there and complain and not provide any proof of what you are experiencing only hinders advances in making things better. How about instead of complaining, go fly the jet, save the track of the problems you are facing and make a bug report about it in order to make it noticed. And if a bug report already exists then add to it if you can. The more evidence/proof you provide that something is off or seems broken could only help make it better. But from my experience, again, I haven't really noticed anything too off. There is only one thing I noticed, and it is dealing with an Air Start F16. And guess what, I am saving tracks in order to make an actual bug report in order to bring light to that particular problem. I'm not going to make a report making a claim and provide no evidence. ED has made it pretty clear that without a track file or even a video they can't see or know exactly what is going on. Most of the time it can just be a small value that needs to be changed in a Lua. And yeah, me saying go watch a video or go read something can only help the person especially when most of the time it is just user error. Not saying this particular case is, but you never know so to discredit me doing that is pretty crappy of you. But you can't say something doesn't work like it should and provide no proof or evidence that it should work XYZ way. But I will end with this. This JDAM issue isn't so much the F16. It is the JDAM and the lack of GPS on the bomb itself. And so far, I haven't noticed it on any other weapon, but that is mostly due to me dealing with GBU-12s and AGM-65s recently because people seem to be confused with certain things with those. I.e. the popup cue for the 12 still gets people. I am going to do more testing and longer to see if I notice anything out of the norm with the JDAMs. But as of today there is going to be an update I am going to wait and see if there is any changes dealing with that issue. If not I will still run the 38s again but I will also run 31s and JSOWs for the F16 and ONLY the F16. Edit: I also want to mention that I am pretty sure the only mode they seem to have implemented for the JDAM currently is Relative Targeting. What sucks is there is no real way to know as they didn't model the RT under the range carot on the HUD. Almost forgot to mention that. nullnull

True. They should put it under the rearm option so we can add restrictions to it. Maybe that would be a better option?

Also, dont forget that when using the TGP you need to TMS UP long. That will send the SPI data to the JDAM.

Unfortunately that is just the way it works. Do it right the first time and it wont be messed up. Avoid maneuvering while the 65 video is up as well as that will cause some issues too. Also, if you are doing a Hot start or Air start there is no reason to do a boresight unless you really have to. You can also just go back to the TGP as SOI and TMS UP again on the target to update the SPI info to the missile.

I just posted these. Check these out. I bet you are having just a problem with how they work. Obviously watch part 1 first.

nullYa'll should really check the ME better. The option for no helmet sight or NVGs is already there. Now for the L16 option, who knows if they will add it. Maybe when the implement the Transmit Power setting then you can just set that to none in the ME and it will actually work. You can set those right now but the options do not do anything from my experience.

I haven't flown the F18 in a very long time like that so I can't tell you why it works differently other than it is a different jet from I think a slightly different time. Other than that, go to this post where it has been and is being discussed still. Lord Vader explains it pretty decently. https://forum.dcs.world/topic/359039-help-getting-highest-ins-accuracy-for-pre-planned-popups/ And I can understand not being able to use the TGP due to clouds. If you need to use your FCR just make sure you find a really noticeable landmark that can be seen with the Ground Radar. Also, try to do a FIX with the GPS switch off. If you do it with it on the filter inside the jet will still try to correct it. From my experience doing a FX with GPS switch on is really only good for doing it with one stpt and it will move the rest to correct it, but you need to be almost spot on. Also, what he said about the JDAMs. The GPS isn't fully finished yet with them.

Also, you should try to verify your target with either the FCR in GM mode or through your TGP. If using the TGP make sure you TMS UP long to essentially transfer that data to the bomb.

Yes, that is correct and normal. Definitely suggest setting up a FIX point in order to a FIX before ingress. You can do a FIX by pressing ICP 8 "FIX" and you can use your HUD, FCR(GM Mode), TGP, or OFLY. Yes you can do an inflight alignment by going to your NAV switch and right clicking to INFLT ALGN, note to do this you need to make sure you are flying in a straight line in a known direction. But I also wouldnt do this unless you really really have to. Start with a FIX first. Highly suggest you read the manual or watch some videos. Video for doing a FIX Video for inflight aligning

DCS Username: Specter_DC13 Used in-game technicolor 1 No external post processing software was used.

Like I said, it is not a warning. It is a caution. A Caution and a Warning are two different things. Caution as defined by the USAF is any procedure or technique which could result in damage to equipment and a Warning is any procedure or technique which could result in personal injury or loss of life. Did you even read the forum post I sent you the link for? If you have two tanks, 120s, 9s, bombs on 3 and 7, and a TGP that is a CAT III load. If you drop your bombs you are still CAT III because of the TGP. If you have 4x120, 2x9s, and a CL tank, then that is CAT I but the stores config light will be on. If you have that same loadout but with a TGP that is CAT III. If you have that same loadout but with no TGP but you have 2x Tanks then that is CAT III. It is a weird system I agree, but that is just the way it works. You gotta remember these pilots brief a lot before they go out so they know when they need to flip that switch depending on what they are doing. There wont be another config, but as a pilot you are constantly checking everything inside the cockpit. You are always checking instruments and always checking that caution light panel. And sometimes the pilot wont press the Master Caution Reset just to keep that reminder. Again, you just ignore that caution if you know what your loadout is. And just about every A2G mission has a TGP on the jet so they will always remain in CAT III. So it is a non issue. Dont understand the frustration or disparity with this. I explained that Cautions and Warnings are different. It is just an advisory for the pilot. And if you are doing your periodic cockpit checks then you wont forget it if you just so happen to go to a CAT I condition in flight. This I do not understand. I was just ensuring that you or anyone else that sees this forum understands what the CAT is for. It is not just you that is on this forum you know.

Please refer to this forum above. This is correctly implemented. Not a bug at all I can promise you that. Just to sum it up, it is on you as the pilot to be in the correct CAT regardless of the caution. The caution lights are more of an "advisory" hence them being called "Caution Lights", whereas the lights on the right glare shield for example (Canopy, HYD, OXY etc.) are your warnings and that is why they are red. Also, per the -1-2 any stores with a TGP or TGP and HTS is always CAT III. ECM pods are CAT I unless loaded to a wing station. And any asymmetric loadout (to include when firing off AAMs) is a CAT III condition. Just two wing tanks is CAT I. It is a weird logic system, but it is correct how they implemented it. Like I said per the -1-2 it is up to the pilot to know the correct CAT to be in. The -1-2 shows loadouts and if the CAT box is shaded in then that means the loading CAT in the SMS does not agree with the actual loading CAT in those cases you ignore it and stay in the correct CAT per the manual. The CAT switch does not limit your G at all. With enough speed and the right conditions, you can rip the wings off the jet.

IRL SEC and EPU checks are done prior to anything else per the checklist which you can find publicly.

You can look at the laser codes in SP missions/campaigns via the mission planner.

My bad I wrote those down for my reference and then must've copied pasted the whole thing I wrote. Would you like the pm? @BIGNEWY