Jagohu

Please add the existing "Unarmed" vehicles into the static objects "Ground Vehicles" list - it'd be nice to be able to use them (or remains of them). Thank you!

I'm quite sure this is not how an MLRS looks like. Please have a look. Thank you!

Thanks for the reply! This is what I see when I click the payload restriction button. WIthout restriction it's fine as it shows empty.

+1

The SH60B by default can't be loaded with anything (it'd be ideal if we could add 2*AGM114s as IRL, but that's not the issue I'm reporting). When "Payload restriction" is selected, "Empty" loadout field changes to AGM-119B Penguin ASM under pylon 1 (not visible on the helicopter).

While the "Draw" mode is selected, the coordinate field is not updated with the mouse cursor's position - this makes it rather difficult to draw airspace boundaries from Lat-Long coordinates. Is there a way to fix it? Cheers

All you can do is to place a static aircraft at the holding point, and once your traffic lands destroy it and replace it with a live one. Or you can go into timings and distances and experiment at what distance the AI initiates a go-around if the runway isn't free - and by the time it gets there just make the aircraft taxiing into a static object and continue making it taxi once your aircraft has landed. You can play around with vehicles though, they don't influence runway usage.

If you want to make sure you're looking at the right file, look up the one mentioned in the error message. It should be located where the error message says it. It only stays there while your DCS session is open, so I'd just switch tasks and look at it right away. There you can figure out which of your LUAs have the issue if you have multiple loaded.

Some countries don't have an option to add infantry units through the Mission Editor. There are a few important ones too. Could you perhaps add them? Even if they're basic models with an AK/M16 it'd be more than nothing. Argentina, Australia, Austria, Belgium, Canada, Chile, China, Croatia, Czech Republic, Denmark, Egypt, Ethiopia, France, Honduras, India, Iraq, Israel, Italy, Jordan, Kuwait, Libya, Malaysia, Mexico, Morocco, North Korea, Norway, Oman, Pakistan, Philippines, Poland, Portugal, Qatar, Saudi Arabia, Slovakia, South Africa, South Korea, Spain, Sudan, Sweden, Switzerland, Syria, Thailand, The Netherlands, Tunisia, Turkey, UAE, Venezuela, Vietnam, Yemen, Yugoslavia

Huh, I missed that completely, I wonder why was it red. Anyhow, thanks for checking it out and letting me know!

La Combattante II, P224 and P225

I'm planning on making one for my campaign, I'll post it here once it's ready

If an unknown track is selected and it's PLID is changed to Friendly or Hostile, the aircraft type is revealed. If it classified back as UNK, it's hidden again.

Single player only, yes

Tried it, taxied from EL3 to CAT4. Requested launch, nothing happens... I'm not alone but every other aircraft are inactive yet. Taxiing to CAT2 (while the assignment would be CAT1) works. So only CAT3/4 doesn't work. No arrivals, the people are out there they just don't react.

Check, will try. Yet if I taxi to the assigned CAT there's no need to request it. But thanks!

If the player taxies to a catapult which is not the one that he's parking spot is designated for, the catapult crew doesn't react, no marshaling, no indication anymore. It used to work and it wouldn't matter if we had proper taxi guidance. ie. spawning on Elevator 3(front), the designated catapult would be CAT1. Taxiing to CAT3 will not trigger the deck crew into action.

Static objects with type FARP, Single Helipad, Oil rig, Gas platform can't be destroyed. No errors in the log, but the object stays on. It seems like it affects the objects which have an ATC frequency. StaticObject.getByName('Static FARP-1'):destroy() no_static_object_destroy.trk no_static_destroy.miz

Many aircraft types from the modern aircraft arsenal seem to miss the datalink functionality, which they have in real life in some form. This forces players to deviate from IRL procedures, ie. tanker rendezvous. Please consider allowing the option of turning EPLRS (until the other datalink standards become available) for the following aircraft types and leave it up to the mission editors/player if they want to use it: A-10A, AV-8B, C-130, C17A, F-117, F/A-18A, KC-135, KC-135MPRS, KC-130, S-3B, S-3B Tanker

The S-3B Tankers seem to not extend the refueling basket unless there's a HOLD task defined after the Tanker task. I've tried it with the ME and also by scripting and the result is the same: as soon as you add a HOLD task after the tanker task it works properly. If it is left alone however, although you can contact the tanker and it'll turn on the lights it will not extend the basket - no matter what you do, no matter how close you are. This makes enroute refueling impossible, please fix this ASAP. Thank you! Mission and track file included. nobasket.miz no_basket_extended.trk

Since the last update I'm getting a lot of these messages in the log - it might have to do with flights on a unique name. It's odd though, because radio usage is selected as OFF for them. 2021-10-22 10:24:17.879 ALERT WRADIO: Error in wMessage::buildSpeech(), event = wMsgFlightPassingWaypoint: [string "./Scripts/Speech/common.lua"]:590: Callname 7 not found for QTR1PJ ! stack traceback: [C]: ? [C]: in function 'error' [string "./Scripts/Speech/common.lua"]:590: in function <[string "./Scripts/Speech/common.lua"]:583> (tail call): ? [string "./Scripts/Speech/common.lua"]:1265: in function 'make' [string "./Scripts/Speech/common.lua"]:1272: in function 'make' [string "./Scripts/Speech/common.lua"]:3135: in function 'make' [string "Scripts/Speech/speech.lua"]:143: in function <[string "Scripts/Speech/speech.lua"]:122>

I wouldn't like to sit in an airplane and use it's auto-throttle if it'd first go to flight idle, no matter what. It just goes against common sense, especially in an approach mode. Even the old analogue ATs I've seen (TU-134/154) didn't do that, let alone the digital ones (based on my experience as a flight engineer in my young days). I'm not a Hornet guy, but Pieterras represents the opinion of a bunch of IRL pilots.

Same issue in this topic, I figured it's more an F-14 issue than a SC.

Spawning on the CVN-70, Carl Vinson with Ramp Start results in: -AI spawned up and running on the catapult -Player spawned cold and dark with chocks on the catapult -No deck crew Files attached. CVN70_ramp_start_on_cat.miz CVN70_cold_start_on_cat.trk

In a scenario when the routing is WP0(spawn)-WP1(hold)-WP2(land on CVN), if there is more than just the holding (until time 08:10:00) task defined at WP1, the formation of 4 will break up and curiously enough depending on the weather preset it'll break up instead of holding. RainyPreset2 - lead will hold as specified, -2 -3 -4 will go for landing RainyPreset3 - lead and -2 will hold as specified, -3 -4 will go for landing If there is only the holding task specified at WP1 it's all ok. Also, if the next WP is another turning point instead of landing it's all ok - even if there are multiple tasks set at WP1. A little bit of explanation: holding is defined for the inbound aircraft to wait overhead until event time before starting the recovery. The Immortal task is set because many times (especially during a CASE I holding) they crash into each other. Track, miz files attached. Please try to fix this. Thank you! hold_ok_immortal_RainyPreset2_WP1-2-3.miz hold_only1of4_immortaltask_holdtask_RainyPreset2_WP1-2.miz hold_4of4_RainyPreset2_ImmortalTask_WP1-2-3.trk hold_4of4_RainyPreset2_noImmortalTask.trk hold_only1of4_RainyPreset3.trk hold_only2of4_RainyPreset2.trk