This got screwed, because in beta1 tutorial campaign used Germany as player's side, but in beta2 we migrated to scheme where tutorial campaign uses two special sides ("TEAM RED" and "TEAM BLUE"). We wanted team red to be separate from Germany so that we can assign availability dates to team red's equipment the way whivch makes sense in the tutorial. But when this transition was made, we forgot to adjust "campaign nation" in the Data/campaign.pzdat. In campaign mode you can buy units only of your own nation to core, so purchase does not work any more. In stand alone mode there is no such limitation, so purchase works there.Kerensky wrote:#18
Cannot buy new core units in tutorial campaign. Looks like something broke, because I'm sitting at 2 core units available, plenty of prestige, all my core deployed, but units in the buy menu are tinted red and the purchase button is greyed out.
Scenario 3 is even worse, now it's 5 available, but still tinted red and greyed out button.
The Bug Thread (Read before posting bugs!)
Moderators: Slitherine Core, The Lordz, Panzer Corps Moderators, Panzer Corps Design
19. Paratroopers have strange disembark functionality when adjacent to aircraft. (unsolved)
I'm not sure how changing to left/right click interface will also change this behavior, but it may also fix it. Currently, if you have an air unit next to a paratrooper in a glider, your selection is currently on the glider, and you click to select the adjacent air unit, your paratrooper instead disembarks.
I'm not sure how changing to left/right click interface will also change this behavior, but it may also fix it. Currently, if you have an air unit next to a paratrooper in a glider, your selection is currently on the glider, and you click to select the adjacent air unit, your paratrooper instead disembarks.
The logic behind this behaviour is this:Kerensky wrote:19. Paratroopers have strange disembark functionality when adjacent to aircraft. (unsolved)
- when you can move to a hex, clicking it moves the unit there
- when you can disembark to a hex, clicking it disembarks the unit there
- when you can move AND disembark to a hex, clicking it moves the unit there; to disembark use "Disembark" button in the UI
This works just fine with sea, rail and air transports, but for paratroopers this results in "strange" behavior sometimes...
Buggy might be the wrong word then. It's Error-prone. I've definitely made the mistake of clicking the paratrooper in transport, and then attempt to select the other paratrooper or ME-109, only to have my initial paratrooper 'drop' from his transport, which is annoying and immune to undo button.
Changing to left/right click should remedy this though, right? Left clicking anywhere will select units only, right clicking will initiate moves and 'deploys'.
Changing to left/right click should remedy this though, right? Left clicking anywhere will select units only, right clicking will initiate moves and 'deploys'.
So if I understand correctly the disembark button would allow dropping the paras on any hex adjacent to the Ju52? Is there a good reason to allow dropping adjacent to the transport? It would be easier to understand if they could only drop at the current hex, that being the only place it ever displays the paradrop icon on.
And yes left/right interface would solve this. It's main purpose is to seperate selection entirely from actions.
And yes left/right interface would solve this. It's main purpose is to seperate selection entirely from actions.
#20 Enemy can become invulnerable.
I'm speechless. See for yourself. Click the link, unzip the file, put it in your save directory, load the save, and try to win the scenario.
http://www.theonslaught.org/forums/atta ... 1299549759
Possible related to #20, pioneers are NOT immune to ambush (Hah I knew I wasn't crazy, I was right!). Use the pioneer at 13,22 and attack the AA gun at 11,21
The save file:
http://www.theonslaught.org/forums/atta ... 1299550548
I'm speechless. See for yourself. Click the link, unzip the file, put it in your save directory, load the save, and try to win the scenario.
http://www.theonslaught.org/forums/atta ... 1299549759
Possible related to #20, pioneers are NOT immune to ambush (Hah I knew I wasn't crazy, I was right!). Use the pioneer at 13,22 and attack the AA gun at 11,21
The save file:
http://www.theonslaught.org/forums/atta ... 1299550548
Re: The Bug Thread (Read before posting bugs!)
Hmm, can't repeat this one. Does it persist after Save/reload? If so, can you post a saved game for this?Kerensky wrote: 17. Mousing over Hex 21,3 in France Scenario (city with German Bridge Engineer) causes CTD. (Unsolved)
17a. Same problem with German bridge engineer located in hex 33,3 of low countries scenario.
Did the other two save files work and preserve the bugs I mentioned?
I'm very curious to hear a reaction/explanation for those.
As for 17 and 17a, I was posting what zimoa mentioned after testing it myself and getting the same error. There's no save file to reproduce though. When he mentioned it, all I did to test was
1. Launch PzC.
2. Start France scenario as Germany.
3. Mouse over bridge engineer unit.
4. Crash.
After some more experiments, I found the game didn't always crash. If I had been playing other scenarios for a while, then quit to menu and started France, the game plays fine.
Then I restarted my computer, and the first thing I did was step 1-4, it crashed all the time every time.
I have a save file now if you still need it now.
I'm very curious to hear a reaction/explanation for those.
As for 17 and 17a, I was posting what zimoa mentioned after testing it myself and getting the same error. There's no save file to reproduce though. When he mentioned it, all I did to test was
1. Launch PzC.
2. Start France scenario as Germany.
3. Mouse over bridge engineer unit.
4. Crash.
After some more experiments, I found the game didn't always crash. If I had been playing other scenarios for a while, then quit to menu and started France, the game plays fine.
Then I restarted my computer, and the first thing I did was step 1-4, it crashed all the time every time.
I have a save file now if you still need it now.
Previous two save files were ok (I had to register on onslaught to get them), and the bugs described are fixed. The unit became invulnerable because the game got into bad state, and so it could not find enemy unit in the list (in order to delete it), so it remained on the map. As for pioneers, this was an oversight on my part - in one place I forgot to check "military engineer" trait.
I suspect that the crash bug is related to uninitialized data or something, and then weather you observe it or not depends on good (or bad) luck. If you have a save which you can load and repro the problem, then I'm willing to get it.
I suspect that the crash bug is related to uninitialized data or something, and then weather you observe it or not depends on good (or bad) luck. If you have a save which you can load and repro the problem, then I'm willing to get it.
Oh so you did have to register. I put it in the public section hoping maybe you wouldn't have to. That's sort of my one stop site for all my upload needs, plus I'm a forum moderator over there too. 
Unfortunately, my save file seems to share the same behavior as my other attempts to recreate the crash.
If I restart my computer, and immediately start PzC and launch the scenario or load the game, it crashes.
If I mess around with other scenarios and campaigns first, then load, the game does not crash.
So unfortunately I doubt my save file will be any use to you.
I dunno how you can go about fixing this, but one thing I did notice when the game crashed is that the name of the unit was always wrong. It wouldn't say Nth Bucknpioneer, it would say something else, like Panzer IIIF or StuG or something.
Hope that helps.
Unfortunately, my save file seems to share the same behavior as my other attempts to recreate the crash.
If I restart my computer, and immediately start PzC and launch the scenario or load the game, it crashes.
If I mess around with other scenarios and campaigns first, then load, the game does not crash.
So unfortunately I doubt my save file will be any use to you.
I dunno how you can go about fixing this, but one thing I did notice when the game crashed is that the name of the unit was always wrong. It wouldn't say Nth Bucknpioneer, it would say something else, like Panzer IIIF or StuG or something.
Hope that helps.
#22 Next day's weather is not 100% accurate.
Icon on the left show today's weather. Then you have the end turn button. Then you have another weather symbol, that I assumed meant 'tomorrow's weather'. But it's not always right, I especially noticed this on Norway where the weather is very temperamental.
Is this intended? Because if it is, that sucks, I would rather not have a prediction at all. Previous, people had a blind guess at to what was coming and had to steel themselves for any possibility, within reason of the scenario(No snow in North Africa). Currently, we are actually being given potentially false information and expected to make decisions based on that? At the very least if you don't want it to be 100% accurate, have a mouse over effect on this icon that says:
90% chance tomorrow's weather will be clear.
Matter of fact, that whole top there could use tool tips, but I won't put that here cause it isn't bug reports.
Icon on the left show today's weather. Then you have the end turn button. Then you have another weather symbol, that I assumed meant 'tomorrow's weather'. But it's not always right, I especially noticed this on Norway where the weather is very temperamental.
Is this intended? Because if it is, that sucks, I would rather not have a prediction at all. Previous, people had a blind guess at to what was coming and had to steel themselves for any possibility, within reason of the scenario(No snow in North Africa). Currently, we are actually being given potentially false information and expected to make decisions based on that? At the very least if you don't want it to be 100% accurate, have a mouse over effect on this icon that says:
90% chance tomorrow's weather will be clear.
Matter of fact, that whole top there could use tool tips, but I won't put that here cause it isn't bug reports.
Yep, this is intended. Unlike PG, where forecast was arbitrary, in PzC it has good accuracy and a fixed chance of error (right now 20%). So, it is good enough to base your decisions on it, but sometimes you will get surprises - just as in real life.Kerensky wrote:#22 Next day's weather is not 100% accurate.
Icon on the left show today's weather. Then you have the end turn button. Then you have another weather symbol, that I assumed meant 'tomorrow's weather'. But it's not always right, I especially noticed this on Norway where the weather is very temperamental.
Is this intended? Because if it is, that sucks, I would rather not have a prediction at all. Previous, people had a blind guess at to what was coming and had to steel themselves for any possibility, within reason of the scenario(No snow in North Africa). Currently, we are actually being given potentially false information and expected to make decisions based on that? At the very least if you don't want it to be 100% accurate, have a mouse over effect on this icon that says:
90% chance tomorrow's weather will be clear.
#24 Units can sometimes exist with 0 strength.
ATG unit at 19,8
Save file:
http://www.theonslaught.org/forums/atta ... 1299821288
ATG unit at 19,8
Save file:
http://www.theonslaught.org/forums/atta ... 1299821288
25. German bridge engineers cannot buy truck transport in the 1939 campaign. (unsolved)
But they can in the tutorial campaign. It's kinda funny that no one has noticed this yet. Bruckenpioneer are just so useful everyone ignored them I guess.
To be fair, I never even considered looking at them myself until like the 7th or 8th time through.
http://img339.imageshack.us/img339/4045/83701699.jpg
But they can in the tutorial campaign. It's kinda funny that no one has noticed this yet. Bruckenpioneer are just so useful everyone ignored them I guess.
To be fair, I never even considered looking at them myself until like the 7th or 8th time through.
http://img339.imageshack.us/img339/4045/83701699.jpg
26. Certain units can improperly engage air units. (Unsolved)
222 Scout Car.
http://img859.imageshack.us/img859/4518/222.jpg
Half Track transport.
http://img151.imageshack.us/img151/462/71542956.jpg
222 Scout Car.
http://img859.imageshack.us/img859/4518/222.jpg
Half Track transport.
http://img151.imageshack.us/img151/462/71542956.jpg
#27 Cannot upgrade paratroopers during deploy phase.
It seems to be caused by the fact that the game does not recognize the paratrooper as an 'infantry' unit but as a transport, as you can see from the expanded unit information panel.
Also affects other units. For example, if you deploy any unit in a sea hex during Norway deploy phase, remove your placement with right click, and attempt to upgrade or give replacements to that unit, the buttons will be greyed out.
It seems to be caused by the fact that the game does not recognize the paratrooper as an 'infantry' unit but as a transport, as you can see from the expanded unit information panel.
Also affects other units. For example, if you deploy any unit in a sea hex during Norway deploy phase, remove your placement with right click, and attempt to upgrade or give replacements to that unit, the buttons will be greyed out.
28. Level bombers can circumvent AD fire in some situations. (unsolved)
Grab level bomber.
Fly over hex that is hidden by fog and level bomb it immediately (the period of time when undo is still available), do not de-select bomber and cause ground units to 'appear'.
Avoid AD fire in the target hex.
I did notice that AD fire in adjacent hexes still 'intercept' properly though.
My Do-17Z bombing an airfield with an AD unit on it, but the AD unit is not bombed and does not return fire.
Bombing the same unit and the same airfield after deselecting and then reselecting my bomber and causing ground units to appear.
Grab level bomber.
Fly over hex that is hidden by fog and level bomb it immediately (the period of time when undo is still available), do not de-select bomber and cause ground units to 'appear'.
Avoid AD fire in the target hex.
I did notice that AD fire in adjacent hexes still 'intercept' properly though.
My Do-17Z bombing an airfield with an AD unit on it, but the AD unit is not bombed and does not return fire.
Bombing the same unit and the same airfield after deselecting and then reselecting my bomber and causing ground units to appear.