Habu_69

Download latest Moose version from here: https://github.com/FlightControl-Master/MOOSE_INCLUDE/tree/develop and Airboss lua file from below. Do minor editing of Airboss lua file as appropriate. Add them to mission with separate ME Do Script File triggers. If single player, set player aircraft as CLIENT in ME. When role selection menu appears in mission, hit ESCAPE twice, then select player aircraft. Use F10 menu item to Commence or Marshal. BOS-100 - Stennis Hornet and Tomcat.lua

When testing a Moose file, I run DCS in windowed mode so I can edit the script without leaving DCS. Use a Do Script trigger: dofile([[e:\Game Data\Scripts\Mission Scripts\Your Script.lua]]) -- complete file path of script. Then when you fly mission from within the ME the edited script loads dynamically. So procedure is reduced simply to edit the script and fly mission from within ME. Rinse and repeat.

Get it from the Moose Github. From Moose demo missions or perhaps download the whole Moose install file that includes it.

Mine runs fine on 2070 super.

Actually has happened in real life. Rookie pilot takes off near dusk with visor down and later can not understand why cockpit is so dark.

I can think of a dozen MAJOR systems of which we have yet to see even a hint: i.e. markpoints, terrain following radar, ECM/decoys, etc.

Suggest you look for help on the SRS Discord channel. Usually quick, knowledgeable help available there.

Not yet implemented. You CAN slew the square TGP LOS icon to a WP on the SA page.

A script is read by the mission only once, so if you need an action to start after the initial script read, those actions must be placed in a SCHEDULER function. Read about it in Moose docs. As an alternative, I suppose you could have a second independent script that is initiated by a trigger action when a trigger condition is met.

in the meantime try Moose Airboss script!

Dang. I thought it lifted the defogged the air and improved visibility.

Anyone ever noticed that the label colors identifying allies and enemies are reversed? In labels.lua lines 205 ColorAlliesSide = {249, 69, 38} the color specified is red. Line 206 assigns blue {0, 82, 199} to ColorEnemiesSide. In the sim the labels do show blue for allies and red for enemies, of course, leading to the conclusion that the .lua code variables are incorrectly named.

Using VR Kneeboard v 1.1.3.19 with Win 10 v 1903 with the client on a Surface 3 Pro and about half the time the Surface 3 client fails to function properly and the program is reported non-responsive by Windoze. Sometimes the images will load on the client, but not on the server, even tho it shows as connected. I understand that Surface is not one of the officially supported tablets, but any suggestions to improve reliability? I have reinstalled a couple of times.

Might be possible to use VA to move mouse cursor to a "safe" monitor screen location on DCS window, then left-click.

I have Reverb V2 with about same usage factor as Harlikwin. I am VERY gentle with the cable and no issues so far. Thanks for the heads-up about being aggressive when issues first begin.

Unsolicited testimonial. Strongly recommend PtControl finger control units. No haptic feedback like in a real pit, but best extant solution. Point with finger, click with thumb. Couldn't be (much) simpler and very intuitive.

Achieve radio distortion mainly by clipping the sound wave to limit freqs to the range of about 600 to 2000 Hz. You can also add mic clicks and background noise like gunfire and hiss. You should also double the loudness/volume.

@ MilesD. PtControl works great, but I still sometimes use the mouse. @Brun. I use PtControl Finger Control Units, which are currently calibrated for DCS Windowed mode. Windowed mode has advantages when DCS is enhanced with auxiliary programs like SRS, Voice Attack, VR Kneeboard, which occasionally need focus. Perhaps I will experiment with Full Screen and see how it goes. Is there a key command to switch from Full Screen back to Window mode?

The files and their folder structure must be put into the main DCS Bazar folder.

I have never had a WH stick (still use my OLD trusty force sensing Cougar), but I use the WH throttle and consider it one of the best available. Cougar sets are hard to find and quite old now, but occasionally one pops up on EBay. Usually over-priced unfortunately.

Most new flight simmers start with inexpensive gear, but as they gain experience soon learn that the gear is limiting their satisfaction, immersion and suspension of disbelief. They then upgrade to the maximum they can afford. I went through 3 such stages.

Just what do these new functions, i.e. Focus Factor, do?

I just noticed my AWACS comms menu has a new item DECLARE. Anyone tested it for functionality?

Have you tried a quick view zoom?

With my VR headset on I find it pretty easy to fumble around my "cockpit" and somehow lose window focus on DCS. I have yet to discover a way to restore focus to the DCS window when that happens. What is the secret??