Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Realistic Flight From KSTL to KDAL in Real Weather

Featured Replies

Just completed an excellent flight from St Louis to Dallas over MSE Missouri and Texas V3 using the PMDG 738 and ProATC-X.  Details hidden below.  I have the latest Windows10 v1709 installed w/the latest KB4051963.  Was able to accelerate to 4x's during most of the flight but the weather was heavy throughout the flight!  On approach, I went to the wingview and watched the landing from there.  Got amazing fps and lots of VAS remaining even though I had a lot of addons running.  Happy about that.  Just wanted to show the flight is possible with FSX (boxed).  If anyone is having issues seeing the Primary Flight Display and FMC's with the PMDG 737 in Windows 10, copy the PMDG Fonts in the FSX folder over to the Windows/Font folder.  Do not replace any current fonts, just add the missing ones.  I thought it was interesting too that FSUIPC did not have to trap any G3D errors.  Usually, on long flights like this one (500 miles), FSUIPC has to trap 5-10 errors.

Spoiler

********* FSUIPC4, Version 4.971 (16th August 2017) by Pete Dowson *********
Windows 10 Home 64 Bit reported as Build 16299, Release ID: 1709 (OS 10.0)
fsx.exe version = 10.0.61637.0
Reading options from "G:\FSX\Modules\FSUIPC4.ini"
Running inside FSX on Windows 10
Module base=57E20000
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 03/12/2017 08:13:28
        0 ------ Module Version Check ------
        0        acontain.dll: 10.0.61637.0
        0             api.dll: 10.0.61637.0
        0        controls.dll: 10.0.61637.0
        0      fs-traffic.dll: 10.0.61637.0
        0             G3D.dll: 10.0.61637.0
        0        language.dll: 10.0.61637.0
        0            sim1.dll: 10.0.61637.0
        0        visualfx.dll: 10.0.61637.0
        0         weather.dll: 10.0.61637.0
        0          window.dll: 10.0.61637.0
        0 ----------------------------------
       31 Trying to connect to SimConnect Acc/SP2 Oct07 ...
       31 FS path = "G:\FSX\"
       94 ---------------------- Joystick Device Scan -----------------------
      109 Product= Cyborg X
      109    Manufacturer= Saitek
      109    Vendor=06A3, Product=0836 (Version 1.48)
      109    GUIDs returned for product: VID_06A3&PID_0836:
      109       GUID= {179AAB00-DC9C-11E6-8001-444553540000}
      109       Details: Btns=14, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V0,X1023,Y1023,Z255
      141 -------------------------------------------------------------------
      141 Device acquired for use:
      141    Joystick ID = 0 (Registry okay)
      141    0=Cyborg F.L.Y.5 Flight Stick
      141    0.GUID={179AAB00-DC9C-11E6-8001-444553540000}
      141 -------------------------------------------------------------------
      141 LogOptions=00000000 00000001
      141 -------------------------------------------------------------------
      141 ------ Setting the hooks and direct calls into the simulator ------
      141 --- CONTROLS timer memory location obtained ok
      141 --- SIM1 Frictions access gained
      141 --- FS Controls Table located ok
      141 --- Installed Mouse Macro hooks ok.
      141 --- Wind smoothing fix is fully installed
      141 --- G3D.DLL fix attempt installed ok
      141 --- SimConnect intercept for texts and menus option is off
      141 --- All links checked okay
      141 -------------------------------------------------------------------
      141 SimConnect_Open succeeded: waiting to check version okay
      141 Trying to use SimConnect Acc/SP2 Oct07
      141 Opened separate AI Traffic client okay
     1234 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
     1234 Initialising SimConnect data requests now
     1234 FSUIPC Menu entry added
     1234 G:\FSX\FLIGHTS\OTHER\FLTSIM.FLT
     1234 G:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
     1453 Monitor IPC:024C (S32) = 0
     1781 Monitor IPC:024C (S32) = 3438284
    15656 Monitor IPC:024C (S32) = 3161556
    21719 Monitor IPC:024C (S32) = 3156216
    23063 G:\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.AIR
    24844 User Aircraft ID 1 supplied, now being used
    24891 System time = 03/12/2017 08:13:53, Simulator time = 08:13:30 (16:13Z)
    24891 Aircraft="Boeing 737-8H4NGX Southwest Airlines (Warrior One) Winglets"
    31969 Monitor IPC:024C (S32) = 2566780
    41969 Monitor IPC:024C (S32) = 2552016
    51781 Monitor IPC:024C (S32) = 2520704
    58469 Weather Mode now = Real World
    61844 Monitor IPC:024C (S32) = 2512972
    71844 Monitor IPC:024C (S32) = 2514508
    82031 Monitor IPC:024C (S32) = 2435000
    92031 Monitor IPC:024C (S32) = 2425460
   102031 Monitor IPC:024C (S32) = 2351640
   112359 Monitor IPC:024C (S32) = 2130452
   112766 Starting everything now ...
   113969 Advanced Weather Interface Enabled
   121953 Monitor IPC:024C (S32) = 2046888
   2451328 Monitor IPC:024C (S32) = 1626892  
  4179625 Monitor IPC:024C (S32) = 1312860
  4189672 Monitor IPC:024C (S32) = 1332280
  4199703 Monitor IPC:024C (S32) = 1342856
  4209750 Monitor IPC:024C (S32) = 1335868
  4219797 Monitor IPC:024C (S32) = 1335816
  4229859 Monitor IPC:024C (S32) = 1335400
  4239891 Monitor IPC:024C (S32) = 1333424
  4249969 Monitor IPC:024C (S32) = 1309356
  4260000 Monitor IPC:024C (S32) = 1342644
  4270063 Monitor IPC:024C (S32) = 1345192
  4278469 === Closing session: waiting for DLLStop to be called ...
  4278828 Sim stopped: average frame rate for last 4168 secs = 34.0 fps
  4278828    Max AI traffic was 261 aircraft (Deleted 0)
  4282672 === DLLStop called ...
  4282672 === Closing external processes we started ...
  4283672 === About to kill any Lua plug-ins still running ...
  4283828 === Closing global Lua thread
  4284828 === About to kill my timers ...
  4285031 === Restoring window procs ...
  4285031 === Unloading libraries ...
  4285031 === stopping other threads ...
  4285031 === ... Memory checking ...
  4285031 === ... Button scanning ...
  4285125 === ... Axis scanning ...
  4285219 === Releasing joystick devices ...
  4285219 === Freeing macro memory
  4285219 === Removing any offset overrides
  4285219 === Clearing any displays left
  4285219 === NOTE: not calling SimConnect_Close ...
  4285219 === AI slots deleted!
  4285219 === Freeing button memory ...
  4285219 === Closing my Windows ...
  4285219 === Freeing FS libraries ...
  4286219 === Closing devices ...
  4286219 === Closing the Log ... Bye Bye! ...
  4286219 System time = 03/12/2017 09:24:55, Simulator time = 08:52:50 (14:52Z)
  4286219 *** FSUIPC log file being closed
Minimum frame rate was 13.4 fps, Maximum was 119.0 fps
Minimum available memory recorded was 1168Mb
Average frame rate for running time of 4168 secs = 34.0 fps
G3D fix: Passes 143962, Null pointers 0, Bad pointers 0, Separate instances 0
Maximum AI traffic for session was 261 aircraft
Memory managed: 1962 Allocs, 1962 Freed
********* FSUIPC Log file closed ***********

 

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.