![]() |
|
#1
|
|||
|
|||
![]()
May have been reported already, but if you are in a Jet (Ar-234 and He-162 tested) and you let the AI takeoff, the engines will catch fire. Curiously, the other AI planes (non-player) this doesn't happen, only your own plane.
|
#2
|
||||
|
||||
![]() Quote:
Aviar
__________________
Intel i7-4790 4-Core @3.60GHz Asus Z97-C Motherboard 16GB DDR-3 1600 SDRAM @800 MHz NVIDIA GTX 760 - 2GB Creative SB ZX SBX Logitech X-530 5.1 Speakers 27" AOC LED - 2752 Logitech G15 Gaming Keyboard CH FighterStick-Pro Throttle-Pro Pedals Logitech G13 Gameboard GoFlight GF-T8 Module WIN 8.1 |
#3
|
|||
|
|||
![]()
Not a really big deal, would be if it happened to the non-player planes (obviously).
|
#4
|
|||
|
|||
![]()
BUG: In an online game using a dedicated server with multiple targets for both sides to destroy, the game erroneously announces "RED WON" or "BLUE WON" when there are still many targets left to destroy.
I have never seen this announcement before in the online game, even though it is common in the offline game. It is very confusing as everyone stops playing, thinking one team has won, when they haven't. I have looked carefully at the target setup and can't see the problem. This has occured on more than one map. Here is the relevant section of the .mis file from one of them. This map announced 'RED WON' when Red had not won. If there is something I need to do differently in in the mis file, please advise. If not, this is a bug. [Target] 1 0 0 0 500 126561 151887 500 1 0 0 0 500 67550 158981 500 1 0 0 0 500 108473 235433 500 1 0 0 0 500 71583 224151 500 1 0 0 0 500 68763 220959 500 1 0 0 0 500 78701 206214 500 1 0 0 0 500 83588 208925 500 1 0 0 0 500 72772 196655 500 1 0 0 0 500 95995 211405 500 1 0 0 0 500 85077 183711 500 1 0 0 0 500 90794 184815 500 1 0 0 0 500 87141 167354 500 1 0 0 0 500 96864 164910 500 1 0 0 0 500 102221 152155 500 1 0 0 0 500 106744 154120 500 1 0 0 0 500 62526 216413 500 |
#5
|
|||
|
|||
![]()
Av,
Thanks very much I'll give them a try. ian |
#6
|
|||
|
|||
![]()
G-forces: Does turbulence create G-forces in IL-2 engine, or is it cosmetic? Will turbulence encountered at the end of a dive, cause the aircraft to break into pieces?
|
#7
|
|||
|
|||
![]()
Example mission (attached) showing a bug with "Test Runways" placed on land
(this bug arises online at all connected players) With 4.10m "Test Runways" do not work, if their centre is over a land (airfields at K-14, L-14, M-14 in attached mission). All players throws up in air and nobody can normally take off with such "Test Runways". With 4.10m "Test Runways" work as usually if their centre is over water (airfields at K-13, L-13, M-13 in attached mission). All players appear on a strip and can normally take off from these "Test Runways". All these "Test Runways" (no matter: over land or over water) worked fine with 4.09m. Players did not throw up in air with 4.09m. Note: height is 0 meters for all places, everywhere a horizontal flat surface. But "Test Runways" placed on land does not work correctly with 4.10m (with patches 4.08m/4.09m all was excellent). |
#8
|
|||
|
|||
![]()
4.10 is supposed to be installed only over a clean 4.09.
|
#9
|
||||
|
||||
![]() Quote:
Aviar
__________________
Intel i7-4790 4-Core @3.60GHz Asus Z97-C Motherboard 16GB DDR-3 1600 SDRAM @800 MHz NVIDIA GTX 760 - 2GB Creative SB ZX SBX Logitech X-530 5.1 Speakers 27" AOC LED - 2752 Logitech G15 Gaming Keyboard CH FighterStick-Pro Throttle-Pro Pedals Logitech G13 Gameboard GoFlight GF-T8 Module WIN 8.1 |
#10
|
|||
|
|||
![]()
Still having no luck with recon. And you can assign a Komet as recon but not a Fw-189. How is that?
|
![]() |
|
|