Habu_69

Seems to lack audio input/output, but I guess wearing a headset would not be too objectionable.

I am BsB user 8 months and have really enjoyed form factor and display res, but I have RTX 4090. I think you would find another 32 GB RAM would be a big boost. Try limiting FPS to 75, but you are probably not exceeding that anyway. Turn off all anti-aliasing, upscaling and shadows. Set textures, water, clouds to medium. Cockpit displays to 512. Clutter, forest, Scenery to low/medium. Smoke and Aniso to 0. Start with these quality settings and experiment with gradual increases. Good luck.

I have, and really like, the BigScreen Beyond, which gets little love among DCS VR users. Like every other current headset BsB requires accepting some compromises, but it is worth considering. Advantages: small form factor, very lightweight, pancake lenses with high res video, native OpenXR, effortless setup, good audio solution with the upgraded headstrap, custom comfortable face gasket, outstanding user support, and excellent tracking with base stations. Detractors point to: high cost, restricted FOV, smallish sweet spot, lens glare (which I find disappears in DCS).

Correct, from DCS munitions and fuzing options. This does not include all combinations and permutations, oc, just ones I found most useful.

Yes, 60 ms (=.06 sec) is a good delay setting for penetrator bombs to attack hardened targets.

So confusing. I made a tabular fuzing guide for myself. You may find it useful. I am open to any corrections/additions. In my testing (against the hardened ammo storage whse with 2 bombs) I found the GBU-24B/B to be the most effective for bunker busting at 91% destruction with the GBU-31(V) 4/B close at 76%. I also found that the FMU-152 functions correctly with GBU's at any of the available delay settings with STORES EFUZ set to DLY1. F18 Fusing KB.pdf

Update post-2.9.7.58923: Issue 1 remains, even after DCS Repair. AFAC will not provide comm menu lasing options. Issue 2. GBU's now guide and strike moving targets when attack Hornet lases by FLIR.

Very promising work! Moose is such an amazing scripting tool with enormous capabilities. BZ to developers/maintainers.

DCS 2.9.6.58056, Win 11, SP, Hornet air start, JTAC Predator. This mission was developed to train LGB deliveries using a JTAC and no TGP. JTAC and Hornet were added to mission following DCS update and a repair. Launcher is disabled and EASY COMMS off. Fusing and laser code were set in the ME payload window. Because the mission has the aircraft starting in the air, the aircraft rearm window is unaccessable. 1. The JTAC comm menu never displays the LASER ON and SPOT options. 2. The GBU-12 bombs detonate, but do not guide, perhaps due to no. 1; however, my experience was that the bombs also did not guide before the update, when the JTAC COMMS were correct. JTAC GBU.trk

This guide might help. Not my work. My understanding is that due to current bug best practice is to set the fuses in the aircraft loadout window in the ME, then repeat the procedure using the rearm window from the cockpit in game.

Well, Sh!t. Lots of troubleshooting hours wasted. Tx for quick advice.

DCS 2.9.6, SP, Win 11, see track. Comm 1 initially on Ch 1, 127.5 mhz. Comm 2 on Ch 1, 264.00 mhz. Using comm menu ATC/Inbound call on Comm 1. ATC replies. BOTH radio channel indicators show incoming transmission delta symbol. Comm 1 scratchpad shows MANUAL channel input symbol (M), and reverts to CH 1 indication (1) after ATC transmission completes. Comm 2 does uncommanded MANUAL channel selection to 127.5, which persists after incoming transmission. Quite annoying. Hornet Radio Bug.trk

Ahhh. Tx for the information. Will fly the mission to test your procedural advice. Start with release above 15,000 and 2-3 miles from the IP.

OK, here is track. I have labels on for this training mission, so I can see I am near the target. I am making all the calls up to SPOT, as I have no indications that the bomb has a laser SPOT. If I use TGDSG on HSI the BFL just stays on the WP of course. Interesting that the LST switch has no function. Chuck's Guide discusses it in detail. So how does one direct the LGB laser seeker to start seeking? I am working on this to gain proficiency on servers with missions dated prior to introduction of TGPs. Habu LGB.trk

I can't figure out how to bomb an offboard lased target by buddy or AFAC when I am carrying no TGP. I have AFAC lasing moving BTR. LGB's are set for AUTO, EFUZE INSTANT, using FMU-139 and AFAC's code 1688, armed, AG mode. I set in the WP provided by AFAC and go IP Inbound. The bombs never seem to search for, nor spot, the laser. I tried turning on the Hornet LST, but it springs to off. What procedural steps am I missing?? Update. Got the LST to switch on through some control modifications, but bombs still do not find laser. What is the cue that the bombs do find the laser?

In Hornet can markpoiints be created based on the ground radar cursor?

I fly DCS VR with the BigSCreen Beyond HMD and, with no FR at all in busy MP missions, I get great visuals and steady 72 fps. This with RTX 4090 and 7800x3D. Your mileage may vary.

My BigScreen Beyond HMD has a screen brightness setting. For similar brightness levels, which is better for visual quality and for performance, the DCS gamma setting or BsB brightness?

2.9.5.55300. Win 11. AGM-56F with Lightning II TGP on Hornet. Single player. MP not tested. Previous behavior: Sensor control to TGP display, right DDI in this example. Use SA waypoint and WPDSG to point TGP near the target. Designate 1st moving target in TGP PTRK. Sensor control to Mav display (left DDI). Missile slaves to target designated by TGP. When in parameters, release missile. Missile (usually) tracks and hits TGP target. For next target SCS-R to TGP. SCS-R again undesignates target 1 and TGP reticle remains ground stabilized at Target 1 to facilitate designating a second target. Designate target 2. SCS-L to Mav display and second weapon attempts to slave to TGP and lock on target 2. And so on. New behavior: Designate target and deploy missile on target 1, as above. Now SCS-R and undesignate TGP target 1. TGP reticle snaps back to WPDSG waypoint instead of remaining ground stabilized at target 1. Slew TGP to new target and designate. SCS-L to Mav display; however, Mav seeker DOES NOT slave to new TGP target, but remains fixed to WP. Greatly reduces utility of Mavericks. One can also observe the HUD TGP cue does not follow the TGP reticle in PTRK. Returning SA to WP navigation (releasing WPDSG) at any point undesignates the TGP target and invokes slaving the TGP reticle to the WP. Tracks attached. MAVf.trk MAVf3.trk

See change log for 2.9.5.55300. value_pressed is .lua function parameter used in the joystick control file.

Anybody know the impacts of this program change?

Ahhhh. Many thanks.

In VR the F10 map and the message fonts Are much larger than I prefer, even though I have them set to 1, the smallest, in Options. Is there some way to reduce the default font size?

Yeah, strange. I do not see the color shift you refer to - only the FOV very edge color shift. Blue-green in the horizontal, red at verticals. Perhaps I won the headset lottery, but I do have old eyes.

Addendum. When looking for the chromatic aberration Kablamoman discussed, I did observe it; however, on my device the effect was so near the FOV limits I had not noticed it previously. I can just say that if upgrading from a G2 the improvement is dramatic. From other devices I cannot comment.