Jure

Hi,Look here: http://simviation.com/hjg/ 18 different DC-8 aircraft to download. :)Regards,Jure

Jim,same here. When ASA is updating weather in FS9, I get multiple flickering. It is not hardware related because I have just replaced my computer (MoBo died) and it is exactly the same as it was on the old one. Before I had an nForce chipset based ASUS MoBo with an Athlon FX57, GeForce 7900GTX, now I have an Intel based machine with a C2D E8500 and a GeForce 9800GT. It is definitely ASA that is causing the flickering, because with ASv6.5 I do not see it (I am using both apps, 50/50)I cannot say that this flickering occurs on every weather update, but certainly on every flight. One more thing I noticed.... with accelerated time ASA seems to be struggling. "Fs location changed" or something like that appears on the main screen and ASA begins the new updating cycle immediately - even if it was right in the middle of one already. 2x is OK, 4x is not OK, I see lots of these messages. 8x is absolutely too much for ASA. EDIT: I forgot, video drivers up to date.Regards,Jure

Hi,same here, SP1 installed Build 355 running FS9, ASA via WideFS. Most notable case on my last flight when I was descending into VHHX, Kai Tak. There was supposed to be a broken layer of clouds, but the closer I got to Hong Kong, the less clouds there were in the sky. Then poof! and all clouds were gone and when I was over the CH VOR, poof! again and I finally got my broken layer of clouds in accordance to METAR - quite spectacular, I might add. :(Regards,Jure

Mack,not to hijack this topic, but 2Gb *should* be enough to handle the strain FS puts on the memory. I do not have Ultimate terrain but everything else and can routinely fly to, let's say, Aerosoft's EGLL, or FSDT KORD & KJFK with PMDG B744. True, I had a few OOMs, but they were invariably a consequence of some rogue LC file. Or a duplicate AFCAD. Ok, back to topic now... I think there is much more to AES than just active gates. Pushback, a follow me car, catering vehicles, buses that bring pax to the aircraft, rain/snow rwy textures and so on. I've seen a few different versions of all these things and like Mac says, AES is a uniform system throughout the sim and the best one at that. So, when I buy an airport, I do not associate the price of an AES credit pack with it. Regards,Jure

Another very satisfied AES user here... like Geddy_2112, I don't even fly to non-AESed airports anymore. I noticed that the other day after installing a really nice freeware airport and when after landing there I arrived at the gate, there was no AES. Well, something was missing and true enough, I haven't flown to that airport anymore. My loss? Yes, for sure, there are many great airports out there that are not supported by AES (yet, I hope :( ) Especially Russia comes to mind with it's many really well made freeware airports (Oliver, if you are reading this.... :()But I really like AES and don't mind paying a bit extra. As it has been said, there are a lot of "AES cheap" and even "AES free" airports, plus free credits really start to accumulate after you buy enough credit packs - I stopped counting after the tenth. This is really just my personal opinion, but I would like even more AESed airports and do not care for any other active gates system. Also, I am buying airports that have AES support exclusively. How much am I willing to pay for fully functional airports? Ugh..., that's a tough one. So far, I haven't complained when I was buying them AES credit packs; in fact, I was more than happy to see that more quality airports got AES support. Flight Simming (FS9 exclusively) is my hobby and I am willing to spend some money on it. I can easily see myself flying FS9 for years to come. FSX I dumped after an intensive two months period and I don't miss it one tiny bit. Consider, how much do you get for 15

Na, I can see the "banding". In the dark and it is quite faint, but visible. I believe it is a "feature" of nVidia graphics cards. You have a geForce card? I remember the shock when I first switched from the good old Voodoo to my first geForce! Faster, yes, but the Voodoo was light years ahead in quality. Anyway, I get this "banding" as well in the (simulated) night skies. My first reaction would be: switch to 32-bit because it looks like a 16-bit image or even less, but it already IS at 32-bit. As I said, I believe it is common with nVidia cards. For lack of a better description, flying at night on an nVidia card is a 16-bit depth affair. :( Having said that, I hope somebody can prove me wrong and this can be indeed "mended". :( Regards,Jure

Steve,ha, I haven't thought of that. Thanks! :(Regards,Jure

Not necessarily... if you stray into an area with "severe icing" even pitot heating isn't always sufficient. Happened to me quite a few times in the past.One way to avoid this is to set icing up in FSUIPC if you have a registered version and not allow for severe icing.Regards,Jure

Paul,got your message, thanks and thank you for your recommendation, too. I replied via e-mail which you probably did not get? I notice that my e-mails often get labeled as spam for some reason. I'll resend it on monday when I get back to work. I am actually thinking of building a new system and your spare RAM could be put to good use, but first I need to see if salvation of my current FS9 installation will succeed. I will know on tuesday if all goes well and will then be able to respond to your offer after I know what I have to do. I liked the three computers setup that I used to run. With WideFS you really have some options to play with. The second and third computer also provide for ample room to make complete backups of my huge FS9 installation. Yes, I want more than one backup. As life has (again) taught me after the motherboard decided enough was enough :( I am now going a full week without FS9 and it's not fun. Addicted? Me? :( Regards,Jure

Hey Paul,confirmed. I ran such a triple setup for a long time. Just like cshark172, one PC had RC and ASv6.5 running while the other had the rest of the apps (FSFK and stuff) running. The FS PC was quite happy with both clients. :(Regards,Jure

Well... a new 9800GT for me also. My old Asus MB bit the dust, so, here we go again... I'd be interested in getting an answer , too. :(Regards,Jure

Geoff,you say "with main 2D view"... are you using a second monitor? I found out that the bloom plugin doesn't work (properly) whenever the second screen is active - when a sub-panel is pulled from the main to the secondary monitor. Has anyone found a solution for that? Other than that, I am also seeing a negligible FPS hit with settings very similar to Johan's. Regards,Jure

This is happening to me as well. FS9 and ASA via WideFS, just like Ben.Regards,Jure

Same here... was flying EGLL-OMDB and as beautiful as the clouds were, I experienced quite a few cloud "pops". Regards,Jure

Guys,are you using Active Camera? If yes, then disable it's "Internal Pilot View". I have mapped the key CTRL+F11 to one of my TQ buttons just for this purpose. It will disable AC, but you don't need it while using TrackIR. When not using TrackIR, just press CTRL+F11 to enable AC again. Regards,Jure

John,if there is another joystick section in fs9.cfg, then delete the old one. In fact, your best bet would be to delete all joystick sections and let FS build new ones. After that, set up your joystick the way you want and put this after JOYSTICK_MAIN... and JOYSTICK_SLEW... lines:LOCKED=1FS will let your settings alone with these line inserted, but be warned, you won't be able to change the assignments within FS!The reason for new joystick section(s) is that you probably unplugged the joystick and then plugged it back in another USB port. Could that be it? In that case you get new JOYSTICK_MAIN... line with a different address in fs9.cfgRegards,Jure

Edin,try "Arm all" on Shortcuts/Cabin Doors menu on the FMS.regards,Jure

Hi Boby,Ok, let's see how I did a custom cfg file for my PSS/Posky B777 merge. You can use this example for every single aircraft in your fleet if you wish.1. find your fs9.cfg in C:\Documents and Settings\USER NAME\Application Data\Microsoft\FS92. Copy it to your main fs folder.3. rename it to FS9_po777.cfg (or whatever you wish)4. I suggest you create a folder on your desktop where you will keep your shortcuts for all custom configurations. Mine is named simply FS5. In this new folder create a new shortcut and name it so that you will know for which aircraft it is intended. In this case, mine is called PSS_Posky_B7776. Fill in "Target" and "Start in" fields as you see on the picture belowWhat is important is the second part in the field "target": the part /CFG:"FS9_po777" tells fs.exe which config file to use. It MUST match the name of the file you just created in your FS9 main folderThe following steps are only valid if you use FSUIPC - registered!7. in Wordpad, open FS9_po777.cfg which you have created in your main FS folder.8. Right on the top, put these two lines (The parenthesis around the word FSUIPC are of course... huh, what's the right word? Well, like all other parenthesis in fs9.cfg, LOL. I cannot use them here. These two lines will tell which FSUIPC.ini to use with your custom settings for this aircraft.{FSUIPC}ControlName=FSUIPC_po7779. Go to your main FS folder/Modules and find FSUIPC.ini and FSUIPC.key10. Make copies of these two files and rename them exactly as you wrote under 8. So, in my example, you have FSUIPC_po777.ini and FSUIPC_po777.key.11. You're done! Double click on your newly created shortcut and if everything is done correctly, just select your chosen aircraft, modify all controls and they will never be changed again. Probably. If FS changes assignements in FS9.cfg or FS9_po777.cfg, you can put a line LOCKED=1 under each JOYSTICK_MAIN.... and JOYSTICK_SLEW.... lines after you have set it up. This will prevent FS from messing with your controller's settings.However, I advise you to assign everything, including the axes through FSUIPC and disable joysticks in FS altogether. Let me know if you have problems, I hope I haven't let anything out. I am using a slightly modified method for my different aircraft where I also copy necessary .dll file(s) from a backup location into the /Modules folder, which is thus kept very clean. Only the necessary .dll gets copied when I start FS9 with a specific .cfg. But that's step two. :(EDIT: as for your question... I am not sure if there is such software. You can use the attribute "This aircraft only" in FSUIPC, but I found out that the FSUIPC.ini quickly becomes totally illegible with multiple aircraft configs, especially if you use some advanced buttons/axes/keypresses programming. I much prefer separate FSUIPC.ini files.Regards,Jure

Hi,yes, I use multiple fs9.cfg and fsuipc.ini files. For each aircraft or aircraft group I have a separate icon. Each of them has custom controls and keys assigned. I am at work right now, but when I am home, I can post a detailed description. Either here or you can send me a mail or a PM. :)Regards,Jure

Thanks for this one, John! Very, very useful! And by the way, congratulations on your new system :(EDIT: Speaking of backups... I use xcopy to regularly backup my FS and Scenery to another computer. Goes quick, with the right parameters it just copies the changes that occurred since the last backupRegards,Jure

Michal,you can also put a "LOCKED=1" statement in FS9.cfg under each JOYSTICK_MAIN and JOYSTICK_SLEW line. Works like a charm and prevents FS from assigning and re-assigning commands and axes each time you start FS. Useful for aircraft where FSUIPC assignments do bad things (Feelthere Airbus) :(Regards,Jure

Well, I "lost" winds aloft as well. I have no clue what was different yesterday when I did my first trans-Atlantic flight, but today, winds aloft were definitely gone. John's method works, but that's not how it should be. Regards,Jure

Paul,sorry, I have somehow missed this post. I have checked and the two entries are both set to false, just like yours. I will do another flight across the Atlantic tomorrow and see what happens. All my flights with ASA were in continental US. Except my morning flight EGLL-CYYZ, that is. No trouble with winds aloft, but I had trouble getting ASA to send a modified destination airport METAR to FS. While ASA correctly showed the changes in three different tabs, including the map, FS stubbornly refused it. Only after I let ASA completely alone after I changed that METAR once more, it finally sent the correct data through to FS. So, that got me thinking... maybe ASA needs to be left alone while synthesizing/submitting weather data? Just for the record, I have kept my ASv6.5 installed. In fact, I haven't touched anything except installed ASA. Jure

That is happening to me as well. I was at EGLL, it was 5:30UT and I set the FS time to 7:30UT. ASA reset the time to 10 something. Jure

John,for what it's worth... I successfully completed my EGLL-CYYZ flight and had winds aloft all the time, just like the nav log of briefing reported them. Jure