Galactic Command Echo Squad SE v2.10.06 Patch

GALACTIC COMMAND - ECHO SQUAD SE VERSION CONTROL
Revised: 04-09-08

REPORTED ISSUES UNDER INVESTIGATION
Attempting to change X-45 joystick buttons in CONFIG results in the game not recognizing the new input and appears to have hung. It probably actually hung, but is still awaiting input.
STATUS: We still cannot reproduce this on our end.

R&D ROADMAP FOR [POSSIBLE] IMPLEMENTATION
Enable use of left mouse click in 3D cockpit MFDs. This would require some major hacking and revisions to various input handlers. The idea is to be able to left click on any of the MFD modes (the Red status boxes at the bottom) and be able to switch to that mode without use of the keyboard (. and ,).
WOT?: We attempted this before, but abandoned it due to the complexities involved due to the cockpit being a full 3D model which has X/Y/Z co-ordinates. So, we're currently researching this again to see if there is any feasible way of doing it. There is a reason why most games like this don't do clickable cockpits (assuming they even have such a thing) when said cockpit is a 3D model.

STATUS: PENDING

Need a more robust error detection system in the event that the creation of a buffer fails due to lack of VRAM. This way the game can employ an adequate fallback instead of crashing or exiting.
WOT?: In some cases, using high value FSAA values would later result in a crash due to insufficient video memory. Due to the large amount of runtime FP16 surfaces, Config has no way of knowing how much VRAM is later needed for the currently selected screen resolution. e.g. selecting 8x or higher FSAA while running the game at 1280x960 will most definitely result in out of memory anomalies (screen tearing, missing textures etc) and a possibly flat out crash.

STATUS: PENDING

[MP]Better terrain object delegation by the server.
WOT?: This would solve a few nagging (but un-seen to gamers) issues which otherwise put the burden on the client, rather than the server.

STATUS: WIP

[MP]Revise handling of terrain object positioning in TACOPS.
WOT?:When viewing a planet in TACOPS, the objects seem to be slightly off the ground, though they are correct when you visit the location by flying there. This is due to how TACOPS handles the position of terrain objects.

STATUS: PENDING

[MP]Implement Bezier Curves on position updates
WOT?: Will make updates even smoother than they are now. Most especially useful for Internet play

STATUS: PENDING

v2.10.06 (04-09-08)
Added violations (VIO) info to the cockpit HUD.
Added medals count to the orders display
Added campaign theatre info to the cockpit HUD. This gives an at-a-glance look at the scenario timers without having to use the VDD/ACM mode.
T - Theatre
S - Start time
E - End time
N - Next scenario start time

Added native support for 1280x800 and 1920x1200 16:10 widescreen display modes.
NOTE:This will delete your configuration file, thus creating a new default one. So be sure to set your Config options again.
Increased the minimum docking range from 1km to 10km
Increased Commlink log size delete prompt from 32K to 1MB
Changed COMMAND menu save game texts to: "QUIT & SAVE WITH RESUME" and "QUIT & SAVE WITH RESTORE"
Time will no longer have passed when you dock and re-launch.
When you dock (to perform repairs, re-arm etc) the world is still being updated. So if the total repairs time is, e.g. 30 mins, when you launch, that amount of time would have elapsed. In some cases, if you had a lot of repairs and you dock towards the end of the current scenario operations, when you launch you may find that the next scenario is already in progress. You can still check for orders you may have missed, but there is a possibility that you may also miss some specific instructions which could get you taken off active duty eventually.
With this revision, even though the elapsed time is still calculated, this time is no longer elapsed when you launch. So if you dock at 21:00, when you launch, the time would be closer to 21:01 than 21:30 (assuming the repairs/rearming took thirty minutes).

In effect, we're just dumbing down the game even further because normally, due to the game's real-time processing nature, this behaviour is normal and thats how the game engine was developed to behave.

The ability to select component repairs stats in Logistix has been disabled.
This used to occur when you click on a fighter component as this calls up the engineering work order. This is part of our underlying game engine that is not needed in the GALCOM due to the singular REPAIRS button which does a batch repair job in a single click and saves time (so you don't have to select each damaged component to repair). Normally, in order to save on repair time (see above), you would just pick the most important components to repair, then launch. This would minimize the time you spent docked and thus ensures that you don't miss much of the on-going fleet operations due to time passing.
FIXED: When using the mouse as the flight controller, axes were swapped if you also had a joystick plugged in and joystick swap roll/yaw was enabled in Config
FIXED: When you dock, the REPAIRS button is not active once the current date/time has been calculated and displayed. You have to switch to WEAPONS, then switch back and click the button before the date/time is displayed.
FIXED: Some minor widescreen (mostly) text display issues in various areas.