Jump to content

f16jockey_2

Registered Users
  • Posts

    1,429
  • Joined

  • Days Won

    1

Everything posted by f16jockey_2

  1. For what good reason are you trying to uninstall FSX or Acceleration? Installing the SDK is a rather tricky step-by-step process (see here), but uninstalling/reinstalling FSX certainly isn't one of them. Wim
  2. An internet search revealed the black box indicates either a pirated or a badly registered install. From what I've read, entering your activation key again should solve the problem. If not: over to Sibwings. Wim
  3. Following procedure allows to backup yr FSX config files (fsx.cfg - dll.xml - exe.xml) on a regular basis. Reason: in case of a mishap, sometimes the standard procedure is to "delete fsx.cfg and let the program rebuild a new one". Works in many cases, but also means you'll have to reconfigure lots of stuff. This approach is to replace fsx.cfg with the "last known working version". In the folder containing fsx.cfg, create a batch file SaveFSX.bat. On Windows 10 that folder is C:\Users\\AppData\Roaming\Microsoft\FSX Copy/paste the following lines: echo Backup FSX system data... copy fsx.cfg fsx.cfg_%date:~-4,4%%date:~-7,2%%date:~-10,2%.bak copy dll.xml dll.xml_%date:~-4,4%%date:~-7,2%%date:~-10,2%.bak copy exe.xml exe.xml_%date:~-4,4%%date:~-7,2%%date:~-10,2%.bak Pause Rightclick the file, and add a shortcut to desktop. When clicking the shortcut, following files will be created: Some may already have noticed the creation date _YYYYMMDD is added to the file name, the others have learned it by reading this line. Wim
  4. You need to restore an older DLL.XML. In my C:\Users\Wim\AppData\Roaming\Microsoft\FSX folder, I see a lot of files named DDL.XML_before_installing_etc.bak or similar. Obviously those were created by 3rd party installers as a backup. I think you should be looking for a file dll.xml.raasprobackup (or similar) and copy/rename that file to dll.xml. Be sure to first check if the file date/time corresponds to the faulty install. Wim
  5. Try setting a lower resolution for FSX. If the lower quality still suits you, it's fixed. If not, it can't be done. Wim
  6. No. It seems to be hardcoded to a certain number of pixels (just like the Z status line). Which means you can eventually trade some resolution for readability. On the same monitor, the text will be 33% bigger on 1980x1080 compared to 2560x1440. Choice is up to you. Wim
  7. You can't. I'm also sad about it. The developer discontinued FSX, because (short version) he claims his FSX models were stolen and converted to MSFS2020 by developers gone rogue. Wim
  8. It's been a while since I used AIFP3, and when I use it's with flightplans from Alpha India. Just to say I'm not familiar with using // to remark out certain lines in the text source files. I don't know if it's even a valid option and honestly, I don't care. To make a long story short: if the above were MY flightplans, I'd stop philosophizing about it, just DELETE the offending line and continue working. Wim
  9. Probably forgot to add the path in FSX.CFG [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 [color=#ff0000][b]SimObjectPaths.6=SimObjects\AI Aircraft[/b][/color] ... Wim
  10. The past tense of the reply seems to suggest this fix is not longer valid, but it still is. Wim
  11. In Windows Control Panel -> Sound -> modify Communications setting Wim
  12. ISDT ATR series are FS9 models AFAIK. No VC merge possible. Wim
  13. You can console yourself with the fact that all you actually want is: for it to be offscreen ASAP! ;) Wim
  14. Please specify which ones. And the name of the wake effect, please. Wim
  15. You've mistuned your NAV radio. You're NOT flying CAT III ILS/DME 28R (IGWQ) 111.70 MHz. which will lead you straight in (284°Mag). What you're flying is LDA/DMA 28R (IFNP) 110.75 MHz, an offset approach. This is already visible on Plan-G in the background of your screenshot. Here's the chart. [EDIT]Technically speaking, you didn't mistune, you tuned correctly to the wrong frequency :pilot:. Wim
  16. Fix your Nvidia Geforce installation first. This is not an FSX problem. [EDIT]My guess is the "Radeon device" is yr on-board GPU chip. Wim
  17. IMO this can only mean yr screen resoultion setting went up. Did you try lowering it? Wim
  18. From what I've read, that's how an ILS approach is mostly flown by a nowadays commercial pilot as well. Wim
  19. With v2.00 they fixed some texture mapping problems, making older repaints buggy. Wim
  20. First of all, I have problems believing the "has no GPS"-part of yr post. Whatever. You may guess the 727 I use from my sig, and I use ISG Gauges (payware) with them. Provides a working FMC (can be updated through Navigraph - also payware), and does a good job for LNAV with SID/STAR. VNAV cannot work, as my 727s have no auto-throttle. Requires a bit more then basic panel editing knowledge. Wim
  21. Take the three fuselage textures and make a copy of them. Rename the copies, adding the letters OP, like this: HS748_FuseA_t.dds -> Copy and rename the copy to: HS748_FuseAOP_t.dds HS748_FuseB_t.dds -> Copy and rename the copy to: HS748_FuseBOP_t.dds HS748_FuseC_t.dds -> Copy and rename the copy to: HS748_FuseCOP_t.dds Wim
  22. fuel_flow_scalar is a multiplier. Pounds/hr or kilograms/hr depend on the aircraft. If a given aircraft consumes 1000 lbs/hr (454kg/hr) with fuel_flow_scalar at 1.00, it'll consume 1100 lbs/hr with a fuel flow scalar at 1.10. So for that aircraft, every 0.10 units of fuel_flow_scalar represents 100 lbs/hr of fuel. For every aircraft this will be different. Wim
×
×
  • Create New...