Content package is missing

[El Condoro]

I have tested a few maps and this error has occurred.

If I load a custom map straight into PzC (1.04) it loads and plays as intended (at least in the small test I did).
However, if I open the scenario in the Editor and save it - nothing else, just click the Save button - and then load it in PzC (or at least, try to load it) the following message appears in a dialog box:

Cannot start game because the required content package is missing.

As I say, I've reproduced the issue on 3 custom scenarios and a campaign start scenario.

[El Condoro]

I just tested this after disabling all mods and add-ons that I had. I then opened the Fall Weiss campaign and it ran as expected. I then opened Poland.pzscn (first scenario in Fall Weiss campaign) in the Editor - saved it without making any changes - tried to open it in the game and got the error above.

[El Condoro]

Just in case this sort of information helps...

I 'converted' my Red Dawn campaign to the new My documents\My Games\Panzer Corps\Mods\Red Dawn\Data\briefings structure and it all worked very well. Again, I opened the first scenario in the campaign in the Editor and saved it without making any changes. Same issue as described above. I wondered if it had something to do with looking for that Mods folder but seems not.

[IainMcNeil]

Alex is going to look in to it but is on a flight from London to St Petersberg right now so it will probably be this evening before he responds.

[Razz1]

Confirmed. I saved as new name, hosted MP game and can not play it.

I was disappointed the editor wasn't available in beta as I would have tested this feature.

We had this problem in an earlier beta.

Try to load Bocage Hell 1.04 off the server in multiplayer.

[El Condoro]

Last night when this was an issue for me I had downloaded 1.04 but not the DLCs. Today I have downloaded and installed the DLCs and the issue seems to be resolved - I can open and save a scenario and it plays without any problems. Is the 1.04 in the DLCs the same as the stand-alone 1.04? I assume they are but nothing else has changed and yet the problem is gone.

[IainMcNeil]

Yes it is the same.

[Razz1]

This still needs to be fixed. It is a major bug.

I purchased DLC 1940 and now games work after using the editor.

[El Condoro]

Maybe there is a difference between the scenarioeditor.exe in the 1.04 standalone download and the one in the DLCs?

[IainMcNeil]

No it is the same. The DLC's just include the same 1.04 patch.

[Blownz06]

i just tried playing razz in bocage breakout 1.04 and got the same message above.

[Razz1]

Yes, that is confirmed. BlownZ06 does not have a DLC package so he can not play my game after I DL the 1940 campaign.

Now our group is fractured between the haves and have nots.

[VPaulus]

I'm sure that this was not on purpose. And the devs will fix it soon.
Here, we will only have "have nots" for a very short period of time.

[Razz1]

Take a look at this.

As you can see in the left circle is new units. Therefore, I have the new DLC 1940.

Note the Circle on the right.

See how the question marks are not visible?


So, why do I have squiggly lines in the editor?

[VPaulus]

So what?
They will fix it for people who don't have DLC.
And even we who have the DLC, not everything is working well with the editor. It wipe Victory conditions from old maps.
They will fix it.

[Razz1]

Every patch has wiped out the victory conditions.

Are you getting the same view in the Editor as me?

That is my point. Am I the only one that is missing the question marks?

If we are all the same then I'm happy. If others do not have the missing question marks then, I have pointed out another problem.

We know this will get fixed but at this point I can not play any NEW MP games and am getting CTD's when playing the DLC.

I never had this problem in Beta.

[VPaulus]

So far, to my knowledge, you're the only one who's getting CTD with 1.04.
Have you tried without any mods?

[El Condoro]

@Razz: I can confirm the squiggly lines in my editor, too.

I'm hoping that with the weekend over, this editor issue can be solved completely.