I'm having a problem with the TDS GTNXi. With the 414 I can only use MSFS as NAV source. With the King Air I can use the TDN. 

31 minutes ago, Cpt_Piett said:

I'm having a problem with the TDS GTNXi. With the 414 I can only use MSFS as NAV source.

Did you also just post this on the FSW Discord site?

I cannot replicate your problem? Suggest you not use any type of C414 third party add-on. Just use a default FSW livery and see if the problem goes away.

If this does not solve the problem, then suggest temporarily removing everything from the Community folder except the TDS GTN 750 and the C414. This is easy to do if you use the Add-on Linker. If you don't, rename your Community folder to back it up, create a new Community folder, and then copy just the TDS GTN and C414 into this new Community folder and restart the sim. If this solves the problem, then something in your original Community folder is causing a conflict with the C414 or TDS GTN.

 

Al

Edited October 27, 20223 yr by ark

2 minutes ago, ark said:

Did you also just post this on the FSW Discord site?

I did. Were you the one who replied to me there? I'm ReverseBarley at Discord. 

Just going to try now without any addon liveries. I don't fly the 414 as much as I did, but I'd like to get it working properly. 

4 minutes ago, Cpt_Piett said:

Were you the one who replied to me there?

Yes.

As I said there, let us know if the addon livery was the problem as the info may help someone else who runs into a similar issue.

Al

Edited October 27, 20223 yr by ark

14 minutes ago, ark said:

Yes.

As I said there, let us know if the addon livery was the problem as the info may help someone else who runs into a similar issue.

Al

Loaded the sim without any liveries. Could select GTN750Xi Unit1 as the source. Then exited and restarted with liveries, loaded a flight with the livery. And that worked fine too. So the issue I had initially could very well have been user error. Thanks for helping though!

11 minutes ago, Cpt_Piett said:

Loaded the sim without any liveries. Could select GTN750Xi Unit1 as the source. Then exited and restarted with liveries, loaded a flight with the livery. And that worked fine too. So the issue I had initially could very well have been user error. Thanks for helping though!

Great, glad you got things working, and thanks for the feedback.

Long story short, due to an unfortunate set of circumstances, FSW has had to put out a couple of C414 updates in just the last few days. As a result of the changes the potential for any type of C414 addon to cause a problem has increased somewhat. According to FSW the worst is over and so I expect things will settle down now.

Al

Edited October 27, 20223 yr by ark

39 minutes ago, ark said:

Great, glad you got things working, and thanks for the feedback.

Long story short, due to an unfortunate set of circumstances, FSW has had to put out a couple of C414 updates in just the last few days. As a result of the changes the potential for any type of C414 addon to cause a problem has increased somewhat. According to FSW the worst is over and so I expect things will settle down now.

Al

Yes -- and to add to what you say above...you (meaning all users) may need to edit the paths for many liveries, to take out the "cessna" word in the pathing in the layout files.

I did this the other day to a livery I like, and it worked like a charm.

On my side, i have problem with the Garmin autopilot. Sometimes, it freezes. Even if i  change the altitude on the altitude selector, the altitude stays on the same on the autopilot and i'm unable to select the VS (up or down).

1 hour ago, Mace said:

Yes -- and to add to what you say above...you (meaning all users) may need to edit the paths for many liveries, to take out the "cessna" word in the pathing in the layout files.

I did this the other day to a livery I like, and it worked like a charm.

Sorry, but if you update to the latest version of the C414 , ver 3.3.3 Hotfix, you may find that livery no longer works "as is".

Al

Edited October 27, 20223 yr by ark

48 minutes ago, Lmaire said:

On my side, i have problem with the Garmin autopilot. Sometimes, it freezes. Even if i  change the altitude on the altitude selector, the altitude stays on the same on the autopilot and i'm unable to select the VS (up or down).

Make sure you have the latest version of the C414, and the latest version of whatever GTN 750 you are using. If the problem persists I would suggest the possibility of a Community folder conflict of some kind, and you might want to try the procedure I suggested above to Cpt_Piett to check for that problem. There are 1000s of C414 users at this point and I am not seeing reports similar to yours, at least not yet.

Al

4 minutes ago, ark said:

Make sure you have the latest version of the C414, and the latest version of whatever GTN 750 you are using. If the problem persists I would suggest the possibility of a Community folder conflict of some kind, and you might want to try the procedure I suggested above to Cpt_Piett to check for that problem. There are 1000s of C414 users at this point and I am not seeing reports similar to yours, at least not yet.

Al

Thank you Al.

12 minutes ago, ark said:

Sorry, but if you update to the latest version of the C414 , ver 3.3.3 Hotfix, you may find that livery no longer works "as is".

Al

Well it's no longer "as is" -- I took out the "cessna" references and it worked great in 3.3.2.

So in 3.3.3 did they change some of the texture mapping?  That would render all liveries obsolete?

6 minutes ago, Mace said:

Well it's no longer "as is" -- I took out the "cessna" references and it worked great in 3.3.2.

So in 3.3.3 did they change some of the texture mapping?  That would render all liveries obsolete?

Not according to the release notes: 

7 hours ago, Cpt_Piett said:

V 3.3.3 Hotfix

UPDATES:

1. Do to all the folder changes we forgot to update the interactive checklist back to the original folder name structure. Sorry for all the recent hotfixes but we are dealing with outside forces and we have to remove trademark names. 

12 minutes ago, Mace said:

Well it's no longer "as is" -- I took out the "cessna" references and it worked great in 3.3.2.

So in 3.3.3 did they change some of the texture mapping?  That would render all liveries obsolete?

Put the 'Cessna' back in.

16 minutes ago, Mace said:

Well it's no longer "as is" -- I took out the "cessna" references and it worked great in 3.3.2.

So in 3.3.3 did they change some of the texture mapping?  That would render all liveries obsolete?

I don't know about "all liveries", but C414 ver 3.3.2 and 3.3.3 have different mappings. There changes were not something FSW wanted to do, but were the result of outside "forces", and resulted in a lot of "extra" work for FSW, and others.

Al

Edited October 28, 20223 yr by ark