Post by CoolP on Sep 4th, 2012 at 1:15pm
Hi, folks. :)
As you recall, we already did some research on other great CS planes like the 727, 707 and so on. Now, we are lining up with the 737 and I would love to discuss some items which are there in 1.0 and shouldn't be in 1.1.
So, if you like, help me to validate some items.
The purpose of this list is to show the remaining bugs with a description and a screenshot. Followed by a text of how it should be. To discuss the item and to check whether it is user driven or an across-the-board lack of function in the 1.0 737 is the last step.
After this verification, tickets have to be written to make sure the items can be processed through the Captain Sim Support. Naming things in this thread alone does not help.
Every verified item has to be set up as a ticket via Your Profile > Customer Support > Trouble Ticket System.
We are not talking about user made problems here, but general 737 bugs and flaws.
The numbers of items do not reflect any priority.
1) The pressurization. (That's an old friend :D)
a) the FLT / GRD switch doesn't have any effect and also starts in FLT while being on the ground.
b) You can dial in a cabin altitude, but the system disregards it and aims for 'some' pressure. One should be able to set the cabin altitude in regard to the small chart on the lower part (which I did) and then receive a cabin altitude aiming for a high differential pressure, so that the cabin alt is as low as possible. The Auto Mode should aim for that state by design but, as seen in the screenshot, goes for a 8000ft cabin and a low differential pressure.
Those 8000ft cabin altitude would be reached at FL370, not at FL300 from the example screenshot. The max differential pressure being 7.80/7.90 psi. With this, the cabin would be around some 5100ft at FL300. Note. This is from the Boeing scale, the CS one in the VC shows slightly higher cabin altitudes. Either way, they are well below 8000ft when cruising at FL300.
2) The TEST setting on the AC selector doesn't work.
3) The fuel temp goes down within minutes, even with full tanks. While a failure isn't simulated, it should take way longer for the fuel to reach warning levels.
4) The Flight Director. Well, we know that one from the 727 and 707. In short, I'm sure he points somewhere, I just don't know where. Seriously, the FD should work on NAV and especially APP. It doesn't. :-/ It shows the HDG only.
5. Correct me if I'm wrong, but I think the clock should show UTC, not local. Well, I can't change the setting. So maybe one could add some feature to allow for a switch.
6. KG or LBS, don't mix them. I love the sharp appearance of the gauges, but it doesn't make sense to use LBS on the fuel gauges and KG on the total fuel and Vref indicator. The PDCS works in LBS too.
7. This leads us to the next item, the total fuel and Vref indicator. The one on the plane doesn't work. The needle does not show proper values, especially when the flap selector (2) is moved (the selector itself stays static in the VC, but one can hear the click) Also, there seems to be a mixup taking place when altering the fuel load setting. At certain values, the needle 'jumps' some 20 knots. Details here at item 3. http://www.captainsim.org/yabb2/YaBB.pl?num=1335036741
8. I once forgot about the pitot heat switches and my airspeed and things always worked. So my guess is that the switches only work the lights, not the pitot heat system.
9. A difficult item to describe. The rate at which the AP intercepts a commanded heading is very slow. Also, it seems to start the roll-out way too soon and then approaches the commanded heading at a very, very shallow bank angle.
The AP reduces the bank angle some 20° before the commanded heading. At some 10° before the commanded heading, it reduces the bank angle some more and at some 5° away, I'm looking at 3° of bank which takes ages while at cruise speed. The 707 shows a similar behaviour by the way.
20° out.
10° out.
This makes VOR navigation and following a course very difficult. I'd expect some 25° of bank and a later roll-out phase really aiming for the commanded heading, not fearing it, so to speak.
10. The audio panel in the VC and the 2D popup are not in line on e.g. the marker audio. Turning it on in the VC doesn't give you the marker sound, one needs to use the 2D popup to get the audio. Besides, I think the plane deserves more than a default radio popup.
11. Engine behaviour and default thrust settings.
On the engine behaviour, I would expect some slow spool up at low rpm and a faster one at high settings. Even more so on low-bypass engines which do not incorporate a huge fan in the front. On the current CS737, this behaviour is reversed. :-/
I know, one has to pull many tricks on the FSX jet engine basis to allow for this and that, but the slow-ish spool up/down really is a source of trouble on the approach where the rw engines would be kept in the state of being able to react faster.
As for the default thrust setting in the aircraft.cfg, I'm thankful for the user mods like the one from Bud. However, maybe it's possible to see those changes in 1.1, leading to a more reasonable performance of the plane, not the current rocket-alike. :D
If you have more stuff or points on the current list, please help. Some other folks have already set up threads, so I'm thankful for their input too, to make 1.1 even better. :)
On items already being reported, see the next post. in
As you recall, we already did some research on other great CS planes like the 727, 707 and so on. Now, we are lining up with the 737 and I would love to discuss some items which are there in 1.0 and shouldn't be in 1.1.
So, if you like, help me to validate some items.
The purpose of this list is to show the remaining bugs with a description and a screenshot. Followed by a text of how it should be. To discuss the item and to check whether it is user driven or an across-the-board lack of function in the 1.0 737 is the last step.
After this verification, tickets have to be written to make sure the items can be processed through the Captain Sim Support. Naming things in this thread alone does not help.
Every verified item has to be set up as a ticket via Your Profile > Customer Support > Trouble Ticket System.
We are not talking about user made problems here, but general 737 bugs and flaws.
The numbers of items do not reflect any priority.
1) The pressurization. (That's an old friend :D)
a) the FLT / GRD switch doesn't have any effect and also starts in FLT while being on the ground.
b) You can dial in a cabin altitude, but the system disregards it and aims for 'some' pressure. One should be able to set the cabin altitude in regard to the small chart on the lower part (which I did) and then receive a cabin altitude aiming for a high differential pressure, so that the cabin alt is as low as possible. The Auto Mode should aim for that state by design but, as seen in the screenshot, goes for a 8000ft cabin and a low differential pressure.
Those 8000ft cabin altitude would be reached at FL370, not at FL300 from the example screenshot. The max differential pressure being 7.80/7.90 psi. With this, the cabin would be around some 5100ft at FL300. Note. This is from the Boeing scale, the CS one in the VC shows slightly higher cabin altitudes. Either way, they are well below 8000ft when cruising at FL300.
2) The TEST setting on the AC selector doesn't work.
3) The fuel temp goes down within minutes, even with full tanks. While a failure isn't simulated, it should take way longer for the fuel to reach warning levels.
4) The Flight Director. Well, we know that one from the 727 and 707. In short, I'm sure he points somewhere, I just don't know where. Seriously, the FD should work on NAV and especially APP. It doesn't. :-/ It shows the HDG only.
5. Correct me if I'm wrong, but I think the clock should show UTC, not local. Well, I can't change the setting. So maybe one could add some feature to allow for a switch.
6. KG or LBS, don't mix them. I love the sharp appearance of the gauges, but it doesn't make sense to use LBS on the fuel gauges and KG on the total fuel and Vref indicator. The PDCS works in LBS too.
7. This leads us to the next item, the total fuel and Vref indicator. The one on the plane doesn't work. The needle does not show proper values, especially when the flap selector (2) is moved (the selector itself stays static in the VC, but one can hear the click) Also, there seems to be a mixup taking place when altering the fuel load setting. At certain values, the needle 'jumps' some 20 knots. Details here at item 3. http://www.captainsim.org/yabb2/YaBB.pl?num=1335036741
8. I once forgot about the pitot heat switches and my airspeed and things always worked. So my guess is that the switches only work the lights, not the pitot heat system.
9. A difficult item to describe. The rate at which the AP intercepts a commanded heading is very slow. Also, it seems to start the roll-out way too soon and then approaches the commanded heading at a very, very shallow bank angle.
The AP reduces the bank angle some 20° before the commanded heading. At some 10° before the commanded heading, it reduces the bank angle some more and at some 5° away, I'm looking at 3° of bank which takes ages while at cruise speed. The 707 shows a similar behaviour by the way.
20° out.
10° out.
This makes VOR navigation and following a course very difficult. I'd expect some 25° of bank and a later roll-out phase really aiming for the commanded heading, not fearing it, so to speak.
10. The audio panel in the VC and the 2D popup are not in line on e.g. the marker audio. Turning it on in the VC doesn't give you the marker sound, one needs to use the 2D popup to get the audio. Besides, I think the plane deserves more than a default radio popup.
11. Engine behaviour and default thrust settings.
On the engine behaviour, I would expect some slow spool up at low rpm and a faster one at high settings. Even more so on low-bypass engines which do not incorporate a huge fan in the front. On the current CS737, this behaviour is reversed. :-/
I know, one has to pull many tricks on the FSX jet engine basis to allow for this and that, but the slow-ish spool up/down really is a source of trouble on the approach where the rw engines would be kept in the state of being able to react faster.
As for the default thrust setting in the aircraft.cfg, I'm thankful for the user mods like the one from Bud. However, maybe it's possible to see those changes in 1.1, leading to a more reasonable performance of the plane, not the current rocket-alike. :D
If you have more stuff or points on the current list, please help. Some other folks have already set up threads, so I'm thankful for their input too, to make 1.1 even better. :)
On items already being reported, see the next post. in
