Shiroka

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 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).

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

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

Hey @AlphaJuliet, not solved yet. See attached track: AV8B - Backup Radio.trk

Ref: NATOPS 2.18.17.6 Gain and Cont (and Sym) should be retained separately in each of 6 different modes: Day mode, all strokes (e.g., MENU/CAS) Day mode, monocrome video (e.g., FLIR, TPOD) Day mode, map (e.g, EHSD or EW with Map (not currently available)) Night mode, all strokes (e.g., MENU/CAS) Night mode, monocrome video (e.g., FLIR, TPOD) Night mode, map (e.g, EHSD or EW with Map (not currently available)) Currently there appears to be one setting for gain/cont that is carried over to all pages and between day and night modes. See attached track (also shows the bug I just reported about unable to switch from night to day on right MPCD). AV8B - MPCD gain-cont-night.trk

Now that we have the OLS and the HPI on the Tarawa it would be great to have the Horizontal Approach Path Indicator (HAPI) lights too, especially as we have no ILS/AWLS. 2 pitch and roll stabilized lights on the port catwalk. Red over white for proper approach glide slope (red over red too low, white over white too high). for more detail, function is described in NAVAIR 00-80T-111 6.5.2.2 and Fig 6-10.

For reference, you can see how it should look in fig. 2-31 in the Tacman vol. 1 (page 2-35 in the copy floating around online).

Just tried again. Definitely can't drop more than one bomb at once (each press of the pickle button in this track should drop 1 bomb from each station). Track attached. Just to reconfirm - I'm referring to DSL(1) mode, not DSL mode i.e., manually selecting fuze with the knob on the ACP. AV8B - DSL1.trk

Not sure this is correct. The TACMAN states: "in the A/G master mode... and a weapon delivery program for each of up to four weapon types ... plus the fuselage gun" (vol. 1, 1.14.3.1). I'm pretty sure I've used more than 2 types of weapon before (e.g., LJDAM, LMAV, and APKWS).

Figma (just the free version online)

Realistic checklists for the RAZBAM Mirage M-2000C covering normal procedures and basic tactical checks. I fly in VR using VR Kneeboard so I wanted to create a set of kneeboards with as few pages as possible to cover normal procedures: start-up, takeoff, descent, landing, and shutdown, along with basic tactical checks. These procedures follow the Manuel Pilote as far as possible along with the RAZBAM checklists. The aim was to create a quick reference matching the real procedures as closely as possible. I tried to remove most things that weren't relevant to the DCS environment. WIP: I'm working on a full English version, but to be honest there isn't much difference. I want to give full credit here to @Minsky here because his awesome Hornet kneeboard suite is what inspired me to do this for the Harrier. His kneeboards are awesome, the Hornet one is here: https://www.digitalcombatsimulator.com/en/files/3314313/ I know RAZBAM is currently updating the Mirage so I'll try to keep this post updated, and happy to hear any comments/feedback. LINK to user files: https://www.digitalcombatsimulator.com/en/files/3318306/ Changelog: Version 1.00 - 08 September 2021 - Initial Release

Still bugged but being worked on apparently.

I’ll take a look at that. In the mean time on the last page there is a “scramble” checklist (also from NATOPS) which should give you just enough to get in the air.