4.10 Support & Bug Reporting

[Aviar]

Originally Posted by Roblex

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?

In the test mission I posted above, the tower will turn the lights on when you get within approximately 5km.

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

[Roblex]

Originally Posted by Aviar

In the test mission I posted above, the tower will turn the lights on when you get within approximately 5km.

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

It could be... you will not get a 'Rodger' from the tower if you ask for the lights before you pass the last beacon. I will try removing the beacons and see what happens.

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.

[Nicholaiovitch]

Originally Posted by Roblex

It could be... you will not get a 'Rodger' from the tower if you ask for the lights before you pass the last beacon. I will try removing the beacons and see what happens.

UPDATE
I removed the blind landing vehicle and 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.

I have done a little research on this issue and posted on the Mission Building forum at UBI about it.

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

[Roblex]

Originally Posted by Nicholaiovitch

- 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

The issue with the lights is not connected to the ILS system as I removed the ILS and all other beacons from the game (and checked the mission file to see akk had gone) and the lights still turn on at 1km.
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.

set the properties of the lights to same color of the base...

Bionde: The lights would not turn on at all if the colour was not set (to be accurate; they would be on constantly)


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!

[Belly]

Hello,

In first, thank you for the job you did with this 4.10

I may inform you that I found a strange thing on the map "Bessarabia":
In sector AS23, few thousand meter south to the monastery Orhei and multi colour band appears. I have checked nothing particular on the 4.09.

Best regards.

Belly.

[NN_LUSO]

Question (may be stupid), but this is not normal with PropPitch 100%, to always have the same engine speed (2700 rpm) with 100%, then 90, 80, 70, 60%, I had to reach 50% for 2650tr, then 2500 to 40%.

[45th Texas]

Yes, seems the position or, presence of becons or, angle of decent does not effect the distance that the lights are turned on. I also tried extending out the lights but not much improvement. Then by accident I turned the whole approach system around and landed from the opposite direction and bingo...could turn on the lights just after the first beacon sounded. This was with the B-25. Seems to be connected with the runway characteristics. Other runways were fine when first tried.

45th Texas

[EJGr.Ost_Caspar]

Originally Posted by Belly

I may inform you that I found a strange thing on the map "Bessarabia":
In sector AS23, few thousand meter south to the monastery Orhei and multi colour band appears. I have checked nothing particular on the 4.09.

Can you pls make a screenshot. Nothing was changed on that map.

[SkyFan]

Dear DT members, next issue concerns playback of ntrk-records created before. As you can see the visualization of bomb's explosions existed earlier in 4.09m and others previous versions is absent during watching the same ntrk-records in 4.10m.
Please compare two attached images: 4.09m (to left) with explosion and 4.10m (to right) without it in the same record.
Is it possible to solve described issue?
Thank you beforehand.
Sincerely.

[Roblex]

Originally Posted by SkyFan

Dear DT members, next issue concerns playback of ntrk-records created before. As youy can see the visualization of bomb's explosions existed earlier in 4.09m and others previous versions is absent during watching the same ntrk-records in 4.10m.
Please compare two attached images: 4.09m (to left) with explosion and 4.10m (to right) without it in the same record.
Is it possible to solve described issue?
Thank you beforehand.
Sincerely.

The tracks actually play the mission again rather than just play a movie. This means that a skip bombing attack that worked in 4.09 will fail when played back in 4.10 due to the 2 second arming rule introduced in 4.10. Even in 4.09 you will sometimes see a mission played in 4.09 will fail when played back in 4.09M. I can remember playing back a mission played in Stock 4.09 but this time with Mods turned on and the plane missed the runway and crashed when in stock 4.09 it landed OK.