# Shader Editor PFX files

**URL:** <https://forums.imgtec.com/t/shader-editor-pfx-files/1969>\
**Category:** PowerVR Insider\
**Tags:** pvrtextool, pvrshaman, pvrshadereditor\
**Created:** [January 2, 2014, 1:07pm UTC](https://forums.imgtec.com/t/shader-editor-pfx-files/1969 "2014-01-02T13:07:02Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![blamejane](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.imgtec.com/blamejane/32/93_2.png) [@blamejane](https://forums.imgtec.com/u/blamejane)\
**Post date:** [January 2, 2014, 1:07pm UTC](https://forums.imgtec.com/t/shader-editor-pfx-files/1969/1 "2014-01-02T13:07:02Z")

</div>

I’m on a macbook pro, mountain lion OS-X, and have the latest PowerVR SDK (3.2) installed. My problem is I need help with the file association with .pfx files.  
  
  
  
I noticed that POD files are associated with PVRShaman and .PVR texture files are associated with PVRTexTool, which makes it very convenient to edit these files. However I’m not able to edit any .PFX files by double clicking the file. These are currently associated with Key Chain Access. When I try to change the file association to PVRShaderEditor, the app is always grayed-out/disabled from being selectable.

---

<div class="post-metadata">

**Author:** ![dgu](https://avatars.discourse-cdn.com/v4/letter/d/94ad74/32.png) [@dgu](https://forums.imgtec.com/u/dgu)\
**Post date:** [January 2, 2014, 1:58pm UTC](https://forums.imgtec.com/t/shader-editor-pfx-files/1969/2 "2014-01-02T13:58:20Z")

</div>

Hello  
  
  
  
you are very right , i never been able to do it from PVRShaman , i only succeeded to associate the file to PVRShaderEditorGUI only  
  
the grayish thing disapear you select the next choice in the combox box “ALL APPLICATION” and not recommended application,  
  
the other way is to use the right click getInfo and change the application to use and then click "change all"  
  
regards  
  
david

---

<div class="post-metadata">

**Author:** ![JoeDavis](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.imgtec.com/joedavis/32/71_2.png) [@JoeDavis](https://forums.imgtec.com/u/JoeDavis)\
**Post date:** [January 2, 2014, 1:59pm UTC](https://forums.imgtec.com/t/shader-editor-pfx-files/1969/3 "2014-01-02T13:59:16Z")

</div>

Hi,  
  
  
  
Unfortunately, this is a known issue that we don’t yet have a solution for. The extension was chosen at the point the PFX format was conceived. It became apparent much later that Apple used the same extension name for another purpose. I’ve filed a report in our internal bug tracker (BRN46374) for an extension name change to be considered for a future SDK.  
  
  
  
Thanks,  
  
Joe

---

<div class="post-metadata">

**Author:** ![dgu](https://avatars.discourse-cdn.com/v4/letter/d/94ad74/32.png) [@dgu](https://forums.imgtec.com/u/dgu)\
**Post date:** [January 2, 2014, 2:52pm UTC](https://forums.imgtec.com/t/shader-editor-pfx-files/1969/4 "2014-01-02T14:52:19Z")

</div>

Hello Joe,  
  
Happy new Year, even by changing the extension of the pfx doesnt “open” the file !!! 🙂  
  
it s not Apple fault here as it is possible to change this extension , but how the soft open it …🙂

---

<div class="post-metadata">

**Author:** ![JoeDavis](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.imgtec.com/joedavis/32/71_2.png) [@JoeDavis](https://forums.imgtec.com/u/JoeDavis)\
**Post date:** [January 2, 2014, 3:39pm UTC](https://forums.imgtec.com/t/shader-editor-pfx-files/1969/5 "2014-01-02T15:39:50Z")

</div>

Hi David,  
  
  
  
Thanks. Good to hear from you. Hope you enjoyed the holidays!  
  
  
  
I meant that we could move to a different extension name in the future, e.g. PVRFX, so there won’t be a clash.  
  
  
  
Cheers,  
  
Joe

---

<div class="post-metadata">

**Author:** ![blamejane](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.imgtec.com/blamejane/32/93_2.png) [@blamejane](https://forums.imgtec.com/u/blamejane)\
**Post date:** [January 2, 2014, 4:38pm UTC](https://forums.imgtec.com/t/shader-editor-pfx-files/1969/6 "2014-01-02T16:38:51Z")

</div>

Thanks for the help, at least I know now. It was bugging me.