Official SEOW

Hi all

Something strange is happening with the TFs in the SEOW Mediterranean that we are flying with Starfire as admin.

The problem is sometimes that they are, sometime they aren't. Last mission I had my TFs ready and moving, now they don't exist anymore. This has been happening for 4 or 5 missions now. Probably next mission they will appear from nowhere again, without me creating then again.

In fact, if I try to create one with the same name as one of the missing ones, planner says that name is already taken. If I create one with a different name it goes ok, but it does not appear on planner.

So it's like they are there but do not appear on planner and can't be given orders. One mission later they are fine.

Any way to solve this please? I don't like moving 30 individual units instead of 4 TFs

Hi Nepe,

Your information is sketchy, but Task Force definitions is potentially one of the things that could break if the mission duration is changed.

Info I need: DB version, DCS version, MP version.

Cheers,
4Shades

Many thanks Shades

Starfire is the host and admin, so he knows better, but I will copy/paste his signature:

semp v4.610a, sedcs 3.2.13, sedb32e & HSFX4.11

Im afraid I can't give you much more info. This SEOW has been running for 32 missions, and we are now in the 3rd day of war. I only became Commander of Axis at the beginning of 2nd day, and as far as I know no one else is using TFs in the map.

Problems started at 17:00 mission, so before any time change should be made (last human flown mission was at 1800, then we have flown 2 more missions without any human flying).

In that 1700 mission the TFs were not to be seen, but as I said before I could not create a new one with the same name as one of the old TFs.

At 1800 the TFs reappeared wihtout nothing special being done. Then next mission they dissapeared again. Next mission reappeared...

And we are still in that loop.

If theres any further info I can give...

Thanks a lot for looking into this.

Hi Nepe,
it was also occurred to me two years ago... maybe you should analize the situation of the TF components into the object mission data table querying them across the missions and check the coords history. I remember one case where one element was somehow placed very far from the TF.

Gross, grazie.

The admin did indeed dissolve all the previous TFs, but that didnt help.

But last 2 missions TFs have been correctly assigned, let's see if the problem just solved itself.

I have a suspicion.

Sometimes I have experianced missions in progress after a mission have been run and analyzed.
Since we are running with truncated missions of both sea and groundunits this should not be happening. On some occasions I have used the "Remove In Progress" button.

Can that ´be the cause?

Hi Starfire,

Really? That is very unusual. It makes me think that there are other errors occurring during the Analyze that interrupt the normal sequence of DCS operations. Do you ever notice any warning/error messages from the DCS?

Cheers,
4Shades

IV/JG7_4Shades wrote:Hi Starfire,

Really? That is very unusual. It makes me think that there are other errors occurring during the Analyze that interrupt the normal sequence of DCS operations. Do you ever notice any warning/error messages from the DCS?

Cheers,
4Shades

Please don't kill me for saying this; But I have had som repeating errors I have been unable to get rid of and since we have been unable to solve it, I have choosen to ignore them. If I read the sedcs error masseges correctly, we have nothning to worry about. The sedcs takes care of it.
(I know what you are thinking: "Moron!" )

Hi Starfire,

Well if we get rid of the DCS errors we may find that the TF errors disappear.

Cheers,
4Shades

This is the error in question. Different units, but always the same error.

With my basic knowledge of db's, the drop X happends because of a duplicate record at the destination.
If my assumption is true, then there won't be any loss at all.
The dcs are 'just' warning the user that there are error in the db.

That is an old DCS error, fixed some time ago. It should not occur in DCS v3.2.22.

Cheers,
4Shades

IV/JG7_4Shades wrote:That is an old DCS error, fixed some time ago. It should not occur in DCS v3.2.22.

Cheers,
4Shades

If I remember correctly, the dcs 3.2.16 and onward are made for the new db or am I in error?

This campaign are still running on the old version MP4.6 and SEDB32E

Hi Starfire,

This is the only option, I suspect:

http://seowhq.net/seowforum/viewtopic.php?t=662

Cheers,
4Shades

IV/JG7_4Shades wrote:Hi Starfire,

This is the only option, I suspect:

http://seowhq.net/seowforum/viewtopic.php?t=662

Cheers,
4Shades

I still don't know what the effect of the error are?
Does it affect the taskforce issue or does it not?
Is it as I assume or something else?

As I see it, I still have at least two options.