Change multiplayer slot logic

[slyvenne]

Hello,

 

I'm wondering if it is possible to change the slot logic in multiplayer?

Instead of pick a slot in a list, The player use an interface like solo action builder. With 4 dropdown list. The first to select calition.

The second the start airfield (or user wich enable multicrew, or observer/combined arms).

The third, the type of aircraft available (with quantity remaining like current ammunition supply menu).

The forth, an available parking slot on the airfield.

 

The interest is for mission editor. We only need to set up the inventory of the airfield without to care to have enough slot available for each aircraft. And we don't need to lock slot. That's the number of aircraft remaining on the airfield that will lock.

 

Currently, I have headache to place a combinaison of hind, huey, Mi8, Ka50, Gazelle of each type , F18 and soon  ah64 to content everybody on on a single airfield.

 

Thanks for your great job!

Edited October 12, 2021 by slyvenne

[FalcoGer]

I believe the player should be able to choose any option and have the other's filtered for that. For example I might decide I want to fly F16, and then pick an airfield from which to start. Or I decide I want to fly from Anapa and don't particularly care which aircraft. Or I want to fly multicrew with a specific other player.

Generally I agree though. Pick what you want, not a slot. You place 16 F16 on anapa then you can just say "F16 on anapa".

Although there are a number of issues with that, most of which would be solved with the DTC being implemented. In the ME players may place multiple flights, affecting data link settings, way points and default loadouts. I think a more reasonable way would be to add multiple filters to the slot list instead of just being able to sort by unit types, names or airfields.

[slyvenne]

Or the possibility to draw waypoint package for player in mission editor and you can load them in the game. Most of the time, it is the same waypoint for all client aircraft.

[Frederf]

Dynamically spawning aircraft from an airbase pool is an understandable idea. Most MP servers operate this way. DCS at its core is designed as more rigid scenario. It's a whole different way of thinking.

The mission planner (MP) being available in multiplayer has long been a desired feature. Lots of things are only really possible with the MP like an Su-25T's flight plan or some airplanes' radio presets or any callsign for instance. It wouldn't be too much of a stretch to include the ability to generate an entirely new flight/group in the MP (single or multiplayer) the same way one does in the ME. Only the warehouse supply would be locked. That would be change #1.

Change #2 would be to the slot join UI which as far as I can tell now is semi-static based on the mission. I don't think the list can change based on runtime events. Personally, I don't think the slot join UI should be purely a list like it is currently. An F10-like map location based initial selection geographically similar to the IL-2 Sturmovik series is more friendly.

The type of mission of "spawn any plane out of the pile anywhere at any time" is not well served by the current system.

[Ashayar]

On 4/6/2022 at 9:39 PM, Frederf said:

Dynamically spawning aircraft from an airbase pool is an understandable idea. Most MP servers operate this way. DCS at its core is designed as more rigid scenario. It's a whole different way of thinking.

The mission planner (MP) being available in multiplayer has long been a desired feature. Lots of things are only really possible with the MP like an Su-25T's flight plan or some airplanes' radio presets or any callsign for instance. It wouldn't be too much of a stretch to include the ability to generate an entirely new flight/group in the MP (single or multiplayer) the same way one does in the ME. Only the warehouse supply would be locked. That would be change #1.

Change #2 would be to the slot join UI which as far as I can tell now is semi-static based on the mission. I don't think the list can change based on runtime events. Personally, I don't think the slot join UI should be purely a list like it is currently. An F10-like map location based initial selection geographically similar to the IL-2 Sturmovik series is more friendly.

The type of mission of "spawn any plane out of the pile anywhere at any time" is not well served by the current system.

I really like the idea of your change #2!

[slyvenne]

Slot designation shall not be an issue because we can spawn on CV or tarawa without slot issue.

Edited August 17, 2022 by slyvenne