All Activity

La7 can be flown against all the axis planes, you can add Russian lend lease A20s, Spitfires, and P47s, use the Kola and Germany maps (I know modern but you can remove objects in mission editor). I am a bit disappointed that third party planes does not have ED damage model, they have a simplified damage model, hope this changes. Some assets for PTO can also be used in ETO and be correct historically.

That's always the problems. The people who don't read the update logs will send a bug report and ED probably doesn't want to bother themselves with that. That's why it would be better to put it as an option, disabled by default that ONLY people aware of it would enable this functionnality. Oh I didn't understand it well. I guess that users should be more aware of what's happening in their sim. Dropping at least 70$ in a virtual plane isn't common so the least thing they could do is to rtfm as @upyr1 said

参考建议：别学随便装企业版系统，正确步骤：卡死关机重启之后上传"C:\Users\---\Saved Games\DCS.openbeta\Logs\dcs.log"的dcs.log文件到论坛或者哪，能看的懂的会有人帮你看什么问题的，一般这种问题是虚拟内存没给够导致的，帮人诊断很多起了，楼主又不仔细看回复瞎折腾。

For me that's a giant wall of bookcases with about 300-400 kits still in boxes awaiting completion. There's plenty finished but still, I know I'll never build them all.

Hey, Nothing seems to be off in Control Settings. Here are the tracks: So can't actuate the switch before pressing it with the mouse cursor. FA-18_Starting_from_Ramp_Hot.trk FA-18_Starting_from_Runway.trk

Hello. What part of the map of Afghanistan is needed for this company? Thank you.

So... Went ahead and did a sanity check before making changes and found that I was able to reproduce the issue in 2D and SP, which seems to indicate that it is something in my client PC. Then I deleted the fxo and metashaders2 folders to no effect. Decided to double check everything before reverting versions (since it was working fine after the last update). First, I turned the PC off and booted again to go into the BIOS (PC is turned off every night). Nothing changed there as expected, but "saved" and exited the BIOS anyway. Tested DCS again and problem went away... So, I'm scratching my head a little bit...

Mission 2 update after latest map update that set trees at starting spot. Cheers

You may need to adjust your stick itself (if you can). The "pulse" coming out of the hardware may be longer than you think. The F-16 trim works really well for me with a VKB Gladiator. -Ryan

Some very valid points in this thread - and i do hope ED are reading them and noting the communities comments. Taking the comments that it might be coming across that interest from ED has waned due to whatever reason - probably sales.. Those who did invest in the Early release should reap some benefits and worthwhile updates... Where there are lots of features on the roadmap.. Perhaps just a bit more focus on what is REALLY needed now to make it a real contender. Not the bells and whistles just the things to make it usable and enjoyable. I'll kick off with an easy one.. Jump in and expand the list if you so wish. No idea if this will have any impact on ED's future approach to updates!! CDU - If nothing else, get it back to the state where black screens did not appear - Make it usable again

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.