Page MenuHomeFeedback Tracker

Error compiling shader PSSpecularAlpha
Closed, ResolvedPublic


Starting ArmA3 gives me a crash with this error message:

Error compiling shader PSSpecularAlpha {F19433}


Legacy ID
Game Crash
Steps To Reproduce

Starting the game (up to date, no dev build)

Additional Information

Launch options:
-mod=@CBA_A3;@ANZINS;@tao_foldmap_a3;@Landtex -nosplash -cpuCount=8 -high -maxMem=6144 -nosplash -maxMem=6144
Error still present without launch options as well.

File check didn´t resolve the issue.

My system:

Event Timeline

AmmokK edited Steps To Reproduce. (Show Details)May 14 2013, 6:31 PM
AmmokK edited Additional Information. (Show Details)
AmmokK set Category to Game Crash.
AmmokK set Reproducibility to Always.
AmmokK set Severity to None.
AmmokK set Resolution to Open.
AmmokK set Legacy ID to 2228118133.May 7 2016, 2:07 PM

We need dxdiag and files from this folder for solve your problem. C:\Users\<Name>\AppData\Local\Arma 3 Alpha\
Can you upload somewhere in winrar package please?
When package will be smaller than 2,097k, so you can attach here. Thank you.

AmmokK added a subscriber: AmmokK.May 7 2016, 2:07 PM

Please install latest graphic drivers. Usage of driver cleaner before installing new drivers will make sure you have no corrupted drivers left on computer.

Can you try install latest Direct X please?

Do you have similar issues with other DirectX 11 games?

Thank you.

Hi again.
Well, i did all of that yesterday (thanks, i needed to rearrange my desktop icons because of that qq ) but sadly that did not help.
So far i don´t have any other game running into trouble. Right now i am downloading Tomb Raider, will give feedback if there are any problems or not in dx11 mode.

This is your problem:
C:\Spiele\Steam\steamapps\common\Arma 3\@ANZINS\dta\bin.pbo - unknown

You are loading an old bin.pbo with newer exe.
Fix: Remove @ANZINS

BI job: Handle dta files to exe mismatch better/with clear error message.

Yeah, absolutely right. Removing anzins from the starting parameters worked perfectly.
Now running without any problems again. Thanks!

Would indeed have helped me a lot if i at least knew where to search for the error.

MadDogX added a subscriber: MadDogX.May 7 2016, 2:07 PM

Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.

If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.