Jump to content

f16jockey_2

Registered Users
  • Posts

    1,431
  • Joined

  • Days Won

    1

Posts posted by f16jockey_2

  1. 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:

     

    gym5zgl.png

     

    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

  2. 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

  3. 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

  4. Now I'm wondering, where can I get the FSX models?

     

    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

  5. 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

  6. 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

  7. 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

  8. Here are my computer specs:

     

    Windows 10

    Ultra Gamer AMD 5 3600X-2060

    Processor: AMD Ryzen 5 3600x (6 x 3,8 GHz)

    CPU Cooler: AMD Boxed

    RAM: 16 GB DD4R 2666 MHz/ Max. 64 GB

    GPU: NVIDIA GEFORCE RTX 2060/ 6 GB GDDR6

    SSD: 1 TB Intel/ NVMe M.2

    Adaptor: Cooler Master 600 Watt (80 PLUS)

     

    FSX only recognizes Radeon as a device, for some odd reason.

    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

  9. Do I have to manually fly it and try to keep the vertical and horizontal lines in the gauge lined up to ensure I'm lined up with the runway.

    If that is the case, the pilots of these craft had a much harder job than modern day fliers������

    From what I've read, that's how an ILS approach is mostly flown by a nowadays commercial pilot as well.

     

    Wim

  10. Any 727

    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

×
×
  • Create New...