Jump to content

Mustang-242

Frozen-Inactivity
  • Content Count

    54
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by Mustang-242

  1. Thanks for the confirmation on those. I've made the corrections. Although not finished, I figured I would share my in-progress coverage map. I mainly wanted to know where the boundaries between Europe, Asia and Africa fell, to ensure I had coverage for my flights. But I guess I won't be downloading the American regions for a while as my around-the-world trip sees me flying east from the UK via Southern Europe and the Middle East. In a single-engine GA, I won't be getting to the Americas any time soon! The two areas I questioned are highlighted yellow. Otherwise the key is as follows: E = Europe A = Asia AF = Africa AU = Australasia Hopefully nobody's geography is so bad that it needs explaining but thought I better state it just in case :wink: It was quickly made with an image I found via Google Image search and the text overlay was done using OpenOffice Calc (equivalent to Excel). It's not pretty (especially because I can't find out how to hide the row & column lines in Calc), but it's a start Hope it's useful for someone - and I hope it's accurate.
  2. First of all, a huge thanks to Daniel and all involved in this release, it's really phenomenal! :smile: Since I've embarked on an around-the-world flight, I wanted to check I had all necessary regions ahead of time to ensure I didn't wander into any bland, default areas. I couldn't find a coverage map so I have started to make one based on the filenames of the mesh files, assuming the latitude & longitude names are based on the lower-left corner of the 10° grid. I'll share it when complete. In doing so, I found a couple of areas of overlap where a 10x10° file exists in two different regions. Which one is used will obviously depend on which one is on top in the scenery library. First, a little background: I have been using FMX since patch 1.03 I believe, so I don't know exactly when some of these files may have been added to my installation, or if any are leftovers from patches 1.01 to 1.04 which are no longer needed. I found the file N30E030.bgl included in both Europe and Asia. The European version is 280MB, the Asian version is 79MB. I assume I should keep the European version due to the higher filesize (=higher resolution data). I also found the file N70E020.bgl in both Europe and Asia. The European version is 22MB and the Asian version is 4MB. Again, I assume I should keep the European version. Naturally, I realise it's possible that I have put a file in the wrong folder during install of one of the previous patches, though I was quite careful. In case this overlap happens with a standard installation + patching routine, other people may have the same on their computers. In case it could cause undesired effects or low-quality terrain areas I thought I'd post it up. As I didn't keep the original installation files, I can't check where these files came from easily. The created/modified dates are based on the time I downloaded them too. Anyway, I'm looking forward to any future developments and will post up any anomalies I find on my travels.
  3. Did you enter your serial number fully in capitals? I found that I could not get the update from Aerosoft until I entered my serial in all uppercase (and with dashes, as far as I recall). The case is not normally important for such things, but in this instance it is. Otherwise it tells you that your serial is no good, as you have said.
×
×
  • Create New...