![]() |
|
#1
|
|||
|
|||
![]()
The P40-M now has mixture control, where you can set the mixture at 100% or 120% However, switching it to 120% even at sea level stalls the engine. Is this a bug?
Other US planes with mixture control like the F4U can fly with 120% mixture to an altitude of a couple hundred metres or so, so can Zeros, Soviet planes usually reach 1500m at 120% mixture before their engines start to smoke. |
#2
|
||||
|
||||
![]()
Bug, fix ready for 4.12.1
__________________
|
#3
|
||||
|
||||
![]()
Would be nice if we could get the rest of the mixture stands from 0 to 99% too for the P40 as well as other planes.
Maybe in a future update? ~S~ |
#4
|
|||
|
|||
![]()
Guys, I have found a bug by casual testing the QMB.
I have set a 4 x 4 planes on my side, some Vals, Zeros, Ki-21 and some more Vals with the mission to attack something above the waves. The initial attack was absolutly bugfree, but after I have ordered the whole bunch of planes to return to base. The wired things started. The Zeros were landbased types and the Ki-21 was never planed to be carrier capable. So they start to land their bellys on the deck of the japanese carriers that were floating around. The Zeros had no problem to land without the Tailhook, all was fine and they disapeared as they should. The Ki-21 landed also save on the decks and disapeared, only one broke his neck as the plane hit the deck a bit harder than the others did. But also the result was satisfing. Now the Vals, the carrier plane of this mixed flight. Had serious problems to keep the gear on the deck of the carriers after landing, they all start to roll of the deck to the right side and explode. Just slip to the right. There is a bug with the Val, havent tested it with other planes but I would like to share it with you guys. Maybe leave the "choks" activated after landing or dont let the planes slip from the deck?! |
#5
|
|||
|
|||
![]()
1.)
On any 2 engine airplane with auto/manual prop pitch, deselecting one engine and switching to manual prop pitch also switches the other engine (this in itself is correct? a limitation of il2?), but enabling auto pitch again only affects the current selected engine, so the unselected engine could quickly become unusable , pretty bad when one engine is damaged , you put it in lower power and control the other one , then switching to manual prop pitch then auto again will most likely kill it. Planes affected: only bf110 and bf109z come to mind (I lost all overview) 2.) There still seems to be an issue with using the autopilot for your own plane and AI airplanes (I reported this 2002 directly to oleg and he blamed dinput, but now so many parts of my system have changed , nothing is the same , only the bug!), so maybe someone from AI coding can finally look at this: Create a quick mission with maximum number of airplanes, preferably ones that will drop flaps while turn and burning (some bf109 and or yaks will do), now enable autopilot for one second, after disabling it , drop flaps 1 notch (combat), try not to get shot , simply fly some manoeuvres around all the AI and let them fight. At some point you will notice that your plane will probably yank around (while pulling a constant turn) and/or you flaps will retract automagically (no , not f4f style ![]() ![]() I suspect some commands override your own control , this happens only if there are many AI , or the effect is more pronounced / more frequent, it maybe happen synchronously while another plane retracts flaps, but I couldn't be exactly sure watching the tracks. This also happens when using the black screen skip autopilot 1 time in campaign with many AI planes in the mission as it uses autopilot and time compression. (track shows simple pre combat , I enable/disable the autopilot and drop flaps 1 notch , as soon as AI call out enemy planes they retract, no axis mapping for flaps and no hud message for retracted flaps!) |
#6
|
|||
|
|||
![]()
Can't find it via search but the Super 2 setting actually gives you better Power in both the Corsair and Hellcat at low alts.
|
#7
|
||||
|
||||
![]() Quote:
My advice to you.....never Unselect an engine. Simply Select the engine you want to control. Try that and see if you still have the same issues. 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 |
#8
|
|||
|
|||
![]() Quote:
![]() |
#9
|
|||
|
|||
![]()
This is a new issue I think introduced with mulit-throttle control.
I have to categorize it as a bug as well. I've posted a few times about the same thing with no response. I always UNSELECT an engine to SELECT the other engines?? I didn't understand your quote at all. http://forum.1cpublishing.eu/showthr...805#post472805 |
#10
|
||||
|
||||
![]() Quote:
![]() Quote:
Quote:
Quote:
__________________
|
![]() |
|
|