Bombsight BZG-2
 

Hi all!

First of all: Thanks TD by your great work, and warm congratulations!:cool:

I've found a problem about the bombsight BZG-2 (it's not a bug).

What if a player needs to perform a recallibration of the bombsight before his bomber reaches the target?


Actually there is not a way to do it after the command "Bombsight Automation" is turned ON by the first time within the mission; and many things could happen: sinking of the plane, changes of TAS, miss of the chosen landmark by clouds, etc.

The Bombsight Automation of the BZG-2 works like a stopwatch; the elapsed time between the ON/OFF switching is computed together the input Altitude to solve the TAS internally, and finally we get the Drop Angle as output. Right?

Well... IMHO we would need a command "Reset Bombsight" to restart the BS callibration as many times as the player needs. By now, the only way to do it is... reflying the mission.:?

You can reset the sight without a reset command.
POST UPDATED WITH NEW INFORMATION: See the proposed solution here.

What you need to do is follow the PDF for the FIRST angle, right?

And after your first run, you need to realize that YOU have to reset the bombsight yourself.

I've had the best success with the following

1. CLOSE your bombay doors.
2. Turn ON bombsight automation again until the hollow triangle (4) has made it's way counter-clockwise and stops. Wait a couple of seconds
3. Turn OFF bombsight automation. UPDATED: NO! See the proposed solution. Do NOT turn off bombsight automation. It will turn itself off.
4. Follow the INITIAL procedure as outlined in the PDF.
5. Make sure you remember to open the Bombay Doors again.

HOWEVER, I've had mixed success with this. Normally if I "re-do" the procedure no matter what the bombsight angle is off by about 15 degrees and bombs almost always land 100-200m LONG of the target.

I'm posting a track for the developers to confirm. Maybe *I* am doing something wrong.

I found that, once I put in the Course Autopilot hotkey, the intervalometer became usable. That little suggestion helped me a lot, thanks!:)

Hi Tolwyn!

Thanks by your advise: I've tested your method, and it works fine. 8-)

About your "red" comment, I'll test it also for to watch the outcomes by myself. But let me ask you: What was your altitude? Were you flying with wind or without it?

Mission attached.

I've been testing this and my outcomes are quite similar than the yours... it seems the BZG-2 actually admits one callibration per mission only.:-|


After the first callibration, I followed your procedure for a second one. But I included the #2 action indicated below:

1) Close bombay doors.
2) Set BS elevation to 0.
3) Switch BS automation ON. (The hollow triangle turns counter-clockwise to its starting position)
4) Switch BS automation OFF once the hollow triangle stops.
5) Look for a new landmark, and restart the callibration following the manual's procedure.

... And always the output is a smaller BS angle than the first, no matter if the BS angle was 0 before the second try or any other value. So, the bombs fall LONG.

My tests were done with 4 x SC250 bombs, 100% fuel load, and steady TAS and altitude along the whole pad.

I'll repeat my tests with your mission data. But surely I'll not get better accuracy than you.

Ok. I had another post here, and I deleted it in favor of this one.

I believe I have this one solved. My mistake was assuming that when resetting the (4) Hollow Triangle back (refer to the readme PDF) to its original position, you should manually turn Bombsight Automation OFF again. YOU DO NOT. It automatically turns itself off. So, after you send the triangle back to its starting position with the Bombsight Automation ON command, DO NOTHING. It'll turn itself off.

There is a NTRK recording attached to prove that this is indeed CONFIRMED.

So, the updated procedure is:

1. Calculate the angle as outlined in the PDF for your first run.
2. Drop Bombs.
3. At your discretion, close your bombay doors.
4. Toggle Bombsight Automation ON until the hollow triangle (4) has made it's way counter-clockwise to its initial starting position and stops. Bombsight Automation will turn OFF automatically (you don't need to do anything).
5. Calculate the angle as outlined in the PDF for the next drop
6. Repeat for any subsequent drops.

Yes! That works!;)

I was a bit confused because when the hollow triangle stops after the reset, the sound of the little motor of the BS can be heard yet. So I thought it was necessary to switch the BS Automation to OFF. But we only need to wait few seconds and the device will switch OFF itself.


Thanks by your research! :cool:

Yup. Me too. I'm glad we got it figured out and that it's not a bug or anything. Maybe just a documentation addendum.

I'm not sure if it's ever been brought up, but here are a couple of bugs that I've taken note of, and that have been in existence from at least 4.07 (the first version of IL-2 that I bought/played):

First, there seems to be an issue with a couple of the loadouts on the B-29. When set to 12x1600lb bombs, when they're dropped only 6 bombs are released and after that the bomb bay is empty. I'm wondering if the 6x1600lb loadout was simply duplicated without actually doubling the number of bombs.

Additionally, when set to 20x1000lb bombs, the bombers will only drop 10 bombs (half the loadout), but the bomb bay will still have the remaining half. A second ground attack waypoint, located at least a few kilometers away, is needed to get these other bombs to be dropped. However, when using other 20xX loadouts (e.g. 20x500lb), the full loadout is dropped without need for a second ground attack waypoint.

Another issue that I've encountered is in the QMB: I've noticed that, for whatever reason, the Ta-152C and the Ta-183, when loaded with X-4s or R4Ms, will simply continue to fly their routes without attacking, even when the opposing (player's side, specifically) planes are entirely bombers/transports. This same problem also affects A6Ms equipped with bomb-rockets.

I'm not sure if any of these have ever been brought to your attention, but I figured that I should do so just in case.