Constructive explanation of issues

[KeBrAnTo]

I'm actually downloading the second patch (April 18th) and I cannot see anything on the README file related to the AI communications over the radio.

I still cannot believe this hasn't been fixed yet and we have no news about when will be done.

It is really appreciated the efforts from the dev team in order to improve performance but IMHO radio communications with the AI is nearly as important issue as performance.

No comms - no mission as simple as that.

[ubermachtig]

Holy crap,

I just decided to chase a few bombers over the channel, and literally saw a sunderland doing 3 corkscrews (or however they are called) within a single second! Heck, I can't even do that with a biplane... The AI must be cheating, or there is a bug in their flight model.

[b101uk]

I was playing in the FMB the other day and wind direction has a BIG error that wind is +90deg out!

i.e. one would assume that in the FMB that “0” wind angle would be North and -180 or 180 would be South and that 90 is east and -90 is west,

BUT if you set wind direction as “90” (90deg) wind comes from the south pushing you north (+90deg error), if you set wind at -90 (270deg) it come from the north pushing you south (+90deg error), if you set the wind to180 or -180 (180deg) it comes from the east pushing you west (-90deg error) & if you set it to 0 (0deg) it comes from the west pushing you east (-90deg error)

Ergo wind is either +90deg out for east/west or -90deg out for north/south even with the latest 1.00.14101 patch! (have just tested)

[Remo]

Saw someone noted that the flight level indicator showed 30 deg. inclination while flying in level flight in a Spit, BF110 has same issues.

1. Sometimes you can start a flight with level indicator functioning 100% , then suddenly it shows an inclination during level flight (usually after a steep turn, but very often after a barrel role) .
2. Display of all compasses (Gyro + Magnetic ) stopped (fixed on North) , if you mouse over the gauge it still indicate correct value though. This issue persisted over multiple missions. I could only get working compasses by restarting game.
3. Slight delay in control input ( especially noticeable with fire button ), when you just tap the fire button on the joystick I notice a fraction of a second delay (quite noticeable though) in both visual and sound of the rounds.
4. Is there some trick to eject from the 110? , Mapped the key etc but pilot cannot 'bail out' from 110.
5. Graphic corruption (or more precisely terrain corruption ) along the coasts and rivers, the game will render stripes of terrain into the water and stripes of water into the land this varies as view angle ,LOD, altitude change. ( this might be part of the frame rate issues ), it occurs on all maps I tested so far and occurs on all coasts. The corruption occurs with Land detail on HIGH and medium.
6. Regarding CPU usage (just a report). With affinity mask set to 254 ( 8 core system , excluding core 0) ,the game seems to make use of all the cores now ( 15 April Beta Patch ) , though the load on the the CPU's avg aroung 20-30% with one core spiking average around 90-100% (not sure if this is Windows+Drivers though since this was core 0). Still have some stutter around large towns / cities ( with Texture quality at High and MEDIUM )
7. Texture quality set at high or medium makes a huge difference on low vram cards , Frame rate increased from avg of 7 to avg 27 ( low over land ).

Spec : (15 April Beta Patch)
Mac Pro 2009 ( 2x quad core xeon 2.6Ghz )
48Gb ram
ATI 4870 ( 512MB )
Dual boot to Win7 64
(Joystick = Ch Product Fighter Stick).