Anyone fly the HUD in Dino's T45?  It seems to be affected by ASN's low visibility in IMC.  The HUD brightness fades in and out...   can someone check?

 

 

 

I've taken a short video in the Lotus L39 at night.  Seems there's a weird fog layer that varies as I fly.  Probably some sort of effect to simulate flying through clouds...

 

But this is what I think is causing the HUD on Dino's plane to fade in and out.

 

That is what I see too, in many planes. Low vis and fog in the real air legacy, totally distracted by the landing light pulsing.

 

Turbulence is their, but far too strong, FSGRW is simulating turbulence better. Think I will hold off for a bit on this one.

 

 

Here I am approaching a storm in the middle of the Caribbean

 

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. 

Andy, it works here. Did you add the line into FSUIPC.INI that Pete advised in the instructions...

 

FSUIPC4 now cooperates with "Active Sky Next" (ASN). Two specific changes apply: first the hooks

normally applied into the FSX/P3D weather system for FSUIPC's smoothing actions are not

performed when ASN is active, as it uses those hooks itself. Second, by adding a parameter to the

[General] section of the FSUIPC4.INI file, thus:

ASNplanWX=<full path to ASN's active plan weather file>

 

LATER: Sorry, I'm not sure that relates to automatically loading the FSX plan into ASN but I can confirm it's working for me on a WideFS setup.

 

Hi Ray,

Could you supply a copy of ASNplanWX=<full path to ASN's active plan weather file> on your networked setup.

I ask this as I am uncertain if the full path includes the network path so a copy of yours will show this. For those tech savvy people please have patience.

Thanks in advance

Deleted

Regarding VC fog you should really have a look into the Hifi Forum.

 

It's tied to different shader mods.

 

 

It would be a good advice (not only for ASN) to get rid of all that shader mods (not talking about DX10 Fixer)

Shader do produce many, many issues in FSX, fog in VC is one thing but you have disappearing clouds and heavy cloud grids and patterns. Some screenshots I see in this thread are tied to shaders.

 

The bad thing about shaders is, that they are not simply to uninstall. It doesn't help just to remove the files and set a number in the FSX.cfg. You have also to copy a vanilla(!) FSX ShaderHLSL into FSX again!

The bad thing about shaders is, that they are not simply to uninstall. It doesn't help just to remove the files and set a number in the FSX.cfg. You have also to copy a vanilla(!) FSX ShaderHLSL into FSX again!

And how can we do that? with out a re-install?

 

Just delete the files?

And how can we do that? with out a re-install?

 

Just delete the files?

Sorry but I'm using tapatalk and not sure how to link you directly to it.

 

There's a link to the stock ShadersHLSL files here on Avsim:

 

If you go to the "DX10 Discussions, Hints and Help" forum, then the "The How to" doc sticky.....scroll down and there is a link to d/l the stock shaders.

HTH

 

Regards

 

Steve

 

 

Regarding VC fog you should really have a look into the Hifi Forum.

 

It's tied to different shader mods.

 

 

It would be a good advice (not only for ASN) to get rid of all that shader mods (not talking about DX10 Fixer)

Shader do produce many, many issues in FSX, fog in VC is one thing but you have disappearing clouds and heavy cloud grids and patterns. Some screenshots I see in this thread are tied to shaders.

 

The bad thing about shaders is, that they are not simply to uninstall. It doesn't help just to remove the files and set a number in the FSX.cfg. You have also to copy a vanilla(!) FSX ShaderHLSL into FSX again!

Really? I always learned if you delete the shader cache FSX will rebuild it the next time you start FSX.

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

 

 

Really? I always learned if you delete the shader cache FSX will rebuild it the next time you start FSX.

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!!!

 

 

Hi Ray,

Could you supply a copy of ASNplanWX=<full path to ASN's active plan weather file> on your networked setup.

I ask this as I am uncertain if the full path includes the network path so a copy of yours will show this. For those tech savvy people please have patience.

Thanks in advance

 

Hi Andrew,

 

In the [General] section of fsuipc4.ini I have the following entry:-

 

ASNplanWx=\\NONFLYING\ASN_Weather

 

NonFlying is the PC where ASN is installed. On that PC you have to share the following folder...

 

C:\Documents and Settings\Usernamet\Application Data\HiFi\ASNFSX\Weather

 

Where Username is your account. I named the share ASN_Weather. You can call it what you like as long as it links up with the entry in fsuipc4.ini.

 

Hope that helps.

Hi Andrew,

 

In the [General] section of fsuipc4.ini I have the following entry:-

 

ASNplanWx=\\NONFLYING\ASN_Weather

 

NonFlying is the PC where ASN is installed. On that PC you have to share the following folder...

 

C:\Documents and Settings\Usernamet\Application Data\HiFi\ASNFSX\Weather

 

Where Username is your account. I named the share ASN_Weather. You can call it what you like as long as it links up with the entry in fsuipc4.ini.

 

Hope that helps.

Thanks Ray

Regards

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

Thanks for your effort to provide a clear, concise and balanced comparison. Some of the protestations from at least one side of this debate have had an unfortunate degree of immaturity and it's most helpful to have a more constructive and scientific approach. Once question... could the difference in turbulence effect be connected to the fact that the Opus cameras and DHM are not connected directly to their own weather engine not be an influence on how they perform with ASN?

 

ANdy 

From what I understand about how the two systems work, turbulence effects are triggered only by their own weather engine, so the turbulence effects I see using ASN are not generated by Opus Live Camera (even if Opus Live Camera is active), simply because Opus, with Live Weather disabled, does not know where the turbulence area is. I suppose that using ASN for weather and Opus for cameras only, causes Opus LC to generate effects for ground roll, engine vibrations and in general evertyhing not related to weather conditions, while the turbulence shake is generated by ASN. 

If this is correct, then turbulence effects in Opus are modelled in order to reflect aircraft shaking also in the instruments, while in ASN they are not.

But again, I am not sure my understanding is correct.

Regards