![]() |
|
|
|
#1
|
|||
|
|||
|
Quote:
sry my bad english |
|
#2
|
||||
|
||||
|
Not an important bug but in the He-111 H-12 there is a problem in the lods transition when engines are off: check the prop position in the external view (press F3 with engine off), it changes during the lods transition.
|
|
#3
|
|||
|
|||
|
Hello everyone again!
I think I've just found a Spitfire FM issue. Nearly all of IXc Spitfires: both F. models, Mk.IXc, and L.F.Mk.IXc with clipped-wings have a mass of about 3390 kg (3387.54 to be exact). However, L.F.Mk.IXc with non-clipped wings is 118kg lighter, which looks quite illogical compared to the planes with the same airframe I listed above; besides, that gives him a climbrate of ~26 m/s at sealevel. I guess that'd be a little too much even for this great airplane. Hope it'll be fixed EDIT: Just looked through other new spits: it seems that L.F.Mk.IXe-25Lbs-CW has a similar bug. It weighs 3270kg only, while L.F.Mk.IXe-18Lbs-CW has a mass of 3440kg - 170kg difference between two differently boosted planes which are identical in all other aspects. Last edited by SDPG_SPAD; 12-29-2010 at 06:29 PM. Reason: addition |
|
#4
|
|||
|
|||
|
Is it it a bug in 4.10 or a deliberate decision or a mistake in the mission itself that the runway lights in the B25 Blind Landing mission do not turn on until it is too late to help?
I edited the mission to use brighter lights so I could be sure when they switch on and it seems they wont turn on until your are 1000m from the threshold ![]() It sounds like a good distance but on approach it is not as seen from this cockpit shot showing that while I can see the red lights I added along the runway, the threshold is under the nose at 1K on level descent. ![]() and if you wonder if maybe the threshold lights are in the view but just a little too dim to see, here is an F2 view showing the bright type-4 lights I changed the threshold lights to ![]() BTW, I don't know if this is a bug but... even though the new FMB allowed me to select all the threshold lights, it would not allow me to change the type of the lights as a group. I had to select the lights one by one to change them from Type-2 lights to Type-4 lights. |
|
#5
|
||||
|
||||
|
Quote:
I did check the B-25 mission and you are correct. I don't know why the late response there...possibly connected with the nav beacons? 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 |
|
#6
|
|||
|
|||
|
Quote:
UPDATE I removed the blind landing vehicle and every beacon on the map (had to edit mission file as FMB refused to admit AR was gone) it makes no difference. The tower will not 'rodger' your request until you are within 2km and the lights do not come on until you are within 1km. 2nd Update I have been making a fairly shallow approach so I tried a higher approach (500m at the 4th waypoint) to see if line-of-sight was the problem but the tower still did not acknowledge my request until within 2km (actually 1.6) and the lights turned on at under 1km. Last edited by Roblex; 12-30-2010 at 12:36 PM. Reason: Updated information |
|
#7
|
|||
|
|||
|
Quote:
There are two issues with this mission...lights and position of the ILS tx object on the map. - The glidepath angle appears to be around 3deg which is correct. The acknowledgement "Roger" to turn the lights on will not be heard until about 300ft on final (just under 2km) so the lights are not switched on until very late. However, there is a further issue... - The object to transmit the signal for the ILS in this mission has been placed too close to the extended cetreline of the runway resulting in you being at least another 1km further out (a total of 3km) when you are on the glideslope at 300ft. If you follow the signal it will fly you into the ground 1km short of the runway. - It helps to re-position the tx object at least 500m futher out on the extended cetreline to get the glidepath correct to arrive at the runway. I believe this also helps in getting the lights to come on just a little sooner as you are now closer to the runway when at 300ft. It certainly helps to add approach lights (light4) in a line before the threshold, but an increase in the distance to accept a call for lights "on" in the new patch would certainly help....please? Nicholaiovitch |
|
#8
|
|||
|
|||
|
Quote:
It is also not related to altitude as I get the same results from a low shallow approach as a very steep high approach. I even tried turning on my landing lights in case it was a visibility problem as I know there is code to allow gunners to see aircraft further out if they have lights on. Quote:
Please can we have the lights turn on earlier? We know that in real life pilots used to ask for the lights to be flashed briefly so they knew where the base was and I am sure they would have been a lot more than 1km away. Even having the acknowledgement a lot earlier (5km?) would be a great help if you could get it in the bug fix release. When I am under 2km away from a blind landing nearing stall speed the last thing I want to be doing is fiddling with the Tab messages Maybe in 4.11 they could even flash the lights briefly when they acknowledge? I must say that, despite any niggles, I am extremely grateful for the work everyone put in. I am not so fussed about the new types of Spit etc but the navigation options and G limits etc. are great! Last edited by Roblex; 12-30-2010 at 01:03 PM. |
|
#9
|
|||
|
|||
|
Quote:
|
|
#10
|
|||
|
|||
|
A big problem: the Spitfire is now impossible to trim correctly.
This fact is not realistic at all ! Have you got any solution ?? |
![]() |
| Thread Tools | |
| Display Modes | |
|
|