![]() |
#91
|
||||
|
||||
![]() Quote:
Nice piloting there El
__________________
GigaByteBoard...64bit...FX 4300 3.8, G. Skill sniper 1866 32GB, EVGA GTX 660 ti 3gb, Raptor 64mb cache, Planar 120Hz 2ms, CH controls, Tir5 |
#92
|
|||
|
|||
![]() Quote:
With Full throttle selected the only thing that is going to cause a prop pitch change is the change in TAS. This same TAS change is going to affect you (and the RPM/Prop) at the same rate whether you are in MANUAL or AUTO. In both cases blade angle needs to be changed ... either by you in MANUAL or by the aeroplane in AUTO. In both cases it can only be done at the same Blade angle change rate. IMO it copes exceptionally well with the TAS changes even in rapid descents. So I don't see how it messes up the prop. Be specific exactly how do you think it messes up the prop ? Its no good just saying it "sucks until they fix it up" If you think there is something wrong that needs fixing then be specific Test/Prove and document the issue. So far you have not done that. The level speed tests proved beyond doubt that AUTO was as good as Manual. I believe exactly the same for climbs etc. I use AUTO On line in combat .... and at any time I have max throttle selected. All my Squadmates do the same. If I need/want a differrent RPM to what AUTO will give me when less than full throttle like in a 1.25ATA climb with 2300RPM then I select Manual. As soon as Full throttle is selected I go back into AUTO. Same in combat. So lots of people are using AUTO quite successfully to reduce workload and still get as good performance as you can get in manual. Its a tool to be used as and when required. Key to using it properly is understanding how it works and then applying that knowledge to the task. Last edited by IvanK; 10-27-2011 at 10:26 AM. |
#93
|
|||
|
|||
![]() Quote:
The only issues I have regard the weird behavior before doing the auto - manual - auto sequence described above. After that it keeps pace finely. Cheers, 6S.Insuber |
#94
|
||||
|
||||
![]() Quote:
![]() |
#95
|
||||
|
||||
![]() Quote:
http://forum.1cpublishing.eu/showthread.php?t=27201 make sure your pp lever is in neutral position when you spawn (that's an issue online) and also make sure you take off at fine pitch. The PP drop is easy to overcome and that way, you get auto PP just as it worked in RL including it's behaviour under 1500RPM. ![]() |
#96
|
||||
|
||||
![]() Quote:
The only time I use manual is when trying to do sustained climbs at low speed. Even then, not always. With WEP/overboost and at a shallow angle you can still outclimb the RAF guys. Maybe not the Hurri if you're way up high. |
#97
|
|||
|
|||
![]() Quote:
![]() Not the way you want, but you made my day! Hope to see you another time in the air ![]()
__________________
AMD Penom ll 6x 1055T Processor 2.8 GHz // 8GB Ram // XFX Radeon HD 7870 Black Edition DD (2048 MB Memory DDR5, GPU 1055MHz) // Windows 7 Professional 64 Bit Version Saitek x52 // Saitek Throttle Quadrant // Saitek Pro Flight Rudder Pedals // Track IR 5 |
#98
|
|||
|
|||
![]() Quote:
2100/1.05 900PS Economic cruise 2300/1.15 1075PS Max continuous 2600/1.3 1310PS 30Min Climb and combat 2800/1.42 1475PS 3Min Emergency Obviously differrent values to the DB601 but it will give you an idea of the sort of relationships between ATA and RPM in AUTO. Remember AUTO RPM is determined by throttle lever position NOT ATA. Obviously below FTH then ATA is also determined directly by throttle lever position so in effect they are the same. The numbers I have seen in CLOD DB601 (below FTH) for the AUTO ATA/RPM relationship are: 1700/1.00 1800/1.1 1.2/1900 1.25/1950 1.3/2050 1.35/2300 1.42/2350 We know the min governed RPM on the DB605 is 2000RPM. This effectively the Min RPM pitch stop. I suspect the DB601 in real life is the same (yet to confirm). If this is the case then it does suggest the CLOD ATA/RPM relationships for 1.0 to 1.2 are a bit low. If some one has documented DB601 values it would help getting this tweeked. The bug on spawn in the E1-E3 and on the E4 when you select MANUAL of the prop winding back is a known bug and hopefully will be addressed. The fix is a quick blip to stop the windback. Re set 12:00 and then you are good to go. I do this this every engine start. I take off in MANUAL (12:00) I select AUTO once I get airborne. Using this technique I have never seen the prop slowly winding back to 8:30 and getting stuck. Last edited by IvanK; 10-27-2011 at 09:01 PM. |
#99
|
||||
|
||||
![]()
Nice one IvanK!
Is it known if the DB 601 'Aa' or 'A' engine is modelled in the E-4? Unfortunately, I don't know what the min governed RPM for 601s was, might as well be lower than 2000RPM. It is great to see all these small issues being addressed and fixed (mind you we started with a E-3 with lever not returning to the central position and now we have got a working Luftschrauben-Verstellautomatik ![]() In order to fine-tune the FMs, it would be great to know which engines and which propellers are being modelled for each subvariant. Easy enough with the propellers - 9-11081E for E-4 and 9-11081A for E-1 and E-3, but the engines in E-4s did quite a difference regarding max ATA / RPM, from which appropriate RPM drop could be calculated as the pilot moves the throttle back gradually. |
#100
|
||||
|
||||
![]() Quote:
|
![]() |
|
|