1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Thanks for the donations everyone. That's another month covered :)
    Dismiss Notice

General Data/Shader/#.fx not found Fix 1.1

Data/Shader/#.fx not found Fix

  1. skullz613
    Update: Version 1.1

    Altiris mentioned it could be the #building.fx file that's missing so the patch has been updated to 1.1 with the #building.fx re-named to #.fx
    What we really need to do is find the model that's causing the error.


    Have you seen the following line in your logs?

    GRAPH3D EffectFactory.cpp ( 323) Error Fx file <Data/Shader/#.fx> not found. Switching to default.

    The file #.fx does not exist in the games folders and it's possibly a mistake somewhere in the games code.

    What I did a few months ago was copy the #default.fx file and renamed it #.fx. I created a folder called shader in my Data folder and put it in there. The errors stopped.

    Download the patch and try it out.
    Installation Pre-requiste(s):
    kipate and tdbaria like this.

Recent Reviews

  1. tdbaria
    Version: 1.1
    this has been persistent in my cxl logs. error of this kind was posted in the "old trafford stadium" mod's discussions (http://xlnation.net/threads/old-trafford-stadium.1825/) way back.

    finally, after testing, the error has gone, log is clear of any shader issues. my cxl runs smoothly, as expected.

    thanks a lot man, excellente!
  2. Masterpiece
    Version: 1.1
    Thanks for sharing, I really needed it! We just place the .patch file in the pak folder, right?
    1. skullz613
      Author's Response
      Yep that's right. Just like any other patch file
  3. Mr.X²
    Version: 1.1
    thanks for creating and sharing, will try it out
  4. lguzman2011
    Version: 1.0
    I have not seen this error, but thank you, will indeed keep for possible issue in the future!
  5. pauliaxz
    Version: 1.0
    I start to think, you guys will solve all crashes in the future ;)
    1. skullz613
      Author's Response
      Yes I think we are slowly finding fixes for them all :)