SEOW installation

[OBT~karl]

I am continuing my investigations, the error could be due to the fact that I did not check the box below in DCS?
because I managed to get the statistics.

pb1.JPG (29.13 KiB) Viewed 285 times

pb2.JPG (99.51 KiB) Viewed 285 times

[IV/JG7_4Shades]

No that's not it.

I have found the bug, and it is my fault. Apologies! After code patching, the DCS front page should look like this for you BEFORE you initialise this type of campaign:



Note the "Initialization Mode" and "Meta-Campaign Mode" settings in blue. These are the controlling parameters that were not handled correctly by the older DCS. When your DCS auto-updates you will see improved formatting (as in the picture above) and there is improved parameter logic behind the scenes.

Now the explanation of the Analyze problems. Because of the DCS formatting bug your campaign was in "Ground Focus" meta-campaign mode, which meant that it was ignoring your IL2 eventlog completely. You couldn't really see that because the DCS didn't show the options available. That should be fixed now in v8.1.0.22.

What to do with your current campaign. Take the following steps:

1. Edit your Campaign_Settings table using phpmyadmin and set the parameters "Initialization_Mode" = 0 and "Meta_Mode" = 0. These values are down at the right-hand end of the long line of settings parameters.
2. In your IL2/HSFX folder rename your eventlog_SE-ardennes-194012150900.lst file to eventlog.lst, i.e. the original logfile after flying the mission.
3. Start up your DCS and let it update to v8.1.0.22. When it starts you should see the settings similar to the picture above (if you have changed the parameter values successfully). This matches your chosen campaign style of "Air Focus: only IL-2, conventional SEOW", and initialized using Standard template mode.
4. Tools/Undo your last Analyze stage. This sets the database to post-Build state, ready to Analyze.
5. Push the Analyze button. This will redo the analysis and hopefully everything should be fine after that.

I tried this with your DB, flying a flight of Bostons to bomb howitzers near a bridge. We hit the target, and the subsequent Analysis and Statistics worked fine.

Cheers,
4S

[OBT~karl]

I updated DCS this morning, so that's why it worked. Thanks for your explanation and follow-up.

[OBT~karl]

I'm giving orders for the 2nd mission, I gave orders to the allies then to the axis and I want to go back to the allies but I have this message. What is it about?, please
I hope you're in good shape, because the questions aren't over yet...

p3.jpg (76.19 KiB) Viewed 201 times

[IV/JG7_4Shades]

The easiest way to find that problem is for you to send me your DB again.

[OBT~karl]

Here is the link for the problematic database
http://gofile.me/6vJ1a/uzDOsn4u3

[IV/JG7_4Shades]

OK, this is amusing. A simple error in the Airforce_Units table.

By default there are two New Zealand air regiments defined for the Ardennes sector, as follows:

Code: Select all

NewZealand	24FSquadron	24 (F) Squadron RNZAF	PFI	Allied	rz	Ardennes	0
NewZealand	25DBSquadron	25 (DB) Squadron RNZAF	PDB	Allied	rz	Ardennes	0

These two records should have a space character in "New Zealand", as follows:

Code: Select all

New Zealand	24FSquadron	24 (F) Squadron RNZAF	PFI	Allied	rz	Ardennes	0
New Zealand	25DBSquadron	25 (DB) Squadron RNZAF	PDB	Allied	rz	Ardennes	0

You can edit your Airforce_Units table to make these 2 simple changes. That should fix things for you. I have made this change in my own development DB so it should be fixed for the next DB release.

Cheers,
4S

[OBT~karl]

Merci!