Official SEOW

All bug reports for SEOW v6.0 to be posted in this thread please.

1st of all big "Horrido!" to the release.

Then I found a minor "bug":
In the costs table the Sd.Kfz. 231; 234/1 and 234/2 "Puma" is missing.

Hi Emil,

THey are definitely in SEDB60, but they are listed as HSFX objects. Maybe you need to enable HSFX Mods in the DCS/DB to see them on the Costs page?

While checking this I noticed that some other little things slipped through. Here is some SQL to correct things. The Littorio has been removed from HSFX, and the new Leopold gun did not have a movement parameter enabled for it.
Cheers,
4Shades

Thank you for the sql-command.

I know that there were a lot of changes but why would the SEDCS think infantry were artillery? In the mission planner they are labeled stationary infantry.


SEDCS::Unknown Stationary unit type: vehicles.artillery.Artillery$GBInfantry. Check template compatibility with your HistorySFX Mod setting in the "Campaign Modes" tab.
The database will be flushed now.

Hi Zoi,

Because they are implemented using the java Artillery class inside HSFX.

Your error message probably indicates a bug, please send me your template file and I'll check.

Cheers,
4S

Thanks Zoi,

Yes, it is a bug in SEDB60. Basically I set up the infantry units top that they are always entrenched when stationary but this has the unintended side effect of making it hard for the DCS to detect an unentrenched unit that may appear in the template file.

There are a couple of fix options here.

1. Always use entrenched infantry in the template. You can covert your template file by changing all occurrences of "vehicles.artillery.Artillery$GBInfantry" to "vehicles.artillery.Artillery$GBInfantryE", and similarly for other infantry nations.

2. Alter the "Stationary" forms of infantry in Object_Specifications to remove the trailing "E" for non-entrenched forms, then re-initialize.

I will release a DCS patch soon that will handle this more gracefully.

Cheers,
4S

I wish I could figure these things out for myself

Thanks Shades!

Static Cameras lose their affiliation when placed my SEDCS. Would it be ok to correct this in the mission builder or a text editor before each mission?

Not sure if this a bug but in my test it showed up.

SEDCS::modMissionAnalyzer.isCombinedUnit: 5 Key cannot be null.
Parameter name: key
Error : 5
Description : Key cannot be null.
Parameter name: key

Entrenched Infantry variants
DCS 6.0.2 handles this transparently.

Static cameras with national alignments
DCS 6.0.2 handles this transparently, but the following DB table structure change is required:

The Cameras table needs to have another column added, called "Alignment". The following MySQL command will do the job:
If this fix is not made, error messages may occur when SEDCS v6.0.2 is run.

Error SEDCS::modMissionAnalyzer.isCombinedUnit: 5 Key cannot be null.
In Zoi's example he was employing sirens as scenery objects which is unusual but permissible. DCS 6.0.2 handles this case transparently.

Cheers,
4Shades

I love the fast service, what did you say you were charging again

Thanks Shades

New feature: Overwhelming Forces.

Cheers,
4Shades

Brilliant.

The Devill made me do it.