Habu_69

Default release sequence is STA 8 PP1; STA 2 PP2; STA 8 PP1; STA 2 PP2. What works to attack 4 targets is default release weapons 1 and 2, MC auto steps back to STA 8. Then manually select PP2, release weapon 3 (STA 8); manually select PP1, release weapon 4 (STA 2). Now, is current behavior how actual jet functions or an artifact of F/A-18C EA? I guess this poor horse has now been beaten to death twice over.

Bug? or pilot error? I set 4 different pre-planned target coordinates for 4 JSOW weapons on 2 dual pylons at stations 2 and 8 using PP1 and PP2. When I release the 4 weapons in rapid succession, I see the MSN display cycle between the 2 stations and PP1 and PP2 as the weapons release. However, Tacview shows that both weapons on each station fly to the same target, indicating that currently the BRU 55 does not send unique coordinates to each weapon as programmed in the MC. Recognized behavior?

Any forecast of when the T-50 CM2 might be restocked?

Upuaut, you da man! this will revive many dead missions for me. Many thanks for seeing this through.

Lua predicates worked under 2.5.5. Have not tested under 2.5.6.

Position is trivial with any script and I think placing a WP very close to the unit will orient it as desired.

I think Moose scripting has several example missions employing a smoking moving vehicle.

As an alternative, one can quite effectively use the TGP to designate targets for JSOW in TOO mode.

Familiar with Microsoft Software Protection Platform Service? Basically one of M$ Win 10 anti-piracy bots. If you check Task Manager you will see its CPU usage occasionally spike to 50%. That must have an effect while flying DCS, no? I found you can stop it functioning by renaming its program: c:/windows/systen32/sppsvc.exe. When you do this, tho, Windows will nag you for not authenticating your Windows, so you have to change it back when operating under low CPU loads. I am by no means a Windows expert, so perhaps someone else can comment with more competency than I.

Escape not applicable to single player. Most mission builders assign the player as "Client" in ME (more flexible, I guess). If you fly mission as a client a "role selection" screen appears. Hit Escape, wait couple of seconds for script to load properly, then Escape again to return to role selection screen. Then select role and hit FLY.

@ Sgt Coyle. Range mission attached. Requires 476th Range Objects mod. Range script attached. Goldwater_Range.lua

@ Sgt Coyle. Range mission attached. Requires 476th Range Objects mod. Goldwater Range Bombs.miz

Welcome to the world of Moose. Download latest Moose from Develop branch here: https://github.com/FlightControl-Master/MOOSE_INCLUDE/tree/develop I use the Moose.lua from the static folder. Github Develop also provides links to download docs and example missions. If you are new to scripting, as I was, this might help you. Follow the Youtube videos on setup and you should be good. Moose developers and experts are usually online in Moose Discord and are happy to help noobies. To use a Moose script in a mission, Use a ME trigger to load the Moose.lua at mission start. Then use a second trigger to load your custom mission Moose script file with a few seconds delay. Moose opens up a world of features for your missions. MOOSE for Non-Coders.pdf

MAIN: Static1 ?? In all multiplayer missions (Hoggit server) I have text displayed near the top of my (F/A-18) wind screen. On left side: MAIN. On right side: Static1. Can anyone explain why this occurs and how to get rid of it?

Can you identify where the player speech sound files are located in the 2.5.6 folder structure? I could not. Concluded the entire speech engine has changes substantially.

Provide an option to silence the Player's voice in game.

Sounds like a good job for a spot of hot glue or zip tie.

2.5.6 rendered the silent pilot mod inoperative. It functioned in 2.5.5 by replacing the main install player voice sound files. Has anyone discovered a way to silence the pilot in 2.5.6?

I have a complete set of original Cougar gimbals with very little use, since I modded the stick to force sensing early on. Will sell them to highest bidder plus shipping. Let me know by PM.

2.5.6 created problems for RAT. Hopefully next patch will resolve them.

No. You can only cage/uncage and slew the TGP LOS.

Your description seems like you have nailed it.

Appreciate Nineline's Tuesday update info.

When I purchased F/A-18C early access in June 2018 I never imagined that approaching 2 years later the module would lack so many major systems, as well as shortcomings of many of the features implemented.

Great to have you modders continuing to support this little community.