Official TouchBuddy Forum - View Single Post

Primaryman · 12-20-2007, 10:10 AM

Psykick,

I've been playing with a new version of the Bombsite calculator that WBK has sent to me and I have found that I get the same error message. Here is the full procedure I used to repeat the error.

1. Launch TB
2. Select IL2 profile and "Lets Go" (In local Mode)
3. Go to Bomb tab straight away
4. push mph>kph button first without any other inputs.
5. Crash with following:

6. After clicking OK program continues to run but with a white box as you discribe.

I have sent a detailed beta report to WBK stating all I found but I did find that when you go to the BOMB TAB for the first time that if you enter some values into the IAS and ALT boxes before clicking the mph>kph button clicking it doesn't cause the crash and the program continues to run fine. Remember that this is with v1.1.0 of the calculator so earlier versions may behave differently but it is worth a try.

Please tell us how it all works out and hopefully we can get this bug squashed.

12-20-2007, 10:10 AM	#7 (permalink)
Primaryman Junky Join Date: Jul 2006 Location: Auckland, NZ Posts: 80	Re: Bombsight Problems Psykick, I've been playing with a new version of the Bombsite calculator that WBK has sent to me and I have found that I get the same error message. Here is the full procedure I used to repeat the error. 1. Launch TB 2. Select IL2 profile and "Lets Go" (In local Mode) 3. Go to Bomb tab straight away 4. push mph>kph button first without any other inputs. 5. Crash with following: 6. After clicking OK program continues to run but with a white box as you discribe. I have sent a detailed beta report to WBK stating all I found but I did find that when you go to the BOMB TAB for the first time that if you enter some values into the IAS and ALT boxes before clicking the mph>kph button clicking it doesn't cause the crash and the program continues to run fine. Remember that this is with v1.1.0 of the calculator so earlier versions may behave differently but it is worth a try. Please tell us how it all works out and hopefully we can get this bug squashed.