sloppysmusic

How to ignore OOMs almost completely...and keep flying!

Recommended Posts

Tell me if you all know this already but you need not lose a flight/approach/landing because of a pesky OOM turning up like a...well you know what I mean.

The OOM is NOT an FSX crash. It's FSX telling you WOAH you reached your VAS limit boy we are not going to load ANY more scenery objects, sounds or whatever. You may as well shut the sim down by pressing this big button down in the middle of your screen.

Except you don't have to. In full screen you have no choice. But in windows mode or in my case full screen windowed mode ( I use the excellent Background Gaming app to do this) all you need to do to keep flying is to click on the main screen outside the OOM box and it disappears and you can keep on flying. Of course it does not actually disappear but just loses focus. Example, I just finished a flight into Gold Coast OrbX with the PMDG 747-400. On approach I got THREE OOM windows cascading on my screen. I ignored then and continued flying. Because at the point of the OOM hitting FSX had already loaded up the airport completely I landed (dealt with overheated brakes), taxied back to gate, and shut down the plane calmly and fully as usual then saved the flight. I switched to my outside view and panned round the aircraft enjoying the scenery. Now remember what I said about not being able to load any more scenery/objects? Well as I had not panned all round my plane in flight ONE of the views had a partial skeleton showing with the passenger seats visible. Big deal! The OOM had been 'defeated'.

Of course this is most useful on landing when the airport loads and the OOM hits. This is because like me you have probably already got all or most of the airport loaded so we are in good shape. If your VAS management is so poor that it runs out mid flight or even on taxi before take off we are not so lucky. We can still fly all the way to our destination but unless you happened to be flying at night already your whole flight will be a green blob below and a blue one above. You can still reach cruise then save it though, to return later.

I landed once at OrbX LOWI, a LARGE user of VAS in the FSW Learjet 35A. As I turned into the valley for the last 10 miles of approach i got several OOM windows in front of me. I ignored them as usual by clicking on the screen above them but because FSX had not yet loaded LOWI itself BEFORE the OOM the nearer I got to the landing the blurrier the textures got until I finally landed on a bunch of Microsoft Blue default textures. Bizarre indeed but at least I had completed the long flight without having to quit and reload (IF I had a reload that is ready to go). I took a screen shot of this which I sadly deleted as rather embarrassing but I can at least still fly after such VAS abuse!

OK, once again if this is common knowledge I apologize! I am sure this trick does NOT work in regular full screen. You MUST be using windowed or full windowed mode for it to work. I love full screen windowed mode because there are no menus to kill the immersion and I can easily move my mouse over to my second screen and look at charts and other usual stuff like ChasePlane and Little Nav Map.

Ignoring the OOM is literally just a click in the right place away(anywhere other than on the OOM warning window on your main sim screen).

Background Gaming, the utility I use has breathed new life into my massive FSX collection of scenery. I still use Scenery Config Editor to keep my VAS in control but if I don't quite get the numbers right I still get to finish every flight as normal, barring a few anomalies because the key point here is that FSX will load ZERO textures/sounds/objects after that OOM. So what you got loaded at the time is what you get to keep until the end of the flight or until you decide on a good place to save and continue.

Thanks to all at AVSIM for this massive depository of info and advice, I hope this advice helps others like me who love our FSX and don't want to start all over. 

 

  • Like 1
  • Upvote 1

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I get the warnings, I ignore them and at some point FSX just shuts down. I also fly in fullscreen windowed mode.

What magic sauce are you using, Russ?

Share this post


Link to post
Share on other sites

I'm not going to spend 1 single word arguing in defence of my chosen simulater here. It would be off topic and in the wrong forum. I chose this forum deliberately for a post that took me half an hour to write when I I could have had more fun flying said sim. I have known for a while there were people here who look down on others and their personal choices , but have not let it affect me. In fact I have posted recently in the other camps forum, the one that belongs to them (as supposed to a communal one we can all feel we belong to), and offered help with problems that don't require me to own their product. I have enjoyed AVSIM for years precisely because of the unilateral love for simulation flying and the community that has existed here. I find it utterly depressing that free speech can be stifled by simply starting an argument in a thread that you want rid of. A sad reality of the current polarized world that I and others seek shelter from in here. Want a thread gone? Post comments like I have read today making sure to offend enough to get a response then smile with satisfaction when the thread is closed and drops off the bottom of the list into oblivion. As long as my chosen sim is supported by AVSIM I shall remain a member and treat the choices of others with respect and comment always and only for the benefit of all not the few. 

  • Like 3
  • Upvote 3

Share this post


Link to post
Share on other sites
On 2/13/2019 at 4:23 AM, speedyTC said:

I get the warnings, I ignore them and at some point FSX just shuts down. I also fly in fullscreen windowed mode.

What magic sauce are you using, Russ?

I'm not sure how many warnings you can ignore Tony before windows takes over and shuts FSX down. Last night I flew all over OrbX new Zealand North Island using 4 airports in one FSX session. NZGS and NZWR (full add-ons) plus NZRO and NZWN (region addons ) with the FlySimWare LearJet 35A. Running at LOD 6.5 and very high scenery settings (Autogen set to 1 notch down from highest) I made it all the way to flying over NZWN for the course reversal before the first OOM warning came. As I had already loaded the scenery I ignored it and flew the approach and parked the plane with the beautiful scenery unaffected by the OOM at all. This was because I was only flying over scenery that FSX had already loaded. If I had diverted then it would have looked rubbish. I will make a video at some stage because with quick and careful scenery choice before flight using SCE and this full screen window tip OOMs do not stop me flying anymore, or landing. 

Share this post


Link to post
Share on other sites
On 2/13/2019 at 3:23 AM, speedyTC said:

I get the warnings, I ignore them and at some point FSX just shuts down. I also fly in fullscreen windowed mode.

What magic sauce are you using, Russ?

Although I have moved to P3D, I had the same experience as you. Sometimes I could continue with the approach, fingers crossed, hoping for the best, and the sim would not crash. Other times, not so lucky. What I ended up doing was using FSUIPC to monitor VAS and used it's AutoSave function if things didn't go my way. 😉

Randy

Share this post


Link to post
Share on other sites

Thanks for replies, guys.

In my case I use the Scenery Configurator and just load the airports I need for a given Point A to Point B flight. One caveat though. I usually fly with the FSL bus and I know that is a "heavy" add-on. My settings are fairly conservative (scenery-wise) as my aging machine is showing signs of kicking the bucket. I usually turn off the FSUIPC autosave function when flying the Bus as a reload of a saved flight has never gone well. Besides, short to medium haul are feasible for a retired old codger like me. When I use the T7, however, Autosave is turned on (but just a single one saving the situation every 10mins or so and overwriting the older one) and that works well.

P3Dv4 is in my future but as I want to do it clean and right that means building a new machine. Eventually. 🙄 So, for the time being, I am still enjoying what Old Faithful (FSX) can give me.

Cheers!

  • Upvote 1

Share this post


Link to post
Share on other sites

I too like to limit my flights from 1-2 hours (sometimes using 4x acceleration).  I have found the descent is the time to be watching the VAS and it sometimes gets very difficult when on the final approach with heavy rainstorms outside.

Share this post


Link to post
Share on other sites

With me the only thing I change for each flight is the scenery itself in Scenery Config Editor and the LOD in Steve's DX10 fixer. FSX with Dx9 and non-steam version I could not handle these days.

I have a simplistic formula to decide my pre flight LOD setting.

I start at 8.5 with an OrbX region with included airports using a non-vas heavy aircraft (in my case the FSW Lear) and lower it from there.

-1 for each mid size OrbX addon airport.

-1 for complex plane like A2A Accusim/PMDG

-2 for each major OrbX addon airport.

So for example KSAN (major) to KPSP (mid size) using PMDG 737 would be 8.5 -2 -1 -1 = 4.5 LOD

If I arrive with more than 500kb (.5mb) VAS left I feel I got the calc wrong and could have had a larger LOD. The LOD to me makes the difference to me whether I look out the window at the amazing scenery or just climb up high and dont care. I'd say 1/4 flights I actually get a single OM near the end and that to me is fine as long as I have the airport loaded up. It's a failure in my calcs if I see ONE Microsoft blue texture!

Of course, I'm the guy who has always been kind of nuts with pushing my system to the limits. Back in the day it was the PMDG MD-11 and JS4100, neither exactly VAS friendly, running on an old PC with no addons except some mesh and photo scenery( big VAS killer!).

I would be running at LOD 2.5 or 1.5 and all my flights would be at night for obvious reasons! VFR has been a recent thing for me. I could get up to 4.5 with the RealAir dukes but I felt so at home with night flights (a bad scenery view ruins the whole flight for me) that I would still only fly at nights. It's why my VOR/ADF nav is like second nature to me I could do it blindfolded...the knock on effect from those years is that even when I fly the PMDG jets now I still ONLY use VOR nav and the MCP to navigate.

OK I'm off topic now but where there's a will there's a way to get impressive flights out of FSX. That's the whole point.  

EDIT Some scenery from OrbX IMHO should be labeled as P3D ONLY as the VAS usage is ridiculously high and therefore a waste of good money and a source of frustration for us FSX users. 

ESSA is huge, LOWI also but better optimized than the former so usable. Orlando City Scene...well that's bordering on false advertising saying it's usable in FSX...

I can only use LOWI and ESSA AND get pretty scenery on approaches IF I take off and land from the same airport. Not exactly a bad option for a scenic trip anyway but otherwise you HAVE to save mid flight and change scenery!

58 minutes ago, Jim Young said:

it sometimes gets very difficult when on the final approach with heavy rainstorms outside.

As Jim says here, weather addons might look sweet but there's another VAS hit. IF weather forecast is 'interesting' I will always take another -1 off my VAS calculations above!

Edited by sloppysmusic

Share this post


Link to post
Share on other sites
42 minutes ago, sloppysmusic said:

As Jim says here, weather addons might look sweet but there's another VAS hit. IF weather forecast is 'interesting' I will always take another -1 off my VAS calculations above!

Yes, there was several times where I saw my VAS dwindling and shutdown the weather and disabled AI.  Rather do that than face a crash after a 2 hour flight!  

Share this post


Link to post
Share on other sites
8 minutes ago, Jim Young said:

Yes, there was several times where I saw my VAS dwindling and shutdown the weather and disabled AI.  Rather do that than face a crash after a 2 hour flight!  

Absolutely!

"Captain we low on fuel we need to ditch the excess baggage if we gonna make the airfield! OK buddy, throw the weather and the other planes out the sky. That should do it. We GOT to make that landing. The whole world depends on us!"

😄

Been there done that sir! At least FSX regains VAS if it does not have more to load after we leave an area of great VAStness. So we can still carry on. Anything but a quit and reload..that never feels right...!

  • Like 1

Share this post


Link to post
Share on other sites

To push the limits of my theory (tested and working!) tonight I broke my LOD rule and used 7.5 LOD for 2 OrbX airports. I ran out of VAS 10 miles out BEFORE the airport had loaded. Ignoring the OOM message as usual by clicking on the main window I landed and taxied to the ramp and then saved the flight. Obviously you would not want this to happen but these screens are proof you can still finish your flight even if the airport never loaded. Get the math right first though and you can land after the OOM (after airport has loaded) and visually everything still looks great. Full screen window mode thank you very much!!

Note: FSX wont let you take screen shots after VAS has run out (try it!) but I actually gained 200k after landing so it WAS possible to take them. FSX will RECLAIM VAS after an OOM but as I mentioned before will NOT let you load any more objects.

CecoJsO.jpg

 

MlA2Nj7.jpg

 

8GtiC9J.jpg

Edited by sloppysmusic

Share this post


Link to post
Share on other sites

Out of curiosity, what airfield were your screen shots taken at, Russell?

Edited by BF Bullpup

Share this post


Link to post
Share on other sites
2 hours ago, BF Bullpup said:

Out of curiosity, what airfield were your screen shots taken at, Russell?

The clue is in the tiny ATC text but for those without magnify glasses it's Orbx Canberra. YSCB plus Canberra Cityscape. You can see the cityscape loaded in the background before the OOM.  Loaded up the airport again right after and it's glorious. The OrbX Australia airports were generally there earlier ones so not so VAS optimized. I had to use LOD 6.5 to get to my next 2 airports. That Lear is ironically one of my fave VFR planes too. Great for scenery watching and fast as heck when I need to skip over some desert! 

  • Like 1

Share this post


Link to post
Share on other sites

Cheers Russell.

Russ or anyone else who has posted recently, can you please once again link to AVSim's OOM guide?  I didn't think to click on it before and now I want to use it to help another FSX user.  I found a couple of guides related to FSX off Jim Young's signature but I don't know if they are the OOM guide referenced in recent FSX OOM threads.  Thank you!

Share this post


Link to post
Share on other sites

Page 36, AVSIM CTD Guide shows a section on OOM's.  Also, if you have a PMDG aircraft, they posted information starting around page 21 of their Introductory Guide.

  • Like 1

Share this post


Link to post
Share on other sites
8 minutes ago, Jim Young said:

Page 36, AVSIM CTD Guide shows a section on OOM's.  Also, if you have a PMDG aircraft, they posted information starting around page 21 of their Introductory Guide.

Thank you Jim.  I just realized that I have Hyper-Threading turned on in my computer.  To my understanding it should be turned on if I do a lot of multi-tasking on my computer (I need 10+ applications open when I use FSX for various applications, third-party and otherwise).  According to that page 36 I would get significantly more VAS if I turned it off.  Around how much more VAS would be available as a result, if you know off the top of your head?

Share this post


Link to post
Share on other sites
41 minutes ago, BF Bullpup said:

Around how much more VAS would be available as a result, if you know off the top of your head?

It all depends on what is loaded.  Most of the entries in the AVSIM CTD Guide are based on information I got from the AVSIM Forums and other flight simulation websites.  Some have seen up to 22% increase in VAS with it off but it depends on what is loaded.  If you 5 or more photo sceneries being loaded, I doubt you would see any increase in VAS or performance.  So you are saying you cannot multi-task with HT off with today's CPU's.  The CPU's and the individual cores are very powerful and not like yesteryear. I turned it off and got better graphics (they were not blurry but sharp and clear; with it on, blurry textures).  Maybe it was because I have an i7 8086K where I can OC all cores (not many cpu's can do this).  Many, many members here at AVSIM have CPU's that do not support hyper-threading and they are having no problems whatsoever. As I have stated earlier, Intel intends to remove HT in future CPU's.  Rob Ainscough, a former member a AVSIM, recommend it be turned off and he was talking about P3DV3 and FSX (32-bit applications). 

One way for you to test how much VAS you saved in a duplicated flight with HT turned on and then off is to set up your FSUIPC utility (freeware or payware) to monitor VAS (explained on page 16, AVSIM CTD Guide).  You can then go to the modules folder and open up the FSUIPC log and see for yourself whether it is good or bad.  I would suspect the amount of VAS saved and the increase in FPS would be different for each person.

1 hour ago, BF Bullpup said:

I need 10+ applications open when I use FSX for various applications, third-party and otherwise

I always love these types of comments where one tries to throw a wrench into every thing. 😀  Not many members would see a situation like this and I'm positive there are situations where FSX just would not run properly with a lot of applications and services running in the background.  I remind you though that Windows does not provide only 4GB's of VAS for everything on your computer but it provides up to 4GB's of VAS for each application.  So, each of your 10+ applications should be using it's own VAS and should not be interfering with FSX VAS.  It could affect overall performance of your computer though and I would not recommend it.

  • Like 1

Share this post


Link to post
Share on other sites

Many thanks Jim.  I just counted manually and I use 13 different applications, most of them small, to support my FSX flying experience.  REX Sky Force, Active Sky Next, PF3, ProjectFly, and so on...!  Yep, I understand VAS applies to individual programs only, and I have 32 GB of RAM so I am not overly concerned.  I'll give turning off Hyper-Threading a try and see if my computer will be just fine with my usual multi-tasking since I now understand that turning Hyper-Threading off improves the FSX experience.

Share this post


Link to post
Share on other sites
1 hour ago, BF Bullpup said:

REX Sky Force, Active Sky Next, PF3, ProjectFly, and so on...!  Yep, I understand VAS applies to individual programs only, and I have 32 GB of RAM so I am not overly concerned

Just to make sure you understand, REX, AS, PF3, and others are addons to FSX.  They fall under the FSX 4GB VAS limitation.  VAS is not RAM and it has nothing to do with RAM or virtual memory like the Page File.  VAS is just space Microsoft gives each application to run on your computer system.

I'm really happy to hear you are going to try the HT off experience to see if it improves the visuals and performance (and VAS).  I hope so.  I do know I have it off in both FSX and P3D and it has dramatically working great for me.  I have posted this elsewhere but here is a flight from FlightBeam KIAD to FSDT Charlotte International over MSE Virginia and WashingtonX in the PMDG737.  Note my FPS and the amount of VAS left...

Spoiler

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 closed
Minimum 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 fps
G3D 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 ***********

 

 

Share this post


Link to post
Share on other sites

I also have HT OFF and although its impact on my VAS is not significant the multitasking IS much better with the external apps running in their dedicated cores. For instance, I just started using Radar Contact 4. The moment it loads up in FSX my fps drops from 35/50 internal to 3/25 internal and flight is too jerky to be possible. But assigning RC processor affinity to Core 2 (FSX runs core 1 I think as it is my fastest core) the problem went away and I could use it again.

Whether or not I could be bothered to do this every time I run RC remains to be seen depending on how much I like it, Either way bye bye HT you've outlived your usefulness with modern multi core CPUs.

  • Like 1

Share this post


Link to post
Share on other sites

I am going to include most of my fsx.cg  here as my post makes more sense when you can see what I am using. Although whatever our settings you cans till ignore the OOM completely by clicking on the background in a full screen window.

Please do NOT copy and paste this as over your cfg file, only the subsections here as my addons are different.

IMPORTANT!!!!

Notice my LOD at the moment is a huge 8.5. This works fine with add on aircraft but NO addon airports other then OrbX FTX Global airports and Vector/Global scenery. I suggest starting with LOD 4.5 and increasing IF you use Texture Max Load 1024 (this makes a HUGE difference!)

Also my affinity mask will only work with an 8 core CPU without Hyperthreading. This is very important!

Steves DX10 Control softwre makes it easy to change the affinity mask to fit your CPUs, as you actually select the cores you wish FSX to use. Do not assign less cores than all of them unless you have other utilities such as weather/ATC you wish to isolate in their own cores. 

DO experiment changing one setting at a time if possible and make sure you back up your fsx.cfg before making any changes and also AFTER something works well so you can always go back to a better config.

Good luck and have fun. Max out your FSX!

[GRAPHICS]
SHADER_CACHE_PRIMED_10=1693751040
SHADER_CACHE_PRIMED=1693751040
D3D10=1
TEXTURE_MAX_LOAD=1024
NUM_LIGHTS=8
AIRCRAFT_SHADOWS=0
AIRCRAFT_REFLECTIONS=1
COCKPIT_HIGH_LOD=1
LANDING_LIGHTS=1
AC_SELF_SHADOW=1
EFFECTS_QUALITY=2
GROUND_SHADOWS=0
TEXTURE_QUALITY=3
IMAGE_QUALITY=0
See_Self=1
Text_Scroll=0
MultiSamplesPerPixel=4
MultiSampleQuality=8
HIGHMEMFIX=0
ForceWindowedVsync=1

[SOUND]
AmbientUIMusicVolume=-6.000000
PrimaryDevice={9DD33330-28FF-4AFD-8996-C665F256BE4A}
VoiceDevice={9DD33330-28FF-4AFD-8996-C665F256BE4A}
SOUND=1
SOUND_QUALITY=2
SOUND_LOD=1
UISound=1
AmbientUI=0
SOUND_FADER1=0.660000
SOUND_FADER2=1.000000
SOUND_FADER3=0.470000
SOUND_FADER4=1.000000
AmbientUIMusic=FSX01


[Display]
ChangeTime=1.000000
TransitionTime=1.000000
ActiveWindowTitleTextColor=255,255,255
ActiveWindowTitleBackGroundColor=0,28,140,64
NonActiveWindowTitleTextColor=255,255,255
NonActiveWindowTitleBackGroundColor=24,33,87,64
InfoUpperRightTextColor=255,0,0
InfoUpperRightBackGroundColor=0,0,0,0
InfoLowerLeftTextColor=255,255,255
InfoLowerLeftBackGroundColor=255,0,0,128
InfoLowerRightTextColor=255,255,255
InfoLowerRightBackGroundColor=255,0,0,128
InfoBrakesEnable=False
InfoParkingBrakesEnable=False
InfoPauseEnable=True
InfoSlewEnable=True
InfoStallEnable=True
InfoOverspeedEnable=False
BLOOM_EFFECTS=0
SKINNED_ANIMATIONS=1
TEXTURE_BANDWIDTH_MULT=40
UPPER_FRAMERATE_LIMIT=0
WideViewAspect=True
ForceVCShadowMap=1
TextureMaxLoad=12

[Main]
DisablePreload=1
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
SimObjectPaths.6=C:\Program Files (x86)\12bPilot\SODE\data\SimObjects
SimObjectPaths.7=C:\ProgramData\12bPilot\SODE\SimObjects
ProcSpeed=9721
PerfBucket=7
HideMenuNormal=0
HideMenuFullscreen=1
Maximized=2
Location=0,0,3840,2160,\\.\DISPLAY1

[PANELS]
IMAGE_QUALITY=1
DEFAULT_VIEW=0
QUICKTIPS=1
PANEL_OPACITY=100
PANEL_MASKING=1
PANEL_STRETCHING=1
UNITS_OF_MEASURE=0

[Weather]
WindshieldPrecipitationEffects=1
MinGustTime=10
MaxGustTime=500
MinGustRampSpeed=1
MaxGustRampSpeed=200
MinVarTime=5
MaxVarTime=50
MinVarRampSpeed=10
MaxVarRampSpeed=75
TurbulenceScale=1.000000
WeatherServerAddress=fs2k.zone.com
WeatherServerPort=80
WeatherGraphDataInDialog=0
AdjustForMagVarInDialog=1
DynamicWeather=0
DownloadWindsAloft=0
DisableTurbulence=0
CLOUD_DRAW_DISTANCE=3
DETAILED_CLOUDS=1
CLOUD_COVERAGE_DENSITY=8
THERMAL_VISUALS=0

[DynamicHeadMovement]
LonAccelOnHeadLon=0
LonAccelOnHeadPitch=0
RollAccelOnHeadLat=0
YawAccelOnHeadLat=-0
RollAccelOnHeadRoll=0
MaxHeadAngle=0
MaxHeadOffset=0
HeadMoveTimeConstant=0
 

[SCENERY]
LENSFLARE=0
DAWN_DUSK_SMOOTHING=1
IMAGE_COMPLEXITY=5
ShowMissingTextureAlert=0
SmallPartRejectRadius=0
MAX_ASYNC_BATCHING_JOBS=2

[TrafficManager]
AirlineDensity=50
GADensity=50
FreewayDensity=6
ShipsAndFerriesDensity=0
LeisureBoatsDensity=0
IFROnly=0
AIRPORT_SCENERY_DENSITY=0

[TERRAIN]
LOD_RADIUS=8.500000
MESH_COMPLEXITY=100
MESH_RESOLUTION=25
TEXTURE_RESOLUTION=29
AUTOGEN_DENSITY=4
DETAIL_TEXTURE=1
WATER_EFFECTS=5

[STARTUP]
DEMO=0
SHOW_OPENING_SCREEN=1
STARTUP_DEMO=
LoadWindow=1
 

[JOBSCHEDULER]
AffinityMask=252

[BUFFERPOOLS]
UsePools=1
PoolSize=2097152
RejectThreshold=131072

[DISPLAY.Device.NVIDIA GeForce GTX 1080.0.0]
Mode=3840x2160x32
TriLinear=0
Anisotropic=1
AntiAlias=1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now