longbreak754

Hi Col, Read my post in reply to your Help! Sign in Win 10 as user thread....

Hi Col, A number of options exist depending on the installation type: Via a CD/DVD - you will need to stop the autoplay feature - this GUIDE tells you how. Once you have stop autoplay you can then browse the CD/DVD and find the install executable file - normally they have a .exe, .bat or .msi extension. you can then use the next method described... Via a executable file - DO NOT double click on the file but RIGHT click on it and select Run as Admin from the resulting list... After installing if you want to run an app with admin rights you have two options depending on how you start the app.... Via the Windows Start Menu, directly from within the app folder or via a desktop shortcut - right click on the and select the Run as administrator option from the resulting list - note though that if you do it via the Windows Start Menu link the resulting menu is restricted to 3 set items and the Run as Admin option is under More option... This option offers a 'permanent' solution to always start the app with admin rights BUT can only be set on a desktop shortcut OR the directly on the .exe file itself. Simply right click on the shortcut or .exe file and select properties from the resulting list. A new info pane will open. Click on the Compatibility tab and then select the Run this program as an administrator option. Click Apply to save the change. The above options should meet your needs but another option that you could use, if you feel comfortable with it, is to either create a second user account that has full admin rights, which you would log onto to install new apps - you will need to remember to check the setting when using this method so that any app you install is available to all users and not just the Admin account. Or you could change the current account you use to a admin account...there are some pros and cons to this approach regarding possible security issues to be aware of - google is a good source of info - but I know many people who use this method and I also do...

FYI the latest version of Edge is actually based on Chromium.... See HERE for some info that you may find useful...

Having the FS9 copies on your system anywhere outside of FSX will not be a problem UNLESS the folder location they are stored in is: A. In the correct hierarchy required by FSX - i.e. the actual .bgl files are within a scenery subfolder (e.g. MainFolderName\Scenery\ AND... B. That folder location has been activated in FSX.... Which brings me to this Q: In all the testing that you have down have you inadvertently de-activated the file Scenery\World\Scenery entry... Some other things to consider... Possible missing models/textures - Use AIFP to check for missing aircraft models/texture used in the traffic files...It is worth noting that some AI traffic files provide textures (i.e. repaints) only for a specific AI model that needs to be sourced separately Location of AI Models/Textures - If you do find that you are missing the models/textures you can then check for them in the Simobjects folder. If found check that the location of the missing traffic textures/models is known to FSX. If you have stored them in a location other than the default SimObject Folders (by this I mean that if you have manually created a specific folder to hold them or the auto installer has created one) it must be listed in the FSX.cfg file under the [Main] section- as shown in this example from my .cfg - entries 7 to 10.... [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=D:\FSX Utilities\TrafficGlobal\TrafficGlobalFleet SimObjectPaths.7=SimObjects\AIFastJets SimObjectPaths.8=SimObjects\AIHeavies SimObjectPaths.9=SimObjects\AIHelicopters SimObjectPaths.10=SimObjects\AITrainers SimObjectPaths.11=SimObjects\HJG Also note that you would need to do the same if you (or the auto installer) install into an unusual folder structure within a default folder - for example if we were to add a new B737 model by company ABC to the default Simobjects\Airplanes folder as follows Simobjects\Airplanes\ABC\\B737\Model files and folders the models won't show unless you either: A. Add a entry to point to the location - e.g. SimObjectPaths.XX=SimObjects\Airplanes\ABC....OR B. Change the folder structure to Simobjects\Airplanes\ABC\Model files and folders by moving the Model Files/Folders up one level into the ABC folder and then deleting the now empty B737 folder...you could also rename the ABC folder to ABC B737 for further clarity.... My final thoughts on this is that you don't need to use the default location to store traffic files...they can (as can most addon scenery) be stored anywhere, included outside of the FSX as long as two prerequisites are met: A. The individual .bgl files are stored in a subfolder called Scenery (e.g. C:\FSX Traffic Files\Scenery...and B. The folder location is known to (i.e. activated in) FSX

Hi, Most of the FSX stuff should work fine in the Steam version...the Steam version is essentially the same as the boxed version of FSX Acceleration and uses the same folder structure. One of the main differences is that a few tweaks are already added to the FSX.cfg file that most users of the boxed edition will have already added. Another is that the whole package was re-compiled using Visual C++ 2013 for better optimization and performance. However, it still makes use of Visual C++ 2005 libraries for backwards compatibility - many pre-steam era addons would have been compiled using 2005 or later. See HERE for more details The main issue will be that, because the Steam version uses a slightly different folder hierarchy ABOVE the standard FSX folder structure with a pre-set naming convention that must be used, the auto installer for most pre Steam product cannot find it...all you need to do is manually point the installer to the correct location... FYI the Steam hierarchy pre-set is used irrespective of what you try to do - here's some examples - the items in BOLD are 'pre-set' items... By default Steam will install FSX (and any other steam game) at C:\Program Files\Steam\SteamApps\Common\\ If you try to install to a dedicated folder - say C;\FSX - the actually install path will actually be C:\FSX\SteamApps\Common\FSX\ As for MS2020 compatibility - that is a non starter - the way in which the new product has been made i means that FSX stuff is incompatible

Hi Mick, Personally, I prefer to do things old school and manually add new entries directly to the scenery,cfg file by editing it in notepad - I don't use the FSX scenery settings page at all....however, a freeware tool that is useful for checking for errors that you may find useful is Scenery Config Editor (SCE) See HERE for info and HERE to download... One of the features offered by the tool is that it will automatically highlight any problem areas... Another feature some find useful is that it can be used as a substitute to the FSX scenery setting page - you can add new scenery or change its location within the priority list via the tool and it will automatically update FSX when you next start it - saves having to visit the FSX scenery setting page once FSX loading has completed to activate/de-activate scenery...

As Wim has pointed out the folder may be hidden by default.... Also, further to my last post...you may find that Local= entry may state Remote= instead... If this is the case simply change Remote= to Local=

Hi... Try this.... Go to C:\ProgramData\Microsoft\FSX and locate the scenery.cfg file. Make a backup copy of the file and store in a safe place. Open the scenery.cfg file in Notepad. You will see the entries for your scenery - they will look similar to this example... [Area.472] Local=Addon Scenery\LSZA Lugano AP Title=LSZA Lugano AP Required=FALSE Active=TRUE Layer=472 The Local= entry is the entry that tells FSX where to find the scenery files...this will need amending for EACH entry Simply remove the 'space' for each problem entry and then save the file....do not rename it. If you make a mistake you can use the back up to create a new copy and start again. For more info on the scenery.cfg file and how it work see the info I have posted in this THREAD... Note my suggestion in that thread regarding using a program called Scenery Config Editor - if you download and install it BEFORE attempting what I have said above you can use its inbuilt editor to make the changes.... it will also highlight the problem areas for you...

As possible reason for the issue is that the Captain Sim website has changed.... It use to be captainsim.com (as per your error message) but if you try to go there you will get an error message... The new website and support forum is now at captainsim.net - here is a direct LINK Go there and they may be able to help you will your problem...

@ Casey... What a contradiction.... Making claims that MS has quote made sure unquote that FSX cannot be run on a Win 10 system whilst admitting that others have been successful is clearly unwarranted and false. It is evident from the many users of Win 10 still enjoying FSX that it certainly can be run on Win 10. Additionally, many users do so with out any issues. Likewise, whilst you may have had no problems running FSX on Win 7 other users have - as documented in many threads in the forum. Most issues encountered on a Win 10 system are well documented and have fixes that work - same also for other versions of Windows. Indeed, many of the issue encountered are common ones that affect Win 7, 8 and 10. As for the full screen/windowed mode issue - I have never encountered the issue and having checked today I have been able to run the sim in both modes although I normally run full screen,,,,

Correct...but... Basically, .NET libraries are used by many programs and their main use is to allow developers to easily code functions within a 'game' or 'app'. Additionally, it allows developers to make sure their product installs the way it was intended and that it runs properly on the targeted platform. .Net is required to be present on a PC to allow the 'game' or 'app' to function correctly. Many FSX addons also utilise the ,NET libraries and again, therefore, they need to be installed. Earlier versions of .NET that where available when FSX was first released (it used V2) have been 'officially' retired from use by MS and were rolled into V3.5... A google search using the phrase does FSX require .Net framework will give you plenty of info on the subject...

@ mikeperry... Just so that you are aware - the comment made by Jorgen regarding the suggested location where to store FSX will not be doable with the steam version. This is because Steam requires a specific folder structure...see this THREAD for info.... That said I would suggest that you don't install the Steam client into its default suggested location which will be C:\ProgramFiles\Steam\... @ surrodox2001... IME the main cause regarding FSX vs FSX-Steam incompatibility issues is this - the Steam Edition is built using a later version of the Visual C++ Runtime libraries - specifically the VS2013 compiler for better optimization and performance. The boxed version was built using the VS2005 compiler. Although compiled using a later version the Steam change log states that it retains backward compatibility of with VS2005. However, as part of its install process the Steam installer installs the VS2013 libraries if it is not present BUT DOES NOT install VS2005 if it is not present. Therefore it is important to check that you have VS2005 libraries installed as well - this is especially important with a new Win10 based PC (or a older PC that has a new vanilla Win 10 install) as older versions of such 'libraries' are not including by default. Some FSX addons also make use of VS 2008 VS2010 and VS2012 so it is a good ideal to check the product requirements before hand. VS versions can be found HERE. Additionally, problems can be caused by another set of essential 'libraries' required by FSX that may be missing - namely .NET Framework versions 3.5 and 4 - if required they can be downloaded from HERE.

You might be able to achieve what you want using the FSX KML tool - see HERE for details

Is it 'Nope' because the issue described in the link that Charlie gave is not the same or relevant OR is it 'Nope' because the item he has pictured is not the same as that you own...? Other thoughts and suggestions on this problem... 1. Does the 'reset' change the settings back to the FSX defaults for both Key and Yoke/Throttle settings or only the Yolk/Throttle settings...? 2. Does it happen with just a specific single aircraft model that you fly most or does it happen to other aircraft...? It is worth noting that some aircraft models available can, when loaded, override other user set control and view settings, instead using pre-programmed settings defined by the author.... 3. Have you installed any drivers and/or software that came with the product...? If yes, it could be that the updates are being downloaded and installed in the background and causing the reset. This may be especially relevant if it only affects the Yoke/Throttle settings. An option to consider making life a little bit easier for you until you are able to resolve the issue... Once you have reset the control options to your liking: Go to C:\Users\\AppData\Roaming\Microsoft\FSX\Controls Make a COPY of the Standard.xml - then rename the COPY to something like Standard_Good.xml. This will give you a backup copy with all the settings as you require them. Make a note of the Date Modified and Size details (these only change when a change is made) of the Standard.xml file and store in a safe location. Next time you suffer the issue you can then: Check the Date Modified and Size details of the Standard.xml file to see when the change occurred and if the size has changed - this may be useful in trying to find out the cause of the issue... Delete the Standard.xml file and then create a copy of the Standard_Good.xml - then rename the copy to Standard.xml.

What OS do you have installed....? What was the .dll related error message...? A possible suspect, based on the age of the product, is likely to be related to a anti-piracy utility called SafeDisc that relies on a system file called secdrv.sys. Back in 2015, on the release of Win 10 MS choose to not include the file as it was a known security issue. At the same time MS issued a patch (KB3086255) to earlier Win versions that disabled the file. If pre Win 10 - i.e. XP, Vista, Win 7 or 8 then you maybe able to resolve the issue by checking to see if the KB is installed and, if so, by removing it. Another option would be to manually re-enable it via the services app. If Win 10 then the fix will not be easy as you will need to source a copy of the secdrv.sys file, install it and then run a Digital Certification activation tool to validate the file. A google search using the phrase KB3086255 will give you plenty of info on the subject...

Hi Steve, Without fully knowing what 'suggestions' you have tried without success here are a few that you may have already tried but are known to resolve the issue you face.... First - check the FSX Graphics Setting page to see if DX 10 Preview is selected - if so untick the box and test. Also, whilst on this page ensure that the FSX screen resolution is set to the same as your monitors native setting. By default FSX loads at 1024x768x16 - change it to the default native setting for your monitor - i,e if its 1920x1280x32 set it to this... If the problem is resolved the the following suggestion is NOT needed BUT may be beneficial... Direct X (DX) - FSX requires version 9 (actually 9c to be specific), and although it is included on the installation disks, it is woefully out of date and incompatible with Win 10 (Win 10, depending on the build state source file, only ships with v10 or above). Again I suggest that you download and install the DX Redistributable pack from HERE. The pack includes 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. Click on the download 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. Once the installation process is complete, reboot using the RESTART option. The reboot is essential to allow the windows registry and important system files to be updated. Also worth noting is that, by default, Win 10 ships without some of the earlier versions of 'libraries' that FSX and FSX addons may rely on. These 'essential' libraries may or may not be on your PC and may be required if you experience other issues 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 (as the DX package did) 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 versions HERE. You will need to download the relevant 'bit' version for your OS (i.e. 32 or 64 bit). As with the DX install 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. .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. A final thought - some people will suggest running a manual windows update after install the packs but my preference is not to. The windows updater service runs regularly to check for updates and will soon pick up any updates if available.

It is for use as a Throttle..... All the way back (i.e. pointing to the - marking) is 0% thrust All the way forward (i.e. pointing to the + marking) is 100% thrust...

Your comment, whilst valid, is in the case of the FSX install location, not relevant...the OP has it stored at D:\SteamLibrary\steamapps\common\FSX\TFDi Design\PACX\PACX.exe as indicated in the fault log entries. What might be relevant is if the OP only has the 'game' stored at the stated D:\ location AND has the Client element located at the default C:\ProgramFiles\Steam\ location. For those unaware the Steam App is best viewed as TWO separate elements - the Client (which controls your access to Steam via your account etc) and the Library (which is where your individual 'Games' are stored on your PC). You can install the Client in one location and, within a specific set folder hierarchy, the library in another single location OR multiple locations. By default the Library is set to the same location as the Client but when you download and install a new 'game' you can specify a new location if you wish. You can also 'move' existing installations to a new location also using the options available. The set folder hierarchy means that all 'games' must be stored in a folder system that starts \SteamLibrary\steamapps\common\ - it is impossible to actually set it to :\FSX - even if you create the folder before hand. Steam will simply create the set folder structure and then install the 'game to :\FSX\SteamLibrary\steamapps\common\ What is important to remember about this is that certain control elements for each individual 'game' (and any addons associated with it) remains stored within the Client element AND it may be something that the client is trying to do that is causing the crash. It the Client is stored at the default location use the 'move' tool available within Steam to change its location

To find all of the forum simply click on the button marked Forum located below the main website header banner. You will find the Swap Meet forum in the first section under the General Interest header and the FSX forum in the second section under the Microsoft Simulators header... Happy flyin'

Hi, Not interested in the disks as I already own the product, however, I suggest that you may get more interest if you: 1. Correctly name the product in the subject title - FS2000 and FSX Gold are TWO totally separate products. 2. Post the ad in the dedicated Swap Meet and/or FSX forums. They have a much higher viewing population and are more relevant.

Hi Matt, I suffered a similar problem with my VRS TacPack installation a while ago after installing a scenery whose install process added SODE reliant elements - got exactly the same type of error message displayed in screenshot #6 and Simconnect.dll related errors. Uninstalled the scenery and then uninstalling and then reinstalling TacPack resolved the issue for me so it may be worth doing the same for your FSPassengers app...

As someone who prefers Mil fast jets I normally fly a complete flight in one go as they tend to be relatively short anyway. When I fly longer legs or use a Mil Cargo type it will depend on how much time I can 'muster' up to 'fly'. Some flights I will have to split as Charlie does using the save/reload method and others I will use upto 16x speed (this is the max you can use when using autopilot) so as to be able to complete the flight.... However, the MOST important thing to remember about how you use the sim is that you do so in a manner that gives YOU the enjoyment that you WANT...

Hi Don, First - Have you changed the FSX default resolution settings to match the native settings of your monitor. By default FSX loads at 1024x768x16 - change it to the default native setting for your monitor - i,e if its 1920x1280x32 set it to this...and test. Second - the list you have given only contains the default FSX scenery areas and alludes that you have not added any additional scenery. If you have please give info of what it was and were you have placed the files associated with it priory to attempting the scenery.cfg 'fix' detailed below... If the problem is not related to the resolution setting try the following to see if it resolves the issue... Note the first 'fix' are based on the assumption that you have not added any additional scenery - if you have the first 'fix' will require you to re-activate the added scenery 1. With FSX closed go to C:\ProgramData\Mircrosoft\FSX and rename the Scenery.cfg file to Scenery.bak 2. Start FSX - a new scenery.cfg will be created - this will only provide details of the default FSX scenery entries only 3. Test FSX. If the problem still exists then try this but note that you will lose any config changes made, any manual added tweaks made to the config file and FSX will restart with the default flight loaded (i.e. the Trike over Friday Harbour). As a check of the video card capabilities will also be made as part of the process the video resolution will be set to the FSX default values of 1024x768... 1. With FSX closed go toC:\Users\AppData\Roaming\Microsoft\FSX and rename the FSX.cfg file to FSX.bak 2. Start FSX - a new FSX.cfg will be created. You MAY receive an error regarding loading the default flight - just click OK to accept it. 3. Make only the following change for now - resolution setting as appropriate. 4. Test.