WHOGX5

I didn't mean to come across as hostile but this is a nonsensical wishlist item and no one in this thread agrees with it. The solution to your perceived issue is quite simple; play on servers that don't use the Gambler livery or make your own missions. There is no reason for you to be bumping this thread as ED will never divert resources to implement a feature that practically no one wants and the effects of which can be achieved with ease using the tools that already exist.

This will never be addressed because no one cares about it except you. If you're not happy having everyone fly with the same skins all the time, then join another server, join a community, whatever you need to do to end up in a place where people change skins. Maybe you can even start your own community where the gimmick is that everyone changes skins after each respawn? A livery randomizer will never be implemented so you can stop bumping this thread.

The AN/AAQ-14 LANTIRN Targeting Pod was the most widely used targeting pod in the USAF F-16CM-50 fleet in 2007. The reason for this is that the USAF block 50 fleet transitioned directly from the LANTIRN system to the SNIPER. However, they kept flying their LANTIRNs alongside the SNIPERs as the SNIPERs extremely narrow FOV made it great for stuff like air-to-air missions but a lot less useful for missions like CAS where pilots fly very close to the target area and need the wide FOV of the LANTIRN when searching for targets and doing talk-ons. I think the confusion arises because the USAF F-16CM-50 did not use the AN/AAQ-13 LANTIRN Navigation Pod and therefore people assume they're looking at a LITENING simply because they look so similar and they don't see a navigation pod. You can however tell the difference between a LANTIRN and a LITENING targeting pod visually: LITENING: http://www.kenmiddleton.net/real_aviation/litening/F-16_Litening_158FW_03.html Shorter than the LANTIRN and has a straight inlet duct. LANTIRN: https://pbs.twimg.com/media/CoehxV-VYAArgYg.jpg A lot longer than the LITENING and it has a canted inlet duct. Practically every photograph you can find of an USAF F-16CM-50 from 2007 will be of it carrying either the LANTIRN AN/AAQ-14 or the SNIPER pod. I actually can't recall ever seeing a USAF F-16CM-50 carrying a LITENING around 2007. I linked an airliners.net search below where you can find a lot of amateur photographs from 2007. Pretty much all of the aircraft in the search are F-16CM-50s with a few block 52's and the likes strewn in here and there. If you want to verify you can always run the aircraft serial number and double check that it's the correct block of aircraft. https://www.airliners.net/search?aircraftBasicType=8185&aircraftGenericType=8185&aircraft=32099&sortBy=dateAccepted&sortOrder=desc&perPage=84&display=detail&page=15 As an example, here is a USAF F-16CM-50 in 2007 from Spangdahlem which is clearly seen carrying the LANTIRN AN/AAQ-14:

Oh, you mean in DCS? Sorry, I was talking real life functionality. Yeah, it's obviously not properly implemented in DCS.

The clock in the F-16CM-50 will always resume where it left off when it was shut down. At a later point during the startup when a GPS signal has been acquired the time will be automatically set to GPS SYSTEM in the time page. If you don't want GPS SYSTEM time this has to be overridden manually on the time page.

This is not the best we can get. There are a tonne of things that could be implemented. Obviously ED can't make a 1-to-1 true-to-life radar simulation in DCS, both due to performance issues and labour costs. You can however emulate behavior with a pretty satisfactory degree of accuracy. As an example, regarding RCS, you could run the DCS F-16 3D model through a radar simulation and save RCS values from all directions in all 3 axes with different loadout combinations and store that as an array of simple numerical values somewhere in the game files. Obviously you might have to do some simple scaling of these calculated values to account for different airframes being made out of different materials, having radar absorbing paint, etc. Once you're in-game and your radar sweeps over a target, you check the angle and aspect that target has relative to the player aircraft as well as which stores it has and use the pre-calculated RCS value for that angle and loadout. Is it a perfect, 100% accurate emulation of reality? Not even close. Is it better than what we have now? Without a doubt. And whether you want to call DCS a simulator or just a game the explicit goal of ED is to make a realistic simulation. Therefore that should be the bar we're aiming for when discussing these things.

You're saying a lot of words, but none of them makes any sense whatsoever. What do you mean by "it works close to perfection, based on its real counterpart" and "my conclusion is that it works exceptionally well"? Based on what? I couldn't even begin to guess what you use as your frame of reference. The radar modelling in DCS is extremely simplified. Ask anyone who's studied or worked on even remotely modern radar systems and they'll tell you exactly that. As an example, a lot of the parameters that govern radar performance in DCS are often set values or percentages rather than actual calculations and statistical probabilities. If the DCS AN/APG-68V(5) behaved realistically, you wouldn't have a specific maximum detection range for a target with a specific RCS and if the target is beyond that range it's invisible. It's all about probability of detection and this probability does not have a purely linear or exponential relationship to the distance of a target. A lot of factors that are dependent on the design of a radar can make it so that, as an example, the radar has a higher probability of detecting a target at 30 miles than at 25 miles even if all the parameters of that target, like speed, altitude, aspect, RCS, etc., are identical. So even if the "maximum detection range" of the AN/APG-68V(5) in DCS for a specific RCS is 40 miles, that shouldn't make it impossible to spot that target momentarily at longer ranges. Now, most of the information about how military radars like the AN/APG-68V(5) work and does signals processing is obviously classified. There are however a lot of general signal processing techniques and military fighter radar behaviours that aren't classified, especially for older radars like the AN/APG-66, that could be roughly emulated in DCS to get us a little bit closer to realistic radar performance and behaviour. The choice to do that however is up to ED.

This is incorrect. The choice between JHMCS or NVGs is set in the mission editor by the creator of the mission for each individual F-16. By default all F-16s will spawn with JHMCS during all times of the day except if the mission creator chooses otherwise.

I only have one wish when it comes to the pilot body: Please, for the love of god, give us akimbo, clickable, physical kneeboards attached to the pilots legs. Preferably kneeboards with tabs that can be setup beforehand. This has been around for ages in certain other simulators and would be fantastic to have in DCS as well.

I would but I'm really strapped on time at the moment so I'm not able to do troubleshooting in the near future. The only flying I do is my communities weekly multiplayer missions which have huge trackfiles which is what I base my opinions on. If someone else could provide it that'd be much appreciated and, if not, I'll try to put some together in the future when my schedule clears up.

Below is an example from a third-party software. As you can see, unlike steerpoints, the VRP, PUP, OA1 and OA2 will be visible throughout the entire maneuver in addition to the actual target and guide you through the very specific attack profile which has been pre-calculated with specific speeds, altitudes, exposure times, tracking times, G-forces, release height, headings, etc. that are adapted to suit your loadout and the type of threat you're attacking. There are other applications for this but this is one example.

The F-16's radar doesn't work too well at all in DCS at the moment and will easily break lock. Datalink is bugged too and will sometimes give accurate locations, sometimes inaccurate and sometimes none at all.

Oh, I've completely missed that! Let's hope we get the fire control radars as well. Thanks for the links!

Honestly, the thing I'm lacking the most in DCS is radar guided, medium to high altitude AAA. We already got the S-60 which is great, but it's still unguided so you have to be at extremely low altitudes for it to start shooting or even have a chance of hitting you. Also, we really need the KS-19. Both of these guns have been involved in pretty much every major conflict since WWII and flying combat missions without a medium to high altitude AAA threat just feels out of place. As far as maps go though, if I had to choose one, I'd choose a Korean theatre. Preferably it'd cover North and South Korea including low detail areas on the Liaodong and Shaodong peninsulas, around Vladivostok and Some slivers of the northern coast of Japan. Maybe even Okinawa including Kadena AFB. It'd allow for the creation of so many different scenarios between various factions and alliances. The only DCS map that comes close at the moment is Syria with the amount of ways you can twist and turn that map for new scenarios, but I believe a Korean theatre would be a notch above even that. Korea just has such an amazing geography and with both the Yellow Sea and the Sea of Japan and presence of Chinese, Russian, Japanese, Korean and American military bases.... I can think of so many scenarios that I can barely contain myself.

Yeah, I think that's what he meant. Last I checked, RCS in DCS is a static numerical value per aircraft. In real life, as an example, pretty much every modern fighter jet has a much bigger radar cross section when viewed from the sides compared to from the front or rear. Here you can see an example of an extremely simplified RCS calculation from the 3D model of a Su-57: https://www.researchgate.net/figure/The-XY-view-of-the-model-and-RCS-dBsm-at-25-GHz-in-the-azimuth-plane-with-Az-11360_fig4_345140504 Also, here's a post containing a picture where you can see the RCS and IR values for pretty much all DCS units in patch 2.5.6:

It was Spudknockers cold start tutorial and as others have already mentioned, it is completely incorrect. BATT is only used for pre-engine tests. Engine is always started with MAIN PWR. As general advice, youtube videos are more fun to watch and perhaps easier to follow, but manuals are more accurate and more in depth. So don't rely solely on youtube.

No, it's your own callsign code. It does not "connect" you to your friend or put you on the same net, that's set through the STN's and fighter channel which are other functions which aren't implemented yet. Your callsign code is simply the first and last letter of your callsign and your flight number. So if you're callsign is Dodge 2-1 your code will be DE21. This is set automatically in the mission but for people who use custom callsigns that aren't in DCS they have to set it themselves. So if you lock a hostile, other players will see DE21 displayed over the target on their HSD. Also when you're just flying around, other pilots will see DE21 over your datalink symbol.

Off of the top of my head, I think it's LIST -> ENTER to get to the D/L page. Once there you use sequence on the dobber switch and there should be a two letter, two number combination on one of the pages (like ED 11 for Enfield 1-1). Then you select that field and use the Increment/Decrement switch and ENTER to select the correct letters and then input the numbers via the numpad on the ICP.

Never had an issue with the HTS not picking up any targets and I always do cold starts so I can't help you with that. Regarding cycling targets however, I found it only works if you lock a target and go TMS Left to bring up the SEAD page on the DED. After that you can cycle with TMS Right.

"What's going to be cool is TGP in AA mode. You HSD SOI a L16 track as PDLT. Slave TGP PDLT and track. Follow the octogon radar silent until in firing position. DGFT, ACM NO RAD, TMS right to slave ACM to TGP track. Lock and fire within two seconds of radar emission from NEZ and immediately back into silent. It's like submarine warfare."

I also really want dynamic weather with moving weather systems and the likes but honestly, the thing we need the most right now is to regain the ability to manually set the cloud layers. We're so limited at the moment by the small amount of weather presets we're actually allowed to pick from.

You can also press OVRD on the FCR page to temporarily disable the radar without affecting other systems.

In it's current implementation in DCS there is no difference in accuracy between stored heading align and NORM afaik. IRL you can get a higher accuracy with NORM which obviously will be important for the employment of GPS weapons like JDAMs. So no, it's not a requirement. You will just get a higher accuracy with a finer alignment.

I don't even think he's referring to Husky to be honest. By emphasizing the usage of the term "Pitbull" itself I'm assuming he's referring to the fact that the DCS AIM-120 doesn't even try to reacquire or acquire a new target once it loses a lock. IRL, once an AIM-120 goes pitbull, it will not only look for the target it was fired at but it will track anything it can find. If it finds something and then loses lock it will try to reacquire the target or acquire a new target. In DCS if an AIM-120 loses a lock, it will either go dumb and fly in a straight line without reacquiring, or it will actively start turning away from the target in circles around itself without acquiring anything either. The target can also do an 180 degree continuous turn and notch the missile for 0.5 seconds and the AIM-120 will loose track and not even make an attempt to find the target again. So in its current state in DCS the AIM-120's MPRF mode has more of a "Golden Retriever Guide Dog" kinda vibe to it.

The ICP is the big block under the HUD with the numpad and other stuff on it, the DED is the green little screen just right of the HUD (which is controlled via the ICP), the HSI is the compass between your legs and the INS page is a subpage in the DED that you can access by press LIST followed by 6 on the ICP. And if you need to go a specific heading you can always set the course knob on the HSI to that course and just make sure that the blue course arrow on the HSI is pointing in the same direction that you're flying. Or alternatively, set a heading using the HDG knob on the HSI and turn on the autopilot with altitude and heading hold.