Habu_69

Raw API/SSE code can be included in a Moose script or stand-alone script along with other scripts in a mission without issue, normally.

@Nalfeyn: By virtue of MOOSE’s hierarchical nature, certain classes “inherit” methods from a “parent” class. The class’s parent, if any, is stated in the MOOSE documentation; and the script writer has available all the methods from the parent class, even though the child class documentation may not restate the inherited methods. For example, the GROUP wrapper class is a child of the CONTROLLABLE class, which is a child of the POSITIONABLE class, which is a child of the IDENTIFIABLE class, which is a child of the OBJECT class. The IDENTIFIABLE class, therefore, includes all the methods documented in the OBJECT class. The POSITIONABLE class includes all the methods documented in the IDENTIFIABLE class, as well as its inherited methods, and so on. The GROUP wrapper class, then, includes all the methods in its family tree. Yes, the "names" are called variables, which are named buckets of data created by the scripter, much like words defined in a dictionary. The names can consist of any combination of letters in the English alphabet and underscores. They are case sensitive and the only prohibited characters are numbers, special characters ( ( ) . % + - * ? [] {} ^ $, etc.), apart from “_underscore”, and about 20 reserved words. Refer to the Lua Online Manual.

Guess I will bump this one time.

Do you mean Warthog throttle or Cougar throttle? Cougar throttle plugs into Cougar stick base, unless the throttle is modified for USB by a TUSBA device. Foxy enhances the unmodified Cougar functionality, but is not required. Warthog throttle is natively an independent windows USB device and switches have device DX assignments. I have owned both a Warthog and unmodified Cougar throttle. Warthog has more switches and better handle function. IMO the Cougar thumbstick outclasses the native Warthog slew control.

Anyone know how to modify this view parameter: iCommandViewAngleDefault for F/A-18C?

Scenario: Neutralize all SAM's except manpads (or assume they have been neutralized). As mentioned, deploy small groups of ground forces from both red and blue in close quarters in many separate locations and rely heavily on JTAC/AFAC to avoid blue on blue. High player penalties for TK's. Limit inventory of GPS weapons. JTAC/AFAC could be high value targets for red Syrian side. Syrian mobile command centers are HVT for blue side. For air combat, Iran operates modern jets from some forward operating base just to add to the regional turmoil. Treat Russian aircraft as neutral for ROE purposes and have blue enforce no-fly zones in blue controlled areas. Russia occasionally supplies Syria with strike helos. Perhaps enter the Kurds. They are open season for red side and protected by blue. Objective Red: capture a number of strategic geographic areas. Objective Blue: destroy a number of mobile command centers. Protect the Kurds.

The 2-stage trigger on my TM Cougar Stick shows in Windows game controller app as DX buttons 1 and 6. I would like to assign a F/A-18C controller function to TG1, but neither trigger button displays in the DCS Controls list of assignable buttons. Is there a way to make the trigger buttons display as assignable, or does a .lua file exist that I can modify to do what I want?

After targeting with the TGP FLIR mode and expending all AG ordnance, I turn off TGP and AG master mode, yet "FLIR" text continues to flash in the HUD and I do not know how to eliminate it. Any suggestions?

Anyone tried this recently? I checked this out a few DCS versions ago and found that DCS did not permit access to os.time(), IIRC.

Yeah, I have also experienced that "random" triggered events seem extremely biased.

Have to say I am impressed with how the .50793 patch now slaves the uncaged IR MAV seeker LOS exactly to the TGP target making MAV seeker lock near automatic in almost every instance. MAV is now a much more effective AG weapon. So now AGM-65F has 2 good targeting modes, slave to WP and slave to TGP, in addition to seeker LOS symbol in HUD. Mark points, when implemented, will make mavericks an an even more versatile and deadly weapon. Kudos to DCS for this one.

Hmmm. Yes, I tried Ground Crew/Request Launch with no joy. Will try again. Second trial: yeah, it works.

When I launch from the SC and recover, then taxi to a cat for another launch, the flight deck crew just stands around picking their . . . noses and adjusting their packages. The only way I have been able to get their attention is to taxi PAST the shuttle, but then OC I am way out of position to launch. Anyone know how to the the deck apes to do their job for a second launch?

Observe one of the "Sticky" threads above in this forum. Mist is a script file that must be loaded into a mission (usually at mission start) using a trigger function.

Suggest you pose your question in Moose Discord channel where you will find help aplenty. AFAIK (and I am a scripting novice) DCS has no such libraries. I believe the more proficient Moose script writers have developed script modules for creating tables of airfields, aircraft types, etc. that run at mission start.

Does a procedure exist to verify DL13 channel assignment prior to TTS=0?

Uh, no, but I can lean in to enlarge DDI. Is VR Zoom helpful in this context?

I, too, would like to see a detailed procedure for employment of multiple AGM-84E, but in English, please. The DDI DL-13 page OSB 15 UFC button to change DL-13 channels is non-functional until TTS = 0 and seeker video displays. Correct behavior? I am assigning DL13 initially to STA3, and stepping to set all weps to TOO. MSN check confirms all weps targeted to desired WP. Still having problems with seeker video. It comes on, but too blurry to find a target. In VR with 1080 res.

Hope that DCS soon fixes the MAV seeker LOS to be congruent with TGP designated target. This futtsing around between MAV and TGP to get a good MAV lock is a royal PIA.

Yes, you can do this. You can also add multiple individual scripts by means of the ME trigger action DO SCRIPT FILE and all will run normally. Word of caution, tho. Ensure that none of the individual scripts include the same global variable, like RedBandit or TargetZone, for example.

Tx. What I missed was BOTH value up and value down = 1.0. Seems odd.

2-Position Switch Something has changed in the F/A-18C joy default.lua. Both the joystick and the keyboard file have the same line to control the Pitot heater switch on the right console: {down = elec_commands.PitotHeater, up = elec_commands.PitotHeater, cockpit_device_id = devices.ELEC_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Pitot Heater Switch - ON/AUTO'), category = {_('Right Console'), _('ECS Panel')}}, I am assigning the command to a WH throttle maintained 2-position switch. Now this line should make the switch operate the ON and AUTO functions depending on switch position, but instead it operates both ON and AUTO functions in the switch down position. That is: switch down for ON, switch up does nothing, Switch down for AUTO, Switch up does nothing. Is this a bug? Any ideas on how to achieve my switch objective?

I have perceived that the DCS random number generator has a bias. In a random selection of 3 units the first unit in the list seemed to be selected out of proportion to true randomness. Not sure about math.random().

Reading the announced V2 description, calling this new headset "Gen 2" seems a stretch. Video enhancement confined to better lenses and audio phones. No change in resolution or FOV, the main features than need improvement. Unless the new lenses are truly revolutionary, doubt I will upgrade from current Reverb.

In SP dogfighting a MiG in F/A-18C. Occurs in 2.5.5 OB and persists in 2.5.6 OB latest patch; Caucasus and PG maps; VR and not VR; OC and not OC; Video freezes while in pursuit with no weapons employment. Log (attached) declares Access Violation. Sorry, no track file. Auto crash report invoked. Intel I5 8600, Win 10 v1809, Gigabyte Z370 Aorus MB; RTX-2070 Super, 32 GB DDR4, NVidia 441.87 driver dcs.log-20200529-175255.zip