So imagine one day you're flying and you see this:

 

 

And this is after doing everything(including reinstalling the 777), but reinstall ASN.(those of you who use it know that there's a limit to how many times you can reinstall it and I only do reinstalls as a absolute last resort) I have been studying this behavior and did some experiments and found that with each sweep of the radar, I got different(sometimes old) returns mixed with new ones. While I am not a expert in weather radar, I don't think it's suppose to give me returns like that.

 

EDIT: Sometimes when the radar sweeps the other way(its sweeping from left to right in that one) it will return the other half of that data, but erase the top half(think of that picture but with the current returns missing and the missing returns showing)

It looks great to me.

Using OpusFSX as data source gives me a bunch of small round circles, which might look realistic at Range 10, but at Range 40 and beyond looks terrible.

Any thoughts?

It looks great to me.

Using OpusFSX as data source gives me a bunch of small round circles, which might look realistic at Range 10, but at Range 40 and beyond looks terrible.

Any thoughts?

You have to use ASN for correct accurate data as this is the only weather engine which will give you the right information for weather radar. Other weather engines will give u returns but they won't be accurate as the weather radar is currently coded to only work correctly with ASN

 

 

Sometimes when the radar sweeps the other way(its sweeping from left to right in that one) it will return the other half of that data, but erase the top half(think of that picture but with the current returns missing and the missing returns showing)

Brian, are you using ASN SP1 Beta ? it is an open beta and can be downloaded at HiFI

Brian, are you using ASN SP1 Beta ? it is an open beta and can be downloaded at HiFI

This was well before beta, but yes I have it downloaded and it is still happening. I believe it is directly tied to the frame rate.(Upon further examination, it looks like the weather radar is trying to "decypher" the data that is being sent from ASN.)

This was well before beta, but yes I have it downloaded and it is still happening. I believe it is directly tied to the frame rate.(Upon further examination, it looks like the weather radar is trying to "decypher" the data that is being sent from ASN.)

Ok, cheers Brian. I may have to check mine. Have not had the time recently to play with the radar, will see if I get the same results.

 

 

And this is after doing everything(including reinstalling the 777), but reinstall ASN.(those of you who use it know that there's a limit to how many times you can reinstall it and I only do reinstalls as a absolute last resort) I have been studying this behavior and did some experiments and found that with each sweep of the radar, I got different(sometimes old) returns mixed with new ones. While I am not a expert in weather radar, I don't think it's suppose to give me returns like that.

 

Nah, what you're seeing is just caused by the building being in the way   (joking, of course - although, in the real world, you'd just get a giant return/shadow because of the building, and you'd probably do some nerve damage to anyone who gets too close to the nose).

 

 

 

In all seriousness, are you running ASN in a networked configuration by chance?

Nah, what you're seeing is just caused by the building being in the way   (joking, of course - although, in the real world, you'd just get a giant return/shadow because of the building, and you'd probably do some nerve damage to anyone who gets too close to the nose).

 

 

 

In all seriousness, are you running ASN in a networked configuration by chance?

Nope, I run ASN locally. I do have a theory though. I use 3 pre-rendered frames and lock my frame rate to 30 in Nvidia inspector. I found a issue with the 777 where if you didn't limit the frame rate using FSX's own internal limiter, if you locked your PC it would go crazy when u took FSX out of its "suspension" At any rate, I believe this is also tied to the pre-rendered frames in Nvidia Inspector. I'll try out an experiment and I'll get back to you.

EDIT: Did my experiment, no changes. Its still the same. That being ruled out, I still believe it is tied to the frame rate.(As you can see its not the best) and besides, the data eventually cleans its self up so I'm not too stuck up on it. If anything its a minor annoyance.