Nice kyle

 

I like your rambling

Thank you guys! Kyle, just 3 questions, if you don't mind:

1. Have the lagging problems coming from networked ASN been solved?

2. As to the rain not showing in your rig, do you mean you don't see rain outside when ASN is networked (thus an ASN-related problem), or do you refer to a rain problem with the 777 radar?

3. What cloud turbulence settings do you use in ASN (min and max cloud turbulence)? I see in the video the nice effect of turbulence occurring only when flying by the cloud, thing that I haven't been able to appreciate on my system.

Thanks! 

Lots of thanks for Kyle...

But rudely, "nobody" thanked FrooglePete!

So thanks FrooglePete. Nice video. :smile:

Wow that looks sweet B)

 

 

Nice kyle
 
I like your rambling

 

I'm glad.  I haven't really figured out how I feel about it.  Sometimes it detracts from the point.  Other times, I feel that it makes it a little more personal.

 

 

 

1. Have the lagging problems coming from networked ASN been solved?
2. As to the rain not showing in your rig, do you mean you don't see rain outside when ASN is networked (thus an ASN-related problem), or do you refer to a rain problem with the 777 radar?
3. What cloud turbulence settings do you use in ASN (min and max cloud turbulence)? I see in the video the nice effect of turbulence occurring only when flying by the cloud, thing that I haven't been able to appreciate on my system.

 

1. I don't think there's a "solution," to that from a programmatic perspective.  That's like asking if the ping time "problem" between DC and Sydney, Australia has been "solved."  When you increase the distance between two entities that need to communicate, you are going to pick up lag.  Additionally, there are so many variables to networking (firewall, ports, SimConnect settings, program settings, permissions, network media, and so on) that it's difficult to say where, exactly, the lag is being picked up.  You simply cannot program around all of those and still have a program that's effective.  I'm sure I could kill some of the lag by hardwiring (direct ether - no router or anything, though that has the possibility of ticking Windows off if it's not done correctly, since multiple paths to the same computers would be the result) the computers directly together, but that's only going to cut some of the lag down.

 

2. Basically, ASN was not being allowed to trigger the sim variable to force rain in the sim over my network.  It isn't an ASN-related problem, because it can trigger the rain locally.  It's a network problem.  My network wouldn't allow it based on settings I have yet to pin down.  It works for others, but the potential frustration really doesn't justify the performance "savings."  Networked ASN may be great for the weaker computers that aren't multi-core, but with FSX not optimized for multiple cores, there's another core out there that can easily pick up ASN without a performance hit to the sim.

 

3. Defaults.

 

 

 

But rudely, "nobody" thanked FrooglePete!

 

His got added later, so the initial responses only saw my original post without Ryan's edits.

 

Regardless, I think his is a lot better.  Definitely more thought and polish put into it.  Mine was more of a last-minute "throw the forum a bone" thing where I just happened to be talking to RSR and Ryan to get permission to put it up.

His got added later, so the initial responses only saw my original post without Ryan's edits.

Oh right, fair enough.

 

Both videos were great, looking forward to it materialising on my monitor.

The "LWR CTR" screen has the advantage of being closest to the WXR panel, making it possible to have both devices at one glance (I hope)...

 

Claus - not trying to pick on you here, but I've seen a few comments like yours and I wanted to just make something pretty clear:

 

 

 

It seems to me that a lot of the people aren't fully understanding the concept of radar adjustments, based on the responses here.  This isn't like being a DJ, or playing a video game, or any other generic constant-feedback loop.  Those jobs, you need to see the controls, and see the immediate outputs that your changes on those controls will be making.  The weather radar, on the other hand, truly isn't a system that you constantly need your hands on (hint: there's a reason it's down on the pedestal and not closer to the yoke, or closer to the screens).  You don't really need to see how your changes are affecting the radar while you make them.  Look down.  Make changes.  Look up and evaluate the display.  There really isn't too much experimentation going on, as some seem to be thinking.

 

Heck, for most people, the AUTO mode will be just fine.

 

I know it's cool, and it's new, and a lot of people want to get their hands on it and twist the knobs, but it really isn't as much of a hands-on device that it's being made out to be.

 

There are a ton of buttons on the audio control panel.  How often do you use them?  The functionality is there for when you need it, but you're not always going to be needing it.  Same for the weather radar.  The functionality is there for when you need to - as an example - tilt the radar down a lot further for an emergency descent in poor weather, but that doesn't mean you need to constantly have your hands on it, making changes, even then.

 

EDIT:

The weather radar will be explained further in the documentation.

 

...now, let's see how many people read it  

2. Basically, ASN was not being allowed to trigger the sim variable to force rain in the sim over my network.  It isn't an ASN-related problem, because it can trigger the rain locally.  It's a network problem.  My network wouldn't allow it based on settings I have yet to pin down.  It works for others, but the potential frustration really doesn't justify the performance "savings."  Networked ASN may be great for the weaker computers that aren't multi-core, but with FSX not optimized for multiple cores, there's another core out there that can easily pick up ASN without a performance hit to the sim.

 

Forgive me if i'm reading this wrong, but are you saying ASN runs on a different core on your processor so the only drain on resources during its use is the GPU?

 

P.S The title says FooglePete 

Video previews by Kyle Rodgers and FrooglePete? Hmm. Kyle's video I could have watched on Christmas day, on the other side from her majesty the Queen, I could have been cosily slumped with a single malt and mince pie. Whereas, while getting ready to go out on a Saturday night, I could have caught Pete's video, cleverly slipped in front of an episode of Power Rangers.

 

 

Forgive me if i'm reading this wrong, but are you saying ASN runs on a different core on your processor so the only drain on resources during its use is the GPU?

 

I'm not sure about the intricacies of it all, but the end result is - with a multi-core setup - the performance hit is negligible.

I'm not sure about the intricacies of it all, but the end result is - with a multi-core setup - the performance hit is negligible.

 

It's alright it's my bad, i forgot ASN isn't a texture pack or anything like that it's just the engine for the weather i'm told? 

Anyone on my question regarding the PAC alert?

 

Thanks...

It's alright it's my bad, i forgot ASN isn't a texture pack or anything like that it's just the engine for the weather i'm told? 

 

Just weather.  Texture packs can come from other add-ons like REX, or the various free ones out there.

 

 

 

Anyone on my question regarding the PAC alert?

 

No idea.

Smooth folks - nice work!!  Looks like the real thing

Dunno why, but I'm pumped that the modeling reflects the "swipe" scan / update feature. Every time I see it say in an instagram or video, I think of that scene in Cast Away, where Tom Hanks walks into the MD-11 flightdeck and sees the impending storm on the ND as the radar scan swipe slides across the screen. 

 

I have no idea if this detail was difficult to model or not - regardless- well done developers. This kind of detail is what makes PMDG, well, PMDG.