All Activity

GPS-Era / STRD HDG Alignment First, let’s start with the most common form of alignment in DCS, GPS-era using a STRD HDG alignment. This is the simplest, fastest, and most common for single- and multi-player. With power to the avionics systems, set the INS switch to STRD HDG and then set the GPS switch to ON. It’s important that the MIDS switch remains in the OFF position. After about 12 seconds, you’ll see an ALIGN indication on the HUD. You’ll then verify the STRD HDG alignment by going to the DED INS page and check the latitude, longitude, and altitude against your location on the F10 map view. After about 60 seconds, you should be aligned and confirm this by the ADI flags being retracted; HSI showing correct magnetic heading, DME, bearing pointer and CDI deflection; roll and pitch correct on the HUD; and RDY should be flashing on the INS alignment DED page after less than 2 minutes. We can now switch the INS switch from STRD HDG to NAV. On the DED INS alignment page, confirm that GPS TIME is displayed one minute after the GPS switch is set to ON. Note that this may take longer if the aircraft is under cover like a hardened aircraft bunker. As such, it is best to align out of cover. With good GPS TIME, set the MIDS switch from OFF to ON. After alignment with GPS correction, you can expect no more than 40 meters of INS drift. Further, if you zeroize the GPS or are flying a REDFOR Viper, you can expect an INS drift of 100 meters or more. GPS-Era / Normal Alignment A normal alignment is much like the STRD HDG Alignment, but we’ll need to manually enter the aircraft starting location because we’re not using a known, STRD HDG location. To start though, we’ll in the INS switch to NORM and not STRD HDG this time. Then set GPS to ON, verify MIDS to OFF, and wait for ALIGN on the HUD after about 12 seconds. The big difference is now going to the DED INS alignment page and entering the aircraft’s latitude, longitude, and altitude as shown on the F10 map. Once done, we’ll verify ADI, HSI, and HUD as before and wait for the flashing RDY indication on the DED INS alignment page after about 8 minutes. Once flashing, set the INS switch from NORM to NAV and verify GPS TIME indication. With that, set the MIDS switch from OFF to ON. These will be the most common alignment scenarios when performing a cold start. However, you may come across a mission or campaign with a date prior to the GPS era. In that case, we’ll only align based on INS with no GPS correction. Non-GPS Era / STRD HDG Alignment Like the GPS-era, set the INS switch from OFF to STRD HDG and wait for the ALIGN indication on the HUD. Then, verify the DED INS alignment page latitude, longitude, and altitude to the F10 map data and verify ADI, HSI HUD, and wait for the flashing RDY indication. We can now move the INS switch to NAV. Once airborne, you’ll then want to conduct alignment FIX procedures using Overfly, targeting pod, HUD, or FCR to remove accumulated INS drift. Please see the earlier videos on fix taking. Non-GPS Era / Normal HDG Alignment The last weight-on-wheels we’ll look at is doing a normal alignment at a mission date prior to GPS. Set the INS switch from OFF to NORM and wait for the ALIGN indication on the HUD. From the DED INS alignment page, enter the aircraft’s latitude, longitude, and elevation using the F-10 map. Next, verify the DED INS alignment page latitude, longitude, and altitude to the F10 map data and verify ADI, HSI HUD, and wait for the flashing RDY indication after about eight minutes. We can now set the INS switch to NAV. Once airborne, you’ll then want to conduct alignment FIX procedures using Overfly, targeting pod, HUD, or FCR to remove accumulated INS drift. Please see the earlier videos on fix taking. So far, we’ve only been talking about weight-on-wheels alignment procedures. We’ll now shift gears and discuss in-flight alignment. We’ll start with the more common GPS-era procedure. GPS-Era / In-Flight Alignment First, set the INS switch to FLT ALIGN and flight straight and level until the ADI flag is retracted. You’ll see INS FLT ALIGN on the DED and STBY on the HUD. Maintain straight and level flight and enter your compass magnetic heading within 20 seconds on the DED and verify that the pitch ladder is displayed on the HUD. Continue to fly straight and level until the ALIGN is replaced with the maximum G value on the HUD and then return the INS switch to the NAV position. Non-GPS-Era / In-Flight Alignment Last, for an in-flight alignment with no GPS, set the INS switch to FLT ALIGN and fly straight and level until the ADI OFF flag is removed. INS FLT ALIGN should appear on the DED and STBY on the HUD. Fly straight and level and enter your magnetic heading on the DED within 20 seconds while ALIGN appears on the HUD, replacing the maximum G indication. We’ll now perform an OFLY FIX within the next 30 seconds. It is required we perform a second OFLY FIX within two minutes to correctly perform velocity calculations. Keep flying straight and level, and once the maximum G field replaces the ALIGN indication, you are done. For best INS alignment, you may wish to perform an OFLY, HUD, FCR, or TGP alignment every 15 minutes for best possible navigation and acceptable weapon accuracy. Manual Alignment as Backup The manual alignment is a backup alignment designed to provide get-home capability only.

No. Pre-planned CCRP strikes are not possible in the F16C in DCS. You must correct steerpoint/markpoint drift with the TGP or HUD for accurate CCRP drops.

For 15 bucks I expect something more than the RWR, double gunners without losing hardpoints, UPK23 pods and the GPS would be needed.

Quite a feat you've done there but I feel too much has been left for the player. I prefer do be a pilot, not a Strike Group Commander, and just get a mission to fly. Would be great to have that option.

Because there's going to be times where you have to dive literally right now with no time in advance to prepare. That Zero on your six isn't going to kindly wait for you to shut all your flaps before shooting. And sometimes you have a target of opportunity that you'll lose if you don't take advantage of it.

ah gotcha. Some really good work there all the same, hopefully the train deactivation fix will happen in the future

The R-77 does not operate in STT mode when firing at 2 or more targets.Only TWS

Try setting your pagefile to auto. You have 64gb ram it is more than enough, and setting it to auto will be easier on your disk space. Multiplayer will always be more demanding on the machine, there is way more going on, and usually MP missions have 1000's of units.

mate your an angel not a devil. All working again, lost all my key binds etc but thats a little price to pay for getting back in the airt. Thanks a lot, owe you a pint

Yeah that is what I meant, sorry for the confusion, I am not very versed in all these names/systems... I hope the Mi-24 sees further development, it is clearly one of the best DCS modules, it is just so much fun! PLUS one to see the SPO-10 improved or the SPO-15LM added!

just started happening after i did a dcs update I uninstalled openxr toolkit and did a full dcs uninstall and reinstall....

DLSS 310.4.0 is out. https://www.techpowerup.com/download/nvidia-dlss-dll/

Using the keyboard, the gear goes up and down. But the same happens in other modules, not only in the F-16. If I keep it pressed (keyboard) it just performs one single action, either up or down depending on the state. To rule out an accidental double press I'm using TARGET's PULSE command to only send one single command when a button is pressed. It's not really necessary to do it that way but that's how I set it up. I just tested with the keyboard instead of the Warthog (no TARGET script running) and even with the keyboard the gear just goes up when I press the keyboard and comes down when I press it again.

Please review the following thread if it explains: In general, we want the CPU bound in the most of time so that DCS can deliver the better play result, especially lots of AI objects (tree included)

I only work on CH assets.

I didn't think I'd like it so much but it's a really fun module to use in MP, doing logistics runs and dropping off capture squads. Hope it gets some more attention and some advanced training missions.

A custom bridge and canvas effect for SignalRGB. I appreciate getting your feedback. Node.js Bridge: Collects exported cockpit data from DCS (gear, AoA, console lights, taxi, strobe, warning test, afterburner) and streams simplified JSON via WebSocket. HTML Canvas: Receives the data and turns it into real-time RGB lighting effects: • Gear → Red bar (up/down/transit) • AoA → Red / Yellow / Green indexer • Console → Green glow • Taxi → White top bar • Warning Test → Color grid • Strobe → Red blink • Afterburner → Orange flame

Thanks, will try later today

Target was waypoint, radar wasn't touched. I think it was the HSD that had everything wrong.

Thanks for the reply. I've adjusted the values downward (they were actually set at a default of 2% and 3,5%) and it does lessen the effect of bumping the pitch trim switch. Thanks for the back-story as well. Very interesting to read!

по программе управления АЛ-31Ф обороты Nвд не превышают 100%

Yeah, that autoexec.cfg was mentioned before already but thanks for pointing it out again, it's crucial for image quality tweaking. I also started on tweaking Quad Views settings. You'll need an empty settings.cfg file in C:\Users\YourUserName\AppData\Local\Quad-Views-Foveated and fill it with the following lines: smoothen_focus_view_edges=0.33 sharpen_focus_view=0.33 peripheral_multiplier=0.33 focus_multiplier=1.0 horizontal_focus_section=0.3 vertical_focus_section=0.33 Feel free to tweak your own values.

Thanks for the feedback. The damage model in DCS can be very binary when it comes down to it. Most sources consider the 9K720 to be equipped with additional armor on the roof and cabin, that's why I've set the 9K720 with its MZKT chassis to a higher armor level than the MAZ based Scud TEL. There doesn't seem to be any hard numbers on thickness available, so it's always hard to estimate the exact outcome of these variables, especially depending on the characteristics of the ammunition fired towards it. But I agree, the 20 mm ammunition you refer to should definitely be able to penetrate and defeat even the slightly up-armored MZKT chassis. I shall make a note and find a suitable middle ground. Edit: I ran some tests and I definitely agree. I've made some changes to the armor level, which now should be more realistic, while still taking into account its additional armor compared to stock chassis of this type.

DCS E-store это швейцарский магазин. Вне юрисдикции РФ. Ну и почитайте лицензионное соглашение прежде чем вспоминать про права.

Hi Bignewey, sure!, my intention was not to give to you data that you can use, just a simple information for the team to check about it.