FMB Memory Issue? BF 109 E4
 

Sluggish performance when working with waypoints for the BF 109 E4:

Create a waypoint or two in the FMB of a BF 109 G2 for starters.

Change that plane to the BF 109 E4.

Select different waypoints and try to move them around.

I get a 2 second delay when selecting waypoints or when trying to move them; seems to affect switching to the BF 109 E4.

Remember, the He-111 was designed as a medium bomber, so with maximum normal combat load of fuel and ordinance it should still take off and fly reasonably well.

By contrast, the Bf-110 was designed as a heavy fighter, with smaller wing area and higher wing loading, so turning it into a long-range strike/convoy escort fighter by attaching a huge drag-inducing fuel tank to its belly and loading up with bombs is going to seriously impair its handling.

More importantly, most of the He-111H series had more powerful engines than the early Bf-110s (2 x 1,300 HP engines vs. 2 x 1,085 HP for the Bf-110). As you observed, the extra HP really come in handy on take-off and landing.

Hello TD. I don't know if someone has already reported it but the BK 3.7 pod on the bf-110 G2 is aiming half a notch too low no matter how the gun convergence is set.

I have to report a bug! I have a problem with the U2VS (LNB). When I tried out the game after downloading and installing the game I tried the U2VS (LNB) out with the diffrent skins inkluded and everythhing worked fine. But now ,from my second game session since updating only the default skin works. If I choose any of the other skins the entire aircraft appears completely white, both in game and in the arming window.

I have had the same problem, are you using a custom 24 bit skin by any chance (its also possible that one or more of the new custom skins for the U2 loaded by TD is a 24 bit), reducing the skin to the older lower bit format will stop this problem from happening, I have already posted this issue with at the TD beta forum, but at least I now know it is not only me that this is affecting.

By the way even though it is blank in the arming screen, if you proceed to the mission the skin you have picked will load correctly.

Edit..... OK just checked, and it would appear that the U2SLNB - Summer 45, Summer 44 and the all the U2 voids are all 24 bit, if you avoid choosing those then you should be able to see the skin you've selected in the arming screen, you may have to launch a mission and go back before it resets though.

This doesn't seem to be a general issue, see video of the same sequence without issues here:
www.youtube.com/watch?v=hV1DFOOngTQ

Best regards - Mike

It seems that the landing light has been deleted from the Bf-110G-2.

G'day Mike

For me it only happens if you re-enter the arming screen before or after a mission, the is no problem with the skin in the mission just in the arming screen.

My sequence to make the issue occur 100% of the time:

1. Load sim
2. Open QMB
3. Select U-2VS (LNB) 1942 (nation or side does not make a differnce)
4. Enter arming screen
5. Select skin summer44.bmp select (skin displays correctly in spin window), select apply.
6. After returning to main setup screen re-enter the arming screen, when arming screen opens the aircraft is in the spin window but now is devoid of any skin (with the exception that the game generated markings and pilot skins, machine gun and the cockpit interior seem to be unaffected as seen below).

http://i94.photobucket.com/albums/l116/305th/blank.jpg

PS. Check PM log file sent.

Thanks Spudkopf, we're getting closer.
You have reply to your PM ;)

Best regards - Mike

Can we have some more details please.