Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
fxc.exe /Tfx_2_0 /LD /Fo"ShaderOutputName.fxo" "ShaderInputName.fx"
Shader input name would be whatever .fx file is already in your Shaders folder of the mod. Shader output name would be the same name, but will be a .fxo file.
For example, my original file was MeshBumpLight.fx so "MeshBumpLight.fx" would replace "ShaderInputName.fx" in the command posted above. Then for "ShaderOutputName.fxo", you would put "MeshBumpLight.fxo".
The command would be:
fxc.exe /Tfx_2_0 /LD /Fo"MeshBumpLight.fxo" "MeshBumpLight.fx"
Then either rename the original MeshBumpLight.fx file to something else or delete it entirely. If that makes sense.
That got it working for me. After having to deal with a few errors with the DirectX installation in the beginning.
EDIT: Ok, originally I couldn't get command prompt to open when right-clicked on the folder. I had to change the registry to do that. I did it now using command prompt open here and got it working. Thanks a lot.
but for them it dont work
If you try to add _new_ shaders (aka using a custom name) they need to be loaded through a meg file of they won't be recognized by the game.
(Technically it's even valid to add a completely empty file with the new name to the meg and then add the actual shader to the default mod folder structure).