Jump to content

Rusty flyer

  • Posts

  • Joined

  • Last visited

About Rusty flyer

Rusty flyer's Achievements


Newbie (1/14)



  1. Great John...go for it!! Best of luck & blue skies! Rusty [btw: You have mentioned GEX USA/Canada a couple of times now. I believe that the most recent edition of GEX for the United States & Canada region is called GEXNA (Ground Env. X North America). It is the latest GEX product for that region and it supersedes the previously published GEX USA/Canada package. Have fun, GEX is a terrific addon, and a "must-have" in my view.]
  2. Hi John, Actually yes, the order that you install the GEX region packages *is* more critical. In fact, you should ensure that you install GEXNA (including any update patches available from Flight 1's site) *before* you install GEXEurope and GEXAFME. The latest version of GEXNA is v1.095, so ensure that is the latest version installed prior to installing GEXEurope &/or the others. If not, download the v1.095 update, and run it before proceeding with the other regions. These instructions are included in the printed manuals accompanying each of the sceneries (or in the .pdf versions if you download the scenery packages), but also take a peek at this reference from the publisher's support forums: http://www.simforums...topic41898.html There are a few reasons for this but, to put it in a nutshell, GEXEurope, GEXAFME and GEXAPT contain texture relationships that update the earlier GEXNA (USA & Canada) texture [relationships]. In a sense, if you were to install the earlier-produced GEXNA after installing the others (published later), you would be negating, practically undoing, those relationships between the regions & the common textures that those these regions share. Hope this helps, Rusty
  3. Hi there, It is true, that is a known conflict; however, good cheer is here... ...there is a solution that completely resolves the issue! The following utility, AI Flight Planner (AIFP 2.1.27), is an incredibly simple utility that will convert your FS9 [AI] traffic files within your FSX installation to FSX format. This resolves the described issues and conflict: http://stuff4fs.com/...rue&Folder=AIFP It really only takes a minute for the utility to scan, find, locate & list *any* FS9 format traffic files that may exist within your FSX installation, and it then gives you the choice of converting them to FSX format. Blue skies! Rusty
  4. Hi John, No, you do not have to perform any pre-installation removals of default FSX textures. GEX incorporates all this into its installation process, and before replacing the default FSX textures, the GEX installation process asks if you want to backup the default textures to a separate location before proceeding with the replacement installation. It is a good idea to execute this backup when prompted by the GEX installation routine, and when you do so, GEX will then proceed to backup the original default textures as directed. Cheers, Rusty
  5. Hi, GEX is a texture replacement package that replaces, for the area purchased/installed, the default FSX foundation set of ground texture tiles with much more realistic appearing and area-representative textures. GEX is a package of textures only, and does not incorporate its own landclass files (the mechanism by which FSX selects which textures will appear where [e.g.: urban textures in city areas, farmland or wooded etc. textures in more rural areas, stoneface textures in canyons, etc.]). Therefore, as a replacement texture set only, GEX is essentially compatible with most everything. Photorealistic scenery, however, will supersede foundation textures (which the GEX installed replacement set becomes), however this is the case whether the foundation textures come from the FSX default set or from a replacement set of textures such as GEX. Because GEX simply replaces the default FSX textures, just like those default FSX textures they will not appear in the Scenery Library. After installing GEX, nowhere in the Scenery Library will you see a GEX entry of any sort. Again, GEX is not a 'scenery package' per se, but is instead a replacement texture tile set for the default foundation set of FSX terrain textures. Thus, there are no considerations regarding its placement in the Scenery Library. I use both UTX and GEX for all their respective available areas, and I cannot recommend them highly enough. UTX compliments GEX and they work together to create a truly enjoyable and immersive flying experience. The GEX lineup also now includes GEX-APT (Atlantic & Pacific Tropics). Coupled with any specific scenery packages that you might have (such as Fly Tampa's St. Maarten and/or Grenadines Caribbean packages), you will feel that you are actually there! I use all of the above, including those two particular Fly Tampa packages; and the flying experience is very immersive and just great! Go for it, you won't regret it! Hope this helps, Blue skies- Rusty
  6. Hi there, Even though I have updated my Corfu X v1.10 to v1.11 (twice now), Aerosoft Launcher, upon checking for updates for my various installed Aerosoft products, keeps advising me that there is the v1.11 update [still] available. i.e.: AL keeps indicating that the presently installed version is 1.10 and keeps coming up with the message "New version ready for download! (Version 1.11)". Any thoughts as to why AL does not recognize that I have executed the v1.11 Corfu X update? I have double-checked the files in the ...Corfu X & ...Corfu X\Scenery folders, and they are indeed the same files contained in the downloaded v1.11 zip update file. Thanks a bunch, Rusty
  7. 4 Nov. Hi Andras, I had always thought that the yellow car was an intended part of Andras Field, and that it was part of its AF's AI cars group. I do not have any traffic addons, etc., so I do not suspect that it is an intrusion caused by another addon. Additionally, the yellow car seems to know where to go! That is, it makes the appropriate turns, it stops at the barracade, etc. Hopefully this helps . Rusty
  8. Ahhhhh...success! I moved a copy of the season.exe utility file to the Aerosoft parent directory (where the installation process had initially created a shortcut link target to), and voila- now when I open the utility from that location, it lists the 3 related sceneries in the box. It seems that the Balearic installation process, has an anomaly whereby it places the season.exe file in the wrong directory. It is placing it in the Menorca X SC subdirectory, when in fact it should be placing it in the parent Aerosoft directory where its shortcut attempts to originally target it. Hopefully, this helps and lets the you and the good folks at Aerosoft know what is actually happening with the Balearic installation process. I am sure that I am not the only one that this happened to. Thanks again for helping me brainstorm this one! Your comment that the respective sceneries should be indicated helped very much, thank you again...Rusty
  9. Ok, thank you Shaun. As I had indicated, the Balearic package installed the Season Tool shortcut with a broken link that was targeting the season.exe file in the wrong directory, in a directory where it was not actually located. The installation process had it targeting season.exe in the ...FSX\Aerosoft parent directory. It was not there. The Balearic installation process actually installed season.exe in the Menorca X SC subdirectory. Therefore, I created a new shortcut to the season.exe utility for where it had actually been situated- in the Menorca X SC subdirectory. Now, when I click on the Season Tool shortcut, it targets the season.exe file in the Menorca X SC subdirectory and sucessfully opens the utility. However, none of my Aerosoft sceneries are listed in the "Support for... Aerosoft's" box. In fact, nothing is listed in there, the box is totally blank. All my [Aerosoft] sceneries seem to be working properly. Could the anomaly whereby no scenery is listed have something to do with the Balearic installation process having initially created an inappropriate shortcut target to the program? Should the installation process have placed the season.exe utility file in the Aerosoft parent directory as the created shortcut had indicated by its target? Or should the target have been towards the Menorca X SC subdirectory where the installation process had actually situated the season.exe file? Is this perhaps a problem with the Balearic package and not with the individual Menorca package? Just trying to figure out why my Aerosoft Season Tool seems not to be locating or identifying *any* sceneries in its list. Note that I do not have any FSX items located in the program files directories- I have FSX and its related addons all located in a separate dedicated directory. Thanks again, Rusty
  10. Hey there Andras, Thanks very much for your response and for taking a peek at this issue. It's not really all that critical, and I know that you have a lot on your plate, so not to worry- I know that you will ponder it when time permits . Hopefully, the fact that this issue seems to pertain *only* to the yellow car will help you track the solution down. Evident by the #06 photo above, even though the other AI vehicles are also casting shadows (if you look very closely, the shadow under the nearest gray truck to the right of the yellow car is just faintly visible under the vehicle), this problem seems to only manifest itself for the yellow car. Thus, perhaps the slight differences in the yellow AI car's programming attributes versus the others' may point us toward a solution. Please let me know if I can help in any way in tracking the cause down!
  11. Hi there, With regard to the Balearic Islands package, I see that there is a utility called "Season Tool" included in the program's group. The link thereto [from the Windows Start Menu] is broken, and the program link's target seeks to find the season.exe utility application in the principal Aerosoft directory. I actually located the season.exe application in the ...Aerosoft\Menorca X SC subdirectory, and I was able to redefine the target (I placed a copy of the season.exe application file in the originally-intended ...Aerosoft parent directory) so that the Season Tool command now successfully opens the utility. I also made a link to the season.exe command that resides in the ...Aerosoft\Menorca X SC subdirectory where the Balearic installation process originally installed it too. My question is this: Inasmuch as I located the season.exe application in the Menorca X SC directory and not in the principal Aerosoft directory that the original link was originally targeting, does the Season Tool utility apply only to Menorca, or was it intended to apply to all islands in the Balearic package? Is it possible, inasmuch as the target was originally seeking to find the season.exe utility in the principal Aerosoft directory, that the utility applies to *all* Aerosoft sceneries that might reside in the Aerosoft directory (eg: Andras Field, Corfu X, etc) as well? Thanks a bunch, Rusty
  12. Hi Ole, Any luck, or word from Andras, on this one? Not that it is a big deal, but just curious as to Andras's thoughts regarding this. Thanks a bunch, Rusty
  13. Hey there Ole, Thanks much! You are right- I actually noticed this anomaly after installing v1.17 on the new machine and prior to my installing the two subsequent updates. The funny thing is, I never noticed any such things on the old machine nor with the older release versions thereon. Whereas my last system was running Win7 Hm. Prem., the my new i7-960 system is running Win7 Ult. The only other very significant difference between the two systems is that the new system's graphic card is Nvidia GTS 450, whereas the old one's was the 250 series. Could it possibly have to do with the difference in the new card possessing GDDR5 memory versus the DDR3 memory of the old card? I don't really know, as I am not really a computer person- just brainstorming with hopes of assisting in tracking this thing down . Let me know if there is any other info. that I may provide [with regard to my system, my installation, etc.] to help Andras and the folks pin this one down. Thanks again, Rusty
  14. Hi folks, It's been a while, but I've a new PC now, and I've therefore begun to set it up, install [all] the software (a total pain-in-the-___ ), etc. Thus, my initial Andras Field install on this new system was the full version 1.17. I followed this by installing [into the AF directory] the two subsequent and recent incremental updates- v.1.18 & v1.19. I installed them directly onto the existing, newly-installed full version 1.17. As always, AF is wonderful and nifty, and I would not do without it. I have noticed two things about which, hopefully, you may have some thoughts, ideas or suggestions: 1) See the photos below. It seems that, for the AI yellow car *only*, there is a graphic artifact, a dark black line, that extends from the car, no matter where it is located at the time, to full across the extent of the AF scenery boundaries- regardless of what other objects may be in the path thereof. This seems to happen only with the yellow car as evident by the photos below. The final photo almost makes it appear that this is an artifact from the car's shadow perhaps. Please let me know what you think. 2) I remember that, some time ago, we had discussed the disappearance of the ambient sounds that had otherwise been so integral to earlier AF version releases. With the current v1.19, some of the ambient sounds have returned, but they appear to be much more muted and much lower in intensity. I do not hear the ambient social gathering voices in the residential houses section of the Airpark anymore, nor is the waterfall very loud- unless you are nearby it via taxiing, etc., the discussions adjacent to the diner seem much less apparent, etc. I found the sounds to have been an enjoyable and significant, if not subliminal, part of the overall immersive AF experience, and I miss their greater intensity! . Would it be possible to reintroduce the more robust ambient sounds with later version releases? Thanks a bunch, Rusty
  • Create New...