"B-17: Queen of the Skies" Emulator

Bug Reports
To Do List

Bug Reports

  1. BUG: Sometimes clicking on the generate mission tab leaves the add button from some other tab. (JollyFE, 21 Jul 2005)

  2. BUG: Sometimes clicking on the generate mission tab leaves the add button from some other tab. (JollyFE, 19 Jul 2005)

  3. BUG: Last guy on plane does not bail out. (JollyFE, 19 Jul 2005)

  4. BUG: One name was duped, and another missing when performing emergency bailout after fuel tank exploded. (Entemedor, 4 Apr 2005)

  5. BUG: I have now a new database (the third!) because the previous one suddenly started returning message 'Error 5 Addbomber () Invalid Procedure call or argument' every time I tried to add a bomber, and the emulator crashed each time. When opening it again, the bomber had indeed been added to the DB, but I took this as a sign of DB corruption and started a new one. (Entemedor, 4 Apr 2005)

  6. BUG: When I lose a crewmember, if I click on him in the airman tab, to see what his stats were, I get an error message (I think it was a string error, but I didn't write it down), then it crashes to desktop. When I try to relaunch, I get a "run-time error '380': invalid property value" I've reinstalled it and it runs fine, just when I do that (the quick answer is 'so don't do that') it kills the game. This has happened three times to me now, though. (kfgreer1961, 8 Dec 2004) Fix in 1.0b2 (if it works)

    The error is occuring in the modAirman.bas module, in the FillAirmanTabFields() function, on this line:

    .cboAssignment.ListIndex = prsAirman![Assignment]

    The airman's assignment is 7, but there are only six items in the combo. The problem though, isn't that his plane (Hunters Honey II) is not in the combo -- because it is. The problem is that I am using a keyfield (7) to do an index to an array. Rather than trying to find where that keyfield occurs in the array, then pointing at that array element.

    I'm not sure why I haven't run into that before, considering all the missions I've run. Especially since that piece of code is accessed on a near constant basis ...

    I think I have this licked, but need to test it some more ...

    Similar (same?) Issue: Preston - Getting a runtime error code of 380 - Invalid property value when trying to add crewman - don't understand why. I click ok and the emulator boots out. I may end up having to do a reinstall. (ixon, 30/Jan/2005, 10:09)

To Do List

These mods are going to have to wait until v2.0.

  1. Add Tom Cundiff's 9th and 12th AF North African bases variant. (That is where Ploesti was launched from.)

  2. These purple mods have similar issues.

  3. Shuttle missions from England to Russia or Italy, and Italy to Russia.

  4. ALTERNATE TARGETS: This will require a DB mod for designating/determining an alternate for each target.

  5. Crashland in neutral territory if it is within fuel range: Sweden, if the target is Kiel, Heide, Tutow, Peenemunde, Swinemunde or Stettin; Switzerland, if the target is Friedrichshaven, Munich, Augsburg, Ulm, Bingen, Mulhouse, Dijon or Lyon; Russian territory, if the target is Berlin, Dresden, Salzburg, Prague or Pilsen, and the date is January, 1945, or later. (option)

  6. Print a damage summary after the mission ends.

  7. Change the look of each maintenance tab to contain a spreadsheet, so the user can see/modify more than one record at a time.

  8. Create screen to allow the user to manually set fighter cover, rather requiring random fighter cover. (option)

  9. Add sound. This may be difficult as testing with about a half dozen different techniques (including Windows APIs) has proven very unsatisfactory.

  10. Use alternate B-3 tables. (option)

  11. TODO: add a save button with an actual save file dialog to the mission log RTF box.

  12. Mission save should generate bomber-specific positions, ammo, etc.

  13. Implement awards system. (The current awards fields are place holders created for this future feature.) Make the awards compliant with those that existed from 1942-1945. Maybe use "Hero Points", accumulated during the mission for different acts, as a measure of what awards to give out.

  14. Use British terms where British planes are used.

  15. Record missions, histories, etc. to some sort of log file.

  16. Track more bomber-specific stats.

  17. Save mission that is in progress. (aka, 'cheat' feature)

Help Index

© Copyright 2002, 2010 by Preston V. McMurry III, http://www.prestonm.com