Shiroka

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

Based on this post: Pressing NWS with TPOD DES/TPOD DES should step to HUD DES/SLV DES to NO DES/SLV VV to SNWPLW. Currently it gets stuck at HUD DES/SLV DES and won't undesignate the system target. Workaround is to manually unbox DESG on the EHSD, but either this functionality is wrong or the description/picture in the post above is wrong. AV8B - NWS.trk

Apologies for the long post. Hopefully succinct and with evidence and tracks. Case 1) Direct routing to a selected point: With a WO/S present, waypoint steering selected and nothing designated, TOT should be to the offset via the waypoint (you must manually select the WO/S steering once over the waypoint i.e., with the EHSD or WOF). Ref: TACMAN Vol.1 1.15.6.1.1 Direct Routing. At present, TOT only takes you to the waypoint. See attached track ("AV8B - TOT WOS.trk"). With WO/S present, waypoint steering selected and the waypoint designated, TOT is to the waypoint direct. Ref: TACMAN Vol.1 1.15.6.1.1 Direct Routing. This functions correctly, no track attached. With WO/S present, WO/S steering selected (designated or not), TOT is to the WO/S direct. Ref: TACMAN Vol.1 1.15.6.1.1 Direct Routing. This functions correctly, no track attached. Case 2) Sequential Routing Where WO/S exists for the TERM waypoint, the SEQ string is from waypoint 0 to the TERM WO/S. I.e., if waypoint 3 is TERM and WO/S3 exists then the string is: W0 -> W1 -> W2 -> W3 -> WO/S3 This is currently correct (you have to designate WO/S manually at the term waypoint but I assume this is correct behavior based on the NSEQ overlay below). However, TOT should be to the TERM WO/S rather than the (current) TERM waypoint. Ref: TACMAN Vol.1 1.15.6.1.2 Sequential Routing At present, TOT only goes to the TERM waypoint even if a TERM WO/S exists (no track for this, but I have a track for the NSEQ version below and it is essentially the same problem). Case 3) Non-Sequential Routing Where WO/S exists for the final IGRS waypoint, the NSEQ string is through all the intermediate waypoints to the final IGRS WO/S. I.e., if the IGRS string is "5, 4, 3", and the EGRS string is “2, 1" and WO/S3 exists then the string is: W5 -> W4-> W3 -> WO/S3 …. -> W2 -> W1 This is currently correct (as before you have to designate WO/S manually at the final IGRS waypoint). I even noticed from the NSEQ overlay that the string is correctly routed through the WO/S (i.e., the EGRS starts from the IGRS WO/S). However, TOT should be to the final IGRS WO/S (if it exists) rather than the (current) final IGRS waypoint. Ref: TACMAN Vol.1 1.15.6.1.3 Non-sequential Routing See track attached ("AV8B - NSEQ WOS TOT.trk"). Note: In my initial post on this on the post about the CS/T bug, I incorrectly stated that the SEQ and NSEQ strings should be through all intermediate WO/S as this is what is stated in the copy of the TACMAN I have access to (2002). However it would appear from more recent NATOPS (2008) that this was changed in H4.0 and beyond so current routing is correct, just not TOT: "With H4.0 only the offset to TERM in SEQ string or the final point of the IGRS string of a NSEQ route shall be included in a route” Ref: NATOPS (2008) 23.9.24 NSEQ Pushbutton AV8B - TOT WOS.trk AV8B - NSEQ WOS TOT.trk

Thanks, will do. Doing some more reading it looks like there was actually a change from H4.0 (and I guess onwards, maybe SME clarification needed) where the SEQ and NSEQ routes only include offsets for the final IGRS waypoint or the TERM waypoint instead of all the intermediate waypoints too. I’ll do some more research and testing and create a separate post with the ref and tracks.

@AlphaJuliet the first part of this (everything in the first post) is solved now (I tested it with a straight waypoint, with TERM, and with NSEQ) - working great, thanks! Second part related to WO/S (my most recent post) still remains. Would you like me to leave it here or create a separate bug report for that one (I have tracks from today’s OB) - then at least you can move this report to solved?