February 3, 201511 yr @HeronjrI have been testing for more then a year, maybe longer on FSX-MS Gold. Switched to DX10 etc. blabla. I can´t really say what exactly made the difference, because I changed everthing, starting with the hardware. Today my FSX run for 9 hours, flying over the Atlantik! I did everthing which was/is not allowed. Turning 100x in external, 2D, 3D cockpit, all wingviews many many times over and over. Fly-bys, 9 hours! SMOOTH!Aircraft: Qualitywings 757-200 (sry, I don´t use PMDG)Departure: Mega EDDF with probably 12-15 hot looking moving Ai around and much more on parking position. I need to adjust the schedule/speeds of those, because SuperTrafficBoard cancels many of them after 9 hours.ASN Weather with REX4 and SoftClouds (ASN on a client). The weather wasn´t really good for the trip today. Many clouds, head- and crosswind 50-100 knots. On top of all I tested the ASN settings to see what´s best. That made my sim always crash, but not today.PFE ATC (client). You can fly the NATS!ORBX FTX Global Base, Global Vector, Global openLC Europe, FS Global 2010 FTX Compatible installed and all active in the libary.TextureMaxLoad=2048AffinityMask=7 lolGSX, AES all active.Destination: FSDT JFK Scenery V2, landed, taxi to gate with follow me smoothly. And again some nice Ai.Other add-on sceneries deactivated.FSX rules if you find the setting for your system. Ah, maybe you should not max out Autogendensity. That´s the only important one I have lowered for one step. It´s on the edge but it works.A 3.4 GHz CPU is too slow... FSX demands POWER! I love it (who needs Steam) Don´t give up.
February 4, 201511 yr Thanks, Jim. Still managing a round in your wintry weather? Hi Rick, I've played about 5 rounds so far this year. I no longer play when the temps are in the 30's but the rest of my group does. I also had a bad case of the flu at the beginning of the year so stayed home until I was fully recuperated. Fortunately no snow so far this year so that's not stopping me. Thanks for asking. Best regards, 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 4, 201511 yr Author I have about 2GB's of VAS as I near the approach at my destination but, as I turn into the approach VAS is running low and I'm suddenly down to less than 1GB of VAS left. Jim, When I START FSX and choose the 777 on a default airport, with or without weather, my VAS shows around 1.7 GB!!! If I go to the outside view VAS goes to 1.3 GB. How, after 2 hours, the above user still has 2 GB??? It is clear my system has a big problem. What VAS should I have starting FSX? 2.5? 3.5? Which software could be eating my VAS? FTX? The 777? Best regards, Heron Domingues, Jr Intel Core I7 10700KF, 3.80GHz (5.10GHz Turbo), Gigabyte B460, RAM 32GB, Corsair 750W, GPU Palit RTX 3060, Windows 10 Pro 64., P3Dv5.4.
February 4, 201511 yr What VAS should I have starting FSX? 2.5? 3.5? Which software could be eating my VAS? FTX? The 777? For me, with the PMDG 777, MSE V2 Ultra HiRes Chicago and Ultra HiRes Baltimore/Washington, FSDT Chicago, FlightBeam KIAD, ProATC-X, ASN, and GEX enabled, I had 3.37GB's at startup. After selecting the PMDG 777 I had 2.92GB's, selected location and time, 1.93GB's, and then sitting at the gate at KORD, 1.58GB's so our figures are about the same. Here's the full FSUIPC log showing VAS remaining at various waypoints along the way: WIDEFS7 not user registered, or expired218 System time = 27/01/2015 15:44:08218 FLT path = "C:\Users\JimY\Documents\Flight Simulator X Files\"250 Trying to connect to SimConnect Acc/SP2 Oct07 ...250 FS path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"343 LogOptions=00000000 00000001343 SIM1 Frictions access gained343 Wind smoothing fix is fully installed343 G3D.DLL fix attempt installed ok343 SimConnect_Open succeeded: waiting to check version okay343 Trying to use SimConnect Acc/SP2 Oct073619 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)3619 Initialising SimConnect data requests now3619 FSUIPC Menu entry added3619 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT3619 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR3900 Monitor IPC:024C (S32) = 3535532 At FSX setup page - 3.37GBs (enabled ASN and ProATC-X before starting up FSX)13728 Monitor IPC:024C (S32) = 342864423790 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\PMDG 777-300ER\B777-300ER.AIR23837 Monitor IPC:024C (S32) = 3064736 Selected the PMDG 777 - 2.92GBs34008 Monitor IPC:024C (S32) = 265822443930 Monitor IPC:024C (S32) = 267920864148 Monitor IPC:024C (S32) = 267869674194 Monitor IPC:024C (S32) = 269244084256 Monitor IPC:024C (S32) = 261481694240 Monitor IPC:024C (S32) = 2503404104224 Monitor IPC:024C (S32) = 2461584114645 Monitor IPC:024C (S32) = 2212028124645 Monitor IPC:024C (S32) = 2021196 Selected location and time - 1.93GBs (major drop in amount of VAS left but almost 2GB's remaining)127406 System time = 27/01/2015 15:46:16, Simulator time = 14:44:12 (20:44Z)127406 Aircraft="PMDG 777-323ER American Airlines"129793 Weather Mode now = Theme131946 Starting everything now ...133178 Advanced Weather Interface Enabled133646 Ready for ASN WX radar134582 Monitor IPC:024C (S32) = 1654296 Sitting at Gate at FSDT KORD - 1.58GBs (another major drop after loading FSX and getting to the gate)144613 Monitor IPC:024C (S32) = 1661156154644 Monitor IPC:024C (S32) = 1658176164690 Monitor IPC:024C (S32) = 1697904174706 Monitor IPC:024C (S32) = 1726616184768 Monitor IPC:024C (S32) = 1728664194830 Monitor IPC:024C (S32) = 1684792204861 Monitor IPC:024C (S32) = 1679540214907 Monitor IPC:024C (S32) = 1620088224922 Monitor IPC:024C (S32) = 1574152234969 Monitor IPC:024C (S32) = 1544456245031 Monitor IPC:024C (S32) = 1527916255062 Monitor IPC:024C (S32) = 1527404275139 Monitor IPC:024C (S32) = 1511212295216 Monitor IPC:024C (S32) = 1510076305232 Monitor IPC:024C (S32) = 1496952325325 Monitor IPC:024C (S32) = 1480760335355 Monitor IPC:024C (S32) = 1452888345402 Monitor IPC:024C (S32) = 1433960355464 Monitor IPC:024C (S32) = 1425156365510 Monitor IPC:024C (S32) = 1413612375572 Monitor IPC:024C (S32) = 1421680395587 Monitor IPC:024C (S32) = 1421004405603 Monitor IPC:024C (S32) = 1422212415634 Monitor IPC:024C (S32) = 1417868425649 Monitor IPC:024C (S32) = 1425968435695 Monitor IPC:024C (S32) = 1454696445742 Monitor IPC:024C (S32) = 1454124455819 Monitor IPC:024C (S32) = 1446000465866 Monitor IPC:024C (S32) = 1450592475897 Monitor IPC:024C (S32) = 1424488485943 Monitor IPC:024C (S32) = 1408168495943 Monitor IPC:024C (S32) = 1383988505974 Monitor IPC:024C (S32) = 1389416515989 Monitor IPC:024C (S32) = 1404228526020 Monitor IPC:024C (S32) = 1400232536051 Monitor IPC:024C (S32) = 1395188546082 Monitor IPC:024C (S32) = 1395620556097 Monitor IPC:024C (S32) = 1459844566159 Monitor IPC:024C (S32) = 1467284576237 Monitor IPC:024C (S32) = 1470188586267 Monitor IPC:024C (S32) = 1476260596298 Monitor IPC:024C (S32) = 1479220606314 Monitor IPC:024C (S32) = 1481004626391 Monitor IPC:024C (S32) = 1377908636406 Monitor IPC:024C (S32) = 1399624646453 Monitor IPC:024C (S32) = 1401220656499 Monitor IPC:024C (S32) = 1340332666514 Monitor IPC:024C (S32) = 1300060676576 Monitor IPC:024C (S32) = 1391920686592 Monitor IPC:024C (S32) = 1392628696607 Monitor IPC:024C (S32) = 1411020706607 Monitor IPC:024C (S32) = 1410164716622 Monitor IPC:024C (S32) = 1361764726668 Monitor IPC:024C (S32) = 1362404736715 Monitor IPC:024C (S32) = 1363172746761 Monitor IPC:024C (S32) = 1365140756792 Monitor IPC:024C (S32) = 1358496766854 Monitor IPC:024C (S32) = 1362496776885 Monitor IPC:024C (S32) = 1358980786947 Monitor IPC:024C (S32) = 1353936796994 Monitor IPC:024C (S32) = 1355904 Waypoint Mobile - 1.29GBs807056 Monitor IPC:024C (S32) = 1357956817071 Monitor IPC:024C (S32) = 1360948827102 Monitor IPC:024C (S32) = 1358980837133 Monitor IPC:024C (S32) = 1358040847164 Monitor IPC:024C (S32) = 1357424857163 Monitor IPC:024C (S32) = 1354260867178 Monitor IPC:024C (S32) = 1350624877225 Monitor IPC:024C (S32) = 1345892887271 Monitor IPC:024C (S32) = 1338276897333 Monitor IPC:024C (S32) = 1339340907349 Monitor IPC:024C (S32) = 1348056927426 Monitor IPC:024C (S32) = 1383584937441 Monitor IPC:024C (S32) = 1382716 waypoint ADIME - 1.32GBs947503 Monitor IPC:024C (S32) = 1383872957534 Monitor IPC:024C (S32) = 1384044967549 Monitor IPC:024C (S32) = 1381584997658 Monitor IPC:024C (S32) = 13826521007657 Monitor IPC:024C (S32) = 13757041017704 Monitor IPC:024C (S32) = 13667121027766 Monitor IPC:024C (S32) = 13686801037766 Monitor IPC:024C (S32) = 13604481047796 Monitor IPC:024C (S32) = 13633961057858 Monitor IPC:024C (S32) = 13664721067921 Monitor IPC:024C (S32) = 13557041077967 Monitor IPC:024C (S32) = 13573921087982 Monitor IPC:024C (S32) = 13656321098029 Monitor IPC:024C (S32) = 13689161118106 Monitor IPC:024C (S32) = 1370456 waypoint OTENS (nearing TOC - FL280) - 1.31GBs1128153 Monitor IPC:024C (S32) = 13718241138152 Monitor IPC:024C (S32) = 13704401148167 Monitor IPC:024C (S32) = 13361041158214 Monitor IPC:024C (S32) = 13369561169228 Monitor IPC:024C (S32) = 13550401179040 Monitor IPC:024C (S32) = 13231841189040 Monitor IPC:024C (S32) = 12580761199117 Monitor IPC:024C (S32) = 13076521209117 Monitor IPC:024C (S32) = 13016961219148 Monitor IPC:024C (S32) = 12542241229148 Monitor IPC:024C (S32) = 13200761239194 Monitor IPC:024C (S32) = 13143441249256 Monitor IPC:024C (S32) = 13306361259303 Monitor IPC:024C (S32) = 13300561269333 Monitor IPC:024C (S32) = 13204881279349 Monitor IPC:024C (S32) = 13172401289489 Monitor IPC:024C (S32) = 13160321299520 Monitor IPC:024C (S32) = 13185161309566 Monitor IPC:024C (S32) = 12633601319597 Monitor IPC:024C (S32) = 12987121329628 Monitor IPC:024C (S32) = 12981961339705 Monitor IPC:024C (S32) = 12930441349705 Monitor IPC:024C (S32) = 1292296 waypoint RIEKE - 1.23GBs1359720 Monitor IPC:024C (S32) = 12890121379813 Monitor IPC:024C (S32) = 12880161389844 Monitor IPC:024C (S32) = 12350401399844 Monitor IPC:024C (S32) = 12706521409906 Monitor IPC:024C (S32) = 12701401419937 Monitor IPC:024C (S32) = 12770001429952 Monitor IPC:024C (S32) = 12590001439999 Monitor IPC:024C (S32) = 12581441450014 Monitor IPC:024C (S32) = 12576321470107 Monitor IPC:024C (S32) = 12586561480153 Monitor IPC:024C (S32) = 12562641490184 Monitor IPC:024C (S32) = 12124041500199 Monitor IPC:024C (S32) = 12743881510277 Monitor IPC:024C (S32) = 12777241520308 Monitor IPC:024C (S32) = 12735561530370 Monitor IPC:024C (S32) = 1275496 waypoint GAABE - 1.22GBs1540416 Monitor IPC:024C (S32) = 12755721550463 Monitor IPC:024C (S32) = 12893641560478 Monitor IPC:024C (S32) = 12907321570525 Monitor IPC:024C (S32) = 12868361580587 Monitor IPC:024C (S32) = 12964041590617 Monitor IPC:024C (S32) = 12839081600680 Monitor IPC:024C (S32) = 12770761610726 Monitor IPC:024C (S32) = 12886121620788 Monitor IPC:024C (S32) = 1286644 waypoint SPOOL - 1.23GBs1630803 Monitor IPC:024C (S32) = 12770761640834 Monitor IPC:024C (S32) = 12764321650849 Monitor IPC:024C (S32) = 12832641660912 Monitor IPC:024C (S32) = 12818961670942 Monitor IPC:024C (S32) = 12993801680973 Monitor IPC:024C (S32) = 13004401690989 Monitor IPC:024C (S32) = 12958041701019 Monitor IPC:024C (S32) = 12941601711035 Monitor IPC:024C (S32) = 12928321721081 Monitor IPC:024C (S32) = 1301040 waypoint AIR - 1.24GBs1731096 Monitor IPC:024C (S32) = 12906321741158 Monitor IPC:024C (S32) = 12917841761205 Monitor IPC:024C (S32) = 12877641771204 Monitor IPC:024C (S32) = 12787961781219 Monitor IPC:024C (S32) = 12807401791250 Monitor IPC:024C (S32) = 12917441801266 Monitor IPC:024C (S32) = 12924281821359 Monitor IPC:024C (S32) = 12890921831421 Monitor IPC:024C (S32) = 12047281841467 Monitor IPC:024C (S32) = 12661721851514 Monitor IPC:024C (S32) = 12666881861560 Monitor IPC:024C (S32) = 12672041871622 Monitor IPC:024C (S32) = 12171521881622 Monitor IPC:024C (S32) = 12530001891653 Monitor IPC:024C (S32) = 12086281901730 Monitor IPC:024C (S32) = 12735401911746 Monitor IPC:024C (S32) = 12743481921792 Monitor IPC:024C (S32) = 12715881951885 Monitor IPC:024C (S32) = 1272100 TOD - 1.21GBs1961947 Monitor IPC:024C (S32) = 12715881971978 Monitor IPC:024C (S32) = 12740681981993 Monitor IPC:024C (S32) = 12721001992024 Monitor IPC:024C (S32) = 12823002002055 Monitor IPC:024C (S32) = 12922122012117 Monitor IPC:024C (S32) = 12882762022132 Monitor IPC:024C (S32) = 12913562032210 Monitor IPC:024C (S32) = 12868722042256 Monitor IPC:024C (S32) = 12893882052318 Monitor IPC:024C (S32) = 12869122062333 Monitor IPC:024C (S32) = 12882322072411 Monitor IPC:024C (S32) = 12899082082473 Monitor IPC:024C (S32) = 12918082092441 Monitor IPC:024C (S32) = 12923242102457 Monitor IPC:024C (S32) = 12845322112472 Monitor IPC:024C (S32) = 12886282122503 Monitor IPC:024C (S32) = 12873002132534 Monitor IPC:024C (S32) = 12854202152627 Monitor IPC:024C (S32) = 12322482162626 Monitor IPC:024C (S32) = 12388962172673 Monitor IPC:024C (S32) = 12337242182735 Monitor IPC:024C (S32) = 12323962192781 Monitor IPC:024C (S32) = 12411002202828 Monitor IPC:024C (S32) = 12416122222858 Monitor IPC:024C (S32) = 12411002232874 Monitor IPC:024C (S32) = 12404842242920 Monitor IPC:024C (S32) = 12486762252982 Monitor IPC:024C (S32) = 12491882263013 Monitor IPC:024C (S32) = 12472762273028 Monitor IPC:024C (S32) = 12467642283090 Monitor IPC:024C (S32) = 12473282293090 Monitor IPC:024C (S32) = 12451082313136 Monitor IPC:024C (S32) = 11996242323214 Monitor IPC:024C (S32) = 12680402333229 Monitor IPC:024C (S32) = 12523602353306 Monitor IPC:024C (S32) = 12513362363322 Monitor IPC:024C (S32) = 12523602373352 Monitor IPC:024C (S32) = 12518482393430 Monitor IPC:024C (S32) = 12504802403476 Monitor IPC:024C (S32) = 12491122413523 Monitor IPC:024C (S32) = 12486002443678 Monitor IPC:024C (S32) = 12505682453724 Monitor IPC:024C (S32) = 12471962483879 Monitor IPC:024C (S32) = 12477082493910 Monitor IPC:024C (S32) = 12482202534034 Monitor IPC:024C (S32) = 12489322544064 Monitor IPC:024C (S32) = 12475642554111 Monitor IPC:024C (S32) = 12468562564157 Monitor IPC:024C (S32) = 12486242574173 Monitor IPC:024C (S32) = 12466562584203 Monitor IPC:024C (S32) = 12491402594234 Monitor IPC:024C (S32) = 12476042604265 Monitor IPC:024C (S32) = 12601002614312 Monitor IPC:024C (S32) = 12607842624374 Monitor IPC:024C (S32) = 12565962634436 Monitor IPC:024C (S32) = 12552282644482 Monitor IPC:024C (S32) = 12559122654482 Monitor IPC:024C (S32) = 1257280 waypoint CSN - 1.192664544 Monitor IPC:024C (S32) = 12479682674544 Monitor IPC:024C (S32) = 12545362684559 Monitor IPC:024C (S32) = 12491682694574 Monitor IPC:024C (S32) = 12481442704636 Monitor IPC:024C (S32) = 12501122714667 Monitor IPC:024C (S32) = 12387842734729 Monitor IPC:024C (S32) = 12401522754775 Monitor IPC:024C (S32) = 13124082915331 Monitor IPC:024C (S32) = 13129202935424 Monitor IPC:024C (S32) = 13124083377203 Monitor IPC:024C (S32) = 12742603387203 Monitor IPC:024C (S32) = 12728923407358 Monitor IPC:024C (S32) = 12704603417405 Monitor IPC:024C (S32) = 11808123427467 Monitor IPC:024C (S32) = 11760323437467 Monitor IPC:024C (S32) = 11591563447497 Monitor IPC:024C (S32) = 11639563457513 Monitor IPC:024C (S32) = 1136948 waypoint LUSIE (top of the Approach to Runway 01C FlightBeam KIAD) - 1.08GBs3467559 Monitor IPC:024C (S32) = 11378843477590 Monitor IPC:024C (S32) = 11380563487605 Monitor IPC:024C (S32) = 11317323497652 Monitor IPC:024C (S32) = 11376563507698 Monitor IPC:024C (S32) = 11339563517729 Monitor IPC:024C (S32) = 11094443527744 Monitor IPC:024C (S32) = 11131203537775 Monitor IPC:024C (S32) = 11164563547806 Monitor IPC:024C (S32) = 11003643557821 Monitor IPC:024C (S32) = 10978803567899 Monitor IPC:024C (S32) = 10780923577867 Monitor IPC:024C (S32) = 10407603587914 Monitor IPC:024C (S32) = 971232 full left turn toward Runway 01C3597960 Monitor IPC:024C (S32) = 7346643608022 Monitor IPC:024C (S32) = 7318643618053 Monitor IPC:024C (S32) = 7015323628100 Monitor IPC:024C (S32) = 6982123638115 Monitor IPC:024C (S32) = 6950443648208 Monitor IPC:024C (S32) = 6964123658270 Monitor IPC:024C (S32) = 6982923668286 Monitor IPC:024C (S32) = 7006963678332 Monitor IPC:024C (S32) = 6851043688347 Monitor IPC:024C (S32) = 6460123698409 Monitor IPC:024C (S32) = 6283683718549 Monitor IPC:024C (S32) = 6302723728596 Monitor IPC:024C (S32) = 626336 halfway down the approach - 612 MBs3738642 Monitor IPC:024C (S32) = 6310403758704 Monitor IPC:024C (S32) = 6349763768766 Monitor IPC:024C (S32) = 6438523778812 Monitor IPC:024C (S32) = 6411163788843 Monitor IPC:024C (S32) = 6233323798905 Monitor IPC:024C (S32) = 6202003808905 Monitor IPC:024C (S32) = 6142203818920 Monitor IPC:024C (S32) = 6062163828951 Monitor IPC:024C (S32) = 6149803838951 Monitor IPC:024C (S32) = 6117163848982 Monitor IPC:024C (S32) = 6197203859012 Monitor IPC:024C (S32) = 6157523869074 Monitor IPC:024C (S32) = 5601443879105 Monitor IPC:024C (S32) = 613812 Touchdown!!! 599 MBs3919166 Monitor IPC:024C (S32) = 6152963920009 Sim stopped: average frame rate for last 3793 secs = 26.9 fps3929244 Monitor IPC:024C (S32) = 5349843939244 Monitor IPC:024C (S32) = 5288443969368 Monitor IPC:024C (S32) = 513464 Gate 501 MBs3972519 Sim stopped: average frame rate for last 50 secs = 18.6 fps3980007 System time = 27/01/2015 16:50:28, Simulator time = 17:15:06 (22:15Z)3980007 *** FSUIPC log file being closedAverage frame rate for running time of 3843 secs = 26.8 fpsG3D fix: Passes 119011, Null pointers 0, Bad pointers 0, Separate instances 0Memory managed: 1720 Allocs, 1720 Freed********* FSUIPC Log file closed *********** I was happy with this flight as I had plenty of VAS remaining. Had I not landed at KIAD, I could have gone much further as I had over 1GB of VAS remaining up to the TOD. If I had stayed at FL280, I am confident the VAS would have remained the same but not sure how much I would have had during the approach and landing phases. As you can see, at cruising, the VAS stays about the same and fluctuates moderately up and down until the descent phase. I do not have autogen turned on as autogen eats VAS like crazy unless optimized. This was proven with P3DV2.0 and subsequently fixed by Lockheed Martin techs when they completely optimized the autogen. Problem being, is the autogen developed by FTX/Orbx optimized too? I personally do not like flight longer than 2 hours, especially in these days where VAS usage seems to be more than usual with high powered computer systems. We really did not have this problem back when our systems were substandard and we were fighting to try to get as much fps out of FSX as possible and tweaking and lowering settings was the only solution. Now everyone has powerful systems and they think they can crank it up and that is a recipe for disaster. Best regards, 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 4, 201511 yr Wise words, Jim, re:today's multi-core hardware, etc giving a false sense of 'everything can be turned on'. Thanks for the other sport update. Glad you have recovered. At least you are not having our minus 9s-10s!! Is the 'Tiger' sliding backwards while his g/f is coming from the pits to the peaks? Rick Almeida
February 4, 201511 yr Author For me, with the PMDG 777, MSE V2 Ultra HiRes Chicago and Ultra HiRes Baltimore/Washington, FSDT Chicago, FlightBeam KIAD, ProATC-X, ASN, and GEX enabled, I had 3.37GB's at startup. After selecting the PMDG 777 I had 2.92GB's, selected location and time, 1.93GB's, and then sitting at the gate at KORD, 1.58GB's so our figures are about the same. Jim, Tks for the numbers and the log. Your system lets FSX starts with 3.1 GB. Mine starts with 2.3 GB on a default field, without the 777. I never see a 3 GB figure. The only explanation is that the FTX artifacts (Global+Vector+OpenLC+Regions) eat at least 1 GB of VAS. My FSX is installed on a machine full dedicated to it and I always reboot it before flying. Tonight I will start to monitor it closer in order to see if there's something extra. The great dilemma I will face now is the investment done in FTX software against pieces to cut. Otherwise, I will keep flying my GA until P3D brings the light. Best regards, Heron Domingues, Jr Intel Core I7 10700KF, 3.80GHz (5.10GHz Turbo), Gigabyte B460, RAM 32GB, Corsair 750W, GPU Palit RTX 3060, Windows 10 Pro 64., P3Dv5.4.
February 4, 201511 yr Tonight I will start to monitor it closer in order to see if there's something extra. If I haven't mentioned it already, you might try using the Process Monitor to see what is loading at startup and what is loading during your flight. See page 4 of the AVSIM CTD Guide on how to set it up so that only FSX and FSX addons are monitored. I discovered a lot when I went through this process to try to find what was causing a freeze almost at the same location in a flight. Turned out to be MyTrafficX and an AI aircraft needed for a flight could not be found and the sim froze at the same location. I found other interesting things too like autogen loading in the PNW even though I had FTX/Orbx disabled and I was flying in Illinois enroute to St Louis. Turns out the autogen was not disabled as it was suppose to be disabled. It's just more ways of investigating the "scene of the crime" (the CTD). Best regards, 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 5, 201511 yr Author I found other interesting things too like autogen loading in the PNW even though I had FTX/Orbx disabled and I was flying in Illinois enroute to St Louis. Turns out the autogen was not disabled as it was suppose to be disabled. It's just more ways of investigating the "scene of the crime" (the CTD). Jim, Really, a very interesting situation. I faced 2 distinct situations this week: the first, arriving at Aerosoft EDDK where clearly happened an OOM, with FSUIPC bells and a Windows message about FSX out of memory, even thought all other addon airports were off. The second, flying the 737NG from FlightBeam KDEN to LatinVFR KSNA, with all FTX scenery turned on (including KPSP) just after overflying KPSP, FSX simply froze without any notice, i.e., I had a frozen screen with a beautiful California sunset and a constant jet engine sound, and no Windows message boxes. This is no OOM nor CTD. The other thing I must do is turn off all of FTX artifacts and measure VAS. At the moment, I am very concerned with FTX regions. What could have triggered your autogen if it was disabled? Turning off autogen means slide its bar all to the left? Best regards, Heron Domingues, Jr Intel Core I7 10700KF, 3.80GHz (5.10GHz Turbo), Gigabyte B460, RAM 32GB, Corsair 750W, GPU Palit RTX 3060, Windows 10 Pro 64., P3Dv5.4.
February 5, 201511 yr What could have triggered your autogen if it was disabled? Turning off autogen means slide its bar all to the left? Orbx/FTX places their autogen files in the main Scenery/World/Scenery. I believe when they are disabled, they are suppose to be shown with an .XXX file extension. Then when they are enabled, they show the regular .bgl file extension. Somehow mine were not disabled. FSX simply froze without any notice, i.e., I had a frozen screen with a beautiful California sunset and a constant jet engine sound, and no Windows message boxes. This is no OOM nor CTD. This is the common AppHang or freeze. Here's what the AVSIM CTD Guide states (and thus all I know about this problem): Freezes During Flight – Freezes are most commonly caused by – • High application/display driver settings. Check. • High settings within commercial weather programs like REX, ASN, and OPUS. Check. Some raise settings to the highest texture settings (4096 HD) within weather programs and/or texture programs like REX. This coupled with high applications LOD_Radius and Texture_Max_Load settings may take up too many resources and application will freeze. • Complications with weather server updates. Application may try to update the weather and the weather server is down or cannot comply with a request. • Running out of Virtual Address Space (VAS) especially on one hour or longer flights (see VAS/OOM discussions). • Bad tweaks. BufferPools and or Affinity Mask are most often attributed to freezes. Rebuild the application configuration to see if this fixes the problem or disable the tweaks. • ENBSeries Module – DirectX hack for better visuals. • SweetFX Module – DirectX hack for better visuals. Best regards, 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 5, 201511 yr Just curious, how did you turn off the Orbx stuffs, turning them off in FTX Central will not remove the sceneries from being loaded. The way I do it is to use scenery config editor and uncheck the entries. Also do you use BufferPools, and what is that set at? BufferPools increases VAS usage so if you use a large number you will reduce the amount available. For the memory hungry 777 it may result in OOM with some sceneries. My GPU is fast enough so I use UsePools=0. Vu Pham i7-13700K 5.2 GHz OC, 64 GB RAM, RTX5090, SSD for Sim, SSD for system. MSFS2020, XP-12, DCS
February 5, 201511 yr Just curious, how did you turn off the Orbx stuffs, turning them off in FTX Central will not remove the sceneries from being loaded. The way I do it is to use scenery config editor and uncheck the entries. Also do you use BufferPools, and what is that set at? BufferPools increases VAS usage so if you use a large number you will reduce the amount available. For the memory hungry 777 it may result in OOM with some sceneries. My GPU is fast enough so I use UsePools=0. It sounds like you know what you are doing but you should only use the FTX/Orbx utility to disable Orbx scenery. Never enable/disable through the Scenery Config Editor. You will have major problems especially if you use the FTX utility again. FTX Central will no longer work if you mess it up. FTX/Orbx strongly recommends you use their utility to enable/disable the scenery and I am positive it works as when I go back to the default, I have no FTX/Orbx entries in the Scenery.cfg. Turn it on and all of them are showing in the Scenery.cfg. So, if turning the FTX scenery off in FTX Central no longer removes the sceneries from being loaded, then FTX Central is corrupted. When mine got corrupted (as I use to do exactly what you do by enabling/disabling through the scenery config editor), I simply reinstalled one of the FTX Scenery and made sure their were no entries in the scenery config editor when FTX Central was set to Default. Best regards, 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 5, 201511 yr Author When mine got corrupted (as I use to do exactly what you do by enabling/disabling through the scenery config editor), I simply reinstalled one of the FTX Scenery and made sure their were no entries in the scenery config editor when FTX Central was set to Default. That's something I didn't give a thought. Sometime ago, let me guess 2 months, CTDs were rare in my system. Thanks again Jedi Jim, we're always learning around here. Best regards, Heron Domingues, Jr Intel Core I7 10700KF, 3.80GHz (5.10GHz Turbo), Gigabyte B460, RAM 32GB, Corsair 750W, GPU Palit RTX 3060, Windows 10 Pro 64., P3Dv5.4.
February 6, 201511 yr It sounds like you know what you are doing but you should only use the FTX/Orbx utility to disable Orbx scenery. Never enable/disable through the Scenery Config Editor. You will have major problems especially if you use the FTX utility again. FTX Central will no longer work if you mess it up. FTX/Orbx strongly recommends you use their utility to enable/disable the scenery and I am positive it works as when I go back to the default, I have no FTX/Orbx entries in the Scenery.cfg. Turn it on and all of them are showing in the Scenery.cfg. So, if turning the FTX scenery off in FTX Central no longer removes the sceneries from being loaded, then FTX Central is corrupted. When mine got corrupted (as I use to do exactly what you do by enabling/disabling through the scenery config editor), I simply reinstalled one of the FTX Scenery and made sure their were no entries in the scenery config editor when FTX Central was set to Default. Best regards, Thanks Jim. I do re-enable all the entries before I use ORBX again, so no problem. I just do not trust ORBX, I guess. Vu Pham i7-13700K 5.2 GHz OC, 64 GB RAM, RTX5090, SSD for Sim, SSD for system. MSFS2020, XP-12, DCS
February 6, 201511 yr Before I startup FSX I always check the SceneryConfigEditor to see what is enabled and to make sure all of the scenery I need is enabled. Since their entries are always at the top of the config, it's easy to see whether they are enabled or disabled. This is another reason why I really like the SceneryConfigEditor. Best regards, 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 8, 201511 yr Author Hi, I did some changes in my system based on our talking in this post and, so far, things seems have stabilized. I could fly a 3 hour leg with the 777 from KMEM default to Flightbeam KPHX, arriving with more than 600 MB in VAS, no FSUIPC bells and all the FTX/ORBX stuff ON. Other addon airports OFF. Great framerates along all the path. I am trying now to make KPHX to KSEA to test the 777 behavior on FTX PNW in a 2.5 hours flight. After this flight, I will come back here with the settings I changed. Best regards, Heron Domingues, Jr Intel Core I7 10700KF, 3.80GHz (5.10GHz Turbo), Gigabyte B460, RAM 32GB, Corsair 750W, GPU Palit RTX 3060, Windows 10 Pro 64., P3Dv5.4.
Create an account or sign in to comment