Shaders not Valid (Mismatch of exe and Data?)

[Chip360]

EDIT: SOLVED


Quote[/b] ]I recieved this error and followed this advice

Quote[/b] ]I think this error occurs when you change which version of ArmA.exe you are using, but do not update your p:\ drive with the relevant support files for the updated ArmA.exe.

Specifically, the bin folder, the product.bin in the dta folder and possibly the core folder.

The bin folder holds the shaders I believe, as well as other files needed.


Planck

and reinstalled O2 and this error went away





====================================================
Okay, so I start up o2, open up my .p3d (a stryker), assign the texture paths, atm the only paths Ive changed are the

p:\stryker_tex\data\stryker_body2_co.paa

and

p:\stryker_tex\data\stryker_body1_co.paa

and all others are with default paths, example:

ca\wheeled\data\stryker_alfa_ca.tga

Now it starts up, and then I get that message [Shaders not Valid (Mismatch of exe and Data?)].

What am I doing wrong?

Edit: It appears im not the only one who needs help with this:


Quote[/b] ]i can't seem to run buldozer from visitor3...

it tries to start but then i get a little 'ArmA' error dialog that says
'No entry bin\config.bin/CfgDifficulties/Regular/Flags.VonID'.

Then when I click out of that I get another 'Arma' error dialog that says 'Shaders not valid (mismatch of exe and data?)'

Following that there's the standard 'ArmA has encountered a problem and needs to close etc etc Send error Report? etc' type box.

Any help?

I also get the same error in Visitor, so basically neither Visitor or Bulldozer will work.

Any help would be greatly appreciated.

[Chip360]

... Okay.. come on you guys, do we have any BiS staff running around here that can tell me what that error message means so I can take measures to fixing it?

It seems to be a serious issue that is not exclusive to myself, I have already reinstalled the game and all of the tools, and now im getting a bit angsty.

=/

EDIT: SOLVED

[jojimbo]

Sometimes installing o2 again doesnt work,i just had this problem but the above didnt work.what i did was...drumroll

unpbo the bin.pbo in:

C:\Program Files\Bohemia Interactive\ArmA\Dta

grab the two shader files:

BICompiledShaders_Default.shdc
BICompiledShaders_nVidia.shdc

copy and paste these two to your P:\bin folder.

phew happy modding

http://forums.bistudio.com/oldsmileys/biggrin_o.gif

[TRexian]

A slightly different solution (I think) is when I changed the directory for the textures, but didn't have the right .cfg stuff. I just changed the texture directory back to the mapped drive root.

Probably not the most elegant solution.

[Sanyix]

for me it's still not working

i don't have working drive, just a working folder, i put there /bin these shader files, but connect with visitor to buldozer -> still invalid shader...

[Miles Teg]

Sometimes installing o2 again doesnt work,i just had this problem but the above didnt work.what i did was...drumroll

unpbo the bin.pbo in:

C:\Program Files\Bohemia Interactive\ArmA\Dta

grab the two shader files:

BICompiledShaders_Default.shdc
BICompiledShaders_nVidia.shdc

copy and paste these two to your P:\bin folder.

phew happy modding

http://forums.bistudio.com/oldsmileys/biggrin_o.gif
Thanks JoJimbo!!!   That worked for me!

Warning to others:  MAKE SURE you used a FRESH De-PBO'ed version of the BIN and not the files from an old DePBO'ed BIN folder that was already there.   I made the mistake of doing that and was about to post here, "AAARG IT DIDN'T WORK!" until I realized what I did wrong.  lol
I still get this error:

No entry 'bin\config.bin/CfgDifficulties/Regular/Flags.VonID'.

However, the important thing is that it still loads up bulldozer and I can see the model and textures which is all I care about at the moment.   If I notice something missing I'll post it on here.  

Chris G.
aka-Miles Teg<GD>

[tgm0]

To me none of the above solutions worked. Until I discovered something that made the difference.

Apparently the buldozer.exe file is nothing but a copy 1:1 of the game executable. In my case the Beta version of ArmaOA.exe.

After discovering it I did the following:

**** MAKE A BACKUP OF ALL OF BOTH YOUR P:\bin FOLDER AND OF THE EXECUTABLE buldozer.exe BEFORE YOU DO THIS!!! ****

1) Renamed my actual copy of buldozer.exe to buldozez.old (the one that installed with the BI Tools 2.5.1 - NO NEED TO DO THIS IF YOU ALREADY BACKED IT UP)

2) Copied the beta C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead\Expansion\betaArma2OA.exe to the P:\ root and renamed it buldozer.exe

3) Extracted a copy of the beta Arma2OA bin.pbo (mine was in C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead\Expansion\beta\expansion\dta\bin.pbo)

If you are using ExtractPBO as I am doing, you should now have a bin\bin directory with the following 5 files in it:
config.cpp
PboPrefix.txt
Shaders_DefPP.shdc
Shaders_DefPS.shdc
Shaders_DefVS.shdc

4) Moved only the shaders files (Shaders_DefPP.shdc, Shaders_DefPS.shdc, Shaders_DefVS.shdc) to P:\bin\ and overwritten the one that were already in place

Done!

Now when I launch buldozer from within Visitor3 i don't get the message any more and buldozer load just fine.

I haven't tried it myself, but I imagine you should adapt this case scenario to your own configuration.
If you just own Arma2 for example you should go to your Arma 2 installation folder and copy Arma2.exe and extract the bin.pbo located under the Dta folder, same if you have Arma 2 OA with no beta installed use the Arma2OA.exe and the bin.pbo located inside the \arma 2 operation arrowhead\Expansion\dta folder.

I hope this have been informative to you.

Happy editing!!!