Obviously this post is for VBH, but I wonder if anyone else has the result I am getting.
My set-up:
I made a copy of my 1.26e folder, and applied the "FXEXE_20160313.zip" to it.
The only changes was that I put the fonts, screens and menu files in a subfolder so that the default ones would be loaded, which is better for my eyesight
I also added the default "maptrans.dat" file so that the targets are displayed in the right places.

This is what I found running FXExeV1.0


Running a 1943 single mission in a Spit IX intercept targets are available in Western France:


I would not expect these targets to be available for an intercept as they are in enemy territory.

However, they should make good targets for a 1943 bombing mission, escort, or interdiction, but they are not


Maybe I have done something wrong,so I wonder if anyone else can reproduce these results?

I think that I have found the cause.
Using my editor I checked the "frntline.dat" file in the "DATA.FXE"
There are 20 frontlines (0-19) and here are the first three and the last:




They are date related for careers, and as I moved through them it was obvious that the one used for 1943 had those targets in Western France in Allied territory.

Using the default 1.2 "frntline.dat" file fixed the problem

I think that the frontline file VBH included was meant for interesting online possibilities, but as you can see there is a problem when it is used for single missions

It's not doing that on my computer or in the online games we've played with this targetset for over a year, perhaps your savedatafolder is corrupt.
My game gives me targets near London, Calais, South of England etc., even switching years gives me appropiate targets.
I do know that the .MSN files become corrupt when you're trying to fly alternative theatres but a new feature in the FXEXE allows users to directly load from the .MSN file and the game will assign an appropiate target/airfield for that plane.
You could try this feature in this situattion, once the game has reset the .MSN file things will run in line from there on and the process doesn't have to be repeated. Iguess you know which mission to load for the Spit9 but just incase you don't it's Default11.MSN

VonBeerhofen

What happens if you have an empty "savedata" folder and you fly a Spit IX 1943 interdiction. Can you select La Pallice as the target?

You can't have an empty savedata folder with a changed targetset, nor can you mess with the frontlines, you should know that by now.
The FXEXE uses an additional frontline but they're not the same ones as in the default game or as in your version.
Because of this the savedata folder isn't transferrable.

VBH

I completely disagree

My folder with the 1.2 frontline file added:


My savedata, effectively empty because of all your files are in the New folder:


Mainscreen:


1943 escort to target 097


Target selection, note the others that are available in the same general area:


I flew the mission and as a result a "Default11.msn" file was saved


Flying again, but with the 1.2 frontline file re-named so it would not be used:


097 is the selected target, from the msn file, but it is no longer a genuinely selectable target, and the others that were selectable originally are no longer. The exe is using the "frntline.dat" in your "Data.FXE" file, and those targets are in allied territory. 1940 and 1943 both use the very first frontline for single missions, so it is using this one:

Ofcourse the mission isn't working without the apropiate Savedata folder, as I said it's essential for the theatre.
You probably misunderstand what I was saying, it's not flying the mission which resets the .MSN file, it only creates one.
I said to manually LOAD Default11.MSN and then fly the mission. Ofcourse if there's no .MSN to load, because you're not using the Savedata folder which came with my theatre, then you first have to create a .MSN and then LOAD it manually to reset it to the targetset in use. A bit like your .MSN editor but without the hassle.

I've written a post in 2005 which explained why single missions and campaigns weren't working but I guess your ignore button was on at the time. Once again, you can't use an empty Savedata folder with a changed targetset and changed frontlines. If you've relied on empty Savedata folders then you very likely will have caused enormous problems for your offline players, as this behaviour goes all the way back to v1.2.

That's why I started releasing proper Savedata folders to individuals for theatres that didn't have one. Add a proper Savedata folder and the problem is solved. There is another way to do it though but I preferred this method as I believed it's fool proof and you don't have to mess around with editors which can't do the job, unless you know how it all works.

The proper execution of a campaign lies with the creator and mine are probably the only ones which fully work, untill you start messing around with them.

VBH

Not true.

ModSquad's BOB and The General's War use simple but accurate modifications to the default campaign files and the default target set.

SPAW and SPAW45 use completely functional rewritten target and TMOD sets.

FWIW, it might be worth the time to try my European target upgrade. All new TMOD set of over 300 TMODs, lots of new cities to attack and a completely revamped railroad system. It has a correct frontline file to go along with the targets and it even manages to include one Italian city in the mix for those who might be interested in a bit of Italian flavoring.

I'm not sure but I think it would be fairly easy to implement as the file set is already included with the 1.5 download.

It is not a changed target set- it is your target set. The only thing I changed were the screens because I prefer readable ones.
Your frontline is useless for single missions
Can you select target "097" for a 1943 allied escort, sweep, bombing or interdiction mission?

1940 allied sweep:



No targets West of "028" available with your files

We'll see Rotton, I hope you understand that I'm trying to be helpfull here and what I say is true, just as it was back in 2005. There are several reasons I can think of which may help to run the campaign and that is when there's already a set of .MSN files which just happen to have the right targets on the right side of the frontline or when the targets were placed in such a way that the game assigns an appropiate airfield and target with the first misson by accident.

When the first mission works then there's nothing to worry about, it will work flawlessly from then on, but there are 29 planes which all need the correct airbase and target on the appropiate side of the frontline. These locations in all campaigns I have played were flawed, except the ones which had no extensive relocations or changed frontlines.

Mr. Jelly's 'helpfull' effort shows the truth in what I say, as you can see it's the most messed up targetset on the planet and it won't work without it's Savedata folder. It's in fact so messed up that I can create new frontlines for it that extend deep into Axis territory, all the way to Berlin, and the game will still find some target/airbase it can use in our online games, even though that sometimes results in a one way trip.

There's a lot more to it then that alone, but in your case I wouldn't release a new set without a Savedata folder but it's entirely up to you. I can't verify campaigns which rely on v1.29 or later but I wouldn't fully trust them without an appropiate Savedata folder and correct .MSN files. With the FXEXE they can be created and set in jiffy but I know from experience that it is a bit of a pain if you have to do it with the .MSN editor.

Good luck with your new targetset Ray, hope you'll have as much fun as I have with the FXEXE but you may want to sort this problem out first as it's closely related:

http://simhq.com/forum/ubbthreads.php/topics/4314965/Picking_sensible_targets_at_Ga#Post4314965

Mr. Jelly I'm not sure of what you're up to this time, ofcourse you can't select targets in the west when it's an Allied sweep, it's friendly territory, nor can you select targets in the east when it's an intercept because intercepts usually happen over fiendly territory. Your pilotmap doesn't even look close to mine, nor do the targetdots. Are you actually trying to run my game or are you accidentally running your game with my files?
I understand your confusion but I'm probably more confused then you because I have no idea what you're on about.

Here's an intercept over friendly target 180 flying a SpiIX in 1943, Allied is white dots, Axis locations are black.
I've selected London for intercept too and some other targets, they're all fine. Intercepts in Axis aircraft are for instance Berlin, Dortmund and usually anything east of the Rhine. It works fine and always has for over a year but with my Savedata files ofcourse. Axis sweeps happen in Allied territory as far as my knowledge on WWII goes, unless it's April fools day.

Even Zander reported back to me it was working fine, maybe an unbiassed person like Russ or Mark are willing to confirm my findings.



VBH

I haven't had problems like this looking back. But I'll have to give it another go if I can find time to load up the game.

What options should I used to test it out?

Just setting the record straight. You stated that as far as you knew you had the only campaigns that worked properly.

I stated that wasn't correct and offered up the fact that four of my campaigns work properly.

Also, the subject of the link has no bearing on my target upgrade so I don't know how that's pertinent.

1. I am running a 1.2 installation in which I ran your "FXEXE_20160313.zip" file to install your FXExe.
So I started with your recommended installation.

2. I find your "Europe1.pic" difficult to read so I removed it so that the default one is used.

3. The first time I tried it the targets were in the wrong places because your "maptrans.dat" matches your "Europe1.pic" but not the 1.2 default version.
So I put the 1.2 "maptrans.dat" in the folder and the targets now appear in the right places.
That is why my pilot map does not look like yours.

4. No other changes have been made. You can see what I am running from the mainscreen I posted.
I was not interested in multiplayer or campaign issues, but just trying the FXExe in single mission mode, nothing more.

5. I found a problem with 1940 and 1943 single missions. The first frontline is always used for these.
The normal version has the frontline running through the channel:

All the targets in France are in Axis territory

Your version of the frontline has this:

All the targets in Western France are in Allied territory, and not selectable for anything other than an allied intercept.

6. The problem is with the "frntline.dat" file in the "Data.RXE" file in your release.
It may be fine for multiplayer, but it is useless for offline single missions.
The proof of this pudding is that the problem disappears when the default 1.2 "frntline.dat" file is put into your root folder.

So I was alerting you to a problem with one of your files when single missions are flown using the FXExe. Nothing more, nothing less

Then we have this unrelated material:



Now of course the multiplayer options in the FXExe are limited, which makes life simple.
The choices in 150 are much more varied, so there is a utility available for the host:



The thread contained advice about selecting an appropriate target for the mission type and the host's "nationality", so that the AIs behave as they should
The settings in the pic would be appropriate for a 1944 allied intercept. The target and both allied bases are in allied territory, with the two axis bases in axis territory

I have a FRNTLINE.DAT dated 2-14-2015 in my FXEXE game folder and the same one in my savedata folder. And Jel is saying the FXEXE exe is reading the frontline.dat from the older DATA.FXE dated 2-6-2014.

So I'm very confused as too witch frontline.dat is being used.

Unfortunately I wasn't able to pick a 1940 bombing target in France, the frontline seemed to be in the same location as it is in 1944. Not sure whats going on.

It is staightforward.
At VBH's site there is a "FXEXE_20160313.zip" to convert a 1.2 folder to FXExe.
It installs a "Data.FXE" file which contains a "frntline.dat" file.
This file is used if there is no "frntline.dat" file in the root, and the targets in Western France are not selectable in 1940 or 1943 for any allied missions other than an intercept.
With the default 1.2 "frntline.dat" file in the root folder it is used in preference, and the situation is reversed.

I downloaded the FXEXE from VBH's site three times over the months and the contents and dates on files have changed, but the filename hasn't. So it's possible some of the content was misplaced.

But after more testing I Still find the frontlines in the early years is set too far back. I'm not even sure if there was any movement in the frontlines in later years in VBH's map. Although the target map did move like the frontlines where in order; Showing me the west side of the map and then the east side , depending on the year.

Ah, the twisted words round. Here's the actual quote 'Master of Interpretation', and it's not what you have typed:

"The proper execution of a campaign lies with the creator and mine are probably the only ones which fully work, untill you start messing around with them.", which is quite different from your quote "You stated that as far as you knew you had the only campaigns that worked properly", that's not how I see 'setting the record straight'. It does however put a big question mark behind many campaigns and I'm showing you how to fix that.

Mark, I kept you updated with a few things prior to the release because my game changes dynamically, your frontline in the folder seems the same as mine but perhaps isn't. You don't have the released version anyway, yours is earlier so it's useless to try to replicate the Launchpad version. The FX dowloads don't contain a frontline.dat in the rootfolder and in all cases the .FXE archive will be used, unless you throw a frontline.dat into the root which will have priority and screw things up. That's why the 1.2 addon works by just changing two .FXE archives plus 2 textfiles. Installing the 1.2 addon removes all .MSN files and they don't come back by themselves if you replace the two .FXE archives with the older ones again, hoping that will restore the release version. With the .MSN files missing the game will no longer work and newly created ones will be corrupt. Vice versa you can't use the .MSN files from the release with the 1.2 addon, which is why it contains an empty Savedata folder. Recently a new online player joined our group and I gave him our latest version, which replaced the FXEXE download. That version is somewhat different from the one released earlier and you shouldn't mix anything from the various releases. Each version is completely standalone because there's no telling what I may have changed, frontlines, targetset, selection choices, routines, AI behaviour, fonts, screens or filenames/extensions, archives get cleaned up and so on. It all depends on what and where we fly. However nothing significant was changed as was shown when Shogun last joined us with the release version and everything worked fine. The dataset definately hasn't changed since the release as I've been busy organising my skysets for most of the time.

Mr.Jelly, your 'straightforward' explanation makes no sense to anyone, least of all me. Are you saying YOU made a mistake or that I made one? You have no idea which frontlines are used in the FXEXE because I haven't told you or anyone else. I can tell you with confidence that your assessment of which lines are 'always' used is totally wrong and if that's what you base your findings on then obviously those are wrong too. It's true that the first frontline is currently used for 1940 but it's just a single byte change to tell the game to use frontline 20 instead. But by doing so the .MSN files become corrupt and need to be changed.

To use the 1.2 frontlines will without a doubt have consequences for the .MSN files if it finds any active target or airbase in the game which is on the wrong side, but you might be lucky, as I explained previously.
The moment you fly such a mission the .MSN will be corrupted too and it can not revert back to my fronlines in most cases, unless it's reset. This may not even work since EAW usually starts from memory, not from the changed gamefolder. A reboot is the only thing I've found which always restarts the game from the folder. It makes changing campaigns on the fly a bit iffy, to say the least, so we don't do that in the Launchpad. This knowledge possibly has consequences for your version as well, which is why I share the information.

VBH

I've just talked with Mark and both you and him seem concerned about the 1940 frontline being that far east with France being occupied.
Now here's the scenario:
The Allieds still occupy France because it hasn't been invaded yet, the Germans are moving in through the Ardennes to attack Dunkirk and Holland is still free. Does that ring an alarm bell? Geez, Mr. Jelly do you want others to have fun your way only, can't I just have fun my way and do what I like? There's nothing wrong with that fronline except your view that it's not allowed to do what I like or it isn't what you want.

My years aren't actual years but just periods in history and I've even contemplated on changing that in the parameter selectionscreen. It is as I intended, like it or not, and it works fine.

VBH

okay, I understand about the files and that I only have a basic core package.

Frontlines; I was going based on v1.2 frontlines and what i remember from history. I'm not trying to shoot you down or cause any problems, just trying to help. I knew I could be wrong in that you intend something else, not that I fully understand it.

I don't want you to get stressed based on anything I have said. I hate stress and I have to walk away from projects when I am. So I know how it can feel.