Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Report Cessna 414AW Chancellor issues

Featured Replies

1 hour ago, Raller said:

Have found two texture bugs so far. One on the right landing gear brake hose and one on the fuel selector - should be called Right Engine.

The fuel selector bug is known and the painter has been made aware.

Good catch on the brake hose -- haven't noticed that before.

Al

  • Replies 1.1k
  • Views 143.5k
  • Created
  • Last Reply

Walk around section 4 A.  The view windows inside the pilot side front baggage compartment have a black line down the left side.  Not sure if this is supposed to be a shadow or not.spacer.png

Walk around section 4 E.  Camera angle has same issue as 3 B.  If you pan around you can see the ground drop off as can be seen in the lower left edge of the screenshot just above the shadow.spacer.png

14 minutes ago, jfwharton said:

Walk around section 4 A.  The view windows inside the pilot side front baggage compartment have a black line down the left side.  Not sure if this is supposed to be a shadow or not.spacer.png

A shadow could be involved, but that "line" exists in the real aircraft.

Al

 

Just grabbed the 1.4.1 hotfix, Fuel flows seem much more reasonable now!

The cowl flap bug is still present. To reiterate, the animations and placards (cowls open vs closed on exterior model, lever positions) all line up with each other, but the actual effect on the CHT's is still reversed. Currently closed cowls are cooling the engine and open cowls are keeping the heat in.

Also, the altitude capture still isn't working on initial climb. As it comes up to assigned altitude, it immediately enters a rapid decent and settles about 300 feet below the assigned altitude. I have to put it back into VS mode and click the capture button again at which point it climbs up and captures as it should. It then seems to work as it should for all other altitude changes for the rest of the flight.

Thanks for the continued hard work! 

27 minutes ago, happydappyman said:

Also, the altitude capture still isn't working on initial climb.

Which ver of the a/c is this -- GNS530, PMS GTN or TDS GTN?

To all: When making a bug report, please indicate to which of the above versions of the plane your report applies. This helps point FSW to the applicable code file.

Thanks,

Al

55 minutes ago, happydappyman said:

Also, the altitude capture still isn't working on initial climb.

I have not been able to replicate this bug in the TDS GTN750 ver of the plane. I tried climbing in ROL and PIT, and also in HDG and VS. And just in case, make sure you remember to arm the altitude alerter in order to capture an altitude (I have forgotten this little detail more than once!).

Al

Edited by ark

5 hours ago, Sender46 said:

The HSI compass card still cannot be adjusted.  It moves a little initially but then flicks back to where it was.

Is the HSI slaved? If so that’s desired behavior as the compass card in the HSI is slaved to the flux gate and will always revert to wherever the flux gate is telling it to point.

54 minutes ago, ark said:

I have not been able to replicate this bug in the TDS GTN750 ver of the plane. I tried climbing in ROL and PIT, and also in HDG and VS. And just in case, make sure you remember to arm the altitude alerter in order to capture an altitude (I have forgotten this little detail more than once!).

Al

Hi ark,

I'm using the PMS GTN750 version. I was actually using IAS for my climb. I'm going to load in a new flight and try it one more time here in IAS mode and see what happens. Then I'll load a new flight again and try it with VS and see if that makes a difference. Will update you when I know.  

32 minutes ago, happydappyman said:

Hi ark,

I'm using the PMS GTN750 version. I was actually using IAS for my climb. I'm going to load in a new flight and try it one more time here in IAS mode and see what happens. Then I'll load a new flight again and try it with VS and see if that makes a difference. Will update you when I know.  

I am also using the 750 version and do not have a problem with IAS climb. It captures just fine for me.

1 hour ago, ark said:

I have not been able to replicate this bug in the TDS GTN750 ver of the plane. I tried climbing in ROL and PIT, and also in HDG and VS. And just in case, make sure you remember to arm the altitude alerter in order to capture an altitude (I have forgotten this little detail more than once!).

Al

Ok I've done my tests. PMS GTN750

I loaded a new flight, set my autopilot, took off and climbed up to 12,500 using VS mode. It captured this perfectly and held 12,500.

I then set 14,500 and engaged IAS mode. As the climb started I pressed the ARM button. At 1000ft to go, the ALT ALERT light illuminated as it should. The light then extinguished itself with 300' left in the climb. This time though I blasted through 14,500' and continued up to 14,800'. At this point the plane began a slow 300 ft/min decent to 14,750' at which point it violently raised the nose and climbed back up to 14,800 where it again began it's slow decent to 14,750 and continued to yoyo. After a few rounds of this, I engaged VS mode and hit the ARM button at which point it successfully captured 14,500 as it should have. 

At this point, I set 16,600 and IAS again. This time it climbed again and with the ALT ALERT light functioning as before, it climbed at full speed until violently and suddenly capturing what ended up being 16,620 feet. No deceleration of the climb like in VS mode, but successfully capturing within 20 feet of what I selected.

Then I decided to try once more. I set a decent this time to 15,500 and selected IAS. This time it descended and captured exactly 15,500' (though again violently with no deceleration). 

Seems like it starts working in IAS only after it fails to capture once. VS mode works perfectly (as you said).

Thanks! And let me know if you need any further information

2 minutes ago, happydappyman said:

Ok I've done my tests. PMS GTN750

I loaded a new flight, set my autopilot, took off and climbed up to 12,500 using VS mode. It captured this perfectly and held 12,500.

I then set 14,500 and engaged IAS mode. As the climb started I pressed the ARM button. At 1000ft to go, the ALT ALERT light illuminated as it should. The light then extinguished itself with 300' left in the climb. This time though I blasted through 14,500' and continued up to 14,800'. At this point the plane began a slow 300 ft/min decent to 14,750' at which point it violently raised the nose and climbed back up to 14,800 where it again began it's slow decent to 14,750 and continued to yoyo. After a few rounds of this, I engaged VS mode and hit the ARM button at which point it successfully captured 14,500 as it should have. 

At this point, I set 16,600 and IAS again. This time it climbed again and with the ALT ALERT light functioning as before, it climbed at full speed until violently and suddenly capturing what ended up being 16,620 feet. No deceleration of the climb like in VS mode, but successfully capturing within 20 feet of what I selected.

Then I decided to try once more. I set a decent this time to 15,500 and selected IAS. This time it descended and captured exactly 15,500' (though again violently with no deceleration). 

Seems like it starts working in IAS only after it fails to capture once. VS mode works perfectly (as you said).

Thanks! And let me know if you need any further information

Just realized I might not be using the newest version of the PMS GTN750. If it's working for everyone else this might be the cause. I'll get the update when I have another minute and report whether my issue is resolved. 

When using IAS it is particularly important that the plane be trimmed for the climb or descent before turning on IAS. 

Also, there are plans to update the IAS code. 

Al

Please note that currently there has been no attempt to bind autopilot buttons to any particular hardware controllers. So clicking on the AP buttons is the safest way to go with the Beta for now. 

Al

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.