Universal Combat: Collector's Edition - Patch v1.00.08

12.08.2008 - Sören Lohse

Download

• File 1:

  ucce_1.00.08.exe

  Grösse:

  27.0 MB

  

Beschreibung

Es gibt einen neuen Patch zur Collector's Edition von Universal Combat, die das Spiel auf Version 1.00.08 aktualisiert.

Changelog:

 1. Compiled with latest FMODex (4.16.08) audio SDK.

General

1. Increased player run and walk movement speeds
2. Changed player walk sound to softer version

Multiplayer

FIXED: Clients reporting different time of day after docking and launching from starbase To resolve this, time no longer elapses when you dock with or launch from a starbase/starstation
FIXED: Issue with airborne (gunships, fighters etc) dynamic objects moving on server
FIXED: Minor revision which seems to have fixed duplicate dynamic (e.g. vehicles) objects when player interacts with them. NOTE: This has nothing to do with each client having a copy of a dynamic object.
FIXED: Client no longer starts inside the scripted starbase object
FIXED: Problem controlling ground vehicles due to position updates.
FIXED: dynamic objects with no previous position information (e.g. objects created by 3DG files or scripted) were not being rendered. This caused the issues with "ghosting" in which the object TTDs were visible but not rendered as well as cases where they appeared below the terrain height.
All ground units in a scene now have their dynamics and tactical state disabled. This prevents them from moving around, doing target acquisition etc and saves on processing.
Restored all player controlled vehicle units to the .3DG scene files
Removed test script which had scripted units in it. This turned out to be a bad solution due to clients having own copies of these objects.
FIXED: Scripted starbase units now appear in the scene so that you can dock with them. There is a slight caveat with this. See above.
Removed all player controlled units from .3DG scene files
Added [test] scripted player controlled units to PROCON/PROCON SB01. This is a test as an alternative to having them in the .3DG scene file and being handled incorrectly by the server.