USAF-Falcon87

OK, I have boresighted the missiles as described above. The first missile will continue to "C", but the following missiles (and yes, I boresighted both stations) stop at T and won't fire. What am I missing? Here are my steps: 1) Hot start on ramp. Choose PRE one Mavs power up. 2) Boresight missiles (AGM-65D) from both stations on nearby aircraft. 3) Takeoff and boresight missiles AGAIN on a ground target. 4) Make TGP SOI, wait until within maverick LAR. 5) TMS Fwd to point track. Maverick screen shows "HANDOFF IN PROGRESS", eventually ending with a "C" over the station number. 6) Fire missile, tank goes kaboom. 7) Choose new target. Again wait until within LAR, TMS Fwd.... and only a T above the station number. Any ideas?

Ok, thanks. I thought the post on Facebook mentioned the 21st, not the 22nd.

OK, I know I've been able to get through this in the past, but i'm drawing a blank. How do I access the modules for the free-to-play period? Only option I have on-screen is to buy the module. Took it until it was asking me for a credit card without seeing a trial button. Thanks for the help! Ric

In the real world, ATC will NEVER give you just "land on runway 21" if there is a left and a right. They will be very specific, and pilots are required to read back the correct full runway number as well. The game, however, isn't quite so directive, so it leaves it up to your discretion. In the absence of air traffic control in the real world (uncontrolled airports), any runway may be used. Since left traffic is standard (at least in the US), it would make sense to land on the left and takeoff on the right, but there is no guarantee that someone isn't doing otherwise by departing from the left (or even departing from the left runway in the OTHER direction in the case of relatively light winds!). All pilots are responsible for maintaining safe separation at all times. 21L for takeoff is the same as 21L for landing. The runway numbers never change. (However, 21L would be 3R is you were landing in the opposite direction.) The same philosophy should hold in-game as in the real world: 1) Trust no one. 2) Maintain a safe path for all operations. 3) NEVER trust another pilot not to screw up.

When I use my Quest 2 connected via USB 3, the battery lasts 4-5 hours. Disclaimer: that's in Elite:Dangerous, not DCS (still haven't gotten my settings to where it's comfortable to play that long in DCS), but that shouldn't affect battery life.

I think the encode bitrate is part of the version 23 software, which is a beta version. From https://uploadvr.com/oculus-link-set-bitrate-update/ "Oculus PC software v23 is currently available on the Public Test Channel. To opt in, navigate to the Beta tab of the Oculus PC app’s settings. You’ll see it start to download in the Library tab."

The most current version of the manual is always available in <GAMEDIR>\mods\aircraft\F-16C\doc\ Cheers!

I think of it like this: the DGFT/MSL OVRD switch sets RADAR modes rather than weapons. MSL OVRD gets you to TWS/RWS and DGFT gets you into bore/vertical scan/HUD modes. The Sidewinder is the default weapon for DGFT and the Slammer is the default for MSL OVRD. But you can change missile types with a long press of the NWS button, or change stations of a type with a short press.

Yeah, I had mine at the end of the file, but didn't know if that made a difference or not--I guess it does!

BWAHAHAAHAH!! Yep--a little! ;)

TGP Snowplow (SP) mode behavior is inconsistent. CCRP steering line does not always point to target designated with pod. Steps to recreate. 1) Press AG. 2) Press OSB2, then OSB 19 to select CCRP. 3) On OSB 12, select TGP. 4) DMS Aft to make TGP SOI. 5) TMS Fwd to put TGP in point track. 6) Slew the pod as desired. 7) Turn if desired, then press SP to enter snowplow mode. 8) Press TMS Fwd or TMS Right to go to point or area track. 9) Move TGP aim--CCRP Aim line and aim box (sometimes) remains on original steerpoint. Behavior is inconsistent. Sometimes selecting SP works correctly, and the aiming box appears on the HUD as it should. Other times it remains aiming at the selected steerpoint. Track file attached. Snowplow bug.trk

In the Viper?

I have the same problem if I try to use BORE from the TMS switch. Activating BORE from OSB2 of the radar MFD seems to work. (Cycles through 20[HUD Mode], 60 [Vert Scan]. and BORE).

Here's how mine works: Go to \program files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Cockpit\Scripts\Displays\DED\indicator\ In DED_init.lua, add the line: try_find_assigned_viewport("F16_DED") In your custom export config file in <GAMEDIR>/config/MonitorSetup, set up a viewport for the DED. Mine looks like this: F16_DED = { x=2585; y = 500; width=311; height=77; } Hope this helps!

That was always just a temp workaround. Now you SHOULD be able to use snowplow (SP on OSB 8), but it seems to be bugged at the moment.

What I meant by no response was that the cursor didn't move. As I was informed above, you have to choose Area Track with TMS Right or Point Track with TMS Fwd/Up before the cursor will move.

That was it--thanks!

Anybody else having this problem since the update? I have a mission with groups of tanks, all of which are on waypoints, the point of which was to test the CZ function. Here is what I do: 1) Select AG. 2) Select CCRP. 3) Select TGP on MFD2 4) Set SOI to MFD2 5) Attempt to move cursor--no response. 6) Select DGFT or MSL OVRD mode, then deselect, but DON'T make MFD2 SO (reads NOT SOI), and cursor will move. 7) Select SOI for MFD2, and cursor doesn't move. Any ideas/suggestions?

I think you are correct--I found the same solution. The mfd_left_init.lua, mfd_right_init.lua, and AMPCD_init.lua are in a very different format than before. Something in my export script was causing the problem. Did a repair, went back to the vanilla files, and it works fine (was only using the files to export a viewport name anyway). As a side (but related) note, the exported displays appear MUCH sharper now than before the patch. So whatever they changed seems to have helped. It was worth troubleshooting this just for that result!

ENEMY grass, you mean.

Went in and tried again. Of course, now that I WANT it to do it, it wouldn't! :) Next time it happens, I'll try to grab a shot. :)

That’s just it. The TPOD is aimed right off the nose I always wait until I can see the marker in the HUD to prevent that problem. It’s like the missile is locked somewhere else and doesn’t want to let go. Sometimes (rarely) keeping the IRMV screen up until it exceeds gimbal limit then trying again will make it work—but not often. Is there a way to undesignate the missile, rather than the TPOD? Maybe that is what I’m looking for.

Usually the IR Mavs work fine for me just like the procedure above—find target with TPOD, uncage IRMV, sensor select up, designate, fire. But many times when I go sensor switch up, the IRMV sensor seems to be locked somewhere other than where the TPOD is looking. I get a sort of box on the screen and a cross to one side that I assume is where the IRMV sensor is looking. No matter how many times I hit designate, the IRMV won’t look anywhere near the TPOD aim point. What am I doing wrong? Thanks for any help!

Thanks Scott!

With the latest beta, my exported displays are washed out/over bright/ whatever. First pic is the exported view in Beta, second is same view in Stable.