January 30, 20197 yr I recently DLd the "AVSIM Crash to Desktop Guide." Really helpful. I took its advice and also DLd FSUIPC. (I took the freeware version, since the registered version functions are far beyond my pay grade.) But after installing and using, I have some really basic questions (Yes, I've read the User Guide) : 1. It displays remaining VAS alright, but it put a great big green band all the way across the top of my screen. Is this normal? 2. I can get rid of the green band by deselecting FS Title Bar and/or FS Window, which I guess defeats the purpose. Nonetheless, the CTD Guide suggests I also select "Normal Log File," with no explanation. OK, but what does that do? How does one access this supposed file, and what will it reveal? 3. The CTD Guide discusses FSUIPC under "How to Fix Most Freezes/Crashes," and I have seen posts on another forum suggesting that installing FSUIPC actually prevents crashes. Is this true, and if so, how? I get why watching your VAS is useful info, but what does monitoring it do to actually prevent crashes, if anything? IS FSUIPC doing something else? Thanks all, Mac6737
January 30, 20197 yr Administrators I have the freeware FSUIPC and have never monitored any of it. Charlie AronAVSIM Board of Directors-ADMIN/Moderator-RegistrarJust going to run a Chromebook and not upgrade to a Windows computer. Too many problems with the new Sims! 😱Trying to keep peace and harmony and the will of Landru on the site seems to be a full time job!
January 30, 20197 yr 6 minutes ago, Mac6737 said: watching your VAS is useful info, but what does monitoring it do to actually prevent crashes, if anything? IS FSUIPC doing something else? Let you know when you are basically .... out of luck. 🙂
January 30, 20197 yr 3 minutes ago, Mac6737 said: Nonetheless, the CTD Guide suggests I also select "Normal Log File," with no explanation. OK, but what does that do? How does one access this supposed file, and what will it reveal? Information about your flight. For FSX, it will show VAS usage at the beginning of the flight to the end of the flight. You can then see the fluctuation of VAS usage during the flight. At the end you will see something like the following - Minimum frame rate was 29.0 fps, Maximum was 81.3 fps Average frame rate for running time of 4061 secs = 52.8 fps Maximum AI traffic for session was 281 aircraft 8 minutes ago, Mac6737 said: It displays remaining VAS alright, but it put a great big green band all the way across the top of my screen. Is this normal? Yes, but you can disable it. It's good to see how much VAS you have remaining on descent where the most VAS is used and especially on approach. If you get below 500MB, you could have serious issues landing or taxing to your gate. 10 minutes ago, Mac6737 said: I have seen posts on another forum suggesting that installing FSUIPC actually prevents crashes. Is this true, and if so, how? I get why watching your VAS is useful info, but what does monitoring it do to actually prevent crashes, if anything? IS FSUIPC doing something else? In the back of the CTD Guide, look at solutions for G3D.dll. It traps the G3D.dll error which was very common back around the year 2007. Computers have gotten more powerful so that error has pretty much gone away but it is still there for 32-bit applications. It also traps other errors that might occur during the flight. When you look at the FSUIPC report (by opening FSUIPC.txt to view VAS usage). Normally it will show it trapped 540 g3d errors during the flight. Something like that. I have yet to do a flight in FSX as I use P3Dv4.4 exclusively and only have FSX to answer questions like yours. I use to have hundreds of saved logs that I saved as KORDKIAD_AS_MSE_VA_PMDG747_FSDT_KORD_FB_KIAD. I could then go back and look at the various flights and look at the FPS and VAS usage depending on conditions like bad weather etc. So I do not have an example of what the fixes line looks like but it gives you an idea how many errors were trapped and saved your flight from crashing. It's a nice tool and free. Thanks for reading the CTD Guide. We think it is pretty comprehensive but an update is forthcoming to eliminate a lot of my rhetoric, to simply some instructions, and to eliminate the last section regarding the various crashes and how to fix them. There really is no one solution that fits all for fixing crashes. I see a lot of members saying I've done all of the recommendations in the CTD Guide and none of them work for me. Well, 99% of crashes can be fixed in FSX by simply removing the fsx.cfg, dll.xml, and scenery.cfg and restarting the sim and see if this fixes the problem. It usually does. Many FSX experts say that just moving the fsx.cfg and restarting the sim and letting it rebuild is the same as reinstalling or repairing the sim. Getting rid of the dll.xml (it will not be rebuilt in FSX) eliminates the possibility of a bad module being loaded, like FSUIPC. FSUIPC is updated frequently and one may have the wrong version. One has to investigate the scene of the crime to find out what module did the dirty deed. Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant 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
January 30, 20197 yr So, just completed a flight from FlightBeam KIAD to FSDT KCLT. Here is my FSUIPC report. As you can see, VAS usage will fluctuate during the flight. I flew over MSE Virginia and default North Carolina. Weather was bad with rain. Glad I still got 146 FPS but an average of 41.7 overall. Spoiler 125 --- G3D.DLL fix attempt installed ok 125 --- SimConnect intercept for texts and menus option is off 125 --- All links checked okay 125 ------------------------------------------------------------------- 125 SimConnect_Open succeeded: waiting to check version okay 125 Trying to use SimConnect Acc/SP2 Oct07 125 Opened separate AI Traffic client okay 1109 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 1109 Initialising SimConnect data requests now 1109 FSUIPC Menu entry added 1109 G:\FSX\FLIGHTS\OTHER\FLTSIM.FLT 1109 G:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 1953 Monitor IPC:024C (S32) = 0 2187 Monitor IPC:024C (S32) = 3470388 13781 Monitor IPC:024C (S32) = 3420556 19906 G:\FSX\SimObjects\Airplanes\PMDG 737-700NGX WL\B737-700WL.AIR 24187 Monitor IPC:024C (S32) = 3000900 32187 Monitor IPC:024C (S32) = 2836104 42250 Monitor IPC:024C (S32) = 2418788 52125 Monitor IPC:024C (S32) = 2443104 55219 Weather Mode now = Real World 62187 Monitor IPC:024C (S32) = 2400520 72062 Monitor IPC:024C (S32) = 2199184 82312 Monitor IPC:024C (S32) = 2063696 85828 User Aircraft ID 1 supplied, now being used 85875 Aircraft loaded: running normally now ... 86203 System time = 30/01/2019 13:12:37, Simulator time = 12:57:47 (16:57Z) 89234 Starting everything now ... 91047 Advanced Weather Interface Enabled 92094 Monitor IPC:024C (S32) = 1649288 102125 Monitor IPC:024C (S32) = 1649356 112125 Monitor IPC:024C (S32) = 1643544 122156 Monitor IPC:024C (S32) = 1655328 152187 Monitor IPC:024C (S32) = 1491808 162219 Monitor IPC:024C (S32) = 1499512 172234 Monitor IPC:024C (S32) = 1460528 202281 Monitor IPC:024C (S32) = 1444336 212281 Monitor IPC:024C (S32) = 1414772 222312 Monitor IPC:024C (S32) = 1393412 232328 Monitor IPC:024C (S32) = 1392472 282422 Monitor IPC:024C (S32) = 1376280 292437 Monitor IPC:024C (S32) = 1376476 312469 Monitor IPC:024C (S32) = 1346852 322500 Monitor IPC:024C (S32) = 1351568 332516 Monitor IPC:024C (S32) = 1350132 342531 Monitor IPC:024C (S32) = 1334232 352547 Monitor IPC:024C (S32) = 1318692 362562 Monitor IPC:024C (S32) = 1320048 372594 Monitor IPC:024C (S32) = 1322588 382594 Monitor IPC:024C (S32) = 1339292 392625 Monitor IPC:024C (S32) = 1360264 402625 Monitor IPC:024C (S32) = 1348744 412672 Monitor IPC:024C (S32) = 1357904 422672 Monitor IPC:024C (S32) = 1320288 432687 Monitor IPC:024C (S32) = 1350016 442703 Monitor IPC:024C (S32) = 1381656 452719 Monitor IPC:024C (S32) = 1349044 462750 Monitor IPC:024C (S32) = 1358132 472766 Monitor IPC:024C (S32) = 1357248 482797 Monitor IPC:024C (S32) = 1366060 492797 Monitor IPC:024C (S32) = 1366612 502828 Monitor IPC:024C (S32) = 1354380 512828 Monitor IPC:024C (S32) = 1344840 522859 Monitor IPC:024C (S32) = 1314468 532875 Monitor IPC:024C (S32) = 1328980 542891 Monitor IPC:024C (S32) = 1329692 552922 Monitor IPC:024C (S32) = 1324776 562922 Monitor IPC:024C (S32) = 1326260 572953 Monitor IPC:024C (S32) = 1330752 582953 Monitor IPC:024C (S32) = 1331320 593000 Monitor IPC:024C (S32) = 1330256 603000 Monitor IPC:024C (S32) = 1297224 613016 Monitor IPC:024C (S32) = 1338092 623031 Monitor IPC:024C (S32) = 1339628 633062 Monitor IPC:024C (S32) = 1340172 643078 Monitor IPC:024C (S32) = 1341640 653094 Monitor IPC:024C (S32) = 1330788 663109 Monitor IPC:024C (S32) = 1346844 673125 Monitor IPC:024C (S32) = 1314248 683156 Monitor IPC:024C (S32) = 1326000 693172 Monitor IPC:024C (S32) = 1576724 703187 Monitor IPC:024C (S32) = 1576224 713219 Monitor IPC:024C (S32) = 1560016 723219 Monitor IPC:024C (S32) = 1562288 733234 Monitor IPC:024C (S32) = 1551104 743250 Monitor IPC:024C (S32) = 1579548 753266 Monitor IPC:024C (S32) = 1580068 763297 Monitor IPC:024C (S32) = 1550284 773312 Monitor IPC:024C (S32) = 1560224 783328 Monitor IPC:024C (S32) = 1580520 793344 Monitor IPC:024C (S32) = 1583068 803375 Monitor IPC:024C (S32) = 1582588 813391 Monitor IPC:024C (S32) = 1581900 843422 Monitor IPC:024C (S32) = 1582588 853453 Monitor IPC:024C (S32) = 1581852 863453 Monitor IPC:024C (S32) = 1547336 873484 Monitor IPC:024C (S32) = 1545936 883484 Monitor IPC:024C (S32) = 1534012 893531 Monitor IPC:024C (S32) = 1533836 913562 Monitor IPC:024C (S32) = 1538348 923578 Monitor IPC:024C (S32) = 1603852 933578 Monitor IPC:024C (S32) = 1608732 943594 Monitor IPC:024C (S32) = 1596636 963625 Monitor IPC:024C (S32) = 1594352 973656 Monitor IPC:024C (S32) = 1591528 983672 Monitor IPC:024C (S32) = 1590116 993687 Monitor IPC:024C (S32) = 1591532 1003703 Monitor IPC:024C (S32) = 1576748 1013719 Monitor IPC:024C (S32) = 1578292 1023734 Monitor IPC:024C (S32) = 1577524 1043766 Monitor IPC:024C (S32) = 1580452 1073828 Monitor IPC:024C (S32) = 1580488 1083828 Monitor IPC:024C (S32) = 1578320 1093859 Monitor IPC:024C (S32) = 1574040 1113891 Monitor IPC:024C (S32) = 1575308 1123891 Monitor IPC:024C (S32) = 1573932 1143953 Monitor IPC:024C (S32) = 1571440 1153953 Monitor IPC:024C (S32) = 1571748 1163984 Monitor IPC:024C (S32) = 1540492 1174000 Monitor IPC:024C (S32) = 1541068 1184016 Monitor IPC:024C (S32) = 1539664 1194031 Monitor IPC:024C (S32) = 1542128 1204031 Monitor IPC:024C (S32) = 1540736 1214078 Monitor IPC:024C (S32) = 1541488 1224078 Monitor IPC:024C (S32) = 1542944 1234109 Monitor IPC:024C (S32) = 1545012 1244125 Monitor IPC:024C (S32) = 1541788 1254141 Monitor IPC:024C (S32) = 1540660 1264141 Monitor IPC:024C (S32) = 1545172 1274187 Monitor IPC:024C (S32) = 1327216 1284219 Monitor IPC:024C (S32) = 1222232 1294203 Monitor IPC:024C (S32) = 1315060 1304250 Monitor IPC:024C (S32) = 1495832 1314250 Monitor IPC:024C (S32) = 1493440 1324266 Monitor IPC:024C (S32) = 1493384 1334297 Monitor IPC:024C (S32) = 1492932 1344297 Monitor IPC:024C (S32) = 1494332 1354328 Monitor IPC:024C (S32) = 1518600 1364344 Monitor IPC:024C (S32) = 1536352 1374375 Monitor IPC:024C (S32) = 1536116 1384375 Monitor IPC:024C (S32) = 1536208 1394391 Monitor IPC:024C (S32) = 1539600 1404422 Monitor IPC:024C (S32) = 1538332 1414437 Monitor IPC:024C (S32) = 1537408 1424453 Monitor IPC:024C (S32) = 1535772 1434469 Monitor IPC:024C (S32) = 1535284 1454516 Monitor IPC:024C (S32) = 1539604 1474547 Monitor IPC:024C (S32) = 1538016 1484547 Monitor IPC:024C (S32) = 1537908 1494578 Monitor IPC:024C (S32) = 1537432 1504594 Monitor IPC:024C (S32) = 1537004 1514609 Monitor IPC:024C (S32) = 1538256 1524625 Monitor IPC:024C (S32) = 1538276 1554672 Monitor IPC:024C (S32) = 1539300 1574703 Monitor IPC:024C (S32) = 1539336 1584734 Monitor IPC:024C (S32) = 1540736 1614781 Monitor IPC:024C (S32) = 1538588 1624797 Monitor IPC:024C (S32) = 1538596 1634812 Monitor IPC:024C (S32) = 1539128 1654844 Monitor IPC:024C (S32) = 1540540 1684891 Monitor IPC:024C (S32) = 1541268 1694906 Monitor IPC:024C (S32) = 1540560 1704937 Monitor IPC:024C (S32) = 1540456 1714953 Monitor IPC:024C (S32) = 1539144 1724984 Monitor IPC:024C (S32) = 1539188 1734984 Monitor IPC:024C (S32) = 1539428 1755031 Monitor IPC:024C (S32) = 1540136 1765047 Monitor IPC:024C (S32) = 1539432 1785078 Monitor IPC:024C (S32) = 1540856 1825141 Monitor IPC:024C (S32) = 1540132 1845172 Monitor IPC:024C (S32) = 1539776 1865203 Monitor IPC:024C (S32) = 1539224 1885250 Monitor IPC:024C (S32) = 1537664 1905297 Monitor IPC:024C (S32) = 1537264 1915297 Monitor IPC:024C (S32) = 1536736 1925312 Monitor IPC:024C (S32) = 1536212 1935344 Monitor IPC:024C (S32) = 1536064 1945359 Monitor IPC:024C (S32) = 1534508 1955375 Monitor IPC:024C (S32) = 1533064 1965375 Monitor IPC:024C (S32) = 1533108 1995453 Monitor IPC:024C (S32) = 1533680 2005453 Monitor IPC:024C (S32) = 1533736 2015484 Monitor IPC:024C (S32) = 1533912 2025484 Monitor IPC:024C (S32) = 1533556 2035516 Monitor IPC:024C (S32) = 1534064 2045531 Monitor IPC:024C (S32) = 1533728 2055547 Monitor IPC:024C (S32) = 1533716 2065562 Monitor IPC:024C (S32) = 1534776 2075562 Monitor IPC:024C (S32) = 1534676 2085609 Monitor IPC:024C (S32) = 1534772 2095625 Monitor IPC:024C (S32) = 1534780 2105641 Monitor IPC:024C (S32) = 1535276 2115656 Monitor IPC:024C (S32) = 1513048 2125672 Monitor IPC:024C (S32) = 1514768 2135687 Monitor IPC:024C (S32) = 1515656 2145703 Monitor IPC:024C (S32) = 1515628 2155719 Monitor IPC:024C (S32) = 1516232 2165750 Monitor IPC:024C (S32) = 1516160 2175766 Monitor IPC:024C (S32) = 1514972 2185781 Monitor IPC:024C (S32) = 1516276 2195781 Monitor IPC:024C (S32) = 1516588 2205828 Monitor IPC:024C (S32) = 1516148 2215828 Monitor IPC:024C (S32) = 1518880 2225844 Monitor IPC:024C (S32) = 1519540 2235859 Monitor IPC:024C (S32) = 1520448 2245875 Monitor IPC:024C (S32) = 1520524 2255906 Monitor IPC:024C (S32) = 1517944 2265922 Monitor IPC:024C (S32) = 1518568 2275937 Monitor IPC:024C (S32) = 1519676 2285937 Monitor IPC:024C (S32) = 1518532 2295953 Monitor IPC:024C (S32) = 1516664 2305984 Monitor IPC:024C (S32) = 1516204 2316000 Monitor IPC:024C (S32) = 1515684 2326031 Monitor IPC:024C (S32) = 1514444 2336031 Monitor IPC:024C (S32) = 1514408 2346047 Monitor IPC:024C (S32) = 1515404 2356062 Monitor IPC:024C (S32) = 1515396 2366094 Monitor IPC:024C (S32) = 1514900 2376109 Monitor IPC:024C (S32) = 1516024 2386109 Monitor IPC:024C (S32) = 1515972 2396125 Monitor IPC:024C (S32) = 1515924 2406172 Monitor IPC:024C (S32) = 1516496 2416172 Monitor IPC:024C (S32) = 1516460 2426187 Monitor IPC:024C (S32) = 1515912 2436219 Monitor IPC:024C (S32) = 1515904 2446234 Monitor IPC:024C (S32) = 1516524 2456250 Monitor IPC:024C (S32) = 1516472 2466266 Monitor IPC:024C (S32) = 1516508 2476281 Monitor IPC:024C (S32) = 1515084 2486297 Monitor IPC:024C (S32) = 1517180 2496328 Monitor IPC:024C (S32) = 1517148 2506328 Monitor IPC:024C (S32) = 1517228 2516359 Monitor IPC:024C (S32) = 1516472 2526359 Monitor IPC:024C (S32) = 1517584 2536391 Monitor IPC:024C (S32) = 1517360 2546391 Monitor IPC:024C (S32) = 1517660 2556422 Monitor IPC:024C (S32) = 1515328 2566437 Monitor IPC:024C (S32) = 1517248 2576469 Monitor IPC:024C (S32) = 1516452 2586469 Monitor IPC:024C (S32) = 1516756 2596484 Monitor IPC:024C (S32) = 1516944 2606500 Monitor IPC:024C (S32) = 1514764 2616516 Monitor IPC:024C (S32) = 1535460 2626547 Monitor IPC:024C (S32) = 1533584 2636547 Monitor IPC:024C (S32) = 1534880 2646594 Monitor IPC:024C (S32) = 1340648 2656625 Monitor IPC:024C (S32) = 1318624 2666641 Monitor IPC:024C (S32) = 1318704 2676641 Monitor IPC:024C (S32) = 1319100 2686672 Monitor IPC:024C (S32) = 1267356 2696687 Monitor IPC:024C (S32) = 1268456 2706703 Monitor IPC:024C (S32) = 1255780 2716750 Monitor IPC:024C (S32) = 1245268 2726734 Monitor IPC:024C (S32) = 1199112 2736766 Monitor IPC:024C (S32) = 1198144 2746797 Monitor IPC:024C (S32) = 1198280 2756828 Monitor IPC:024C (S32) = 1197696 2766844 Monitor IPC:024C (S32) = 1194924 2776875 Monitor IPC:024C (S32) = 1194792 2786875 Monitor IPC:024C (S32) = 1194884 2796891 Monitor IPC:024C (S32) = 1195396 2806906 Monitor IPC:024C (S32) = 1196144 2816937 Monitor IPC:024C (S32) = 1216820 2826969 Monitor IPC:024C (S32) = 1215876 2836984 Monitor IPC:024C (S32) = 1216884 2847000 Monitor IPC:024C (S32) = 1218768 2857000 Monitor IPC:024C (S32) = 1247292 2867016 Monitor IPC:024C (S32) = 1304916 2877047 Monitor IPC:024C (S32) = 1299344 2887062 Monitor IPC:024C (S32) = 1306736 2897109 Monitor IPC:024C (S32) = 1307192 2907125 Monitor IPC:024C (S32) = 1307400 2917125 Monitor IPC:024C (S32) = 1486960 2927156 Monitor IPC:024C (S32) = 1485556 2937156 Monitor IPC:024C (S32) = 1485052 2947187 Monitor IPC:024C (S32) = 1484472 2957187 Monitor IPC:024C (S32) = 1481856 2967203 Monitor IPC:024C (S32) = 1482348 2977234 Monitor IPC:024C (S32) = 1482356 2987250 Monitor IPC:024C (S32) = 1481464 2997266 Monitor IPC:024C (S32) = 1481916 3007297 Monitor IPC:024C (S32) = 1484368 3017312 Monitor IPC:024C (S32) = 1487664 3027312 Monitor IPC:024C (S32) = 1492256 3037344 Monitor IPC:024C (S32) = 1495444 3047359 Monitor IPC:024C (S32) = 1503468 3057375 Monitor IPC:024C (S32) = 1509160 3067391 Monitor IPC:024C (S32) = 1509424 3077406 Monitor IPC:024C (S32) = 1508176 3087422 Monitor IPC:024C (S32) = 1517652 3097453 Monitor IPC:024C (S32) = 1517184 3107453 Monitor IPC:024C (S32) = 1517224 3117484 Monitor IPC:024C (S32) = 1519316 3127516 Monitor IPC:024C (S32) = 1518340 3137516 Monitor IPC:024C (S32) = 1498748 3147531 Monitor IPC:024C (S32) = 1498216 3187609 Monitor IPC:024C (S32) = 1498740 3197625 Monitor IPC:024C (S32) = 1497936 3207641 Monitor IPC:024C (S32) = 1498392 3227672 Monitor IPC:024C (S32) = 1498348 3237687 Monitor IPC:024C (S32) = 1497804 3247719 Monitor IPC:024C (S32) = 1497864 3257734 Monitor IPC:024C (S32) = 1497792 3277766 Monitor IPC:024C (S32) = 1498304 3287781 Monitor IPC:024C (S32) = 1498372 3297812 Monitor IPC:024C (S32) = 1499404 3307812 Monitor IPC:024C (S32) = 1499364 3317844 Monitor IPC:024C (S32) = 1499436 3327859 Monitor IPC:024C (S32) = 1499420 3337875 Monitor IPC:024C (S32) = 1498932 3347891 Monitor IPC:024C (S32) = 1498920 3357906 Monitor IPC:024C (S32) = 1499000 3367922 Monitor IPC:024C (S32) = 1498916 3377937 Monitor IPC:024C (S32) = 1499460 3387953 Monitor IPC:024C (S32) = 1498824 3397984 Monitor IPC:024C (S32) = 1499864 3407984 Monitor IPC:024C (S32) = 1499948 3418031 Monitor IPC:024C (S32) = 1501040 3428031 Monitor IPC:024C (S32) = 1500488 3438062 Monitor IPC:024C (S32) = 1499768 3458078 Monitor IPC:024C (S32) = 1499680 3468094 Monitor IPC:024C (S32) = 1499616 3478125 Monitor IPC:024C (S32) = 1500308 3488141 Monitor IPC:024C (S32) = 1499752 3498156 Monitor IPC:024C (S32) = 1498896 3508172 Monitor IPC:024C (S32) = 1497444 3518187 Monitor IPC:024C (S32) = 1493012 3528203 Monitor IPC:024C (S32) = 1494696 3538234 Monitor IPC:024C (S32) = 1494708 3548250 Monitor IPC:024C (S32) = 1495112 3558281 Monitor IPC:024C (S32) = 1496244 3568297 Monitor IPC:024C (S32) = 1496640 3578297 Monitor IPC:024C (S32) = 1499280 3588328 Monitor IPC:024C (S32) = 1498888 3598344 Monitor IPC:024C (S32) = 1500668 3608375 Monitor IPC:024C (S32) = 1500196 3618391 Monitor IPC:024C (S32) = 1498616 3628391 Monitor IPC:024C (S32) = 1498584 3638406 Monitor IPC:024C (S32) = 1499168 3648422 Monitor IPC:024C (S32) = 1498544 3658453 Monitor IPC:024C (S32) = 1497536 3668484 Monitor IPC:024C (S32) = 1497016 3678484 Monitor IPC:024C (S32) = 1497316 3688500 Monitor IPC:024C (S32) = 1493956 3698531 Monitor IPC:024C (S32) = 1493940 3708547 Monitor IPC:024C (S32) = 1495468 3718562 Monitor IPC:024C (S32) = 1495500 3728594 Monitor IPC:024C (S32) = 1494968 3738594 Monitor IPC:024C (S32) = 1494312 3748609 Monitor IPC:024C (S32) = 1492736 3758625 Monitor IPC:024C (S32) = 1493684 3768641 Monitor IPC:024C (S32) = 1491092 3778672 Monitor IPC:024C (S32) = 1490532 3788672 Monitor IPC:024C (S32) = 1489848 3798703 Monitor IPC:024C (S32) = 1489904 3808719 Monitor IPC:024C (S32) = 1488916 3818734 Monitor IPC:024C (S32) = 1296652 3828766 Monitor IPC:024C (S32) = 1264376 3838797 Monitor IPC:024C (S32) = 1215916 3848797 Monitor IPC:024C (S32) = 1193240 3858828 Monitor IPC:024C (S32) = 1182260 3868859 Monitor IPC:024C (S32) = 1182276 3878875 Monitor IPC:024C (S32) = 1182492 3888891 Monitor IPC:024C (S32) = 1182324 3898906 Monitor IPC:024C (S32) = 1181700 3908922 Monitor IPC:024C (S32) = 1139992 3918953 Monitor IPC:024C (S32) = 1261604 3928953 Monitor IPC:024C (S32) = 1104448 3939000 Monitor IPC:024C (S32) = 1134416 3949031 Monitor IPC:024C (S32) = 1126844 3959031 Monitor IPC:024C (S32) = 1123224 3969062 Monitor IPC:024C (S32) = 1116308 3979094 Monitor IPC:024C (S32) = 1114148 3989109 Monitor IPC:024C (S32) = 1105928 3999141 Monitor IPC:024C (S32) = 1099376 4009156 Monitor IPC:024C (S32) = 1099244 4019156 Monitor IPC:024C (S32) = 1078676 4029266 Monitor IPC:024C (S32) = 1055984 4039187 Monitor IPC:024C (S32) = 1075680 4049234 Monitor IPC:024C (S32) = 1113188 4059250 Monitor IPC:024C (S32) = 1116916 4069250 Monitor IPC:024C (S32) = 1120600 4079281 Monitor IPC:024C (S32) = 1136704 4089297 Monitor IPC:024C (S32) = 1148748 4099328 Monitor IPC:024C (S32) = 1150208 4109344 Monitor IPC:024C (S32) = 1155520 4119359 Monitor IPC:024C (S32) = 1148804 4129391 Monitor IPC:024C (S32) = 1133444 4139391 Monitor IPC:024C (S32) = 1132008 4143375 Sim stopped: average frame rate for last 4058 secs = 41.8 fps 4143375 Max AI traffic was 146 aircraft (Deleted 0) 4149437 Monitor IPC:024C (S32) = 991780 4159453 Monitor IPC:024C (S32) = 1046800 4169469 Monitor IPC:024C (S32) = 1072952 4179500 Monitor IPC:024C (S32) = 1072412 4190828 Sim stopped: average frame rate for last 47 secs = 38.6 fps 4190828 Max AI traffic was 146 aircraft (Deleted 0) 4199750 Monitor IPC:024C (S32) = 1080924 4200703 === Closing session: waiting for DLLStop to be called ... 4205187 === DLLStop called ... 4205187 === Closing external processes we started ... 4206187 === About to kill any Lua plug-ins still running ... 4207344 === About to kill my timers ... 4207344 === Restoring window procs ... 4207344 === Unloading libraries ... 4207344 === stopping other threads ... 4207344 === ... Memory checking ... 4207344 === ... Button scanning ... 4207437 === ... Axis scanning ... 4207547 === Releasing joystick devices ... 4207547 === Freeing macro memory 4207547 === Removing any offset overrides 4207547 === Clearing any displays left 4207547 === NOTE: not calling SimConnect_Close ... 4207547 === AI slots deleted! 4207547 === Freeing button memory ... 4207547 === Closing my Windows ... 4207547 === Freeing FS libraries ... 4208547 === Closing devices ... 4208547 === Closing the Log ... Bye Bye! ... 4208547 System time = 30/01/2019 14:21:20, Simulator time = 14:15:11 (18:15Z) 4208547 *** FSUIPC log file being closedMinimum frame rate was 16.9 fps, Maximum was 146.0 fps Minimum available memory recorded was 969Mb Average frame rate for running time of 4105 secs = 41.7 fpsG3D fix: Passes 55156, Null pointers 0, Bad pointers 0, Separate instances 0 Maximum AI traffic for session was 146 aircraft Memory managed: 1948 Allocs, 1948 Freed ********* FSUIPC Log file closed *********** And here are a couple of pictures. The first one, over MSE Virginia, the fps showed 158. The second one, at KCLT in rain, it showed 46 fps. Click on images for more detail. Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant 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
January 30, 20197 yr Wow, in the first picture the groundscenery over the wingview looks very nice... 😮 Hard to believe it's FSX. How did you do that
January 30, 20197 yr Jim's hardware setup should give you an idea of how far he can push FSX, Kalorien 😉 MSI Pro Z690-A DDR4 | i5 13600KF | G.Skill Ripjaws V 32GB 3600MHz | RTX 3080 (12GB) | Samsung 980 M.2 NVMe 500GB | Samsung 980 M.2 NVMe 1TB | Samsung 850EVO 500GB | Crucial P3+ 2TB NVMe | 2TB Seagate HDD | Deepcool AK500 CPU Cooler | Thrustmaster T16000M HOTAS | CH Yoke | Various Winctrl hardware | 21:9 1440p UW monitor | Win 11 23H2 build | MSFS2020 | Tony K.
January 30, 20197 yr Author Thank you, Jim. But I must be a slow learner. How do you find the Report? Looking for FSUIPC on my PC yields nothing. Do you have to end the flight? Close FSX? BTW, since I've been messing around in the past 2 weeks, I seem to have reduced my CTDs a lot. Knock on wood. After a fatal HD crash last summer, I had to replace my PC, reinstall FSX, etc., but then I added a bunch of Orbx scenery and some high-maintenance payware planes to take advantage of my greatly-upgraded PC. I found my sim was unstable and unreliable to the point of unusable. On advice of old pros on forums, I did the UI AutomationCore.dll thing, made a few changes to the cfg, and disabled some scenery I'm not currently using. Also found TweakFPS very helpful, although I have recently gone back to my original cfg. Mac6737 i7-8700 3.7 GHz GeForce GTX 1070 Ti; 8GB onboard AORUS Z370 Gaming 5 LGA 1151 ATX motherboard 16GB RAM 2 TB hard drive 27” MSI gaming monitor, set at 2550 for FSX
January 31, 20197 yr FSUIPC module is located in the Module folder of FSX/P3D. Look for FSUIPC.txt. 28 minutes ago, Mac6737 said: I found my sim was unstable and unreliable to the point of unusable. Respectfully, it is not FSX that is unstable but the user. FSX runs great with default aircraft, scenery, and settings. In fact, with your current system, you probably could exceed 300 fps at the default KLAS (Vegas) in the default F16 or the Baron. The problem is that the unstable user, decides to tweak his FSX.cfg cus he saw something on the Internet where someone has awesome performance by just inserting a tweak. Like NickN (a computer/FSX guru) says, tweaks are bad and they do not work especially on brand new modern computer system. AVSIM has stated the same in the AVSIM FSX Configuration Guide which has the best settings for FSX users. Sure NickN recommended them with old systems as old computer systems needed help to run something that was scenery intensive and texture had to be called and drawn instantly. I have never been a proponent of tweaks. The FSX Config Guide provides some of the various tweaks out there but be careful using them. If FSX crashes, it is not the fault of an unstable FSX but the fault of the unstable user who is trying to throw everything at the simulator (cus he has a powerful system and, well, it should handle it at max settings and it can but not for any length of time as you have to fight running out of VAS). Developers who make addons are appreciated but they throw in a lot of eye-candy that can bring your computer to its knees. In regards to the Windows OS file called uiautomationcore.dll, it is a placebo. Back in the 2007 days, someone posted it on the Internet as the holy grail of fixes for CTD's. It is not as you will eventually suffer another crash or freeze and you then wonder why the uiautomationcore.dll did not stop the crash before it happened. I have mostly used FSX without the placebo... I mean the uiautomationcore.dll in the main folder and did not have any issues for a long time but, when I did get a crash, I would throw the uiautomationcore.dll in the main folder and wa-la, no more crash. But I forgot I had shutdown FSX and reloaded everything so that probably was the fix and not the uiautomationcore.dll as the Microsoft developer's never put it there in the first place. Secondly, the uiautomationcore.dll is part of the Microsoft.net package. So you might have had the wrong version of Microsoft.net that caused the crash. Problem with developers is that Microsoft programmed FSX/Acceleration and installed an early version of Microsoft dotnet. Developers like Orbx have in their packages that Microsoft dotnet 4.6 is required for this scenery. Make sure it is installed. Most people do not know how to find out what is installed and what is not so why I put it in the AVSIM CTD Guide. A method to find out exactly what is installed. I really do not know why developers cannot use their installers to see if a certain version is installed and, if not, install it for you. Microsoft dotnets are used by applications to make sure the product runs properly. I do know that the uiautomationcore.dll that many want you to install in the main directory of FSX is from Vista, the OS used to develop FSX. I suspect the package was updated when Vista was replaced by Windows 7. Still, if you want to place the uiautomationcore.dll in your main directory, go for it. It will not prevent crashes though. You have a nice system which surely can run FSX well but remember, you could have super computer twice as fast as the one you have now, it will still crash when you run out of VAS or you have an incompatible piece of scenery or aircraft or module. But your system is future proof and, I would strongly recommend moving up to P3Dv4 which is FSX but updated and it runs much better and you do not have the limitations of VAS. Still it can crash too if you have an incompatible piece of scenery or aircraft or module. Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant 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
January 31, 20197 yr Hi Jim, You are quite correct with the usage of the Vista UIAutomationCore.dll in the main FSX folder, it will not prevent Generalised CTD's within FSX, nor will it solve setup or incompatible addon scenery/aircraft AI, CTD crashes, but at the time of its proposed implementation as a potential solution for a specific FSX CTD it was quite effective, though nolonger needed under Win10 it may still be useful in Win7/8.1 to rectify the CTD caused by opening/accessing FSX menu bar items, where after several consecutive clicks FSX would CTD. On a side note: how I wish I could get +100FPS ( mine is locked @32 ) where it mostly hovers between 28 - 31.9 - 32 over relatively dense cityscapes, weather and mid AI traffic, mostly maxed graphical / scenery settings, but alas my hardware is now ancient, and need to treat it respectfully, like a three legged dog, it can still bark and bite but has trouble chasing me down, like a best friend this old dog (my PC) is what it is, reliable and trustworthy knowing all its quirks, the rewards are many if I give it a pat every once in a while. Cheers Jethro Cheers Jethro
January 31, 20197 yr Off topic I know, but is anyone else really jealous of Jim right now? Best regards, Neal McCullough
January 31, 20197 yr Author Thank you, Jim. But I must be a slow learner. How do you find the Report? Looking for FSUIPC on my PC yields nothing. Do you have to end the flight? Close FSX?
February 1, 20197 yr 3 hours ago, Mac6737 said: Thank you, Jim. But I must be a slow learner. How do you find the Report? Looking for FSUIPC on my PC yields nothing. Do you have to end the flight? Close FSX? Not sure what you mean by this as I provided the answer in my long post above. It was the first thing I answered. I said - FSUIPC module is located in the Module folder of FSX/P3D. Look for FSUIPC.txt. 3 hours ago, Mac6737 said: Do you have to end the flight? Close FSX? The report will not be available to you until you shutdown FSX. Then you can go into the modules folder and open up the fsuipc.txt and it will provide you all the details as it did for me. Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant 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
February 1, 20197 yr Author Quote Jim, Yes, you said that. And I did look for FSUIPC.txt, and I also used the Win10 search function -- which, as I said, could find nothing. (I've only had Win 10 since August, but IMO it's sort of like Mr. Magoo.) My mistake was to actually look in FSX/Modules for a file named "FSUIPC.txt," and I, too, found nothing. But there's a happy ending! Today, I found a file (no postscript) called "FSUIPC4_prev" in FSX/Modules. I guess this is the log of the last flight before I shut down FSX. Anyway, it has a bunch of entries like the example you gave, above. No value lower than 1.7 BG VAS remaining, which I guess is good news. The bad news is that FSX crashed twice on me yesterday, both times when my FPS was at the preset limit, and MS Process Explorer said my VAS used was below 2.0. So, there's something else afoot besides VAS. In any case, I appreciate your time and thoroughness. I am pondering P3Dv4, and will start looking at those forums to see how error-free it really is. I don't mind the "Professional" price tag, but I am not enthusiastic about learning a new system. (After all these years, I know a lot of FSX keystrokes.) Finally, you indicate I should rely on the AVSIM FSX Basic Config Guide. OK, but that says it's for FSX with "no commercial or freeware scenery/aircraft add-on." For the time being, I shall persist with FSX and my beloved Orbx sceneries, which produce eye candy like the jpeg I have now failed to attach to this post. Mac6737
February 1, 20197 yr Commercial Member 9 minutes ago, Mac6737 said: My mistake was to actually look in FSX/Modules for a file named "FSUIPC.txt," and I, too, found nothing. The log file is called FSUIPC4.LOG (or FSUIPC5.LOG for P3Dv4), not TXT. Cheers! Luke Kolin I make simFDR, the most advanced flight data recorder for FSX, Prepar3D and X-Plane.
Archived
This topic is now archived and is closed to further replies.