The Bug Thread (Read before posting bugs!)
Moderators: Slitherine Core, The Lordz, Panzer Corps Moderators, Panzer Corps Design
Kerensky wrote:These buttons only function if your unit is deficient in some way. For example, a 10 strength unit does not have the 'reinforcement' button available to see or use, it is greyed out. A unit with full fuel and ammo is not able to use the supply button.Powell wrote:i just tried the new version, but the replacement and elite reinforcement button didn´t work, what is wrong here?
i just saw no button from the unit screen (refuel, embark disembark... is working)
Does this help solve your problem, or was it something else not working?
Same here buttons for refuel, replacement, elite replacement, etc do not work - useing the shortkeys works, also upgrading, replacment, etc in the deployment screen does not work... very anoying
Can you post a screenshot of what 'not working' buttons looks like? Are they just greyed out when they shouldn't be or is something else wrong? What OS are you using? More details are necessary to help solve this problem, because it's clearly not a problem for everyone, myself included, so it's very difficult to pinpoint what's wrong.MrWhite wrote:Same here buttons for refuel, replacement, elite replacement, etc do not work - useing the shortkeys works, also upgrading, replacment, etc in the deployment screen does not work... very anoying
1. Undo Move, Supply, Sleep, Replacements, Elite Replacements, Upgrade, Embark, Mount - "Unit buttons" do not work when they are should (when they are enabled). Clicking on them simply do not work.Kerensky wrote:Can you post a screenshot of what 'not working' buttons looks like? Are they just greyed out when they shouldn't be or is something else wrong? What OS are you using? More details are necessary to help solve this problem, because it's clearly not a problem for everyone, myself included, so it's very difficult to pinpoint what's wrong.MrWhite wrote:Same here buttons for refuel, replacement, elite replacement, etc do not work - useing the shortkeys works, also upgrading, replacment, etc in the deployment screen does not work... very anoying
The ninth button does not work as well, but I think it is not implemented (the "tank in the sight" one).
For example, on screen:
Sleep, Upgrade, Embark are highlighted and they should work - but they don't.
Keyboard shortcuts for those buttons work and thats the only reason I was able to play. With only one exception: ESC doesn't work as UNDO button (instead of UNDO I am getting System Menu opened).
2. Previous, Next, Toggle Air / Ground, Toggle Strategic Map can be pressed only once. Once pressed, they cannot be pressed again.
For example, after pressing "Next" it is needed to press some other button in order to be able to press "Next" again.
3. Informational panels (Unit List, Stats Panel) can also be pressed only once. I can show Stats Panel, but to hide it I need to click some other button - only after that I am allowed to click on "Stats Panel" button again.
System: Vista 32bit SP2
Last edited by skarczew on Sat Apr 30, 2011 11:47 am, edited 1 time in total.
I found those names on some WW2 map and sometimes it is hart to distinguish "a" from "o" but Lubov(i)na was definitely marked wrong on that map. Nothing to be surprised with. Thanks for reporting. Will fix this.Pupec wrote:Scenario Poland has incorrectly named Slovak cities.
Zilino -> Zilina
Lubovina -> Stara Lubovna (Lubovna)
I'm happy for Slovak troops in the game, I was born to Slovakia.
Tried to load a file from an older version by accident. Only realized something was wrong when the main menu screen wouldn't change after each attempt.
In future may want a VERSION check, so the user can know what's going on here.
In future may want a VERSION check, so the user can know what's going on here.
Experience Ratio = (def exp level + 2)/(att exp level + 2)
Entrenchment Ratio = (def entr rate + 1) /(att entr rate + 1)
After uninstall:
I remember it appeared when I was uninstalling previous version too.
Game seems to be uninstalled properly, I have no idea why this message appeared (this happens sometimes to other applications, too).
Vista 32bit SP2
Code: Select all
Problem signature:
Problem Event Name: BEX
Application Name: uninstall.exe_Setup Factory Runtime
Application Version: 9.0.1.0
Application Timestamp: 4d495ec6
Fault Module Name: uninstall.exe
Fault Module Version: 9.0.1.0
Fault Module Timestamp: 4d495ec6
Exception Offset: 001b3f14
Exception Code: c0000409
Exception Data: 00000000
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1045
Additional Information 1: 058c
Additional Information 2: ae6f41d1e064762df7f70a7c2843a9b3
Additional Information 3: 8999
Additional Information 4: b35e53a583b6be2b62ab1d89063e2de3
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
Game seems to be uninstalled properly, I have no idea why this message appeared (this happens sometimes to other applications, too).
Vista 32bit SP2
Suggestion, when starting a scenario, let us know ahead of time who will get first-turn initiative before placing units. I hate being burned off the HARD WAY by losing up-front precious units like artillery etc this way, simply because the enemy got to act FIRST.
Experience Ratio = (def exp level + 2)/(att exp level + 2)
Entrenchment Ratio = (def entr rate + 1) /(att entr rate + 1)
Graphic bug
Graphic Bug.
I'm in London and some of the 2 lbr's due not have the highlight glow.
This is strange as an icon is an icon.
Is it possible these units were at the start of the scenario and hence they have the old icon from the last build?
5th of 2 pounder
16th of 2 pounder
http://www.photoshop.com/users/razz1234 ... 3bcbd7c3a1
I'm in London and some of the 2 lbr's due not have the highlight glow.
This is strange as an icon is an icon.
Is it possible these units were at the start of the scenario and hence they have the old icon from the last build?
5th of 2 pounder
16th of 2 pounder
http://www.photoshop.com/users/razz1234 ... 3bcbd7c3a1
I really like having a bug report thread.
But could we please make it into a separate thread / beta version?
Once something has been fixed, it needs to show up max once in the new version (to verify it was actually fixed).
As it is now, trying to find if a bug has been fixed previously... not a nice task. In a previous beta I was involved in users posted bugs and other users voted on them. Top bugs got fixed, lower ones stayed on through versions. Wouldn't that be better?
And sorry, I'm really not trying to be a pain in the A(xi)s. I think the game works great so far. Maybe I've just been involved in enough game projects to know "bug structure" is needed.
But could we please make it into a separate thread / beta version?
Once something has been fixed, it needs to show up max once in the new version (to verify it was actually fixed).
As it is now, trying to find if a bug has been fixed previously... not a nice task. In a previous beta I was involved in users posted bugs and other users voted on them. Top bugs got fixed, lower ones stayed on through versions. Wouldn't that be better?
And sorry, I'm really not trying to be a pain in the A(xi)s. I think the game works great so far. Maybe I've just been involved in enough game projects to know "bug structure" is needed.
One more thing:Kerensky wrote:About buttons not working. Strange, I'll make a report and add it to the list.
- in previous version (0.93 I think) the Unit Stats and Unit List do not toggle properly as well;
- in previous version Unit Keys (undo, upgrade, etc) usually worked; When they were bugging, I was fixing them by clicking on window frame - after that they functioned normally;
On a unrelated note: game window keeps mouse cursor inside and initially it is impossible to leave the game screen. To leave it it is needed to click on window frame :] .
BTW, Sebastian, I've asked you some questions in respnose to your initial feedback (about window frames etc.), can you look at it?skarczew wrote: On a unrelated note: game window keeps mouse cursor inside and initially it is impossible to leave the game screen. To leave it it is needed to click on window frame :] .
Separate thread per beta would be confusing and require too many stickies. The entire point is to have as few threads as possible. Plus some bugs have persisted between betas, or have actually been 'fixed' only to appear to have been broken in a new way. #9 Was 'fixed' twice only to need to be 'adjusted' again and again. This will create too much cross-thread overlap.eskimo68 wrote:I really like having a bug report thread.
But could we please make it into a separate thread / beta version?
Once something has been fixed, it needs to show up max once in the new version (to verify it was actually fixed).
As it is now, trying to find if a bug has been fixed previously... not a nice task. In a previous beta I was involved in users posted bugs and other users voted on them. Top bugs got fixed, lower ones stayed on through versions. Wouldn't that be better?
And sorry, I'm really not trying to be a pain in the A(xi)s. I think the game works great so far. Maybe I've just been involved in enough game projects to know "bug structure" is needed.
Verification for fixed bugs is the second post.
Why vote on bugs? All of them need fixing, but people should understand that sometimes fixing bugs is a very involved process, and a lack of detailed reports can hinder this process. First page first post = bug description in a single sentence. If anyone wants details, they can dig through the thread, but the important idea is communicate problems to the devs in a manner that is easy and accessible for them. Many bugs have been solved after being noticed on the first page, and when you see a dev ask questions about it in the thread itself, it means they are requesting more information.
Multiple threads may be easier for users to organize or sort through, but it forces a developer, who doesn't have time to scan through 5 or more threads because he needs time to actually spend fixing bugs, to look all over the forums to find obscure bug reports that anyone randomly posted wherever they felt like it.