I have a strange issue where I have problems now with the 414 after updating.

1) The TDS GTNxi no longer lights up after the avionics master is switched on. The A/P and Transponder work but not the GTN.  The normal GTN program is running and showing connected to MSFS.

2) I no longer have any liveries that were for the 414 in my Community folder showing up on the livery selector.

 

Did Flysimware change something that is disconnecting these two things and does anyone know how to fix it ?

I’m missing downloaded liveries too, would love to know what happened there.

Which update?

40 minutes ago, MarkW said:

I have a strange issue where I have problems now with the 414 after updating.

1) The TDS GTNxi no longer lights up after the avionics master is switched on. The A/P and Transponder work but not the GTN.  The normal GTN program is running and showing connected to MSFS.

2) I no longer have any liveries that were for the 414 in my Community folder showing up on the livery selector.

 

Did Flysimware change something that is disconnecting these two things and does anyone know how to fix it ?

The GTNxi in the 414 is livery specific.  And I believe I am also using Bert's 414 GTNxi mod v2.9. I only had one addon livery, the N140J from Ryan, and it is still in place.

1 hour ago, MarkW said:

I have a strange issue where I have problems now with the 414 after updating.

Updating the 414?  To which release level?

19 minutes ago, fppilot said:

And I believe I am also using Bert's 414 GTNxi mod v2.9.

Frank, you should keep this mod at the same level as the base C414.  Are you still on V2.9.?  I am on V3.1.

3.2 is the update I have. I just assumed the updates are released with GTMxi comparability. 

56 minutes ago, MarkW said:

3.2 is the update I have. I just assumed the updates are released with GTMxi comparability. 

The C414 ver 3.2 works fine with the TDS GTNXi using the standard FSW liveries. I don't have any experience with any addon liveries for the C414.

Do the click spots on the EFB screen work? If not, if you happen to have the Heavy Division 787 addon in your Community folder, remove it. This mod is known to disable the C414 EFB and GTN screens.

Also, just FYI, there is a mandatory update out (to ver 2.1.45) for the PMS50 GTN. Don't know if just having the older version of the PMS50 GTN in your Community folder could cause problems even if not loaded.

Al

Edited October 10, 20223 yr by ark

2 hours ago, Bert Pieke said:

Frank, you should keep this mod at the same level as the base C414.  Are you still on V2.9.?  I am on V3.1.

Bert. I do.  Where may I find 3.1?  And what versions are current on the 310 and 337?

Just now, fppilot said:

Bert. I do.  Where may I find 3.1?  And what versions are current on the 310 and 337?

FSW keep updating the C414.. but if you are happy with C414 V2.9,  I see no need to change it.

If you do go to V3.1. the tablet may not work correctly with my V2.9 mod loaded... keep them in synch!

3 hours ago, MarkW said:

I no longer have any liveries that were for the 414 in my Community folder showing up on the livery selector.

 

A way back, the C414 was updated to add the "W" to the name.. that disabled addon liveries until they too added the "W".

If you have not updated in a while, this may be catching up to you now..

Just FYI, current ver of the C414AW is 3.2, available from FSW, SimMarket or the MarketPlace. Here are the last few Change logs:

v 3.2.0 FULL RELEASE.  

1. Wing lockers were showing luggage when not loaded. This was from our recent update as we did a major change for enabling the exterior clickable items.

2. Since SU10 is now out they fixed a bug we reported as the NAV 1 morse code would not play if we have three nav sources as we did. So this update removes our custom nav 1 sound as now the default sounds works.

v 3.1.0 FULL RELEASE.

1. Upper door was not easy to find hotspot for the handle to open and close. Fixed.

2. Gear parts were not linked to some of the animations from a recent update and is now fixed.

3. The exterior tail lock handle is now available to click from the interaction checklist or the interior cameras.

4. Taxi light logic got changed recently and the toggle sound was missing. Fixed.

5. Stall speeds got updated recently and were entered reversed. Fixed.

v 3.0.0 FULL RELEASE.

1. Taxi light now allow you to use hardware binding controls (joystick buttons) and mouse at the same time.

2. Landing light now works with default hardware and mouse control at the same time. The mouse 3 way position has not changed where as the default hardware will give you only a 2 way position but still extend while turning light on or retract while turning light off.

3. The alerter tooltip was fixed.

4. The yoke control lock will no longer appear accidently from the interactive checklist.

5. We solved a huge mystery where the clicking through LCD screens like the tablet was causing switches in the background to be clicked. This was also reported to Asobo as they plan to add this info to the SDK. This also allowe us to re enable the click spots for the exterior walk around.

6. All exterior walk around click spots are re enabled. You can now open things like the wing and nose lockers, engine doors, fuel caps, oil cap, hydraulic cap, place/remove chocks, place/remove tie downs, place/remove engine plugs, place/remove static wicks, place/remove pitot covers and rudder lock.

7. Some of the overhead map light frame seems to be hidden. Fixed.

8. If both LH and RH air valves are pulled more than 10% the pressurization will no longer pressurize and will dump pressure until equal with outside air pressure.

9. The tablet code got a new update that speeds up the code for changing pages and other visibility so there will be no visual delays.

Al

 

Edited October 10, 20223 yr by ark

50 minutes ago, Bert Pieke said:

A way back, the C414 was updated to add the "W" to the name.. that disabled addon liveries until they too added the "W".

If you have not updated in a while, this may be catching up to you now..

That makes sense as it had been a while since i updated.  I assume that’s something we can poke around in the repaint files and correct?

6 minutes ago, regis9 said:

That makes sense as it had been a while since i updated.  I assume that’s something we can poke around in the repaint files and correct?

Yeah it's not hard.  Anywhere the aircraft.cfg and texture.cfg say 414A you need to add a "W"

Example from aircraft.cfg for my paint:

You see sections like base_container, Title, Model, Panel, Sound, ui_type etc.

Base container is most important for repaints.  If the file path doesn't exist/is wrong you'll get pink textures or no textures.

[VARIATION]
base_container = "..\flysimware_Cessna_414AW"

[FLTSIM.0]
Title="Cessna 414AW N140J GNS530"
Model=""
Panel=""
Sound=""
Texture="N140J"
KB_Checklists=""
KB_Reference=""
description=""
wip_indicator=0
ui_manufacturer="Cessna"
ui_type="414AW"
ui_variation="N140J GNS530"
ui_typerole="Twin Engine Prop"
ui_createdby="Flysimware"
ui_thumbnailfile=""
ui_certified_ceiling=14600
ui_max_range=920
ui_autonomy=6
ui_fuel_burn_rate=13.5
atc_id="N140J"
icao_airline=""
atc_id_enable=1
atc_airline=""
atc_flight_number="N140J"
atc_heavy=0
atc_id_color="0x00000000"
atc_id_font=""
isAirTraffic=0
isUserSelectable=1
isFlyable=1
canBeUsedByAITraffic=1
Effects=""
atc_parking_types="RAMP"
atc_parking_codes=""

[FLTSIM.1]
Title="Cessna 414AW N140J GTN 750"
Model="\..\..\flysimware_Cessna_414AW\model.GTN750"
Panel="\..\..\flysimware_Cessna_414AW\panel.GTN750"
Sound="\..\..\flysimware_Cessna_414AW\sound"
Texture="N140J"
KB_Checklists=""
KB_Reference=""
description=""
wip_indicator=0
ui_manufacturer="Cessna"
ui_type="414AW"
ui_variation="N140J GTN750"
ui_typerole="Twin Engine Prop"
ui_createdby="Flysimware"
ui_thumbnailfile=""
ui_certified_ceiling=14600
ui_max_range=920
ui_autonomy=6
ui_fuel_burn_rate=13.5
atc_id="N140J"
icao_airline=""
atc_id_enable=1
atc_airline=""
atc_flight_number="N140J"
atc_heavy=0
atc_id_color="0x00000000"
atc_id_font=""
isAirTraffic=0
isUserSelectable=1
isFlyable=1
canBeUsedByAITraffic=1
Effects=""
atc_parking_types="RAMP"
atc_parking_codes=""

In the Texture.cfg you need to add the AW as well example

[fltsim]
fallback.1=..\..\flysimware_Cessna_414AW\texture
fallback.2=..\..\flysimware_Cessna_414AW\texture.base

 

Ryan is of course correct. But it may be easier to look at the Flightsim.to site for the repaint authors' updates to the new standard. Many of the most popular repaints were updated to meet the new standard. (Most authors did this in late July or August 2022.) Of course, you may prefer to do this by hand.