[RESOLVED]MetaShader build error (x86) folder

[BIGNEWY]

I have just had some feedback from one user via PM

 

He moved it from x86 folder to his c drive and it is working for him now, please let me know if you have similar results

[MSM]

I can confirm that the problem has gone away when I moved my installation out of "program files (86)" and onto a different drive.

[BIGNEWY]

I can confirm that the problem has gone away when I moved my installation out of "program files (86)" and onto a different drive.

 

great news!

 

I think the dev team have found the problem.

 

I will feedback to the team

[Johnny_Rico]

I can confirm that the problem has gone away when I moved my installation out of "program files (86)" and onto a different drive.

 

 

I wonder if this Shader problem is because people are NOT running DCS as admin?

Edited April 26, 2018 by Johnny_Rico

[Juuba]

Just a note from outside: Program Files requires Admin rights to write in.

 

Try running the game as the administrator.

 

Or relocate it.

[BIGNEWY]

Yes worth trying to run as admin also.

[Kronuxen]

So is relocating the game working? I have the same issue, ive done cleanups and repairs of DCS but it will still give me the same error as other. I've got DCS too in program files and im running it always on administrator both the run.exe and the updater as I've always done for years now..

 

Is there any other fix apart from relocating DCS to another place? and in the case of having to do so, can I move the whole folder or do I need to change resgistry keys, licencing etc...?

[BIGNEWY]

So is relocating the game working? I have the same issue, ive done cleanups and repairs of DCS but it will still give me the same error as other. I've got DCS too in program files and im running it always on administrator both the run.exe and the updater as I've always done for years now..

 

Is there any other fix apart from relocating DCS to another place? and in the case of having to do so, can I move the whole folder or do I need to change resgistry keys, licencing etc...?

 

So far users reporting moving it out of x86 folder has fixed the issue.

 

I am sure the dev team will have a fix for the next patch.

 

you do not need to touch the registry or activations

 

you may need to edit any shortcuts you have to point to the new path

Edited April 26, 2018 by BIGNEWY

[MSM]

Relocating out of the program files(x86) worked for me.

 

The error message looked like it might have been having problems with string handling logic dealing with in the pathname.

 

"./Bazar/shaders/metashaders/shadingModels/shadingModel_MapTex.decomposed.meta.hlsl(12,6-12): error X3000: unrecognized identifier 'Program'"

[Guille H. Mono]

I was not running DCS as admin. :music_whistling:

 

Moving the folder out of (x86) solved the problem.

 

 

 

 

i5 7200u @ 2.5Ghz

12GB Ram

Nvidia GTx950M

[BIGNEWY]

thanks for trying this workaround, we appreciate it.

[Johnny_Rico]

So far users reporting moving it out of x86 folder has fixed the issue.

 

I am sure the dev team will have a fix for the next patch.

 

you do not need to touch the registry

 

Stupid question time .....

 

DCS is 64 bit, why is it not installing to Program Files instead of Program Files (x86) ?

[BIGNEWY]

Stupid question time .....

 

DCS is 64 bit, why is it not installing to Program Files instead of Program Files (x86) ?

 

I don't think it does by default, but the user can change the install path if they wish

[MSM]

In the case of long time steam users the program may well be installed under program files (x86) in the steam apps folder that was created by steam back in windows 7 days. The OS may then have been updated to the latest Windows 10 version, but it will have left the program files(x86) folder and contents where they were.

[BIGNEWY]

The team will have a fix for the next patch.

 

Thanks to everyone who helped with this issue :thumbup:

[sslechta]

...and as far as I know, previous non-Steam versions of 2.5 would install to "C:\Program Files\Eagle Dynamics" by default. I wonder if the install package had changed this path?

[MrDieing]

Also confirmed on this side, moving from x86 to 'regular' Program Files worked. Thanks everybody, BIGNEWY, and the ED team for the quick help and workaround!

[Kronuxen]

Can confirm too, I cut and pasted DCS folder outside program files and was able to do a quick flight with the f5 so it seems to work. Thanks!

[norwegianwiking]

So moving the folder works, but is it enough to run as admin?

[MrDieing]

So moving the folder works, but is it enough to run as admin?

 

No, only running as admin will not work.

You will have to move your game from C:\Program Files (x86) to C:\Program Files and you are good to go. It takes one second because you are not actually moving files on your disk as you would when you move them to a different drive. You lose nothing, so you keep all your settings and controls.

[BIGNEWY]

So moving the folder works, but is it enough to run as admin?

 

No, it is not. A fix will be required by ED, should be next patch

[norwegianwiking]

Can confirm, moving from program files (x86) to program files does work.

[USSR_Rik]

Thanks for all, catched and fixed in internal version. Will prepared to hotfix.

[ST0RM]

I wonder if this Shader problem is because people are NOT running DCS as admin?

 

I run ALL of my programs as Admin. So not the cause.

 

Hopefully a quick hot fix this week?

[Slazi]

So for Steam users, we can either opt out of OpenBeta (3.6gb download) or wait for the patch?

 

I was just about to fly :(