Jure

Rafal, use Imagetool from the terrain SDK for FS2004. Put the file to the textures folder, go to DOS mode (RUN->cmd) and for starters, typeimagetool -?to get a list of all possible parameters. You could try this one (but please try it first on a few .bmp's in a temporary folder):imagetool -DXT3 -nogui -nomip *.bmp (if you don't want mipmaps use the "-nomip" thing, otherwise don't use this switch)I am not behind my FS computer right now, but I am pretty sure this will work. I remember Imagetool saving files with different extension than .bmp in some case, but that can easily be ammended by using the right parameter. Experiment... :)Regards,Jure

I concur.... :( Regards,Jure

They would remain installed if you went through with all the steps and after copying the "new" FS9 rename the original folder back to c:\FS2004. The problem with this approach is that if you wanted to uninstall a scenery from your current FS9 installation and install it to the new one on a different drive, the installer would only always find the current FS9 because of the registry entries. I often install scenery to a dummy folder, copy the contents to a folder of my choice (I keep a strict folder hierarchy and placement for scenery) and then uninstall it. With some sceneries this won't work, of course, depends what kind of protection the authors put in place. What you could do is install a second copy of FS9 to the same drive. Current one in C:\FS2004, for example, and the fresh one in C:\FS2004new. Then you could uninstall a scenery from your current FS9, after that go and rename the folder C:\FS2004 to something like C:\FS2004Current and rename C:\FS2004new to C:\FS2004, thus fooling the installer in thinking that it is still the same FS9 and install the scenery to your virgin FS9 installation.I have such a case, one FS9 installation I use for heavy stuff flying and the other for VFR flying. Both can share the same scenery (just a matter of editing scenery.cfg a bit) but aircraft are totally different. Just remember to always rename the wanted FS9 installation folder to what you have in the registry - in our example, c:\FS2004. Phew... I hope it doesn't sound too complicated!? :(Regards,Jure

It could be done... what I did was to rename my current FS installation from c:\FS2004 to c:\FS2004xxxxxx and installed FS9 again - into the same location so you don't mess up the registry. Once installation is done, simply move the contents of this newly created c:\Fs2004 to the other drive (let's say, D:\FS2004), delete the folder c:\FS2004 and rename c:\FS2004xxxxxx back to c:\FS2004....Regards,Jure

Hey Paul, great to hear from you as well! :( All is well here, I hope you are doing great, too. I am starting to go into GoFlight modules direction these days. And that 3-monitor setup with TH2GO is very tempting, too. And a secondary PC through WideView for instruments display and.... argh! :( But I digress...You are using FSUIPC, right? If so, then you might be interested in multiple FSUIPC.ini's as well. Each add-on aircraft that I fly has practically it's own fsuipc.ini with it's own settings. Much more readable than using "Aircraft Specific" settings in a single fsuipc.ini. Here's how (I'll use a B744 as an example):1. Create a new fs9.cfg in your main FS9 folder and name it "fs9_b747.cfg" or something like that.2. Create a shortcut as described and point FS9.exe to this .cfg file.3. Go to your Modules folder and make a copy of "FSUIPC.ini" and FSUIPC.key"4. Rename the copies of these two files to "FSUIPC_b747.ini" and FSUIPC_b747.key" respectively5. Open fs9_b747.cfg and right on top insert these two lines (brackets are square, of course)(FSUIPC)ControlName=FSUIPC_b7474. Save fs9_b747.cfg, double-click on your new shortcut and FS9 will start with these custom fs9_b747.cfg and FSUIPC_b747.ini files. 5. Change settings to your content and never look back. :( Regards,Jure

Hi,I have four installations on two different drives without any problems. What I did was to simply copy a virgin FS9.1 installation three times and that was it. One is kept as a clean installation, the other three serve different purposes. So, simply duplicate the whole FS2004 folder. One thing... I use custom fs9.cfg files that reside in each FS installation main folder, not the one in C:\Documents And Settings\<USER>\Application Data\Microsoft\FS9\FS9.CFG. What you do is copy the fs9.cfg file from the above location into your FS9 installation(s) main folder and create as many shortcuts as you have fs9.cfg files. You can name them as you wish, for example, the one in your main FS installation could be "MyFirstFS9.cfg". Right click on the shortcut and in "Target" put a statement like this:"C:\Program Files\FS2004\FS9.exe /cfg:MyFirstFS9.cfg"When you click on this icon, the correct FS9 will start. Do the same for your second installation... if it is, for example on the D: drive in FS2004 and you renamed the fs9.cfg file to MySecondFS9.cfg, put the following into the second shortcut's "target" line:"D:\FS2004\FS9.exe /cfg:MySecondFS9.cfg"Again, when you double-click on this icon, the FS9 on drive D: will startYou can have as many fs9.cfg files as you wish and call on them in the way described. I use this for different jostick/yoke mappings, to run different FSUIPC setups for different aircraft and so on.Regards,Jure

Ya, this started happening to me as well. Never, ever I had a g2d.dll error before and in the end I came to the conclusion that the only things that was changed was - adding REX... now, before accusing anybody of anything, more testing needs to be done. It could well be just one rogue texture that spoils the game.... had a loooong flight from Dubai to JFK yesterday and right on approach to 13L, a few miles before the turn to CRI VOR, suddenly all clouds disappeared and poof! a g2d.dll error. I was so disgusted that I went, resaved ALL clouds textures that REX made for me (in the main Texture folder) and restarted the flight. Went without a hitch...Bottom line is that this error creeps up once in a while and I simply cannot reproduce it. When I then re-save all clouds textures in FSImagetool, repeat the flight and all is well. Without exception!As I said, more testing is needed, because it could well be something entirely else than REX (which is more than fantastic!), but so far, events point into that direction.My 0.02

Yes, that truly is a neat little gadget! If I am not mistaken, a first in FS!? I find myself shifting from RC towards PFE more an more as of late. As for the map, well, FS Flight Keeper has it all! That, in my opinion is one of those "must have" add-ons. Switch on the ACARS gauge and there's your map. With selectable amount of details, too. An awesome combination with PFE...Ok, commercials over, let's get back to the movie. :( Regards,Jure

Great video, yes, but recorded at 1/10th speed and then speeded up. Look at the video "Landing jfk.. not perfect but...AMAZING quality!!"....Regards,Jure

Since I also assign everything in FSUIPC, I usually delete all assignments for joysticks/yoke/pedals in fs9.cfg(s) and put the statement "LOCKED=1" below each controller's first line. Thus FS9 cannot assign anything to any controller on it's own. I still get one or two "ghost" commands once in every blue moon, so maybe I should upgrade my drivers, too... thanks for the tip! Such a "ghost" command ruined my flight the other day. Just above the rwy treshold at LaGuardia the autopilot came ON and the Emb-135 immediately went into a sharp left turn! The crash was quite spectacular.... :( Regards,Jure

Hi,it happens to me occasionaly. A CTD without any error message whatsoever. I found a solution that works for me - a bizzare one but it works. Now, these CTD's usually happen when I fly to my home airport LJLJ sometime in spring. I found that if I go to LJLJ when I start FS, I will get a CTD, but not always. If it happens, I simply restart FS, go to LJLJ again and - it will load normally! Then I simply go to the departure airport and do the flight. The trick is to go to the "offending" airport first and all will be well. Why? I have no clue... Like you, I also deactivated all add-ons, AI and whatnot - I even use the Modules folder clear of .dll's that belong to add-on aircraft (I use custom fs9.cfg's and batch files to copy only the relevant .dll to the modules folder when I fly that particular aircraft), all to no avail. But the above solution works for me. For some reason. I have no explanation... if I remember correctly, there is a sort of a seasonal bug within the FS9 (when seasons are changing) that could cause a no-error CTD, but I really don't remember the details about that. :(Regards,Jure

Well, I like what Eric has done. As for what is improved and what not, here is the full list so it is clear: http://emarciano.free.fr/Cockpit/MCDUDoc/D...on.html#versionOne thing that always draws me back to the Airbus is how beautiful the Fly-By-Wire system is. I am using a Thrustmaster T.16000M joystick which is supposed to be VERY precise - and it is. It is an absolute joy to hand fly the Bus with this setup....I don't and never had any issues, FPS are great, no stutters, no CTD's, no nothing. Like it was said before, do not assign axes in FSUIPC for this bird and all will be well. True, there are still issues (or bugs if you will) that might or might not be resolved, but they are not major show stoppers. Combined with FS2Crew, both, Vol.1 and Vol.2 are very flyable and most likely the only ones we will ever get for FS9 - at least that is valid for the big buses, the A330 and A340. Regards,JureP.S.: If if were not for the publishers, there would be more Service packs, too. But somebody very wise decided to pull the plug on further development (or bug squashing)

Benjamin, I just checked... it used to be in the library, but apparently got lost when AVSIM was hacked. File name was vc_light.zip. I can send it to you if you wish or better still, I should upload it to the library again. Will do so when I get home later today....Regards,Jure

For what it's worth, I find the Feelthere Airbus' Fly-By-Wire excellent. A real joy to hand fly, precise and responsive. Apart from the problems already described, both, vol.1 and vol.2, are decent and I still fly them a lot. Better than PSS? No doubt, at least for me. With a bit of planning it is not hard to bypass the flaws in the vertical profile logic of the FMS - the rest works ok. Just my 0.02

Roger,how about a setup like this:- Main PC: TH2GO, driving 3 monitors in one "stretched" view - ONLY outside view, no instruments!- Secondary PC: connected via Wideview driving 2 monitors below the 3 monitor display for instruments only On the secondary machine you can have FS settings at absolute minimum, because it only shows instruments. I've seen a few setups like this on the net and I am building one myself these days. Regards,Jure

Yes, this is true. I got this very same idea long ago and actually tried to change some of the default textures to try it out. I changed a bunch of them to 512x512, but it didn't work. Default textures are limited in size, just like Feng wrote. Unfortunately. Regards,Jure

No log message? I had just such a case a few days ago. It was a faulty .bgl file in one of the scenery packages. I would temporarily disable ALL add-on sceneries and try another flight. This way you can at least establish if an add-on scenery is to blame. Good luck!Jure

Philip,probably... have you checked for duplicate AFCAD's? Or rogue landclass files residing in a wrong folder? Could also be a corrupt texture on one of your AI aircraft... Have you looked in your event log to see which of the .dll's crashed? Right click on "My computer", select "Manage", then select "System Tools/Event viewer/Application" and look for any message with FS9 in it. Regards,Jure

Dallyborr,sounds great, I'm very interested to get my hands on a good LYBE airport... :( any chance for AES?Thanks!Jure

Great idea; I'm in, of course.... :( I won't switch to FSX, so a NGX for FS9 would indeed be nice.Regards,Jure

:( :( :( FS9.75 you say? I have it, too, you know, but until now I wasn't aware it was so close to FSX with it's version No. B) I second Mad dog's suggestion, try the ENB series bloom, that should raise the version No. even higher...We've never had it this good, methinks. These are the "good old times", right now. Regards,Jure

... and one more. The lil' Fokker is among the best add-on aircraft, period. :(To ease the learning curve there are also a couple of excellent tutorials available. My first flight was a tutorial flight and after that I was able to fly anywhere. Regards,Jure

Hi,I mainly use ASv6.5 because it is fast and reliable. Sometimes, when I have enough time, I do use ASA and it does indeed give "nicer pictures", but it simply isn't where it's older brother is. Cloud pops, screen flicker and it's overall speed (try running your sim at anything faster than 2x!) simply make me go back to ASv6.5. But I haven't given up on ASA, I am sure Damian and the crew over at HiFi sim will iron these little buggers out. One thing for sure - ASA has LOTS of potential! :(Regards,Jure

Hi (again) Steve, :( I got REX yesterday and I must say I love it to pieces! Just like you, I use a bunch of custom files like Halo.bmp, then envmap.bmp, sunglow.bmp, spotlight.bmp and so on... I even have some batch files to swap some of these files depending on which aircraft I fly (I use multiple FS9.cfg and FSUIPC files - one for each "major" add-on aircraft). Did I have any problems with REX? No, Sir! I can select what I want REX to install and so far, it kept it's part of the bargain. :( Just to add, I use FE, GEII Pro, FS Elemental Natural Pack, some custom water/dusk/dawn/contrails stuff that I incorporated into FE, then sometimes I use ASG dawn and dusk textures and I can be quite picky as to what I want overwritten and what not. If you are just after clouds & sky & water - go get REX! I must say water hasn't convinced me, but it's still early days, have only tried one set so it is not really fair to say that. Sky & clouds are fabulous... :( Anyway, take a minute or two to configure REX to your liking and it will not overwrite anything you don't want it to. To be on the safe side, make a copy of your FS9/texture and FS9/scenery/world/texture folders if you wish. But even that REX will do for you with initial backup. Regards,JureEDIT: forgot to add, I also use ASv6.5 and sometimes ASA

Hi Tim,thanks! Sounds great... WideFS support means a lot to me - I tend to keep my FS computer as clean as possible and run all "auxiliary" applications on my secondary rig. For a while I even had a third computer in that role... :( Steve: As far as I understand things, REX v.2 will let you install only the things you want and leave the others (for example: runways textures, etc... ) intact if you so desire. Right now I am running an interesting combination of FE, GEPro II, ASG and a few freeware sets of water and clouds on my FS9 installation. Regards,Jure