# Improper File Suffix Exported

**URL:** <https://forum.navigraph.com/t/improper-file-suffix-exported/14062>\
**Category:** Desktop\
**Created:** [November 30, 2023, 4:50pm UTC](https://forum.navigraph.com/t/improper-file-suffix-exported/14062 "2023-11-30T16:50:39Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![shaines](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/shaines/32/460_2.png) [@shaines](https://forum.navigraph.com/u/shaines)\
**Post date:** [November 30, 2023, 4:50pm UTC](https://forum.navigraph.com/t/improper-file-suffix-exported/14062/1 "2023-11-30T16:50:39Z")

</div>

Navigraph Charts recently implemented a new feature where it lists all of the Simbrief chart export formats within the Export feature. Today I selected the JAR DESIGN AIRBUS option which is listed as a .txt file. This is correct. However the file that was saved had an additional “.pin” suffix which rendered the file unreadable by the A330 FMS import feature within the aircraft MCDU. The proper file suffix should be just “.txt”. Thank you for correcting this small error.

Steve Haines  
[steve@hainesdesign.com](mailto:steve@hainesdesign.com)

---

<div class="post-metadata">

**Author:** ![skysail](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/skysail/32/304_2.png) [@skysail](https://forum.navigraph.com/u/skysail)\
**Post date:** [November 30, 2023, 5:11pm UTC](https://forum.navigraph.com/t/improper-file-suffix-exported/14062/2 "2023-11-30T17:11:37Z")

</div>

Hello! Thanks for posting this.

We are aware of this issue and already have it on our bug tracker. We’ll make sure to fix it in time for the next release! Apologies for the inconvenience in the meantime.

Kind Regards,  
Malte

---

<div class="post-metadata">

**Author:** ![shaines](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/shaines/32/460_2.png) [@shaines](https://forum.navigraph.com/u/shaines)\
**Post date:** [November 30, 2023, 5:27pm UTC](https://forum.navigraph.com/t/improper-file-suffix-exported/14062/3 "2023-11-30T17:27:57Z")

</div>

No problem Malte. Just wanted you to know. Thanks for the quick note.

Steve Haines

---

<div class="post-metadata">

**Author:** ![aeronauta](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/aeronauta/32/16132_2.png) [@aeronauta](https://forum.navigraph.com/u/aeronauta)\
**Post date:** [December 1, 2023, 3:44am UTC](https://forum.navigraph.com/t/improper-file-suffix-exported/14062/4 "2023-12-01T03:44:42Z")

</div>

Most of the exports have the extra .pln extension at the end , the Majestic I am trying to use also…

Jorge

---

<div class="post-metadata">

**Author:** ![skysail](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/skysail/32/304_2.png) [@skysail](https://forum.navigraph.com/u/skysail)\
**Post date:** [December 1, 2023, 9:05am UTC](https://forum.navigraph.com/t/improper-file-suffix-exported/14062/5 "2023-12-01T09:05:55Z")

</div>

Thanks for the report! Yes, that sounds expected. This issue affects any of the new export options as long as it has a new and previously not used file extension.

Apologies for the inconvenience!

Kind Regards,  
Malte

---

<div class="post-metadata">

**Author:** ![skysail](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/skysail/32/304_2.png) [@skysail](https://forum.navigraph.com/u/skysail)\
**Post date:** [December 11, 2023, 12:25pm UTC](https://forum.navigraph.com/t/improper-file-suffix-exported/14062/6 "2023-12-11T12:25:01Z")

</div>

This has been fixed internally, and the fix will be included in the next update!

Apologies for the inconvenience in the meantime.

Kind Regards,  
Malte

---

<div class="post-metadata">

**Author:** ![skysail](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/skysail/32/304_2.png) [@skysail](https://forum.navigraph.com/u/skysail)\
**Post date:** [January 22, 2024, 3:33pm UTC](https://forum.navigraph.com/t/improper-file-suffix-exported/14062/7 "2024-01-22T15:33:18Z")

</div>

This issue should now be fixed in the recent release of `8.32.0`!

Please do confirm if this solved the issue for you!

Kind Regards,  
Malte
