New Release: SEDCS v3.3.0, SEDB33A, MP4 v4.75x
Posted: Tue 12 Apr 2011 10:35 am
Hi everyone,
After much endeavour by the SEOW team, we are about to issue the new release of the SEOW system, which is compliant with TD v4.10.1 and with HSFX v5.0.1. There is much new functionality that is directed to supporting the realistic climatic, radio and navigation features in TD v4.10.1, plus a lot of HSFX v5.0.1 event logging and ground war logic.
Before the full release is issued (to be reported later in this thread) I will present a summary of the significant SEDB structural changes, and also a note on a migration of the DCS library environment.
1. SEDB33A Structural and Data Changes
The following structural changes have been made:
AircraftLoadout
HSFX_Loadout <- new field
Campaign_Settings
Coop_Mod_Slot <- new field
Coop_Mod_Slot <- new table
Destruction_Targets
Windsock_Strong <- new field
Windsock_Medium <- new field
Windsock_Light <- new field
Factory_District_Large <- new field
Factory_District_Medium <- new field
Factory_District_Small <- new field
Factory_Partial <- new field
Destruction_Targets_HSFX <- new table
GroupMissionData
Default_Ord_Verbose <- new field
Industrial_Installations
Damage_Level <- new field
Sector_Climate
Wind_Speed_Max <- new field
Wind_Gust_Max <- new field
Wind_Turbulence_Max <- new field
Mean_SL_Temperature <- new field
Mean_Declination <- new field
Mean_SL_Pressure <- new field
Sector_Weather
Actual_WindSpeed <- new field
Actual_WindDirection <- new field
Actual_WindGust <- new field
Actual_WindTurbulence <- new field
Axis_WindSpeed <- new field
Axis_WindDirection <- new field
Axis_WindGust <- new field
Axis_WindTurbulence <- new field
Allied_WindSpeed <- new field
Allied_WindDirection <- new field
Allied_WindGust <- new field
Allied_WindTurbulence <- new field
and
The Axis/Allied 6hr and 24hr Outlook fields need to have length 255.
The following tables have changes to their data loads:
Airbase_Layouts
Airbases
AircraftLoadout (complete revision)
Airforce_Units (complete revision)
Bridges
Campaign_Settings
Convoys_Vehicles
Destruction_Targets
Flags
Highway_Intersections
Highways
Industrial_Installations
Object_Costs
Object_Roles
Object_Specifications
Radar_Maps
Railway_Intersections
Railway_Stations
Railway_Waypoints
Resupply_Points
Route_Blockages
Sector_Climate
Sector_Dominance
Sector_Movement_Cost
Sector_Recon_Parameters
Sector_Seasons
Sector_Weather
Tile_Map_Codes
2. SEDCS v3.3.0 Library Change
The DCS application has been built from .NET Framework 1.0, 1.1, 2.0 library calls for many years, using VB .NET Visual Studio Express 2003, 2005, 2007 versions. This has changed. For v3.3 the development IDE has been updated to Visual Basic 2010 Express, and the development library is .NET Framework 4.0. All other references remain unchanged (e.g. MyODBC v3.51.x). This .NET change means that systems where SEDCS v3.3.0 will be deployed will likely require .NET Framework 4.0 to be installed and patched. On my XP32 development machine, the new DCS works fine with MySQL and MS Access database variants.
Note that the full DCS source code project (VB 2010 Express) is now downloadable from the SEOW CVS tree.
Not long to wait now!
Cheers,
4Shades
After much endeavour by the SEOW team, we are about to issue the new release of the SEOW system, which is compliant with TD v4.10.1 and with HSFX v5.0.1. There is much new functionality that is directed to supporting the realistic climatic, radio and navigation features in TD v4.10.1, plus a lot of HSFX v5.0.1 event logging and ground war logic.
Before the full release is issued (to be reported later in this thread) I will present a summary of the significant SEDB structural changes, and also a note on a migration of the DCS library environment.
1. SEDB33A Structural and Data Changes
The following structural changes have been made:
AircraftLoadout
HSFX_Loadout <- new field
Campaign_Settings
Coop_Mod_Slot <- new field
Coop_Mod_Slot <- new table
Destruction_Targets
Windsock_Strong <- new field
Windsock_Medium <- new field
Windsock_Light <- new field
Factory_District_Large <- new field
Factory_District_Medium <- new field
Factory_District_Small <- new field
Factory_Partial <- new field
Destruction_Targets_HSFX <- new table
GroupMissionData
Default_Ord_Verbose <- new field
Industrial_Installations
Damage_Level <- new field
Sector_Climate
Wind_Speed_Max <- new field
Wind_Gust_Max <- new field
Wind_Turbulence_Max <- new field
Mean_SL_Temperature <- new field
Mean_Declination <- new field
Mean_SL_Pressure <- new field
Sector_Weather
Actual_WindSpeed <- new field
Actual_WindDirection <- new field
Actual_WindGust <- new field
Actual_WindTurbulence <- new field
Axis_WindSpeed <- new field
Axis_WindDirection <- new field
Axis_WindGust <- new field
Axis_WindTurbulence <- new field
Allied_WindSpeed <- new field
Allied_WindDirection <- new field
Allied_WindGust <- new field
Allied_WindTurbulence <- new field
and
The Axis/Allied 6hr and 24hr Outlook fields need to have length 255.
The following tables have changes to their data loads:
Airbase_Layouts
Airbases
AircraftLoadout (complete revision)
Airforce_Units (complete revision)
Bridges
Campaign_Settings
Convoys_Vehicles
Destruction_Targets
Flags
Highway_Intersections
Highways
Industrial_Installations
Object_Costs
Object_Roles
Object_Specifications
Radar_Maps
Railway_Intersections
Railway_Stations
Railway_Waypoints
Resupply_Points
Route_Blockages
Sector_Climate
Sector_Dominance
Sector_Movement_Cost
Sector_Recon_Parameters
Sector_Seasons
Sector_Weather
Tile_Map_Codes
2. SEDCS v3.3.0 Library Change
The DCS application has been built from .NET Framework 1.0, 1.1, 2.0 library calls for many years, using VB .NET Visual Studio Express 2003, 2005, 2007 versions. This has changed. For v3.3 the development IDE has been updated to Visual Basic 2010 Express, and the development library is .NET Framework 4.0. All other references remain unchanged (e.g. MyODBC v3.51.x). This .NET change means that systems where SEDCS v3.3.0 will be deployed will likely require .NET Framework 4.0 to be installed and patched. On my XP32 development machine, the new DCS works fine with MySQL and MS Access database variants.
Note that the full DCS source code project (VB 2010 Express) is now downloadable from the SEOW CVS tree.
Not long to wait now!
Cheers,
4Shades