Page 9 of 22

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 9:17 am
by Nomad
ORIGINAL: Kitakami

ORIGINAL: Pharnakes

That normally means you have different pwhexe.dat files from the main folder. pwzlink and pwzone are also possible culprits, you need to get your versions synced or you will quickly start running into desync errors.

I must have old versions... where can I get the correct versions for this? I have received the results of Turn 1, but don't want to start desyncing.

Here: https://sites.google.com/site/dababeswi ... tended-map

Or John could send you his three files.

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 9:19 am
by Kitakami
ORIGINAL: Nomad
ORIGINAL: Kitakami

ORIGINAL: Pharnakes

That normally means you have different pwhexe.dat files from the main folder. pwzlink and pwzone are also possible culprits, you need to get your versions synced or you will quickly start running into desync errors.

I must have old versions... where can I get the correct versions for this? I have received the results of Turn 1, but don't want to start desyncing.

Here: https://sites.google.com/site/dababeswi ... tended-map

Or John could send you his three files.

Thanks! :)

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 11:26 am
by btd64
Dutch Surface TF's 412 and 413 have Depth charge, Torp and AAA amunition level problems. DD's only. Some are set too low and some are loaded to high. This is turn one of BTSL. See example image below....GP

Image

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 3:46 pm
by Kitakami
Had to reinstall from scratch, but that solved all problems.

Initial attack at Pearl delivered interesting results (in case the information is helpful to twink scenario details):

- 1x BB sunk.
- 4x Severely listing BBs (flotation 83, 76, 61, 51).
- 2x Severely topside damaged BBs (system 62, 52).
- 1x Moderately listing BB (flotation 25).
- 1x Severely listing CL (flotation 63).
- 1x Severely listing DD (flotation 52).
- 1x Moderately topside damaged DD (system 20).
- 1x Severely listing xAP (flotation 52).
- 2x Moderately damaged SSs (system 31, 29).
- 1x Moderately listing AVP (flotation 32).
- 1x Moderately topside damaged AV (system 29).
- 2x Moderately topside damaged DMs (system 23, 23).
- 1x Moderately topside damaged AM (system 15).

Severe (57) runway damage, moderate (36) airfield service damage, moderate (24) port damage.
11x planes destroyed on the ground, 4x planes damaged.

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 5:46 pm
by John 3rd
Thanks for Posting that Jorge.

I used all three CarDiv to hit PH. Normal KB (the six heavies) carry 129 Z, 138 V, and 138 K. The three re-done CarDiv struck PH with 112 Z, 147 V, and 122 K. Very comparable numbers...

Would like to see how everyone's Strike went? Did you use all three CarDiv?

Do we keep everything together or can we strip off a CarDiv for use elsewhere?

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 6:54 pm
by ny59giants
A target is worthy of ALL of KB or none of KB.

Quote from "Shattered Swords" [&o]

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 8:49 pm
by AdmNelson
ORIGINAL: NorthCarolinaDidNothingWrong

I've sent out the 1st turn to AdmNelson. I am, tentatively, playing IJN [/b]on the light module. I have a backup of the first turn ready so if AdmNelson decides to reverse course on any particular matter for any particular reason (not that I would mind, I've been slightly terrible about communication in this particular matter). we shalln't lose anything from it. We're running no house rules and stacking limits. I have tracker, but I had to install 64 bit Java for something a while back and that has borked it for the time being. I'm running the economy as though i'm playing a normal campaign instead of a shorter one. Ki-43 and Ki-44 production (especially the Ki-43) are both being expanded as to quickly phase out the Ki-27. The A6M2 is also being being expanded to keep up with the inevitable heavy losses.


Also, Pharnakes, if you aren't already partnered up, I'd be fine with partnering with you. The PBEM games I'm playing or are going to be playing are all slow enough I still have a lot of time to burn and i'm fine with any combination of options or modifications.



First turn done, second is back. Landing are every where Ambon, Merising, Dutch Harbor, Adak Island, Jolo. Forgot what it like being Allies first turn. So much to move.

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 8:50 pm
by larryfulkerson
I started an AAR for my game with Brian so I wouldn't clog up this thread with so much detail about everything that happens. It's right here:
https://www.matrixgames.com/forums/tm.a ... =&#4798148

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 9:37 pm
by ny59giants
Switches - need list of them all and what they do. Cannot go through over 50 pages in Beta thread to find them.

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 9:51 pm
by Nomad
What switches are you talking about?

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 10:28 pm
by larryfulkerson
It appears that there may be some duplicate values in the database. I'm not sure what they are but here's the error message I've been getting:

C:\Matrix Games\WITP-AE BTS-L\SAVE\Tracker for my game with Brian>java -Xms384m -Xmx512m -jar "WitPTracker.jar" nomap
Initializing WitP Tracker AE database.
java.sql.SQLException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_PK_123
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source)
at witptracker.Database.InsertRow(Database.java:54)
at witptracker.ProductionGlobal.InsertInTable(ProductionGlobal.java:294)
at witptracker.SaveFileReader.ReadProductionPool(SaveFileReader.java:643)
at witptracker.SaveFileReader.ReadScenarioInfo(SaveFileReader.java:406)
at witptracker.SaveFileReader.<init>(SaveFileReader.java:118)
at witptracker.Main.main(Main.java:141)
Insert Error code = -104
Table=ProductionGlobal Values=(2,20495,51989,2,193,13011,1)
java.sql.SQLException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_PK_51
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source)
at witptracker.Database.InsertRow(Database.java:54)
at witptracker.Device.InsertPoolInTable(Device.java:251)
at witptracker.SaveFileReader.ReadProductionPool(SaveFileReader.java:654)
at witptracker.SaveFileReader.ReadScenarioInfo(SaveFileReader.java:406)
at witptracker.SaveFileReader.<init>(SaveFileReader.java:118)
at witptracker.Main.main(Main.java:141)
Insert Error code = -104
Table=ArmamentPool Values=(251,2,0,70,0)
java.sql.SQLException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_PK_51
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source)
at witptracker.Database.InsertRow(Database.java:54)
at witptracker.Device.InsertPoolInTable(Device.java:251)
at witptracker.SaveFileReader.ReadProductionPool(SaveFileReader.java:654)
at witptracker.SaveFileReader.ReadScenarioInfo(SaveFileReader.java:406)
at witptracker.SaveFileReader.<init>(SaveFileReader.java:118)
at witptracker.Main.main(Main.java:141)
Insert Error code = -104
Table=ArmamentPool Values=(252,2,0,80,0)
java.sql.SQLException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_PK_51
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source)
at witptracker.Database.InsertRow(Database.java:54)
at witptracker.Device.InsertPoolInTable(Device.java:251)
at witptracker.SaveFileReader.ReadProductionPool(SaveFileReader.java:654)
at witptracker.SaveFileReader.ReadScenarioInfo(SaveFileReader.java:406)
at witptracker.SaveFileReader.<init>(SaveFileReader.java:118)
at witptracker.Main.main(Main.java:141)
Insert Error code = -104
Table=ArmamentPool Values=(254,2,0,36,0)
java.sql.SQLException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_PK_51
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source)
at witptracker.Database.InsertRow(Database.java:54)
at witptracker.Device.InsertPoolInTable(Device.java:251)
at witptracker.SaveFileReader.ReadProductionPool(SaveFileReader.java:654)
at witptracker.SaveFileReader.ReadScenarioInfo(SaveFileReader.java:406)
at witptracker.SaveFileReader.<init>(SaveFileReader.java:118)
at witptracker.Main.main(Main.java:141)
Insert Error code = -104
Table=ArmamentPool Values=(518,2,5273851,0,0)
java.sql.SQLException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_PK_51
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source)
at witptracker.Database.InsertRow(Database.java:54)
at witptracker.Device.InsertPoolInTable(Device.java:251)
at witptracker.SaveFileReader.ReadProductionPool(SaveFileReader.java:654)
at witptracker.SaveFileReader.ReadScenarioInfo(SaveFileReader.java:406)
at witptracker.SaveFileReader.<init>(SaveFileReader.java:118)
at witptracker.Main.main(Main.java:141)
Insert Error code = -104
Table=ArmamentPool Values=(519,2,12482387,0,0)
java.sql.SQLException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_PK_51
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source)
at witptracker.Database.InsertRow(Database.java:54)
at witptracker.Device.InsertPoolInTable(Device.java:251)
at witptracker.SaveFileReader.ReadProductionPool(SaveFileReader.java:654)
at witptracker.SaveFileReader.ReadScenarioInfo(SaveFileReader.java:406)
at witptracker.SaveFileReader.<init>(SaveFileReader.java:118)
at witptracker.Main.main(Main.java:141)
Insert Error code = -104
Table=ArmamentPool Values=(520,2,20495,13470,0)
java.sql.SQLException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_PK_51
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source)
at witptracker.Database.InsertRow(Database.java:54)
at witptracker.Device.InsertPoolInTable(Device.java:251)
at witptracker.SaveFileReader.ReadProductionPool(SaveFileReader.java:654)
at witptracker.SaveFileReader.ReadScenarioInfo(SaveFileReader.java:406)
at witptracker.SaveFileReader.<init>(SaveFileReader.java:118)
at witptracker.Main.main(Main.java:141)
Insert Error code = -104
Table=ArmamentPool Values=(521,2,51989,13482,0)
WitP Tracker AE tables loaded in 4 seconds
WARNING: Could not initialize SigInt information for first turn.
WARNING: Could not initialize Operations report for first turn.
ERROR: base 517 name of <Camp Pendleton> does not match the name in the import file (San Clemente Island)
ERROR: base 749 name of <Buin> does not match the name in the import file (Shortlands)

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 10:34 pm
by btd64
Command line switches. I have a sheet I can upload. Just have to find it. Tomorrow morning I'll look for it....GP

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 10:38 pm
by btd64
Larry, does tracker still load....GP

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 10:41 pm
by larryfulkerson
There are all kinds of error messages but it DOES still load.

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 10:50 pm
by btd64
There are about 4 different db files in the tracker directory. Delete them all and then use the nomap executable to restart the program. If that doesn't work then you should post to the tracker thread....GP

RE: BTS Play-Testing

Posted: Fri Apr 17, 2020 10:58 pm
by Nomad
I created a tracker for Japan using the BTS-L files and got no errors.

RE: BTS Play-Testing

Posted: Sat Apr 18, 2020 1:20 am
by John 3rd
I've been running Tracker (now January 1944) with Sean and had no issues. It is BTSH.

RE: BTS Play-Testing

Posted: Sat Apr 18, 2020 1:25 am
by larryfulkerson
I was surprised to find three airfields that didn't have any support for it's aircraft. So I flew the aircraft to different places. I'll look into sending some AF guys to those places later.

Image

RE: BTS Play-Testing

Posted: Sat Apr 18, 2020 2:39 am
by ny59giants
Command line switches. I have a sheet I can upload. Just have to find it. Tomorrow morning I'll look for it....GP


Thanks!!

Send me via email also.

RE: BTS Play-Testing

Posted: Sat Apr 18, 2020 2:52 am
by NorthCarolinaDidNothingWrong
I hit Pearl with all the carriers sans CarDiv 2, which i sent to reinforce KB-4 to enable me to rampage though the DEI as well as to protect the CVL and CVE taskforces in the area. Since only the B5N's hit the harbor and all of the D3A's focused on smashing the airfields (The B-17s and PBYs are both high value, difficult-to-replace targets.), damage was pretty minor but the usual midget landed a torpedo in the usual victim (washington). A couple of ships had heavy damage and heavy fires, but the main goal of simply disabling the battleships for the time being was achieved. Since the allied carrier position at the start is relatively weak, i'm fine with having KB split like this at the very beginning to accelerate operations across the map for a time but for sure it should be a single unit by Jan 30th at latest. I detached Ishitaka and Kawachi from the KB and used them to destroy the fleet that starts in NorPac to cover my operations there.