JTLS-GO

8056 record(s) found.

Improvement List


Area: Subarea: Sort By: Status

Search Description:

InfoAreaSubareaDescription
MCR: JTLS-2026-17758
Date: 2026-06-02
Status: Accepted
C4IHK42 - Fire Mission IMT Configuration Options

JESTC requests that a new "Fire Mission Type" tab be added to the configuration options in the Fire Mission IMT to permit filtering by "Waiting" and/or "Fired". Also, Fire Missions should not automatically vanish after a few minutes. Instead, add a "Clear" button to the upper right corner (just like the Air Mission IMT) that deletes all the "Fired" missions only.
MCR: JTLS-2026-17757
Date: 2026-06-02
Status: Accepted
C4IAlert Message Separate Naval Tab

JESTC staff requests that a third tab be added to the Alert Messages panel that effects only Naval units (separate from non-Naval units).
MCR: JTLS-2026-17756
Date: 2026-06-02
Status: Accepted
C4IBe Able to Create New Types Of Barriers During Game Play

The desire is to create new types of barriers during game play.
MCR: JTLS-2026-17755
Date: 2026-06-02
Status: Accepted
ToolsInconsistent AAR And SDC Filter Capabilities

he jsdc_SC.conf and the jaarc.conf files are similar, but you cannot put qualifiers (i.e. not equal) in the jsdc_SC.conf. Therefore, the SDC cannot be filtered with the same granularity as the AAR. Taiwan would like to be able to exclude supply cat damage and crewman damaged in the SDC as in the AAR “AAR_ENGAGEMENT_SURFACE_ITEM”. Developer Note: It is true the SDC only allows table level filtering. As for the AAR we have never done timing tests to determine if the penalty for filtering is worth it, especially since disk space, which is what a database is, is so cheap. If the issue is that the SDC is having a hard time keeping up with the game, we recommend a separate SDC for each force side. This allows inserts to be handled in parallel by Postgres w/o us spending the resources attempting to parallel process the SDC. Regardless their request is an ECP and I have changed the priority to such.
MCR: JTLS-2026-17754
Date: 2026-06-02
Status: Accepted
ModelWant Withdraw Order Option - Do Not Destroy Targets

A withdrawing unit destroyed same-side supply storage targets along its route because there were no friendly units nearby. See routines DESTROY.CACHE.ON.LEAVING which calls IS.TARGET.SAFE. There were no enemy units nearby either. Losing all those storage targets upset the players. Taiwan wants us to make this an option on the Withdrawal Order
MCR: JTLS-2026-17753
Date: 2026-06-02
Status: Accepted
ModelAlter Naval Unit Strength Computation

The OPFOR perceives a DEFOR (blue) ship as 69% strength, which is accurate. The icon on the OPFOR map has a partial yellow displayed. The DEFOR map has the ship entirely blue. Why the difference? The JODA shows 69% for both the OPFOR and DEFOR sides. The ship is not damaged; it is short personnel combat systems on purpose. I can’t find the CEP parameter(s) that determine how much yellow to display. In the JSYSMS, the symbol thresholds are 100%, 85%, 60%, 35%, 15%, and 0%. This came up because the Director wants to know why the OPFOR can detect that the DEFOR ships are 69% due to missing crew. I know the DEFOR ships have been continuously detected since StartEx (over 48 hours ago), so they have almost real-time intel and total identification. I know that’s the way the model works, but is hard to justify the OPFOR being able to determine the ship is 69% only because the ship doesn’t have a full personnel complement. Perhaps we should reconsider how foreign ship strength is reported when a detected ship is undamaged and is simply short on personnel? Possible ECP. Perception of foreign vessel strength should not include personnel combat systems.
MCR: JTLS-2026-17735
Date: 2026-05-13
Status: Accepted
ModelJTLS-GO Needs Ability To Change Federation Unit Data

Every unit in the game can start out in one of three federation owners: ->JTLS_ONLY ->JTLS ->External Model, such as MUSE GESI, VBS4, or JCATS. Currently only the MUSE External Federate is actively being used. Once the scenario starts, there is no way to alter the Federation Owner setting. This needs to be implemented because during exercises situations changes and the Federation Owner needs to change.
MCR: JTLS-2026-17647
Date: 2026-03-23
Status: Accepted
DatabaseGroup Join of Networks

I am currently working with railroad networks within JTLS-GO and have encountered a limitation when attempting to join network elements. At present, we are required to manually select each individual rail name when performing joins, which can be quite time-consuming and inefficient, particularly when working with larger datasets. I wanted to inquire whether it would be possible to implement a feature similar to those available in other tables, where a group join option is available. Having the ability to join multiple rail elements at once would significantly improve workflow efficiency and usability.
MCR: JTLS-2026-17646
Date: 2026-03-25
Status: In Work
ModelCannot Change Port Location For Port Task

If there is an existing Enter Port Task, the user cannot alter the location at which the ship should travel to enter port. The only option is to cancel the Port Task and resubmit the task with a new location. The desire is to allow the suer to change the location of the port task instead of going through the cancellation process.
MCR: JTLS-2026-17625
Date: 2026-03-14
Status: Accepted
C4IHave Dashboard Track ELS Too

In order to monitor all of the JTLS simulations (CEP an ELS), it is essential that the DASHBOARD service include an option to display the game status and speed of the ELS (through the EODA). Currently the Dashboard only displays the state of the CEP. Also adding an 'uptime' to the ELS and CEP would be nice. Adding the ability to monitor multiple games would also be desirable.
MCR: JTLS-2026-17624
Date: 2026-03-13
Status: Accepted
ModelAllow JTLS Air Missions To Shadow MUSE Missions

A situation occurred where there was an air mission being flown in JTLS, and a similar mission was being flown in MUSE. Both missions are on the same force side. It would be useful if one mission could shadow/follow the other mission. This would result in both missions staying close together in location. No combat would be involved. Developer Note: This situation seems very specific. When implementing consider more robust generic capability. No need for Same Side missions. We can only be concerned about JTLS shadowing MUSE missions.
MCR: JTLS-2026-17621
Date: 2026-03-13
Status: Accepted
WHIPACM Shape Colors by Usage

Currently, players can set individual ACM colors using the Modify ACM order, but not all ACMs of a specified shape or usage can be set en masse. Also, the color selection in the ATOT is set by ACM shape only (e.g. all polygons are yellow). Players would would like the capability to set color by ACM usage or by shape. For example, all AAR shapes set to yellow, independent of the shape type. The ATOT would also have to incorporate that capability.
MCR: JTLS-2026-17619
Date: 2026-03-13
Status: Accepted
ModelAdd System Start Time To OEX File

Suggestion from Donna during KE26 - Suggest adding a line to the OEX file to hold the local time and date when the CEP was started or restarted. This will help tech control to anticipate when the model will be up and ready to accept orders and begin time advancement.
MCR: JTLS-2026-17618
Date: 2026-03-13
Status: Accepted
ModelELS IMT Display From EODA

Develop an IMT-like viewer to display the ELS data for external missions (and possibly other objects) and their associated combat system entities. This IMT like viewer would be connected to the EODA. Developer Note: This could possibly be linked to the entity level WHIP that displays the location of entities as shown held by the EODA.
MCR: JTLS-2026-17617
Date: 2026-03-13
Status: Accepted
ModelELS More Control Over Entity Publication

Allow the user to Turn Off publication of some entity-level objects by type (e.g. convoys, HRU, certain missions, etc).
MCR: JTLS-2026-17616
Date: 2026-03-13
Status: Accepted
ModelELS Checkpoint Selection

Enter a description to allow the ELS Checkpoint Number to be specified when the ELS is restarted. This can get the ELS closer to the current game time than starting from time zero. It currently uses the same checkpoint from which the CEP was last started.
MCR: JTLS-2026-17611
Date: 2026-03-10
Status: In Work
ModelFix Support Unit Truck Counts

The IMT shows the number of Tanker Trucks and Cargo trucks owned by a Support unit. There are several issues with these counts that cannot be fixed unless a JDSP change is made. These problems are: ->The number of HETs owned by a support unit is not tracked. ->The counts assume that the Support Unit has only one type of each truck type. This is no longer true. Support units can own and use several types of Cargo, Tanker, and HET trucks. This needs to be fixed.
MCR: JTLS-2026-17525
Date: 2026-02-02
Status: Accepted
ToolsICP WHIP Tab Needs Search Capability

For a recent large exercise, there were over 700 WHIPs defined. There is no way to search for a specific WHIP other than scrolling through the WHIP list.
MCR: JTLS-2026-17524
Date: 2026-02-02
Status: Accepted
C4ICount Of TACELINT Messages Sent

For exercises we are often limited by the number of TACELINT messages that can be sent in a day. We can dial the frequency of TACELINT messages that go out to adjust if the service is sending the messages out too fast. To make this decision, the service should be able to tell Technical Control the number of messages that have been sent out since midnight or something similar.
MCR: JTLS-2026-17523
Date: 2026-02-02
Status: Accepted
WHIPAllow Entry Of Polygons Via Keyboard

Currently the only way you can enter a Polygon field on an order is by drawing the polygon on the map. The users need an accurate manual method by typing in the latitude and longitude information. This suggestion was first submitted for the ACM order, but should be implemented for all Polygon fields.
MCR: JTLS-2026-17522
Date: 2026-02-02
Status: Accepted
WHIPIMTOPM Links From IMT Tables

Direct Access to OPM data pages from some of the IMT screens would be very useful instead of having to submit a Controller order to show data. For example: -> Aircraft Class data from the Squadron or Air Mission IMT screen -> Prototype data from the numerous unit IMT screen.s
MCR: JTLS-2025-17510
Date: 2025-12-31
Status: Accepted
ModelAirTwo New ATOT Summary Table Functions

From the ATOT Mission Summary Page, JWC would like two additional functions: Allow User To Mark A Mission As Do Not Include ->Only Method Currently Available Are Time Intensive ->->Delete Mission From ATO File ->->Delete Missions From Order Groups Allow User To Change Mission To Alert Mission ->Ignore All Of the Instructions In The ATO File
MCR: JTLS-2025-17509
Date: 2025-12-31
Status: Accepted
ModelNavyAllow Single Ship Formation To Accept Naval Shadow Order

The Formation requirement exists so the ship can embark a unit or carry supplies as part of a sealift. More information is needed why this is needed. Just need to confirm this is what they want for the replenish naval unit order.
MCR: JTLS-2025-17508
Date: 2025-12-31
Status: Accepted
ModelNavyAdd Delete All Tasks To Naval Move And Naval Patrol Order

JWC wants a Delete All Task field on Naval Move and Naval Patrol Order.
MCR: JTLS-2025-17507
Date: 2025-12-31
Status: Accepted
ModelAirIMT Quick Change Altitude Order

Users want a Quick Change Altitude Order for air missions
MCR: JTLS-2025-17506
Date: 2025-12-31
Status: Accepted
ModelAirACM Route Creation Improvement

JWC / ICC Use ACMs With Multiple Points These Points Are Numbers 1, 2, 3, … ICC Says Get On ACM Alpha At Point 5, Get Off At Point 12 Our Order Does Not Use Point Numbers – It Uses Locations Of Point Numbers It Was Done This Way To Be More Universally Acceptable To US INDOPACOM JWC Wants The Order To Refer To Point Numbers Not Locations
MCR: JTLS-2025-17505
Date: 2025-12-31
Status: Accepted
DatabaseDDSAbility To Remotely Stop DDSC Similar To WHIP Capability

There is currently no way to find or stop a user's DDSC.
MCR: JTLS-2025-17411
Date: 2025-10-06
Status: In Work
DatabaseDDS Selection by RIC

Allow user to select a CS by RIC as well. If we want to insert a new TUP (SUP-HUP) by knowing the RIC, we have to filter CS table by RIC and then copy the name of the CS and insert it in the TUP CS table. By allowing a user to insert a CS by typing the RIC it will make the process easier, without opening multiple tables. Same concept might be applied to POT but this is probably more demanding (pre filter by Target type).
MCR: JTLS-2025-17410
Date: 2025-10-06
Status: In Work
DatabaseDDS Prototype Selection

The DDS user wants to change the prototype of multiple units to a given prototype. To do this they use the multiple record “Set Value” capability. They: • Highlight the records that should be changed, • Go to the column header for the data parameter that should be changed, in this case the Prototype column • Right Click and select the “Set Value” option. • This presents a drop-down list of all Tactical Unit Prototypes. There is no way to type in the prototype name to “cull” or “whittle” down the list. You must scroll through the extremely long list looking for the one prototype you need. This is difficult and time consuming. This Multi-Record Set Value Drop-Down list should work exactly like the list works when you go to the unit’s individual prototype cell. You start typing in the name of the desired prototype and the drop-down list opens, and the list is whittled down shows only the TUPs that start with the letters being typed. This will make it easy for them to find and select the prototype they you want. This should be a “general” capability – and not limited to just the Unit Prototype Multi-Record Set Value function. All Multi-Record Set Value Drop Down lists should work this way.
MCR: JTLS-2025-17409
Date: 2025-10-06
Status: Accepted
DatabaseAPP6 Symbols in JDSP

Alter the JSYMS program to have two Graphics Symbol identifiers, one for 2525 and one for APP6. The two symbol identifiers will be placed in the JSYMS save files and will be read in by the model. Every unit will have two JODA attributes for their symbol identifier, one indicating the unit’s 2525 Symbol identifier and one for the unit’s APP4 identifier. These same two attributes will be represented in the SDR database. The model takes the baseline identifiers created within JSYMS and adds information such as echelon and country code. Currently the Country Code format that should be used is hard-coded within the CEP. This will change and become two database parameters, “2525 Country Code Type” and “APP6 Country Code Type”. The published unit identifiers will use the Country Code specified in the database. Currently JTLS-GO does not use the Graphics Symbol identifiers. They are provided to support the interface between JTLS-GO and various C4I systems. The only C4I Interface Program that uses the identifier is Land Command and Control Information Service (LC2IS), which we have been told will no longer be supported. Updating LC2IS Message Service is not expected to be a significant change and will be accomplished under this FMR if there is a need to do so. he proposal or issue here.
MCR: JTLS-2025-17408
Date: 2025-10-06
Status: In Work
DatabaseCAP Codes in Database

Prototypes express a specific capability. In NATO we have CAP codes list. Such a list is updated yearly. Every prototype can be assigned multiple cap codes (like CS). In JWC repository capabilities are nowadays recorded as a Comment field. This is making the update mechanism extremely complex.
MCR: JTLS-2025-17390
Date: 2025-09-17
Status: Accepted
ToolsAllow Political Country Region Filtering

Both the WHIP IMTs and the DDSC Tables have the ability to filter by geographic regions that are definable by the users. The JTLS-GO database has the geographic Regions defined by the represented Pollical Countries. The desire is to allow the user to filter on the Political Country regions.
MCR: JTLS-2025-17358
Date: 2025-09-02
Status: In Work
DatabaseDDS Combat System Access For Units

User should be able to access a specific unit's prototype (and possibly the prototype CS) from the unit table. Similar functionality as user has today for unit owned targets.
MCR: JTLS-2025-17357
Date: 2025-09-02
Status: In Work
WHIPCommand Hierarchy Name Alias Support

User should be able to visualize (and search) for units in the ORBAT window using both short name and C4i name or both (visualize both values). Developer note: Should it be limtied to those two names or all anes that a unit can have, Short name, long name, UIC, C4I Name.
MCR: JTLS-2025-17356
Date: 2025-09-02
Status: In Work
ToolsMake Classification Available In JDSP

Although Classification was recently added to the JDSP Simulation State Object, it is currently not fully implemented across all JTLS-GO Tools and Programs. This ECP is designed to fully implement the change so the controller can simply change game classification and all program that need game classification will obtain that information from the JODA data structure or the SDC as appropriate.
MCR: JTLS-2025-17355
Date: 2025-09-02
Status: In Work
ModelIntelHandle Large DSAs

In our work to improve our use of satellite functionalities, we have identified an issue with the current collection method using DSA. We need to be able to utilize collections in bigger areas than 10000 sqkm. Our proposal is to introduce a new order for collection interests specifically tied to satellite collection.
MCR: JTLS-2025-17268
Date: 2025-07-19
Status: Accepted
ModelRepresent AirFish Drne

The AirFish Drone is a Wing-In-Ground (WIG) Aircraft that creates an air cushion allowing the aircraft to fly low over water. Its characteristics need to be better integrated with a wide variety of other aircraft capabilities that JTLS-GO currently cannot represent. ->Float Planes, like the AirFish, which must take off and land in water ->Fixed Wing Aircraft that do not need a runway. They are launched from a catapult type system and parachute back to the ground. ->Look at the "Loyal Wingman" drone concept. The entire concept of equating: ->Fixed Wing with runway takeoff and landing requirement and fast ->Rotary with no runway requirement and slow is no longer working for everything.
MCR: JTLS-2025-17200
Date: 2025-05-27
Status: Accepted
ModelAutomatically Load Breakpoint File

Some users do not allow changes to be made to code during an exercise. Instead, model experts must develop ways to catch cashes before they happen and develop work arounds. This normally means setting a breakpoint in the code prior to bad code being executed. Some exercises can have 10 or 20 breakpoints. If the model is restarted and the breakpoint file is not submitted to the model, it is bound to crash again when already deleted errors occur again. The desire is for tje breakpoint file to be loaded automatically. Technically I don't have a clue of how to implement this.
MCR: JTLS-2025-17198
Date: 2025-05-27
Status: Accepted
ToolsRefresh Of CEP Start Panel

User would like a Refresh button on the CEP start Panel. This user leaves the CEP Start Panel open at all times and it doesn't know about new checkpoints as they are created. Instead of closing the panel and reopening the panel, they user wants a refresh button
MCR: JTLS-2025-17197
Date: 2025-05-27
Status: Accepted
ToolsCreate Automated Synchronization Tool

User wants a tool to automatically synchronize game time to real time is we are coming up from a crash or fall behind for any other reason.
MCR: JTLS-2025-17196
Date: 2025-05-27
Status: Accepted
WHIPDesire To Have Multiple WHIP Layouts

Currently you can have only one WHIP layout. The user wants named layouts similar to the Filter and views.
MCR: JTLS-2025-17195
Date: 2025-05-27
Status: Accepted
ModelAirNeed Current Manual Pair Flag On IMT

The current manual pair flag should be on the IMT.
MCR: JTLS-2025-17194
Date: 2025-05-15
Status: Accepted
WHIPAllow User Selection Of E-mail Output Format

Code exists to format e-mail output of IMT screens as either plain text with columns separated by a bar ("|"), plain text with data quoted and columns separated by a comma, plain text with columns separated by tabs, or data embedded in an HTML table. Despite the various output formats available, the code is hard- coded to a single format. It would be desirable for the end user to specify which output format they desire.
MCR: JTLS-2025-17193
Date: 2025-06-04
Status: Accepted
ModelLogProvide Capability To Select Exact Types Of Truck In A Convoy

The desire is to expland the Directed Resupply Order to allow the user to indicate exactly what trucks by type and number that should be assigned to the convoy.
MCR: JTLS-2025-17192
Date: 2025-05-15
Status: Accepted
ModelIntelAAR Collect All DSA Data

Currently the AAR does not get the detection data for Combat Systems and wreckage seen in DSAs. A detection event is sent to the AAR via 2 JDSP objects: an AAR_DETECTION_EVENT identifies the object doing the detection, the sensor, the DSA searched if a DSA is involved, etc; a series of AAR_DETECTION_ITEMS identify each item detected, their location, and their percent capable. This provides only the most basic detection information and does not provide the detailed information expected in a DSA report including numbers and types of combat systems, wreckage, etc.
MCR: JTLS-2025-17146
Date: 2025-04-28
Status: Accepted
ModelRepresent Impact of Jammer Altitude On Jamming Power

Currently the altitude of a jammer on an aircraft or satellite is not considered as part of the jammer power degradation. The end user believes it should.
MCR: JTLS-2025-17145
Date: 2025-04-28
Status: Accepted
ModelPlayer Orde rTo Transfer SAM/AAA TArget Supplies

The players want to take supplies from a SAM/AAA target and give those suppli9es to someone else. The controller can do this from the SET TARGET PARAMETER order followed by a LOGIN BUILD order to another unit. Taiwan believes this capability should be available to the player. They don’t want the magic movement of the supplies, just the ability to take supplies away from one owned target with the Directed Resupply order and take those supplies to a different unit.
MCR: JTLS-2025-17144
Date: 2025-04-28
Status: Accepted
WHIPOrder Map Selection For Barriers.

Users have requested that a map select capability be added to Barrier fields within order panels.
MCR: JTLS-2025-17143
Date: 2025-04-28
Status: Accepted
ModelRepresent Artillery Firing Limitations

Tech Control is discussing what can be done to stop the users from putting in so many explicit fire missions. The players are not comfortable with Lanchester. One idea is to add a max number of rounds that can be fired in an hour from a gun before is gets “too” hot to be used properly.
MCR: JTLS-2025-17142
Date: 2025-04-28
Status: Accepted
ToolsNew Air Defense AAR Report

Taiwan would like a new AAR Air Defense report that lists Air Defense kills broken out by type of Air Defense Site firing and type of Aircraft kill.