![]() |
#381
|
|||
|
|||
![]()
Real life ammo count is exactly the effect of that difficulty switch. Maybe you're lucky to be in aircraft that carry large amounts of ammo, or you're just an incredibly good shot so that you simply don't need a lot of ammo.
Planes that are fairly short on ammo are the Yak's, if you want to try them. |
#382
|
||||
|
||||
![]()
In IL2 1946 4.11m version.
Some static objects like AAA guns or cannons respawn after being destroyed. It happend that I destroy some static objects. I shoot them. They burn. Server display Ennemy AAA destroyed. After some time they respawn and open fire again... Is it a bug. If yes is it fixed in 4.11.1m ? Thx all for your great job. |
#383
|
|||
|
|||
![]()
I assume you're playing online.
The host can implement an AI respawn time into the mission. There is no bug. |
#384
|
||||
|
||||
![]()
Thanks Luno13.
I found the parameters in the [RespawnTime] section. |
#385
|
||||
|
||||
![]() ![]() Last edited by FenbeiduO; 04-27-2012 at 09:53 AM. |
#386
|
|||
|
|||
![]()
4.11.1 AI / Jet bug:
Jets like He162 and Me262 can't take off anymore. They overheat when they're half way the runway and have diffculties gaining altitude. They fail to climb and/or their engines catch fire. Tested with he162 and single mission 'rapid strike mission'. With the rapid strike mission, the first he162 cannot gain sufficient alititude and crashes into the woods at the end of the runway. edit: small correction. Bug is also present in 4.11 + hotfix. Base closure with YP80 catches fire when taking off and 'rapid strike' mission produces the same result. I.e. he162 is unabnle to take off and it's engine starts to burn. Rgs, Mark
__________________
Intel Core i7 2600 @ default clocks MSI P67A-GD65A Motherboard Vertex2 SSD Raid1 1 Tb data disk 8GB DDR3-1600 MSI Geforce 680GTX @ default clocks Hotas Cougar X-Fi Music Last edited by Fall_Pink?; 04-28-2012 at 03:33 PM. |
#387
|
|||
|
|||
![]()
I just made tests and I have no issues with the jets. Make sure to increase power slowly. Too fast and the engine will catch fire.
Also, I tend not to add more than 80% power, to avoid overheating. Acceleration is slow, and jerking the plane off the runway won't help. I pull back on the stick just enough to raise the nose. The plane will roll on the main wheels until it's "ready" to fly, and will lift off on its own at the right speed. Raise gear immediately, lower the nose to accelerate and raise flaps in increments. |
#388
|
|||
|
|||
![]() Quote:
Manually there will be no problem with any jet I guess and I think it's the auto pilot that messes it up some how. I tested the he162 'rapid strike mission' with auto pilot enabled for take off. I checked a couple of times and nearly all of them crash into the hillside. Please check if you get the same behavior with this mission. Rgs, Mark
__________________
Intel Core i7 2600 @ default clocks MSI P67A-GD65A Motherboard Vertex2 SSD Raid1 1 Tb data disk 8GB DDR3-1600 MSI Geforce 680GTX @ default clocks Hotas Cougar X-Fi Music |
#389
|
|||
|
|||
![]()
The Heinkels indeed crash, but it already happened in 4.09. Do you know the last version it worked with? Overheat in 4.11 came too quick for some jets, but this was corrected in 4.11.1 and should no longer be an issue. I haven't seen one catching fire on take off, yet.
|
#390
|
||||
|
||||
![]() Quote:
I tested the Rapid Strike mission and the jet AI all take off just fine. However, they do crash into the hill. This may be due to new FM's. I tried a quick workaround and it worked. Just open the mission in the FMB and give all the 262 and 162 flights 65% fuel instead of 100%. This makes them lighter and they don't crash anymore. 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 |
![]() |
Thread Tools | |
Display Modes | |
|
|