Gizmo

Commercial Member
  • Content Count

    81
  • Joined

  • Last visited

Community Reputation

0 Neutral

Contact Methods

  • Website URL
    http://shadeforfsx.blogspot.com/
  • ICQ
    0

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No
  1. Gizmo

    What is Prepar3D?

    Humm gonna check this out when i get back on the desktop PC,i guess its worth a months fee upfront to checkout and see how far under the hood i can stick my nose ;)Cheerssteve
  2. Gizmo

    Bojote's Shader 3.0 mod for FSX

    try this taken from the Ozx Bell206 HD readmeControl Panel -> Folder Options -> View Tab -> Scroll down and put a bullet in "Show hidden files and folders" -> Click "Apply"then look in Windows XP : C:\Documents and Settings\[Your Username]\Application Data\Microsoft\FSXWindows Vista\Win7 : C:\Users\[Your Username]\AppData\Roaming\Microsoft\FSX
  3. Gizmo

    Bojote's Shader 3.0 mod for FSX

    change your ALLOW_SHADER_30=2to ALLOW_SHADER_30=1looks like you miss keyed it while adding it to your cfg filehope that fixes it for youLatersGizmo
  4. Gizmo

    Bojote's Shader 3.0 mod for FSX

    Hi Wolfgangyour talking about the uncompiled shader code paths,at runtime FSX compiles those shaders and stores them in a cache under a users doc/app path as pointed out by paulso any changes you make to the uncompiled shaders (like this sm3.0 mod) needs to be passed through FSX to be recompiled,without forcing FSX to recompile the new shaders either by removing the old cache or asking FSX to recompile its shaders by altering the SHADER_CACHE_PRIMED= line in the FSX.cfg your not going to see any change as fsx will contiune to use its cached code
  5. Gizmo

    Bojote's Shader 3.0 mod for FSX

    Thats your problem right there the X850 did'nt/doesnt have support for the SM3.0 code pathas i recall the highest shader path it can manage was SM2.0B