Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Accept or deny of these DLLs is then stored in the fsx.CFG file, in folder
C:\Users\<USERNAME>AppData\Roaming\Microsoft\FSX
in the [Trusted] section of this file.
In your case, I would recommend deleting the lines under the [Trusted] section in fsx.CFG, so that you should get again the Popups for enable these DLLs next time the A/C is choosen for a flight.
Accept the DLLs as Trusted when asked for, and choose to keep them permanently enabled. New corresponding lines will be created in the [Trusted] section of fsx.CFG
Can you please tell us what gauges are missing Kyemo and do you mean in the 2D or 3D cockpit?
- Martin
An example of the problem with screenshots:
Beechcraft King Air 350 - What I assume are all 3d and 2d gauges in front of the pilot are just blank or missing
http://steamcommunity.com/sharedfiles/filedetails/?id=874176420
http://steamcommunity.com/sharedfiles/filedetails/?id=874175865
Beechcraft Baron 58 - All gauges are present in 3d and 2d, but what I assume are radios on the right hand side of 3d view are just untextured wireframes.
http://steamcommunity.com/sharedfiles/filedetails/?id=874179115
I only just started playing the game, so I don't have a lot of experience with it, but it seems some airplanes perfectly fine, others are missing bits and pieces here and there. The King Air 350 is probably the worst one I've found.
Already tried verifying the install via steam.
Tried deleting the Trusted dlls on your suggestion. No change, or message about trusting dlls, and after running fsx it's just started adding dlls to the trusted list again by itself.
Running Windows 10, nVidia GTX 970 on DirectX 12 (DirectX 10 preview in game is turned off), graphics turned to top preset, 1920x1080x32.
[Edit]
Just had a look, and \gauges\KingAir_radio.dll and KingAir.dll both appear in the trusted section of fsx.cfg
That's odd, FSX should have resubmitted popups to accept the DLLs...
You confirm FSX was closed when you edited fsx.CFG ?
Also, could you post the line for KingAir_radio.dll that FSX wrote into fsx.CFG ?
Another try maybe: can you rename fsx.CFG to some other backup name, and start FSX, so that it creates a new one. Select then the king air, you should see the popups for accepting the DLLs
1. Sign out of Steam
2. Delete the contents of the "<drive:>\Program files (x86)\ Steam\SteamApps\Common\FSX\" and all subdirectories
3. Log on to Steam
4. Select "View Games Library" from the "Games" menu
5. Right-click the Microsoft Flight Simulator X: Steam Edition icon and select "Properties"
6. Select the "Local Files" tab and click on "Verify Integrity of Games Cache"
That will reset everything. After the process is complete start the sim up as normal. If you see any pop up boxes asking you to agree to anything please click yes.
If you continue to have the same issue can you please contact our support team via our website:
http://dovetailgames.kayako.com/
We will have to take a closer look at your setup and what exactly is going on.
- Martin
http://steamcommunity.com/sharedfiles/filedetails/?id=874783469
I got the dll pop-up this time, with windows 10 you can select to always load or never load dlls from particular publishers, I wonder if it's possible I accidentally clicked never run the first time, not understanding what it was? And maybe FSX was adding the dlls to fsx.cfg trusted but windows itself was stopping them from being loaded? I mean, at the time of first run, I would have been expecting the publisher to be microsoft not DTG, and are some of those gauge dlls signed by dovetail and some signed by microsoft? That may have been the problem?
Anyway, thanks heaps to both of you for your help.
In case you're curious, the contents of the Trusted section of fsx.cfg after taking deleting all entries and then booting FSX to take those screenshots last night:
[Trusted]
D:\SteamLibrary\steamapps\Common\FSX\gauges\KingAir.dll.iinalktwqtlqccciiazqczuhwakutlwuozcnnnke=0
D:\SteamLibrary\steamapps\Common\FSX\gauges\Cessna172.dll.hbwtnutbtwiknohcqeboobaklaoboekzocwttruk=0
D:\SteamLibrary\steamapps\Common\FSX\gauges\KingAir_radio.dll.wkchunleooqwqokntquawuleeaeluuzbezrlettn=0
D:\SteamLibrary\steamapps\Common\FSX\gauges\Magnetic_Compass.dll.wwnollnroioclnihchrrnnubboknchwrkciahhno=0
D:\SteamLibrary\steamapps\Common\FSX\gauges\Bendix_king_radio.dll.ireezhoubaeboqthobhbabzulbuloobtuhllzoqz=0
[Edit]
I checked, and all appear to be signed by dovetail. Maybe windows was allowing the cab files to be loaded, but not the dlls?
What is important to notice in the lines you sent, is the =0 at the end of each lines.
If not =1 or =2 , then it means the DLL is not considered as trusted. But as the line is recorded in the section, it does not prompt again for accepting it.
You can compare these lines with the current ones you have in your current fsx.CFG
Just a word also when editing your fsx.CFG: Remember to always have FSX closed, as this file is written by FSX when FSX closes down. Otherwise, you will loose any change that you did in it.
I had an issue. I downloaded a gauge that required simconnect and the installation of 3 different versions of that program.
The gauge didn't seem to work so I uninstalled all of the simconnect installs I saw. After that, all of my gauges didn't work.
The solution was to fully close FSX, verify the game files with Steam, open the game and Steam should reinstall a version of simconnect that shouldn't be uninstalled.