To add....you would replace your existing ShadersHLSL folder directly in your FSX folder with these stock files.

 

NB-advisable to back up/copy first tho!!!

 

You would also need to delete the 2 shader folders in:

....AppData/Local/Microsoft/FSX folder too so that the shader cache rebuilds.

 

Regards

 

Steve

 

 

 

Webmax

 

See my last post...we've cross-posted!!

 

The link gives you the stock shaders but you ALSO need to delete the 2 folders that form the shader cache in ....AppData/Local/Microsoft/FSX

 

Regards

 

Steve

 

PS-i hate Tapatalk!!!

My bad mixing up the actual shader files with the shader cache. Of course you first need to make sure you have the original shader files before rebuilding the shader cache.

 

Sorry for the confusion and no...I'm not a big fan of Tapatalk myself ;-)

Jackson,

I think that was a good balanced write up.

 

Just to Note and nothing else , I think the turbulence is down to opus DHM no working with ASN, in the PMDG you do see the plane fighting the turbulence, speed, hight and direction are all being worked hard and you can also set the amounts in the options.

 

Thanks for taking the time to do the flights.

Although it's not hard to work out an expected runway in use based on weather and winds, but with FSX it's predicting what ATC/Ai is going to use is difficult. For example, among a great deal of things other than the wind direction, (or rather the aft and side vector components), in FSX even the place you are parked in or will be parking in is taken into consideration at airports with multiple runways in use.

Yesterday I tried to make a comparison between ASN and Opus. I have been using Opus with full satisfaction for the last year and I was curious to compare it with ASN, after all the hypes and comments following its recent release. To run this test I used Opus beta 3.38.0 and ASN trial version. Both Opus and ASN settings were default ones. FSUIPC version 4.924a with weather settings off. The configuration was a networked one, i.e FSX on the main desktop and ASN/Opus on a networked laptop.

The route was EDDM-EGKK @ FL320 using the NGX -800 and the weather was rich of interesting situations: foggy with 300 mts rwy visibility on both airports, low overcast on both airports and a series of variable conditions enroute, ranging from overcast to cavok, which gave me the opportunity to see how the two products performed in terms of cloud transitions.

The two flights were done one immediately after the other in order to have the weather conditions as consistent as possible between each other. On the first flight I used ASN for the weather and Opus for Live Camera (Live weather disabled), on the second flight I used only Opus both for weather and cameras.

 

Overall both products are outstanding, with some areas where IMHO one is better than the other and viceversa.

 

Ground movements with reduced visibility: Great depiction of the foggy weather from both products. ASN seemed to give a slightly thicker fog but overall the differences were really minor.

 

Climb: Climb until 3000 ft was done in full IMC conditions. Breaking out of the clouds was slightly more subtle and gradual with ASN but overall very realistic in both cases.

 

Enroute: Absolutely no wind shift and no clouds popping or noticeable cloud transitions for ASN (very impressive indeed). Some instances of minor wind shifts and clouds popping for Opus.

 

Descent/Approach and Landing: Same as above. The weather turned from cavok above the Channel to ovc in EGKK area with amazing smoothness with ASN and just slightly less smooth with Opus. No wind shifts in either case. The final ILS approach on rwy 26L was flown with zero visibility and rwy becoming visible only at 150 ft agl. Again, ASN gave a very thick and solid ovc layer while Opus left some “holes” here and there, but this may have been caused by weather conditions not being exactly the same from one flight to the other (the two final legs were flown at about 2 hrs difference between each other).

 

Turbulence effect: I prefer the Opus one, as it can also be “seen” on the instruments (needles oscillating, heading, roll and pitch indicators actually moving due to the aircraft shaking), while with ASN the instruments are rock steady. ASN also seemed to give a too strong turbulence effect, but this may have been a consequence of having at default settings the option to enhance turbulence effect selected on.

 

Visuals: The way the low altitude haze layer is depicted in Opus is second to none, while ASN skies seemed to me to be a little too much “clean” when looking down. From FL320 the ground seemed to be too much clear than I have ever seen in real world. Maybe it is just a matter of playing around with visibility settings. As already said above, overcast depiction seemed a little bit more “thick and solid” with ASN.

 

FPS impact: No noticeable differences between the two products. Performance wise, running with the weather engine on a networked laptop has been my preferred solution for a long time now and I did not notice any difference between ASN and Opus

 

Conclusions: Both products give a very realistic depiction of the real weather with some areas where one is slightly better than the other: HiFi guys seem to have found the holy grail for wind shifts and cloud popping issues with Opus slightly behind but on the right track as well; Opus visuals and turbulence effects are still number one.

 

Competion is up and running and we, as simmers, will definitely benefit from this.

 

Regards

Good write up and analysis.

 

One question....is this with the latest beta from opus?

 

I have found the latest beta to be excellent

So I replace the Stock ShadersHLSJ within my main FSX folder with the ones found on the "how to DX10 forum.

 

Delete the 2 shader folder in app/roaming etc

 

Job done?

 

is that right?

 

------------------------------------------------

 

@Glenn

Read the 3rd line again.

To run this test I used Opus beta 3.38.0

 

Is there any need to quote? just a "@" Jackson would do!, we don't need to see it all again.

Good write up and analysis.

 

One question....is this with the latest beta from opus?

 

I have found the latest beta to be excellent

Read the third sentence.

So I replace the Stock ShadersHLSJ within my main FSX folder with the ones found on the "how to DX10 forum.

 

Delete the 2 shader folder in app/roaming etc

 

Job done?

 

is that right?

Yes that's it - simple - and you would be back to stock shaders.

 

If you applied the old "swarm cloud fix" you would need to reapply that but otherwise you'll be good to go.

 

I'm sure you would do anyway but I would advise to save/backup the folders first...just in case!!

 

Steve

 

 

Yes that's it - simple - and you would be back to stock shaders.

 

If you applied the old "swarm cloud fix" you would need to reapply that but otherwise you'll be good to go.

 

I'm sure you would do anyway but I would advise to save/backup the folders first...just in case!!

 

Steve

 

... and if i already run and use FSX happily with Steves superb DX10 fix, then i do not need to do anything here now - correct?

Cheers, Christoph

I don't have any shader mods. This effect came directly from ASN. It's not a landing light. It's just a mist that fades in and out slightly in front of my plane.

Thanks guys

 

I got a new GPU and only deleted the two folders in app roaming. I will replace the ones in my fsx folder.

... and if i already run and use FSX happily with Steves superb DX10 fix, then i do not need to do anything here now - correct?

Cheers, Christoph

Christoph

 

You would only need this if you wanted to get back to stock shaders.

 

I think Nyxx is wanting to go back to stock to test or rule out an issue he may have with ASN.

 

If you'res aint broke...there's no need to fix - if you're running and using FSX happily, then there's no need for you to change or amend anything.

 

Regards

 

Steve

 

 

Thanks guys

 

I got a new GPU and only deleted the two folders in app roaming. I will replace the ones in my fsx folder.

I'm sure you've already done it...but your old GPU line/details would need deleting from your cfg too - not sure if this does cause issues or not but removing the old card details from the cfg can't do any harm!

 

Regards

 

Steve

 

 

No Steve the main reason is I was told to delete them because I installed a new GPU a gtx660.

 

 

Christoph

You would only need this if you wanted to get back to stock shaders.

I think Nyxx is wanting to go back to stock to test or rule out an issue he may have with ASN.

If you'res aint broke...there's no need to fix - if you're running and using FSX happily, then there's no need for you to change or amend anything.

Regards

Steve

 

Thank You very much for Your reply Steve!

Thought so, but now i have proof!

Thank You very much again for answering my question!

Very much appreciated!

Cheers, Christoph

 

 

I don't have any shader mods. This effect came directly from ASN. It's not a landing light. It's just a mist that fades in and out slightly in front of my plane.

 

The fog behave is also tied to shader mods!

 

But that doesn't mean that this is the reason in your case, especially if you say you are sure to not have any shader mods (I had myself shader mods installed without knowloedge btw.)

 

The VC fog is balanced to fit for the most addons and highly depends on which addon you use.

With your plane especially we have not tested it. I can only say, with NGX, 777, Dash8 etc, there is no issue.

 

But beside this a note on the Hififorums would be helpful to give them the chance to find the right balance probably

Could you tell me what texture selection you are using? I have been trying to find a cloud set from REX that I like and so far I haven't even seen what appears to be a thunderstorm yet but if I do get near one I would like it to look nice. 

I use Hde V2 freeware texture pack. The 512x texture that came with it. (it comes with all resolutions, but high resolution clouds does not mean it will look realistic.)

 

I never had realistic storms with Rex.