Some important things :
- WitpAE Patch 2 introduced some new features in WitpAE which lead to array index errors in WitpStaff. A 'hotfix' is available from http://85.214.61.75/witp/witpStaff0.8.zip. The files within the zip file go into the tools/witpStaff directory (i.e. overwrite witpDecoder2.jar and insert the other ones).
This is actually an intermediate version, so the event window might show strange things. As most releases with a new version number it changes the database schema. This time it might actually try to fix your old database, but no tests have been done whether that works. Better delete and create a new one. - A library in the 1083/1084 patch (the latter also known as Patch 1) used by WitpStaff needs a library update from Microsoft installed (see at Microsoft or post 84). As different people need different versions of it, seemingly automatically installing it with the patch didn't work out. For the technical minded: Details on what this is all about can be found in the comments on Microsoft's Visual C++ blog
- The V0.7b of WitpStaff (With the 1083/1084 patch) changes WitpStaff's database format. You have to delete old WitpStaff's databases (easiest by deleting the generated subdirectory) before starting it.
- WitpAE's save file format changed. WitpStaff from 1083/1084 can only read WitpAE save files from 1083/1084.
WitpStaff from 1080 can only read save files from 1080 and 1079. See post 91 for a workaround. - How to peek into the database (but don't get your hopes high, nothing in there you can't see in the game directly). And Reg and Morphin created a way to use Openoffice to access WitpStaff'S database.
- If you take the planning map and scale it down, you can replace WitpStaff's auto-generated map files and get a much nicer looking Map Overview tab. See post 12 for that. (Please note that I would assume that you are not allowed to distribute the scaled down map.)
- WitpStaff will not work with most (all?) of the small scenarios.
- There is a problem in Vista where the path to 'java' is unknown. Easiest solution: Click on the witpdecoder2.jar file in WitpStaff's directory.
- If you get a 'witploadAE.exe failed' error, you most probably specified a wrong scenario number.
Solved in the 1083 patch (plus several new features):
- Ranges shown in the Aircraft window are way off.
- All (?) radars shown in the ship classes view are marked as air-search radar, even surface search ones.
- Sometimes destroyed LCUs are shown in the inconsistency window as having no leader or no HQ which is actually to be expected.
- Sometimes savegame load doesn't work giving a failure messages saying "no parent LCUsMarchOnlyToExistingBases". This is caused by an oddity in the save game files. Possible but not really satisfying workaround in post 47 and a better one in post 66.
- WitpStaff generates a logfile which might contain additional info. Especially it often lists the LCU/ship/Airgroup/... which caused the problem. Please look at it. It is called *cough* witpDecoder.log (seemingly a point missed when renaming things).
- If the error message you got is of the kind "Couldn't write things to the DB due to java.sql.SQLException: Check constraint Violation:XXXXXXXXX:YYYYYY the data you tried to read into WitpStaff violated one of the 'common sense' constraint I put into WitpStaff (comes for free when you use a database). The XXXXXXX describes the constraint, the YYYYYYYY the type of object violating it.
- The logfile might contain the name of the unit. So have a look there.
- If a name is given, have a look at that unit in game and check whether that unit violates the constraint.
- If yes, try to fix it in game, save the turn and try to load it again into WitpStaff.
- If it loads you found the error and can produce a quite good bug report in the forum.
- For analysing a non-identified bug I need from you (only sent this when asked to, I don't want to get swamped in save files):
- All the .csv files from the database directory you created in WitpStaff.
- The save game producing the error. If you suspect it might be an error due to some previous database content, I also need the save from the turn before.
- The side you are playing.
- If it is PBEM, I need your password.