Matrix Games Forums

The ability to use uncompressed .scen files. So we can actually see and hand code the scenario if needed.

ORIGINAL: Tomcat84

- that the editor when adding A/C, numbers them incrementally callsign 01, 02, 03 rather than 1, 2, 3 as it does now.

This prevents my list from looking like
Archer #1
Archer #10
Archer #11
Archer #12
Archer #2
Archer #3
Archer #4
Archer #5
Archer #6
Archer #7
Archer #8
Archer #9

and just makes it

Archer #01
Archer #02
Archer #03 etc.

This +1

ORIGINAL: brassem

ORIGINAL: Tomcat84

- that the editor when adding A/C, numbers them incrementally callsign 01, 02, 03 rather than 1, 2, 3 as it does now.

This prevents my list from looking like
Archer #1
Archer #10
Archer #11
Archer #12
Archer #2
Archer #3
Archer #4
Archer #5
Archer #6
Archer #7
Archer #8
Archer #9

and just makes it

Archer #01
Archer #02
Archer #03 etc.

This +1

Added in Build 455.

Thanks!

Means I have a lot of work to do to "fix" my scenarios though lol

My new request: Event that causes damage when there is a trigger.

I prefer this than teleporting the unit out of the area of operations.

Btw speaking of this: any chance of getting one or both of the following:
- Ability to change names easily I'm edit AC window
And/or:
- ability to set what digit to start numbering with.

Cause in real life different flights often not only have a different name but also number e.g.
Archer 11 through 14, snake 21 through 24, poker 31 through 32 etc.

ORIGINAL: Sunburn

ORIGINAL: brassem

ORIGINAL: Tomcat84

- that the editor when adding A/C, numbers them incrementally callsign 01, 02, 03 rather than 1, 2, 3 as it does now.

This prevents my list from looking like
Archer #1
Archer #10
Archer #11
Archer #12
Archer #2
Archer #3
Archer #4
Archer #5
Archer #6
Archer #7
Archer #8
Archer #9

and just makes it

Archer #01
Archer #02
Archer #03 etc.

This +1

Added in Build 455.

ORIGINAL: jomni

My new request: Event that causes damage when there is a trigger.

I prefer this than teleporting the unit out of the area of operations.

You mean a "please kill this unit" ?

Yes. For example, a terrorist unit enters an airbase and kill it along with all aircraft inside. Teleport would just move it elsewhere.

ORIGINAL: Sunburn

Added in Build 455.

It just keeps getting better and better! Many Thanks.

"Side changes Posture" as an event action.

The ability to SBR reference points. And to change their global position by key entry for specific location.

They can then be used a standard for such things as border lines, no fly zones, etc, so the mission builder can load them in as a building block module for their new scenario.

(Currently you need to add each and every point individually, and move them by cursor to the approximate position, then save it all as a .scen file. Then build you new scenario over the top of this one. The .scen is compressed so the mission builder has no access to the specific details to check accuracy by text editor numeric.)

In "add unit", it would be nice to be able to sort by unit and by current date.
Like "show all turkish frigates available in 1978"

please add in the event action of changing weather/sea state - ie, so it can be set to possibily changing mid scenario or even occurring in just a localised RP defined area - (one could make a separate unplayable 'weather' side)

also the ability for a mission type to change per trigger, - this could also make alot of dynamism in a larger scenario (or is this currently possible with the current options and just a lot of big think on the part of the scen developer?)

Added.

A way to change nuclear posture by event.

Removed "EE trigger: Unit is detected" as it has been implemented in Build 469. If you voted for this you can vote again.

If I currently want to assign a certain unit to a Side in scenario that in reality does not posses such unit I would have to "borrow" it from a country that has it in the DB.
The problem is that whenever you click on that unit in your scenario it will be IDd as "Russian" or "American" or "French" unit. Can we have generic units that don't belong to anyone?
You could create a generic instance of every unit, don't assign any weapons or sensors to it, let the scenario designer build the unit as he sees fit for his side.

Are you talking about the names?

Make sure no reference points are selected, select the unit, press the r key and rename.

mike

it doesnt matter too much... the tech is that sides, they did not develop it.

if you tentatively ID something using the contact report, you should expect a lower level of SA anyway...

but the side data is whichever side owns that unit, not specific to the DB but specific to the game you are playing.

1- when adding a new unit, have the country filter set by default to the country selected as the side (or remembers filters from last add)

2-have filter by keyword checked by default when adding a weapon/mount

3- option to auto create a call sign when adding aircraft

something like "aircraft type" Sqn, Det "ship/facility" (i.e. adding F-14s to the Enterprise--> "F-14 Sqn, Det Enterprise"