Shiroka

I guess it’s optional to accept the update after you’ve performed it? On the PCN?

+1 on this, thought I’d try out the Sky Warrior campaign - no wingmen take off from Tarawa.

+1 on this

I think they are 2 different things. The police light on/off commands adjust switch 23, there is also meant to be a switch on the throttle, but I’m not sure how it operates.

The HOTAS Police Light Toggle binding has a weird function that adjusts the landing/taxi light and not the police light. Pages are ref the Manual RC6 When Police Light Toggle HOTAS binding (ser 6 on pg 40) is pressed, the police light does not toggle. Instead it's function depends on the position of the police light enable/disable switch (switch 23 on pg 30): If switch 23 is disabled (rear), the HOTAS binding toggles switch 22 (the taxi/landing light) to atterissage (forward). If switch 23 is enabled (forwards), the HOTAS binding toggles switch 22 to arret (rear). I'm not sure if the HOTAS binding is supposed to move switch 23 (maybe a question for the SME), but either way it's not doing anything to do with 23 (the police light), rather affecting the landing/taxi light (22). M2000C Police Light.trk

From reading discord I think it was binding confusion about “TDC action” vs “action/no action toggle”

This literally just happened to me. @AlphaJulietis this on RAZBAM side (and if so should we make a report in the AV8B forum) or ED?

https://www.digitalcombatsimulator.com/en/files/3306023/

I think that’s correct as is. The bingo calculations assume that the aircraft is clean (NFM 2.20.1.4 is the ref) whereas the cruise page accounts for stores.

I posted that mod a while ago back when the MFDs were unreadable in VR - RAZBAM resolved the issue a few months ago so it should no longer be necessary (I left it up in case anyone was using an old version but haven’t updated it).

I use VR Kneeboard as a separate app. Works really well and can have tabs set up.

I don't see why necessary if the Pilot and CPG have different bindings. You don't need to bind "Set Pilot Seat" if you are already in the pilot seat (and vice versa with the CPG seat) - can just bind "set CPG seat" in the pilot bindings and "set pilot seat" in the CPG bindings to the same button so in effect that button works as a cycle button.

I know it's not a functional switch but, on the same subject, the RPS/YAW switch currently starts in the TEST position, rather than the ON position. Also, according to NATOPS the NWS/ANTI-SKID switch should perhaps be ON rather than NWS but I'm not sure if this changes shore vs LHA.

Thanks - I had this problem and it fixed it for me also. Just as an FYI for some reason it didn't work when I used the .msi installer file (I still had the same problem and it kept telling me that an update was available), only worked when I used the manual .dll installation.

So if the modifier is button x set in DCS, when it is switched on you are no longer pressing F2, rather x+F2, which DCS reads as a different command. I guess one way around this would be to bind “x+key” to all the keyboard commands you use in addition to just “key”, so external view is bound to both F2 and x+F2. Sure there are better workarounds.

Yeah I looked for it in the NFM too but couldn’t find it. Looks like it’s in the TACMAN instead (at least the 2008 version)

Not quite - it’s to change the coordinate geodesic Datum (WGS84, NAD27 etc). That will affect the local Mag Var but also everything else - coordinates, true north etc. Not sure different Datums are modeled in DCS (I guess not) but when you push this it should display the default datum, which is 47 (WGS84) and allow you to enter a new 2 digit number from 01 to 47. There is a table mapping numbers to Datums in the TACMAN (Vol 1, fig 1-169, pgs 1-256 and 1-257).

Thanks, it’s been much better recently. I really like that you can adjust the symbology width with SYM on the left MPCD, think this would help with a range of hardware if it was also working on the right MPCD too (I posted another bug report about that already but putting it here too as I think it would really help any residual issues with readability across a range of hardware/VR etc.)

Confirm fixed, thanks

Not quite - my original issue was that I couldn’t turn back from night to day, disregard this. The other issue I was alluding to is that on some of the controls (eg the Armament control Panel) the LMB and RMB move switches in a different direction to every other DCS module (at least all the ED ones are standardized such that RMB moves a switch down and LMB moves it up). I’d messed with the lua file to correct it and made a copy paste error relating to this button which didn’t have any LMB/RMB issues (which I’ve now fixed).

This is [No bug] - I was using a lua edit to bring the clicks in line with ED modules (RMB down, LMB up - I personally think you guys should implement this anyway) and there was an error in the mod code (which means it probably existed at one point but has already been fixed).

It’s the “reprojection” option. Can’t remember exactly but look on here for the reprojection settings (in fact if you haven’t seen this awesome guide then follow it from the top): https://vr4dcs.com/2020/12/24/how-to-nail-reverb-setup/

If it helps I only ever get SteamVR crashes when I have the frame rate locked (45/90Hz). I leave it unlocked now and no more crashes.

Seconded - happens in snowplow mode on the TPOD very often, it moves to a ground stabilized track without any input even if set up with a large deadzone.

Pressing the TOO button should command A/G master mode and call up the last weapon selected. Ref: TACMAN Vol.1 2.4.6.2 TOO Designation AV8B - TOO.trk