Habu_69

Yes, lua very fussy about commas. My cut/paste failed to get that last comma.

HMD Brightness Knob Solution Open file in the Your Install\Mods\aircraft\FA-18C\Input\FA-18C\keyboard\default.lua in Notepad++. Find this line:-- HMD Knob. Replace the 2 lines below it with these: { pressed = hmd_commands.BrtKnob, cockpit_device_id = devices.HMD_INTERFACE, value_pressed = -0.5, name = _('HMD OFF/BRT Knob - CCW/Decrease'), category = {_('Instrument Panel')}}, { pressed = hmd_commands.BrtKnob, cockpit_device_id = devices.HMD_INTERFACE, value_pressed = 0.5, name = _('HMD OFF/BRT Knob - CW/Increase'), category = {_('Instrument Panel')}},

HMD Brightness Keybind Not listed in F-18C Sim list of keybinds. Did DCS Repair and F/A-18C module reinstall, but still nogo. Knob works in cockpit. keyboard default.l.ua looks like this: --{ pressed = , cockpit_device_id = , value_pressed = -0.5, name = _('HMD OFF/BRT Knob - CCW/Decrease'), category = {_('Instrument Panel')}}, Any advice?

Hmmmm. Wonder if there is a way to add F10 menu item(s) to turn silence on/off, using script? I will put this on my to-do list, but not that much different from switching radio channels.

I am a new-ish MOOSE user with practically no previous background in coding. Regarding Doodenkoff's post, starting with Notepad++ may be fine for one's first venture into MOOSE, BUT once the power of MOOSE becomes apparent, a new mission designer will very quickly want to start tweaking the example scripts and developing unique scripts, for which LDT/intellisense is an invaluable tool. Regarding the LDT 1292 error, it pops up all the time and can be ignored, if the intellisense is working. Related issue: Not sure of other's experience, but any MOOSE script that includes a SCHEDULER method generates an LDT error: "Something probably wrong with this script" upon opening the script. Error disappears when I start typing.

With my 1440x2560 monitor 32" monitor, ball is easily visible at over 3/4 mi.

Absolutely. Not like MS flight Sim/VRS Superhornet where the meatball was near invisible and no help at all.

Never mind. Working now. . Well, my mod install of Desert FARP (V 1.2) does not appear as available static in ME. Looked in both Heliports and Structures. Installed both with JSGME and directly into main DCS OB Bazar, but it will not appear in ME object list. Files are definitely present in the correct Bazar folder. Any ideas? Win 10; DCSW 2.5.3.23225; PG Map

Should have thought of that!

Anyone know how to make them shut-up? They constantly step on other radio comms.

Anyone have a simple example of method: BIGSMOKEPRESET.MediumSmokeAndFire? to smoke static or coordinate?

I do not remember reading this as a required step, BUT sure enough, that was the issue. Much obliged.

@Upuaut: I do enjoy the realistic environment your mods add to DCSW. I have had an issue, however, with your Helipad mod (Oct 15 version). I have a mission script that iteratively selects and destroys a set of static objects (simulated bomb/artillery hits). When the script selects any of your heliports, the destroy fails, script halts and log enters an error. I have double-checked install and it seems fine. Heliport visible in 3D. DCSW 2.5.3.23225. PG map.

I have successfully set up TACAN and ILS in the ME for USS Stennis in many missions, However in this ONE PG mission it just will not work. In cockpit HSI, the TACAN search arrow just rotates ceaselessly. ICLS does not work either. I have double-checked TACAN/ILS channel settings, it is ON, HSI TACAN steering selected, etc. All the obvious stuff. ME setup image attached. Any clues? Bug? Anomoly?

dcs,log used to record sequentially all the mission EVENTS, hits, births, deaths, etc, but no longer does that. Is it a setting somewhere? Or program coding change? EVENTS are also not recorded in my debrief.log.

I think once you gain some familiarity with MOOSE you wll be amazed at the control you can impose on random, and any other, spawn process. The folks who hang out at the MOOSE Discord channel are most generous with their assistance.

Please correct me if I am mistaken, but I believe the install instructions regarding the autoexec.cfg file all have an error. The instructions should include a comma following the word /staddons. Like this: table.insert(options.graphics.VFSTexturePaths, "./Bazar/World/textures/staddons,")

@Tiramisu: I suggest you would find your scripting goals much easier to achieve using a LUA-based script extension like MOOSE or MiST rather than raw LUA. Example: Set up a group in ME, then in MOOSE use GROUP:FindByName( "Your Group" )

AI multi-ship group formations make "flanking" turns rather than "wheel" turns, as they must do to maintain relative formation stations. Therefore a ship stationed at 000 relative assumes a new station at 090 relative after a 90 turn to port.

F/A-18C has little use for cargo. Unless we have a travel pod.

Nice little inexpensive payware program Goldwave has a robust set of sound manipulation features. Primarily what you need is high/low band filter to reduce fidelity to about 800 to 1800 freq range. That reduces volume, tho, so you need to boost it back up. Goldwave also allows mixing in radio static, background noise, etc.

This is using BOMB POINT ON MAP, right? As stated above I have had NO success with BOMB GROUP, etc.

Lol. I have a nice little MOOSE script that creates random explosions in a defined zone.

AI bombing targets or groups appears broken, or at least unreliable, but I have had success with bombing a point on the map. Also with big bombers, they execute best when the WP with the bombing action is at least 20 miles from target and the turn towards target at that WP is less than 45D.

I have a MOOSE script that destroys an object when Hit.