FSGlobal Real Weather decodes and imprints the WX conditions pretty accurately, however I think with all the other features that come with Active Sky Next makes ASN the king of WX simulation.

My FSGlobal Real Weather no longer works for some reason.  I cannot get the live weather connectivity anymore.

 

My FSGlobal Real Weather no longer works for some reason.  I cannot get the live weather connectivity anymore.

 

I believe they are using new servers with new IP addresses. Update your software

It's weird how software in this day and age still uses IP addresses. DNS was invented for a reason!

Update what software?  Windows 7?

He means FSGlobal Real Weather

In my research,  I cannot find any type of "Updated" software for FSGlobal Weaher.  Just the download.

http://www.fly2pilots.com/Cms/Ui/Pages/Products/MainPage.aspx?id=253b8b5c-0a91-4935-8d01-b3c70aee6034&pageid=b769000e-6101-4815-9eea-b19eeedde129

 

That download is the latest version. Full installer  V 1.7 Build 029

 

If I remember well, you just run the setup.exe, from the downloaded zip-file, over your previous install. Thats it, you have the latest version.

It's weird how software in this day and age still uses IP addresses. DNS was invented for a reason.

 

It's not weird at all. You are not entering in an IP address to reach "X" server. It's built in. You don't touch it. Why would DNS be a factor? Because it uses an IP address, DNS is completely eliminated as it is used to resolve IP addresses to a name. Also, skipping DNS speeds up the process.

 

It's weird how software in this day and age still uses IP addresses. DNS was invented for a reason!

 

 

First lets ping the URL of avsim:

 

C:\Windows\System32>ping forum.avsim.net

 

Pinging forum.avsim.net [205.252.89.43] with 32 bytes of data:

Reply from 205.252.89.43: bytes=32 time=21ms TTL=55

Reply from 205.252.89.43: bytes=32 time=19ms TTL=55

Reply from 205.252.89.43: bytes=32 time=21ms TTL=55

Reply from 205.252.89.43: bytes=32 time=27ms TTL=55

 

Ping statistics for 205.252.89.43:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 19ms, Maximum = 27ms, Average = 22ms

 

 

Now lets ping the IP Address:

 

C:\Windows\System32>ping 205.252.89.43

 

Pinging 205.252.89.43 with 32 bytes of data:

Reply from 205.252.89.43: bytes=32 time=18ms TTL=55

Reply from 205.252.89.43: bytes=32 time=21ms TTL=55

Reply from 205.252.89.43: bytes=32 time=19ms TTL=55

Reply from 205.252.89.43: bytes=32 time=19ms TTL=55

 

Ping statistics for 205.252.89.43:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 18ms, Maximum = 21ms, Average = 19ms

 

 

Catch my drift?

I understand how DNS works. But if they used a name, they simply need to change the DNS record if they move the servers to different IP addresses. Then they wouldn't need to release a new bit of software, with the new IP addresses.

 

You stated

 

 

I believe they are using new servers with new IP addresses. Update your software

 

Well that's a bit terrible don't you think? Update your software because IP's have changed..... or just use names and nobody would even know.

 

Catch my drift?

 

Also, while DNS would slow the process down very slightly, we're talking about a very small amount of time here that it's not worth considering

Who knows, maybe they changed other things in the background. Anti-piracy measures; who knows. I am not the dev.