I'm trying to install the DX10 fix for FSX by Steve Parsons but I'm having a bit of a problem.

 

When I try to run setup.bat I get the following message:

 

"general10.fx shader has readonly attribute set"

 

I've checked the file in question, and indeed the entire folder and it does *not* have the read only attribute set. I've tried running the installer on my laptop install of FSX as well and get exactly the same message. I see in the original thread someone had a similar problem and was advised to run the "take ownership" app on the FSX folder, which I have done to no avail. I also see that Paul J uploaded the modified shader to his Dropbox but the link is now dead....

 

Does anyone know how I can get the installer to work properly, or failing that would a kind soul please send me the modified general10.fx file so I can try the fixed DX10 mode?

 

Many thanks.

I'm trying to install the DX10 fix for FSX by Steve Parsons but I'm having a bit of a problem.

 

When I try to run setup.bat I get the following message:

 

"general10.fx shader has readonly attribute set"

 

I've checked the file in question, and indeed the entire folder and it does *not* have the read only attribute set. I've tried running the installer on my laptop install of FSX as well and get exactly the same message. I see in the original thread someone had a similar problem and was advised to run the "take ownership" app on the FSX folder, which I have done to no avail. I also see that Paul J uploaded the modified shader to his Dropbox but the link is now dead....

 

Does anyone know how I can get the installer to work properly, or failing that would a kind soul please send me the modified general10.fx file so I can try the fixed DX10 mode?

 

Many thanks.

 

Hi Engine Room:

 

1). Where is your FSX located?

 

2). Sorry, ER. the links in the doc and pdf link correctly to the Avsim library and to the Dropbox and both work: also there is another link on the first post of the "How-To" thread...

 

3). Here is a 3.2.2 ready-to-use ShadersHlSl folder. First, though - start FSX in DX10 mode before you install the modified shaders folder, to make sure that DX10 does work on your pc. Then simply copy your original "somewhere" and then unzip this into it's place. Don't forget to delete the Shaders10 cache folder after this is done. OK?

Thanks for your help Paul.

 

The link you've posted is to the 3.2.2 installer which I already have and can't get to work. I have FSX installed in D:\Flight Sims\FSX. It's not in the Program Files folder. I unzip the installer in my downloads folder and when I try to run the setup.bat I get a DOS window and another window pops up with the message about general10.fx shader being read only - which it isn't! I've also tried right clicking and running as administrator with the same result.

 

I've read the readme again and again and as far as I can tell I'm not doing anything wrong?

Hello EngineRoom

 

I agree, the link Paul posted is not to the ShadersHlSl folder, but to the shader_release_v3.2.2.zip file.

 

That said: Windows 7, security "blocks" files whenever you download a file from an unknown source. Including ZIP files and their content. When you unzip them, the files extracted inherit the blocked flag, and behave as RO.

 

It does not matter whether you run as Admin or not, said files remain “blocked” until you explicitly “unblock” them.

 

I see no risk as the file came from our trusted friend Paul (in my case from AVSIM),

but beware that other sources might not be safe.

 

Try this: Right Click on the Downloaded shader_release_v3.2.2.zip file.

Select Properties and click on Unblock at the bottom of the applet. (Read the security message)

 

 

(As you can see the Read-Olny checkbox in empty, BUT the file is blocked)

 

Once the ZIP file is unblocked, you must unzip it again and then try reinstalling.

 

Hope that works for you.

Hi ER:

 

Whereabouts (in the world) are you? If you like we can hook up on the Avsim TeamViewer, and I can take a better look at this dilemma! - or do that at a more convenient time, perhaps?

 

There has to be more to this, as hundreds of these shaders are installing without issues.

 

Sorry, I must be blind on the Ready-to-use folder. You're right. Here it is. Let me know right back if you will. Thanks,

 

pj

Thanks very much for the help gents.

 

Try this: Right Click on the Downloaded shader_release_v3.2.2.zip file.

Select Properties and click on Unblock at the bottom of the applet. (Read the security message)

 

I don't have that option - only the read only and hidden check boxes and the advanced button. Perhaps because I have UAC disabled?

 

 

Sorry, I must be blind on the Ready-to-use folder. You're right. Here it is. Let me know right back if you will. Thanks,

 

Thanks Paul, that should do the trick. It's a curious problem for sure - the read only attribute is most definitely NOT set on anything in my ShaderHLSL folder. I've tried copying the installer folder and running setup.bat from various places including my download folder, desktop, root C:, root D:, and my FSX folder and it always comes up with the same error. It doesn't even search for my FSX installation, it just immediately throws up that error.

 

 

And as you can see my general10.fx shader doesn't have the read only attribute set:

 

 

Thanks for your help again Paul I'll drop the modified shaders in and try them.

Engineroom the file Kabronicus is showing is zipped, yours is unzipped. Maybe you do have the unblock option on your zipped version.

Try running everything as an administrator.

All my FSX files and folders are marked as read only but it worked perfectly.

I have Windows 8 with UAC turned off.

I got everything and up and running using the modified shaders Paul sent me.

 

All I can say is wow, what a difference! My litmus test for framerate is to load up the default C172 at Orbx Moorabin, take off and head towards Melbourne city centre which will put both Essendon and Melbourne Intl airports into the frame along with a huge amount of autogen and the Melbourne skyline. With my DX9 setup I would get around 10fps with this scenario. With the DX10 fix I get 16fps. However the real improvement for me is in the texture loading. With DX9 I would always get blurries in a high stress scenario like this. With DX10 the texture loading is *much* better and the texture LODs stay much sharper. In this respect I'd say FSX/DX10 is probably even better then P3D/DX9.

 

Thanks very much for your help Paul, and of course Steve Parsons for fixing DX10. The modified shaders are tucked away safe now on my backup drive.

 

One thing that is a little curious though.... the modified shaders file is smaller than the "DIY" installer. In which case would it have not been more straightforward to have just distributed the modified shaders in the first place?

Just did another quick test - a visual circuit at Orbx Anacortes with "Anacortgen", detailed marinas and refinery scenery options enabled, and OpusFSX live weather (broken clouds) flying the RealAir Duke. This airport scenery has a reputation for being something of a framerate hog. Under DX9 I would get 12-14fps on approach here and blurry textures. With DX10 I'm getting 16-18fps and clear textures all the way down to the runway. The only fly in the ointment is the flashing streetlights.

 

I'm pretty happy with DX10 at this point!

I got everything and up and running using the modified shaders Paul sent me.

 

All I can say is wow, what a difference! My litmus test for framerate is to load up the default C172 at Orbx

 

One thing that is a little curious though.... the modified shaders file is smaller than the "DIY" installer. In which case would it have not been more straightforward to have just distributed the modified shaders in the first place?

 

The Shader is is under constant revision, EngineRoom, and, as in life - one change might trigger an idea, which is acted upon, and the file is modified and tried - sometimes it works, or a better way is found. That better way might mean that a chunk of earlier code is removed, and so the file gets smaller. Remember the DX10 code was left "as is" - before ACES could finish it. Steve is simply continuing that development process with all the benefit of six years of HLS language experience under his belt. Back in 2006 all this was new tech.

 

Hope this helps!