CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
Moderator: MOD_Command
CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
Command: Modern Operations is coming soon. In this piece, let us take a look at two of the most hotly anticipated new features, as well as some of the less conspicuous interface additions.
User Interface and Experience Part I is available here.
Brace yourselves for User interface and experience, Part II (featuring the TacView and LOS).
Seeing is believing: Tacview support
This has been a very popular request for years, one which we are now very happy to oblige. Support for Tacview, a 3D simulation-visualization and flight analysis tool, has been a feature of Command PE for a while, and now a subset of this functionality is being made available to the commercial edition as well. A key difference is that PE also supports after-action mode (ie. exporting sim state to a text file and then playing it back in Tacview), whereas CMO supports only real-time streaming.
(IMPORTANT NOTE: To use Tacview with CMO, purchasing a Tacview Advanced or Enterprise license is required, because only these versions support real-time streaming.)
We have been in close contact with Frantz Raia (creator of Tacview) over the years and he has made several additions to the software, upon our request, which have been very useful both to us and to his own professional work (such as the real-time streaming feature). We worked hard together with Frantz on finding a way to make CMO work well with Tacview. What we came up with is an optional ability to stream part of the simulation information to Tacview.
The player can select a “3D view” menu option, and if Tacview is installed, a new window pops up which contains the 3D visualization (this requires Tacview Advanced edition in order to work). This window behaves similar to all other secondary windows in Command, so it can be resized, placed anywhere atop the main map window, or parked on another monitor. The player can jump from one unit to another, rotate and plan the camera etc., just like when normally using Tacview as a standalone app.
Using two or more monitors is a common choice in this configuration, as it allows a full-size 3D window without sacrificing map area:
The association between the database and Tacview’s 3D models (which model to display for unit-XYZ?) is handled by two Excel spreadsheets (one for DB3000 and another for CWDB) which list all database entries and the most suitable model for each (because there are not enough models for all platforms in the databases, often generic models or “close enough” substitutes are used instead of precise matches). The 3D models are stored as individual .obj files (Alias-Wavefront format). This is important, because it means that end users can tweak the associations and add their own custom models as desired.
Some more examples of Tacview connectivity…
Close air combat
ASW torpedo engagement
Antiship standoff-LGB attack
Going out in style
This time around, the default icon style is “Directional Stylized” (the pro version retains the NTDS + NATO APP-6 as default), to aid players not familiar with military symbology. This has allowed us to add something that has been on our wish list for a while now: dynamically resize icons to represent a ship/sub’s actual dimensions. This is a static example:
And here is how it can look when zooming in on a close-range action, for example in a littoral firefight:
Littoral firefight
As an extra styling feature, the datablocks can now optionally have the color appropriate to the unit or contact’s posture (blue for friendly, red for hostile etc.). This can help declutter the map in “busy” setups and also more clearly distinguish between multiple sides:
I got my eye on you: LOS tool
Let’s start this segment with a public announcement of sorts. To those that have been complaining that Command is not full stressing your multi-core CPU: Your rig’s sadistic torturer has arrived, and its name is the Line-of-Sight (LOS) tool.
This handy feature enables the player to view the “line of sight” from a selected unit. The LOS coverage will appear as a colored (semi- or fully-opaque) area around the unit, making it useful for determining what the unit in question can see or detect. The tool can be applied to either a friendly or detected enemy unit, meaning it can be used to either plot offensive (“hmm, this mountain is a nice radar blocker….”) or defensive (“Since my ground-based radar stations can’t see well over here, I should send my fighter patrols over to cover the gap”) strategies.
The line of sight tool in action, with lime green selected as the color. To the north is mostly barren desert where the tool can reach its max distance. To the south is a mountain range where it’s frequently blocked off.
There are several customizable options on the tool.
- Max distance. This sets the maximum range in nm the tool will extend to. It can be reined in either for the sake of performance or for showing a sensor with very limited range.
- Target altitude (m AGL). This shows the altitude at which the LOS target is determined. Higher flying units can obviously be seen from farther away, and the setting can be changed in light of the usual attack profile of the scenario’s threat units (ie, threat aircraft with terrain following suites like F-111s or Su-24s will go at lower altitudes than ones that don’t have them, like earlier and/or simpler aircraft). The “same as observer” box can be checked to assume that the target is at the same altitude as the selected unit.
- Horizon type. The “Radar/ESM” option, assuming an “electronic horizon” capable of reaching longer distances than visual sight, is the default. The shorter range “Visual/EO/Laser” option can be checked if need be, such as for a unit that uses those as its primary sighting system.
- Shade color. Clicking “change” opens up a palette of colors that can be selected as the one to display. Color can be changed to avoid conflicting with other map elements or for the sake of aesthetics/ease of sight.
Finding things quickly
Another popular request has now been fulfilled: The ORBAT (order of battle) window can be held open continuously through a game session, as it updates automatically. In addition, key-search on the ORBAT list is now possible, allowing players to easily find a specific unit that they are looking for:
And the clincher: Now contacts are also listed on the ORBAT window, AND their list is also dynamically updated, AND they too are searchable:
We got a score to settle
The scoring & evaluation window has also received its fair share of love. Players have asked for a better sense of how their current (or final) score compares against the best & worst possible outcomes; so what better way to visualize this than a tachometer gauge:
Players have also asked for a more visual representation of how the current score has fluctuated as a result of things happening in the scenario. So we added an interactive graph that allows easily browing the various events that changed the score:
Sticks & levers
We know for a fact this will make quite a few users happy: The speed & altitude orders window (aka “F2 window”, because of the hotkey) has been reworked to more clearly distinguish between having selected a waypoint of a unit’s plotted course or the unit itself.
Example with waypoint selected:
Example with the unit itself selected:
Also, by using the white “previous” and “next” arrows next to the unit/waypoint description, it is possible to select the previous/next waypoint or the unit itself without leaving this window.
The unit-status column now also includes a small panel with shortcuts for the most common throttle & altitude commands and presets, so that a unit’s (or waypoint’s) behavior can be altered without necessarily bringing up the F2 window:
Where was I again?
This one proved a huge timesaver during development & testing, and we hope it will do the same for players: Command now keeps a tally of the most recently loaded saves or scenarios, and allows quickly selecting any of them to load, instead of having to use the “Load scenario” window:
Marshall the troops
Another player request: When having one or more units selected, a summary list of them (grouped by unit class) appears on the map. This makes it easy to quickly remember what forces you are currently actively issuing orders to. It can also act as a convenient way to quickly get up to speed on available forces in a theater (simply drag-select everything in the area and glance at the “shopping list”):
(Yes, we loved Homeworld in its day. Why do you ask?)
At a glance
One other persistent player complaint over the years has been that unit icons and datablocks present only the barest information like course, speed & altitude, plus basic fuel status & structural damage. For almost any other piece of information, the player’s eyeballs have to jump from the map to the right column for the detailed information, and hop back to the map to watch the action. If only the player was able to get more information about a unit or contact without leaving the map…
Thy will be done:
We call this the “hover info box”, because it appears only when the mouse cursor hovers over the icon of a friendly unit or contact (and the player holds down Ctrl. There are times that the box gets in the way or hides things, so the player must actively consent to have it show up).
One of the nice things about this summary view is that it is quite configurable; players can dictate which information parts they want to see in this view and how they will appear:
This feature works best when combined with the slide-in/out of the right column: If the information provided by the hover-box is sufficient, it means that the right column can be left tucked out of the way for most of the time, substantially increasing the available map space.
Pick me! Pick me!
Another new feature aims to solve one of those small but persistent annoyances: When lots of units/contacts are stacked closely together on the map (not uncommon, especially in zoomed-out view), in order to select a specific unit the player must either zoom-in to declutter and pick out the desired one, or alternatively click repeatedly on the stack until the desired one is selected. Both approaches work, but neither is ideal.
So here’s a better way:
As the player clicks on a stack of units, a dynamic menu lists all the bunched-up units. The player can then select the one he wants.
A map for every taste
One other popular request has been the ability to quickly jump from one place of the theater to another, without having to zoom out and back in to the desired location (or to repeatedly pan the map). The quick-jump slots already provide this ability, but these seem to be a criminally under-used feature. What players really wanted was a minimap.
And we got the three of them.
In the above example, we are using concurrently the “global” and “scenario” versions of the minimap. The former always shows a global map with the positions of units and known contacts, whereas the latter focuses on the dimensions of the operating theater (defined roughly as a bounding box of the units & known contacts). There is also a third mode available, “Camera”, which acts as a “zoom-out” of the current map window, centered on the current map location.
Running on empty
One more frequent user request: display the remaining flight range for the currently selected aircraft, based on current speed and fuel consumption. This can be quite useful for quickly visualizing targets (and divert airfields) within reach of an aircraft in its current state. The feature is treated like other range-ring options and persisted as part of the map profile. Note that this displays the aircraft’s remaining _range_, not _radius_. Here is an example:
That was a long ride! Don't miss our next deepening: The grunt’s lot
User Interface and Experience Part I is available here.
Brace yourselves for User interface and experience, Part II (featuring the TacView and LOS).
Seeing is believing: Tacview support
This has been a very popular request for years, one which we are now very happy to oblige. Support for Tacview, a 3D simulation-visualization and flight analysis tool, has been a feature of Command PE for a while, and now a subset of this functionality is being made available to the commercial edition as well. A key difference is that PE also supports after-action mode (ie. exporting sim state to a text file and then playing it back in Tacview), whereas CMO supports only real-time streaming.
(IMPORTANT NOTE: To use Tacview with CMO, purchasing a Tacview Advanced or Enterprise license is required, because only these versions support real-time streaming.)
We have been in close contact with Frantz Raia (creator of Tacview) over the years and he has made several additions to the software, upon our request, which have been very useful both to us and to his own professional work (such as the real-time streaming feature). We worked hard together with Frantz on finding a way to make CMO work well with Tacview. What we came up with is an optional ability to stream part of the simulation information to Tacview.
The player can select a “3D view” menu option, and if Tacview is installed, a new window pops up which contains the 3D visualization (this requires Tacview Advanced edition in order to work). This window behaves similar to all other secondary windows in Command, so it can be resized, placed anywhere atop the main map window, or parked on another monitor. The player can jump from one unit to another, rotate and plan the camera etc., just like when normally using Tacview as a standalone app.
Using two or more monitors is a common choice in this configuration, as it allows a full-size 3D window without sacrificing map area:
The association between the database and Tacview’s 3D models (which model to display for unit-XYZ?) is handled by two Excel spreadsheets (one for DB3000 and another for CWDB) which list all database entries and the most suitable model for each (because there are not enough models for all platforms in the databases, often generic models or “close enough” substitutes are used instead of precise matches). The 3D models are stored as individual .obj files (Alias-Wavefront format). This is important, because it means that end users can tweak the associations and add their own custom models as desired.
Some more examples of Tacview connectivity…
Close air combat
ASW torpedo engagement
Antiship standoff-LGB attack
Going out in style
This time around, the default icon style is “Directional Stylized” (the pro version retains the NTDS + NATO APP-6 as default), to aid players not familiar with military symbology. This has allowed us to add something that has been on our wish list for a while now: dynamically resize icons to represent a ship/sub’s actual dimensions. This is a static example:
And here is how it can look when zooming in on a close-range action, for example in a littoral firefight:
Littoral firefight
As an extra styling feature, the datablocks can now optionally have the color appropriate to the unit or contact’s posture (blue for friendly, red for hostile etc.). This can help declutter the map in “busy” setups and also more clearly distinguish between multiple sides:
I got my eye on you: LOS tool
Let’s start this segment with a public announcement of sorts. To those that have been complaining that Command is not full stressing your multi-core CPU: Your rig’s sadistic torturer has arrived, and its name is the Line-of-Sight (LOS) tool.
This handy feature enables the player to view the “line of sight” from a selected unit. The LOS coverage will appear as a colored (semi- or fully-opaque) area around the unit, making it useful for determining what the unit in question can see or detect. The tool can be applied to either a friendly or detected enemy unit, meaning it can be used to either plot offensive (“hmm, this mountain is a nice radar blocker….”) or defensive (“Since my ground-based radar stations can’t see well over here, I should send my fighter patrols over to cover the gap”) strategies.
The line of sight tool in action, with lime green selected as the color. To the north is mostly barren desert where the tool can reach its max distance. To the south is a mountain range where it’s frequently blocked off.
There are several customizable options on the tool.
- Max distance. This sets the maximum range in nm the tool will extend to. It can be reined in either for the sake of performance or for showing a sensor with very limited range.
- Target altitude (m AGL). This shows the altitude at which the LOS target is determined. Higher flying units can obviously be seen from farther away, and the setting can be changed in light of the usual attack profile of the scenario’s threat units (ie, threat aircraft with terrain following suites like F-111s or Su-24s will go at lower altitudes than ones that don’t have them, like earlier and/or simpler aircraft). The “same as observer” box can be checked to assume that the target is at the same altitude as the selected unit.
- Horizon type. The “Radar/ESM” option, assuming an “electronic horizon” capable of reaching longer distances than visual sight, is the default. The shorter range “Visual/EO/Laser” option can be checked if need be, such as for a unit that uses those as its primary sighting system.
- Shade color. Clicking “change” opens up a palette of colors that can be selected as the one to display. Color can be changed to avoid conflicting with other map elements or for the sake of aesthetics/ease of sight.
Finding things quickly
Another popular request has now been fulfilled: The ORBAT (order of battle) window can be held open continuously through a game session, as it updates automatically. In addition, key-search on the ORBAT list is now possible, allowing players to easily find a specific unit that they are looking for:
And the clincher: Now contacts are also listed on the ORBAT window, AND their list is also dynamically updated, AND they too are searchable:
We got a score to settle
The scoring & evaluation window has also received its fair share of love. Players have asked for a better sense of how their current (or final) score compares against the best & worst possible outcomes; so what better way to visualize this than a tachometer gauge:
Players have also asked for a more visual representation of how the current score has fluctuated as a result of things happening in the scenario. So we added an interactive graph that allows easily browing the various events that changed the score:
Sticks & levers
We know for a fact this will make quite a few users happy: The speed & altitude orders window (aka “F2 window”, because of the hotkey) has been reworked to more clearly distinguish between having selected a waypoint of a unit’s plotted course or the unit itself.
Example with waypoint selected:
Example with the unit itself selected:
Also, by using the white “previous” and “next” arrows next to the unit/waypoint description, it is possible to select the previous/next waypoint or the unit itself without leaving this window.
The unit-status column now also includes a small panel with shortcuts for the most common throttle & altitude commands and presets, so that a unit’s (or waypoint’s) behavior can be altered without necessarily bringing up the F2 window:
Where was I again?
This one proved a huge timesaver during development & testing, and we hope it will do the same for players: Command now keeps a tally of the most recently loaded saves or scenarios, and allows quickly selecting any of them to load, instead of having to use the “Load scenario” window:
Marshall the troops
Another player request: When having one or more units selected, a summary list of them (grouped by unit class) appears on the map. This makes it easy to quickly remember what forces you are currently actively issuing orders to. It can also act as a convenient way to quickly get up to speed on available forces in a theater (simply drag-select everything in the area and glance at the “shopping list”):
(Yes, we loved Homeworld in its day. Why do you ask?)
At a glance
One other persistent player complaint over the years has been that unit icons and datablocks present only the barest information like course, speed & altitude, plus basic fuel status & structural damage. For almost any other piece of information, the player’s eyeballs have to jump from the map to the right column for the detailed information, and hop back to the map to watch the action. If only the player was able to get more information about a unit or contact without leaving the map…
Thy will be done:
We call this the “hover info box”, because it appears only when the mouse cursor hovers over the icon of a friendly unit or contact (and the player holds down Ctrl. There are times that the box gets in the way or hides things, so the player must actively consent to have it show up).
One of the nice things about this summary view is that it is quite configurable; players can dictate which information parts they want to see in this view and how they will appear:
This feature works best when combined with the slide-in/out of the right column: If the information provided by the hover-box is sufficient, it means that the right column can be left tucked out of the way for most of the time, substantially increasing the available map space.
Pick me! Pick me!
Another new feature aims to solve one of those small but persistent annoyances: When lots of units/contacts are stacked closely together on the map (not uncommon, especially in zoomed-out view), in order to select a specific unit the player must either zoom-in to declutter and pick out the desired one, or alternatively click repeatedly on the stack until the desired one is selected. Both approaches work, but neither is ideal.
So here’s a better way:
As the player clicks on a stack of units, a dynamic menu lists all the bunched-up units. The player can then select the one he wants.
A map for every taste
One other popular request has been the ability to quickly jump from one place of the theater to another, without having to zoom out and back in to the desired location (or to repeatedly pan the map). The quick-jump slots already provide this ability, but these seem to be a criminally under-used feature. What players really wanted was a minimap.
And we got the three of them.
In the above example, we are using concurrently the “global” and “scenario” versions of the minimap. The former always shows a global map with the positions of units and known contacts, whereas the latter focuses on the dimensions of the operating theater (defined roughly as a bounding box of the units & known contacts). There is also a third mode available, “Camera”, which acts as a “zoom-out” of the current map window, centered on the current map location.
Running on empty
One more frequent user request: display the remaining flight range for the currently selected aircraft, based on current speed and fuel consumption. This can be quite useful for quickly visualizing targets (and divert airfields) within reach of an aircraft in its current state. The feature is treated like other range-ring options and persisted as part of the map profile. Note that this displays the aircraft’s remaining _range_, not _radius_. Here is an example:
That was a long ride! Don't miss our next deepening: The grunt’s lot
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
These are really great improvements. Thanks alot.
Does it mean Alt-tab out of C:MO, Tacview is also inactive? This would be essential for me
This together with steam workshop - wow.
Keep up the really great work. [&o]
ORIGINAL: Daniele
... This window behaves similar to all other secondary windows in Command, so it can be resized, placed anywhere atop the main map window, or parked on another monitor. ...
Does it mean Alt-tab out of C:MO, Tacview is also inactive? This would be essential for me
ORIGINAL: Daniele
platforms in the databases, often generic models or “close enough” substitutes are used instead of precise matches). The 3D models are stored as individual .obj files (Alias-Wavefront format). This is important, because it means that end users can tweak the associations and add their own custom models as desired. ...
This together with steam workshop - wow.
Keep up the really great work. [&o]
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
There is no next article?
That means....next is release???!!!! [:D][:D]
That means....next is release???!!!! [:D][:D]
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
Look good, but I have a question, how does it run, the original command did not use any multi threading support it was unplayable on HDT machines.
Modding tools for TOW and IL2 series (archive extractor and 3d model converter)
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
Phenomenal amount of improvements. Stunning.
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
Nice! The Tacview feature is really appreciated as it adds to immersion immensely!
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
Love the changes. Total support.[&o]
I've already picked my perfect christmas present [;)]
I've already picked my perfect christmas present [;)]
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
ORIGINAL: AlesMrak
Look good, but I have a question, how does it run, the original command did not use any multi threading support it was unplayable on HDT machines.
That's simply not true. CMANO already does a ton of multi-threading. The reason it cannot fully saturate more than 4-5 threads has to do with the shallow execution depth of each thread (which BTW is a good thing, because it means that the individual threaded "pieces of work" are run very fast).
If you read guides such as this: https://www.nimaara.com/practical-paral ... duce-in-c/ ...you will notice that even super-simple threads, simply cannot utilize a multi-core CPU over a certain limit when they are not "deep" enough. Apps that fully utilize modern CPUs (3D raytracing, video editing, map-reduce pattern apps etc.) do so by having each thread be a long-running independent one, which is not feasible in a discrete-time simulation where by necessity you have tons of synchronization overhead and some parts of the code must inescapably run synchronously.
CMO does run faster than CMANO but achieves this by other tricks and improvements, not some magical breakthrough in parallelism.
Now, if you ARE looking for a way to fry your CPU.... the LOS tool is what you've been waiting for. We warned you [:D]
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
BTW if you have performance problems in a 4K desktop with Command, your first recourse is this: https://www.matrixgames.com/forums/tm.asp?m=4190908
And this: https://steamcommunity.com/sharedfiles/ ... 1374061499
And this: https://steamcommunity.com/sharedfiles/ ... 1374061499
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
One user in spanish forum pointed to something intereseting. He said that now maybe tacview would make some kind of cheat, as for example in the video of the akula sub when deep dives in tacview, that information is not shown in the map of cmano.
I don't know if that happens or not, but my question is: Will tacview only represent what is known of the contacts? When it doesn't know the deep (altitude), exact location of the contact (but know it is there), or even if it is a contact you don't know which class of it, it is, how is going to be that represented in Tacview? I hope the same way that in Cmano (jumping 3D objects for not known real position contacts, blanc 3D for not really known contacts, etc...)
Thanks!
I don't know if that happens or not, but my question is: Will tacview only represent what is known of the contacts? When it doesn't know the deep (altitude), exact location of the contact (but know it is there), or even if it is a contact you don't know which class of it, it is, how is going to be that represented in Tacview? I hope the same way that in Cmano (jumping 3D objects for not known real position contacts, blanc 3D for not really known contacts, etc...)
Thanks!
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
ORIGINAL: Japo32
One user in spanish forum pointed to something intereseting. He said that now maybe tacview would make some kind of cheat, as for example in the video of the akula sub when deep dives in tacview, that information is not shown in the map of cmano.
I don't know if that happens or not, but my question is: Will tacview only represent what is known of the contacts? When it doesn't know the deep (altitude), exact location of the contact (but know it is there), or even if it is a contact you don't know which class of it, it is, how is going to be that represented in Tacview? I hope the same way that in Cmano (jumping 3D objects for not known real position contacts, blanc 3D for not really known contacts, etc...)
Thanks!
The user is correct; Tacview was originally designed as an AAR tool so it's geared to always show the "ground truth". So using it in conjunction with Command can lead to the user "cheating". (Of course, Command has always inherently left to the user's discretion whether to stay within the restrictions of realistic fog-of-war; for example, it is trivial to cheat by running a scenario in ScenEdit mode).
If there is sufficient interest post-release, we can examine the possibility of tweaking the streamed information to approximate the own-side view of the theater instead of the ground truth.
- HalfLifeExpert
- Posts: 1161
- Joined: Mon Jul 20, 2015 3:39 pm
- Location: California, United States
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
All these new features look great! I am especially happy about the fuel range rings and the selection menu for units bunched together!!
I'll just have to remember to immediately switch the icons to NATO/NTDS, as I find them vastly superior, to the point where I even made the strong suggestion in my new user guide to use them over the stylized Icons.
That being said, I have a question about this feature:
Does this apply to the NATO/NTDS icons as well? I ask because there have been occasions when i've realized that I have no idea if this surface contact is a small sailing boat or a large cruiser. Seems like Radars should be able to tell that general size in short order so that I can immediately dismiss small contacts if i'm on the lookout for a medium size warship.
If not then perhaps this is a future addition that can be considered for contact information, just a basic note as to whether the contact is tiny, small, medium, large, or massive.
I'll just have to remember to immediately switch the icons to NATO/NTDS, as I find them vastly superior, to the point where I even made the strong suggestion in my new user guide to use them over the stylized Icons.
That being said, I have a question about this feature:
dynamically resize icons to represent a ship/sub’s actual dimensions.
Does this apply to the NATO/NTDS icons as well? I ask because there have been occasions when i've realized that I have no idea if this surface contact is a small sailing boat or a large cruiser. Seems like Radars should be able to tell that general size in short order so that I can immediately dismiss small contacts if i'm on the lookout for a medium size warship.
If not then perhaps this is a future addition that can be considered for contact information, just a basic note as to whether the contact is tiny, small, medium, large, or massive.
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
ORIGINAL: HalfLifeExpert
All these new features look great! I am especially happy about the fuel range rings and the selection menu for units bunched together!!
I'll just have to remember to immediately switch the icons to NATO/NTDS, as I find them vastly superior, to the point where I even made the strong suggestion in my new user guide to use them over the stylized Icons.
That being said, I have a question about this feature:
dynamically resize icons to represent a ship/sub’s actual dimensions.
Does this apply to the NATO/NTDS icons as well? I ask because there have been occasions when i've realized that I have no idea if this surface contact is a small sailing boat or a large cruiser. Seems like Radars should be able to tell that general size in short order so that I can immediately dismiss small contacts if i'm on the lookout for a medium size warship.
If not then perhaps this is a future addition that can be considered for contact information, just a basic note as to whether the contact is tiny, small, medium, large, or massive.
It's only for directional stylized for now, sorry!
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
Wow! Everything looks great and very useful at the same time. Can't wait. Really glad to see so many wish list items about user interface and info features being added.
----------------
Dave A.
"When the Boogeyman goes to sleep he checks his closet for paratroopers"
Dave A.
"When the Boogeyman goes to sleep he checks his closet for paratroopers"
-
- Posts: 3
- Joined: Sun Oct 19, 2014 5:58 am
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
Now we have G-Tolerance readings on planes, right?. That's awesome
-
- Posts: 131
- Joined: Mon Jan 08, 2018 12:25 pm
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
Since you mentioned performance improvements. How many more missiles can I shoot at once compared to CMANO? Basically are we looking at a respectable 20% performance boost or something more extreme like 50%?
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
That LOS tool is right on the money. Useful for route and attack planning. Awesome!
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
With these 'Directional Stylized' symbols that are dynamically resized, to me, it would really make sense to consider a future option to automatically switch from 'NTDS + NATO APP-6' symbols to 'Directional Stylized' ones when the formation editor is brought up, or if the map is zoomed in close enough for the dynamic resizing to take effect (or perhaps at customizable 'Camera Alt').
For me, 'NTDS + NATO APP-6' are absolutely the default way to go due to their clarity and... leanness. But I could see the benefit of 'Directional Stylized' particularly in situations mentioned above.
For me, 'NTDS + NATO APP-6' are absolutely the default way to go due to their clarity and... leanness. But I could see the benefit of 'Directional Stylized' particularly in situations mentioned above.
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
ORIGINAL: AKar
With these 'Directional Stylized' symbols that are dynamically resized, to me, it would really make sense to consider a future option to automatically switch from 'NTDS + NATO APP-6' symbols to 'Directional Stylized' ones when the formation editor is brought up, or if the map is zoomed in close enough for the dynamic resizing to take effect (or perhaps at customizable 'Camera Alt').
For me, 'NTDS + NATO APP-6' are absolutely the default way to go due to their clarity and... leanness. But I could see the benefit of 'Directional Stylized' particularly in situations mentioned above.
Great idea!
-
- Posts: 100
- Joined: Thu Feb 09, 2017 5:58 pm
RE: CMO User interface and experience, Part II (featuring the TacView, LOS, ORBAT, and more)
ORIGINAL: mikerohan
ORIGINAL: AKar
With these 'Directional Stylized' symbols that are dynamically resized, to me, it would really make sense to consider a future option to automatically switch from 'NTDS + NATO APP-6' symbols to 'Directional Stylized' ones when the formation editor is brought up, or if the map is zoomed in close enough for the dynamic resizing to take effect (or perhaps at customizable 'Camera Alt').
For me, 'NTDS + NATO APP-6' are absolutely the default way to go due to their clarity and... leanness. But I could see the benefit of 'Directional Stylized' particularly in situations mentioned above.
Great idea!
+1
I really like this idea!