longbreak754

A slightly different view to expand on Charlie's suggestions: AI Aircraft - Most users will simply put them into the appropriately named default folders contained in the default SimObjects folder but you can create new folders to hold them - for example AIModels or AIFastJetModels etc. To do this you simply need to create the holding folder within the SimObjects folder (or outside if you wish) and then add a path entry in the [Main] section of the fsx.cfg file so that FSX can find them - here are examples of changes required: [Main] User Objects=Airplane, Helicopter SimObjectPaths.0=SimObjects\Airplanes SimObjectPaths.1=SimObjects\Rotorcraft SimObjectPaths.2=SimObjects\GroundVehicles SimObjectPaths.3=SimObjects\Boats SimObjectPaths.4=SimObjects\Animals SimObjectPaths.5=SimObjects\Misc SimObjectPaths.6=SimObjects\AIFastJets SimObjectPaths.7=SimObjects\AIHeavies SimObjectPaths.8=MySimObjects\AIHelicopters SimObjectPaths.9=C:\MySimObjects\AITrainers The first 6 SimObjectPaths entries (0 to 5) are the FSX default items. Entries 6 and 7 are holding folders created within the default SimObjects folder. Entry 8 is a new holding folder created outside of the default SimObjects folder but still inside the main FSX folder. The last entry is an example of folder created outside of FSX - note that, in this instance, you have to provide a full path name including the drive letter. Addon Aircraft - you could use the same principle as outlined above for AI but IME they are better off being placed in the default folders. Most payware addons will automatically suggest to install into the default location but you can usually select a different location. But note that not all payware will allow this and some will only install into the default location. 3rd Party Scenery - Again you can create a folder structure to meet your needs inside or outside of FSX - even on a different drive(s) if space is a problem. As with payware aircraft, most payware addon scenery will act the same as described above. The important things to remember are these: 1. All scenery files (i.e those that have a .bgl extension) MUST be placed within a subfolder called Scenery. 2. All texture files (i.e .bmp, .agn, .dds) MUST be placed within a subfolder called Texture. 3. The scenery location must be known to FSX i.e activated - achieved by using the Scenery config page and pointing to the folder system when activating the scenery. To clarify points 1 and 2 - Say you create a new folder called Scenery A and then: 1. Simply place all the files in the folder - the scenery will not display and may cause issues with other parts of the immediate area or in rare cases cause FSX to crash. 2. Create a Scenery subfolder (e.g Scenery A\Scenery\) and place all files into the subfolder - at best the scenery may partially display the scenery (namely those elements associated with the .bgl files (airfield runway, taxiways etc) but not display any texture based elements etc. At worst, it will display nothing or cause issues with other parts of the immediate area or again, in rare cases cause FSX to crash. 3ed Party Timetables - The accepted default location for traffic files is FSX\Scenery\World\Scenery folder but as they are essentially scenery files (they have a .bgl extension) they can be placed in any active scenery location - again inside or outside of FSX. Another important thing to think about (touched on briefly by Charlie with his reference to any included README file) is that some scenery may include extra files that must be placed in specific folders for it to display correctly. A common example is if the altitude of the new scenery is different from the original FSX default. This is normally accomplished by the inclusion of a custom .bgl file that must be place in the default Scenery\World\Scenery folder. Some will also contain 'global' texture files that will need to be placed in the Scenery\World\Texture folder

Hi Bernd, Some of the files you want can be found on the MAIW website suggested in post #2. They are mostly contained within the Mirage 2000 packages - as per the info contained on the mirage4fs website. the reason why you get the MAIW bad URL link is because the MAIW website was recently updated/rebuilt. Also note that for many of the MAIW sceneries you will also need to download the MAIW Objects Library You will need to create a free account to be able to download the files but you can browse as a guest and read the info appertaining to the package

@ Loki, Totally agree. IME it started when it went from being an 'on demand' app to a 'always on' app and the company released press briefings that implied that instead of the product being solely viewed an anti-malware (AM) product to be used alongside a AV suite it could actually replace a user's AV suite. This implication was misleading and it was later clarified by the company that it was not a 'true' AV tool That said, Norton can also be aggressive but most of its false positives come from a 'in-house' virus definition, namely WSReputation1. Norton make it quite clear on the website that this warning is flagged solely on a file/apps reputation based on its usage by Norton users - the fewer the users the more likely it is to be flagged.

Hi Blue, Agree with the comments made by Leon... Have both Malwarebytes (M) and Norton (N) installed: 1. With both M and N active only M gives warnings. 2. With only M active get warnings. 3. With only N active get no warnings. 4. With both M and N deactivated get no warnings from Windows Defender (WD). Downloaded file and scaneed it: 1. M says it contains PUA - potentially unwanted app. 2. N says that it is clean. 3. WD says it is clean. For final clarification uploaded the file to a website called Virus Total - LINK - this tested the file against 40+ anitvirus suites and cam back clean. You can deactivate M and will still be safe as WD will start up - WD is an inbuilt AV tool that comes with Windows. It is automatically disabled if a third party AV suite is detected.

Hi Rick, Welcome to the forums..... There are a number of useful guides on the FSX Hanger Main page - found HERE. Look at the left hand column and about halfway down you will see an entry titled Install Guides - plenty of good info there. If you are having particular trouble following the guides or with a particular download - some can be simple installs and some can be more complex depending of how the model was constructed by its author - then you are more likely to get help from others if you are more specific about the download itself. Provide info such as the download file name, where you got it from and details of the issue(s) encountered. Also check out the full file contents as there maybe a readme with specific install instructions. A final suggestion is to use the correct forum - i.e. for FSX issue the dedicated FSX forum - as this will increase your chances of getting answers to your problems..

Once the install has finished you can use the tools available in your Steam account to move the installed files to somewhere else - a lot quicker than deleting and then reinstalling again....

I also think that it is worth noting that, from my reading of a number of articles and other threads, is that, like FSX and FS2004 before it, the install will include a number of essential files into locations on the C:\ drive by default, irrespective of where you install the main program. And, like in FSX/FS2004, these files will not be 'movable'.

Hi Jonny, Yes, based on the info available you should be able to install on a different partition or a separate drive. How you will do that will depend on how you buy it via digital download - either direct from MS or via Steam - or if you buy it on the 10 DVD package available from Aerosoft - this is in the EU only. See this thread for some additional info on what will be required. As for framerates - IME of using FS2004 and FSX on both a different partition and on a separate drive I wouldn't think there will be any loss.

Hi Rob, It could be that the fs9.cfg file is there but with a different or corrupt extension...for example fs9.bak Try a search using fs9* - the inclusion of the * is a "wildcard" instruction so it will list any file that starts with FS9. Or you could try *.cfg - this will list all files that ends with a .cfg extension. It could also be that the file is hidden by windows by default. There are a number of ways to change the settings to display hidden files see HERE

I think it just the guy's personality - he has started a number of threads regarding VR where he insists that VR is the ONLY way to go, that WE all should be buying it and if WE don't use VR then we are not TRUE simmers like HE (supposedly) is.....

Hi Rob, Could it be that your system is missing some 'essential libraries'... Use Programs and Features to check if you have any of the following 'libraries' installed or, if you wish, simply download and install them - the installers will check for any previous install and will replace any missing/invalid/corrupt files or install the complete package as appropriate. Direct X (DX) - FS2004 requires version 9 (actually 9c to be specific), and although it is included on the installation disks, it is woefully out of date and is known to be incompatible with Win 10 (Win 10, depending on the build state source file, only ships with DX v10 or above). I suggest that you download and install the DX Redistributable pack from HERE.The pack includes full versions 9, 10 and 11 and the install process will only install missing versions and/or replace missing/corrupted/incompatible files of the versions it finds installed. Visual C++ Runtime Redistributable packs - specifically version 2005 and 2008 but I also recommend installing 2010 as well. You can find download links for earlier versions HERE. .NET Framework - specifically versions 3.5 and 4 - download from HERE The DX download contains both 32 and 64 bit OS versions and will install the necessary files for both as required. However, for the C++ and .Net downloads you will need to download the relevant 'bit' version for your OS. For all downloads - Click on the required link and a standard download option box will appear - DO NOT run the installer from this but select the Save As option and save the file to temp location. To install, right click on the file and select the Run as Administrator option. Install each package separately - in the case of C++ and .Net starting with the oldest version first , and reboot using the RESTART option between each install. The reboot is essential to allow the windows registry and important system files to be updated. It is worth pointing out that you can have multiple versions of these 'libraries' installed. They are not just required by FS2004 but are used by many programs and apps. They will work happily along side each other and a program or app will automatically use the most compatible version.

A relatively cheap but good joystick to consider until you can get the Saitek or other gear is the Logitech Extreme 3D Pro... It has a twist handle for rudder, a throttle, a hat switch for view changing, and 12 programmable buttons and has proven to be very durable - I brought my first one in late 2007 and replaced it with another one a few of years ago (Feb 2017) - the old one, which still worked well at the time of its demise, got broken when my young niece decided to drop it down the stairs along with my alarm clock, mouse and an assortment of other things. All in all, IMO, a good all rounder for its price BUT beware, a quick look at both Amazon and Ebay shows a big different in pricing. Also beware of second hand items as they may have issues...

Just to add further to Jim's comment... The process to do so will depend on how you purchase 2020... If direct download from MS or on DVD - when installing it will probably offer a 'default' path. Somewhere on that screen should be an option to install into another location. Normally it will be done by simply browsing to the required location or sometimes you will have to select a 'tickbox' (like you do with FSX) to signify you want to change the location and then the browse function becomes available. If from Steam - First Steam should be viewed as two separate elements - the Client and the Library. The Client is the element that acts as your access gateway to Steam - it provides your account access to its website, the shop, your purchases etc. The Library element is where your DOWNLOADED content, i.e. the game(s), are stored locally on the PC. By default, Steam installs both elements into the same location. The Library element is stored within the following folder structure - \SteamApps\Content\ located within the main Steam folder. You can, however, separate the two elements so that the Client is on one drive and the Game(s) is/are on another. You can even spread the Library element over several disks but note that irrespective of the name you give the target folder Steam will always install using the \SteamApps\Content\ structure - e,g install Game A at D:\Game A the installed game will actually be installed at D:\Game A\\SteamApps\Content\Game A... You will need to select the new location prior to downloading OR let it install into the default area and then MOVE it to the new area. A google search will throw up plenty of info on how to make the changes

Hi, If installed correctly you will files dated both 2006 and 2007 scattered throughout the root directory and folders. The only thing I can think off regards the Alienware is that the initial install of deluxe worked but the subsequent install of Accel failed. There is a well known issue regarding installing Accel (that seems more common on Win 10) regarding an error with the associated registry key see this THREAD and/or this THREAD for a solution. I have also replied to your PM...:)

The only registry hack required to run FSX on Win 10 is if you add the Acceleration pack and it fails to activate. Ensure that you CORRECTLY install the main program first - i.e. install, activate, fly for a few mins and then shutdown the sim then reboot the PC using the RESTART option - this is an important step as it will allow the necessary registry keys to be updated. Install Accel, start FSX and test. If Accel fails to activate follow the info in this THREAD to make the required changes in the registry. See also my post in this LINK regarding possible missing essential libraries. You will see mention of the DX redistl pack - this is also worth installing and can be found HERE

So some simmers don't deserve respect based on the assumption they 'PROBABLY' trashed early sims etc..a very wide statement - especially if it is in direct response to the last line in my post that you have quoted. If is in direct response to that last line then it is clearly aimed at those who have posted in this thread and the others you have started and clearly shows once again your general arrogant and disrespectful attitude towards fellow simmers. Simming has and will always advance in new directions irrespective of 'these kind of simmers' as you put. In fact, it could be argued that such criticism has be the catalyst for the advancement of flight sims in general. Clearly you are not a 'true simmer' because your mind is clearly not 'open'...Your approach has been to put forward your views and, when others have given a negative view/response to adopting VR or their views/experience of using VR does not agree/match your own view, you trash their response as if it is irrelevant or disrespectful. If that is being 'open minded' then I have clearly missed something...

@ terrykpointer, I think you have missed the main point here..... Over several threads GhostTown (and also posting as VRDude) has repeatedly attempted to bestow the virtues of VR. Debating something is a two-way street that should respect the views of both sides, whether it is positive or negative. Clearly something that GhostTown doesn't accept because, when others, some of whom have clearly stated that they have tried or actually use VR, have given their own negative opinions, he has repeatedly derided them simply because their views/experience does not agree/match with his own view. I have stated several times across various threads that this attitude is not the way forward but he continues to do so and now it seems has taken to using the PM function to harass individuals. This is arrogant and shows a lack of respect for others who enjoy the hobby in their own way.

So, all of us who have posted in response to your other posts on the various other threads that you have started about VR and have either not accepted YOUR views and/or the way in which you have approached the subject are now, to use your term, "naysayers". Name calling is NOT the way forward, is insulting and clearly shows the lack of respect that you have for fellow simmers that do not have the same views as you. As I stated in THIS POST on one of the other threads there are many reasons why people don't use, or want to use, VR for flight simming and insulting them is simply going to make them even more less likely to listen to what you have got to say about the subject.

Something to consider if someone outside Europe is considering buying....DVD Regional Coding. The source DVDs will probably be coded for the Europe region and, therefore, will not run in, say, USA/Canada DVD players without them being 'changed' to the correct region number setting. Although its possible and a easy task to change the region, it can only be done a small number of times....

It is VERY debateable - You have your opinion and that is fine but don't tell others who don't agree with you that they are wrong just because you are so stuck on VR, think that it is the only way to use the sim and the only game in town worth having. Flight simming is a hobby that attracts many different types of people who have their own views on what they want from the hobby and how to achieve that. Some will jump straight in and simply use it to fly from A to B and never explore its deeper contents whilst others will go the whole hog and build a replica cockpit and, yes, SOME will choose to use VR. Ultimately, its the individuals choice. Being arrogant, deriding those who don't bow down to your views and continually pushing the same rhetoric is not, IMO, the way to go and simply shows a lack of respect for others who enjoy the hobby in their own way - having looked at the VR webpage you linked earlier in the thread this seems to be a re-occurring theme amongst those who post there. At the end of the day, there are many reasons why people don't use, or want to use, VR for flight simming - get over it and move on.

First - installing the DX Redist first may be an issue because the subsequent FSX install may have corrupted the new files - FSX need version 9c and it is included in the disc but it is known that the version included is incompatible with Win 10. I would therefore reinstall the DX Dist package - ensure that you do so using Admin rights. There are also some other essential libraries that you may be missing that have not been mentioned by others... You can use Programs and Features to check if you have any of the following 'libraries' installed or, if you wish, simply download and install them - the installers will check for any previous install and will replace any missing/invalid/corrupt files or install the complete package as appropriate. Visual C++ Runtime Redistributable packs - specifically version 2005 and 2008 but I also recommend installing 2010 as well. You can find download links for earlier version HERE You will need to download the relevant 'bit' version for your OS (i.e. 32 or 64 bit). Click on the required link and a standard download option box will appear - DO NOT run the installer from this but select the Save As option and save the file to temp location. To install, right click on the file and select the Run as Administrator option. Install each package separately, starting with the oldest version, and reboot using the RESTART option between each install. The reboot is essential to allow the windows registry and important system files to be updated. .NET Framework - specifically versions 3.5 and 4 - download from HERE - download and install using the same procedure for the C++ files. It is worth pointing out that you can have multiple versions of these 'libraries' installed. They are not just required by FSX but are used by many programs and apps. They will work happily along side each other and a program or app will automatically use the most compatible version.

Hi Steve, Glad it made you laugh...my intentions were not to slag off those who like/use VR - I have actually tried it in non FS related games - but simply to make a point about the general attitude of the OP in this thread and the others that he has started. Everyone is entitled to an opinion but to try and force a specific view on people in the manner in which he has so far attempted is, IMO, the wrong way to go about it

An alternative VR Q&A.... Q. Does it affect your ability to see things realistically? A. YES - it makes you think that its the only thing around and all people must convert. Q. Does it give you tunnel vision? A. YES - it makes you think that its the only thing around and all people must convert. Q. Is it some form of Religion? A. YES - it makes you think that its the only thing around and all people must convert.

IMO/IME there are a number of methods to install scenery and how you do it will depend mostly on what type of scenery you are adding. In this particular case, where you adding new global textures there are two methods that will work. Method 1 - this is basically what you have done already - overwriting the original default files. Ideally, if you use this method you should backup the original files so that you can restore them if the new scenery files cause an issue or are not to your liking. Failure to backup the files make it harder to return FSX back to its original state if necessary - your only options without backup files is to either attempt a repair, which is likely to fail and/or may make other changes that damage/destroy any other addons that you have, or to do a full un-install and then re-install. Method 2- Instead of physically replacing the default files create a new holding folder for the new scenery. This folder can be be located within FSX or outside of FSX. Create a Scenery subfolder and a Texture subfolder within the new folder and then place the appropriate files into the appropriate subfolder (i.e files with a .bgl extension into the scenery folder and .bmp, .dds, .agn etc) into the Texture folder). Activate the new folder within FSX as normal. I would also move it down the Priority Listing so that it sits ABOVE the default FSX scenery entries but BELOW any other addon scenery you may have..

Hi Andy... Great pics... Could your fuel problems be down to carrying a little extra weight - not accusing you of anything but somebody seems to have nicked the wheels of the truck parked next to fuel pump at Telluride