Cepheus76

Another option for CAS in DCS Liberation missions is to load laser guided munitions and then use LSS mode of the ATFLIR to find targets designated by the drone, which is usually around.

I'am all for the modelling of limitations, for all modules. However, this is only one part of the equation, the manuals should then have a "Limitations" section, so that we can plan our flights accordingly. And while we're at it, a "Performance" section would be more than welcome, too. I just hate to take-off and having no clue what the expected fuel consumption is. Please note that I am not asking for a copy-paste from the actual flight manuals. Chiefly, because they are probably classified anyway. But even if they weren't, they wouldn't be 100% applicable, since we're operating with a flight model here, so I guess (basing that guess on the discussions here regarding pylon drag, for example) that there will be some inconsistencies. Oh, and to finish my documentation wishlist here, I would also appreciate a list of approved load-outs for a the aircraft a module is representing.

@Tippis Thanks a lot for taking the time to explain where some possible pitfalls may be. I guess I would be already happy if the track is only detailed when the tanker is orbiting. For tankers not spawned yet, or sitting on the ground waiting for their take-off time, perhaps the kneeboard page would then have to reflect the tanker's entire flightplan- I am working on the assumption that waypoints and timings are available in the background.

I support the OP's request. Proper documentation should be, in my opinion part, part of a high fidelity module, to allow those who wish to, to plan their missions properly. So even some simple climb, cruise, and descent charts would be highly welcomed, at least by me I see the point that it will cause sooner or later bickering in the forums, but I think that this can be handled like all other performance related discussion. After all, the charts would be eventually just visualizations of what people are experiencing in the sim anyway.

As far as I know, in real life information about tanker tracks are part of the briefing package pilots receive. Therefore, I wondered if it is possible to create automatically a kneeboard page, detailing the station area, inbound track, leg length flight level, speed etc, when a tanker is present in the mission? I don't know anything about programming, but I think the suggestion might be worthwhile, if it is possible to extract the tanker information, which are present in the mission editor, into a kneeboard page. Such a page would greatly help with setting up the rendezvous with the tanker and we could do away with the radio calls, which some people (rightfully) decried as unrealistic. Last but not least, it would add to the immersion, at least for me, to leaf through the kneeboard to get the tanker information.

@Fri113 good points. But perhaps I can refine my hypothesis further: By requiring separate entries for latitude and longitude, a data entry error for e.g. latitude can be corrected directly, without introducing the risk of corrupting the valid longitude value which exists when the whole set of coordinates must be entered anew. In any case, I could also entertain the idea tthat the whole thing has little to do with risk management in the first place and is just a bit of a design-quirk which can occur in any complicated project

Your laser is not firing yet. You need to assign TDC priority to the FLIR page and press the pickle button. Once the laser is firing and the seeker picked it up, the cross on the seeker page will turn into a solid square and the Maverick is good to launch.

Just speculating, but having to undertake extra steps to enter coordinates for a weapon may serve as a risk control measure. When entering flightplan coordinates wrong, you can catch gross errors when your HSI planview doesn't match what the line on your map. If your avionics give you the flight plan total distance, you can compare that to the total distance shown on your flight log. With a weapon's coordinate you have not as many possibilities to catch an error. Sure, you can, and probably should, confirm the coordinates after entry, but when tired or exhausted, or being under combat stress, a pilot may not detect an error. By requiring two distinct steps for entering latitude and longitude for a weapon waypoint can reduce the risk of data entry error, with all its undesirable outcomes.

Did you try to adjust the brightness? There are two little levers (looking like horizontal black rectangles) just next to the indicators, which can be moved up/ down to adjust the lights' intensities.

What durka-durka says, however, for the up/down arrows, I use the num-pad plus- and minus keys. Also, for the Master Mode selection, I mapped the keys "1" to "6" on the keyboard to the ICP buttons, so pressing "1" gives ne access to the UHF, "2" to the VHF, you get the drift.

I am not sure, but I think the Hornet uses compressed air supplied by the APU to turn the compressor for engine start, so there shouldn't be a starter cycle limit. Same goes for the ignition circuitry, provided its rated for continous operation.

I observed the same, in a DCS Liberation 2.5 mission. An AI Tomcat was circling the carrier at 350 knots and 150' altitude, probably with the intention to land but obviously unable to do so.

No worries, this text just discusses some of the Secret Weapons of the Luftwaffe

Thank you all for the quick replies!

Hello all, As per the title, I am looking for information about the maximum landing mass for the F-16. Any input is greatly appreciated! Thanks in advance, Cepheus76

Make sure that you set both the burst quantity and the number of salvos to one. For the intricacies of the programming steps, I suggest that you consult the excellent Chuck's Guide for the Viper.

I share your feelings regarding the defensive suite of our Viper, but I am certain that ED will revisit it, sooner or later. In the meantime, to only dispense either chaff or flares, I set program 1 to dispense flares and set program 5 to chaff, since in a BVR engagement there's always the time to take the hand off the throttle and to use the slap-switch (or in our case, to press the appropriate key on the keyboard).

I second the OP's request. An automatically created W+B sheet, along with the appropiate performance figures, would greatly improve immersion. Cepheus

And a Post Scriptum to my previous post: Even use of the "R-Shift R" key combination works now again; previously, its use lead inevitably to a crash. Cepheus

@Fra298 It seems as if you found a valid solution. As per your suggestion, I changed my video settings to match the driver settings and chose one of the predifined settings one and could play normally, it did not even require a fresh install. Thanks a million! Cepheus

@BIGNEWY Thank you for looking at the issue. Please find attached two screenshots, one with the blurry coordinates, the other with adjusted contrast. @Harker Thank you for providing the background information. much appreciated.

Hello all, As it says in the title, the data block showing the coordinates of the location the ATFLIR pod is looking at suddenly became quite blurry. This can be addressed somewhat by adjusting the contrast settings of the MFD, but I find this somewhat curious, especially since the other captions/ legends on the display are rendered without any blur. A short track is attached. Thanks and have a great weekend, Cepheus Blurry Coordinates Data Block in ATFLIR.trk

I experienced it too once after the update to 2.7. However, I was unsuccessful when trying to reproduce it.

If a Hornet can pick up a fighter sized target only at ranges around 50 nm, so be it. But I wonder if we get sooner or later VSR? As far as I understand, this mode allows to determine the azimuth of contacts farther away, so it would be a welcome addition to overcome the shortened detection ranges.

I just wanted to say "thank you" for introducing the speed awareness calls. I really find them useful to maintain situational awareness in a fight. Just one question, and I hope that I don't come across as greedy, are there also plans for Jester calling out g's? Thanks again for the useful addition, Cepheus