neil0311

I get that hardware upgrades aren’t inexpensive. I just recently upgraded after 8 years with the same system. It’s why when I do upgrade, I go all out for top of the line to try and “future proof” the upgrade. I read threads like this and am reminded of threads 20 years ago, when people swore they would never upgrade from FS8 to FS9, and then later from FS9 to FSX. Likewise with the people who swore they would never, ever, never, ever upgrade to Windows 7 from Windows XP, and people prior to that who swore they would never install Windows XP SP1. To each their own. Everyone can do what makes them happy with their own simming experience. It’s just humorous to me that no matter what point in time you look at Avsim, there’s always some group that’s declaring they’re not going to upgrade. 😀🤷‍♂️

I had the Sublogic simulator add ons from the late 80s. I wish I had saved them.

I just came back to MSFS after a few years away. I flew in MSFS2020 for a couple of years and then took a break. I’m a real world pilot and have been using MSFS since the Artwick days in the 1980s. What’s funny is I can go away and come back years later and the threads on Avsim are almost the same. FS2000, FS8, FS9, FSX, P3D, and things that aren’t working and patches that never got released. I do think that 2020 and 2024 are the best versions ever, and the support from Asobo has been light years better than in house versions like FS9 and FSX. I just bought a new system for 2024. My previous system was state of the art in 2019, and I used it for P3D and then 2020 when that released. So I will be enjoying 2024. I will keep in mind that this is in fact a computer game that’s mass marketed to people who have never flown an aircraft and will never fly a real aircraft. And they don’t care about the minutia. They just want to fly over their house, and some want to pretend to be an airline captain and pretend to fly airliners. That’s the reality. It’s a game. One that we love. One that I’ve been having fun with since before my grown adult children in their 30s were born. So yes…I’m still having a ball with the sim. 😁

It’s an Acer XB321HK.

My current monitor has the chip. It’s the full Gsync, not “compatible” or Freesync.

Yes

No, 32” is not a limit for me. It’s what I have now, and 8 years ago was the sweet spot for cost/performance. If I could add HDR to what I have, I’d probably be content. I’m just trying to get clarity on whether a wide or curved monitor is a good choice for FS or not, and whether Track IR is obsolete.

New high end system with Ryzen 7 9850X3D CPU and Nvidia RTX5080 GPU. Old monitor is 8 years old and was high end in 2018, Acer 16:9 32” 4K LED. I use TrackIR and am completely confused whether a wide and curved monitor would be best or maybe a larger 16:9 4K screen with HDR. Any suggestions? I want to improve the experience with FS2024.

Nice. I took my primary training and got my certificate flying out of KFIT when I lived in New England. I really, really miss it.

MyTraffic 6 was $20 and the install was simple and took about 15 min. Much simpler for me and no issues. I fly GA aircraft, so I just want traffic that is plausible and varied. I don't care about various repaints, schedules, gate assignment, etc. MyTraffic can be installed with FSX boxed, FSX-SE, or P3D, all from the same install. Well worth the $20.

After scanning my system, it looks like I have hundreds of duplicate AFCAD files, resulting from a mix of Ultimate Terrain (most current version of every region installed), MyTraffic 6, and various add on airports from FSDT, Imaginesim, FlyTampa, and others. While I have these files layered correctly in the scenery.cfg, with MyTraffic at the lowest priority, then Ultimate Terrain, then add on airports, does having these files cause a conflict? I've read that even with proper priority, it's necessary to disable all but the file in use at the highest priority. Is that the case?

They overclock the CPU, run diagnostics and stress tests, and pre-load the application. They don't have any "secret sauce" or do much (if anything) that any high end gaming PC builder doesn't also do.

It's interesting to read the various ways people flightsim, and what can be a showstopper for some isn't even important to others. For me, I'm a real world GA pilot and I've been simming for about 30 years, since the days of DOS and SubLogic. I've also been using MyTraffic since the first versions with FS2002 and FS9. I want airports that aren't empty and skies with traffic that ATC can warn me about and that I can hear as chatter. I could not care less about what airline or livery is at a gate or what time a flight leaves or arrives. I just want plausible traffic in the correct geographies as background, just like in real life I have no idea what flight numbers or schedules are for air traffic near me.

N60JBravo...you are going way over my head. I am dev challenged. What I'm experiencing is when I am selecting LGA from the free flight menu, I go to New York and La Guardia is in the list and when I select it with the default "active runway" it shows Edo. This is with all 3rd party LGA add ons disabled (or AFAIK disabled).

Hmmm...after posting on their forum, I found out that he adds bgls in scenery\world\scenery that are labeled with the airport identifier with ALT. Rename or remove those and your runway issues may be fixed. I'm not educated enough on where the info for the location picker comes from, but something is messed up. It's unfortunate but the scenery is unusable to me with single digit fps, despite a cutting edge overclocked system. I also get OOM errors in about 30 sec, which do not happen with the Imaginesim KLGA and FSDT KJFK both enabled. I should have done the trial first, but saw the package on sale and read good reviews.

Reviving this old thread.... I purchased Drzewiecki's NY Airports X which includes KLGA - La Guardia. As far as I know, everything was working fine previous to the installation. If I disable the add on and go back to default, when I select "active runway" at La Guardia, what comes up is "Edo" and KLGA is not properly rendered in the sim. If I choose a specific runway or gate, then all is well. Anyone know what's up here? Did the add on package step on or remove some default bgl or info?

I've only been a casual user at Avsim, but have been coming here for about 13 years. Thank you for providing a place like this for the flight sim community. All my best wishes Tom for you and your family during this very personal time.

It doesn't look like either one shows up in FSX. Does anyone know of a good freeware or payware add on? I checked the Avsim library and nothing appears to be available there.

I bought the Steam Edition as many have done to get the sale price and as a backup. Can anyone comment on the Windows 8.1 (dare I mention Windows 10?) compatibility? Is the FSXSE more fully Win 8.1 compatible?

Thanks for both suggestions. I can check tonight, but do you know if that will work with a non-licensed copy of FSUIPC?

I have a pretty robust system (6 core i7-3930K) with 8GB RAM and a GTX580 1.5GB VRAM. I use mainly photoscenery without autogen in the US and fly small GA aircraft such as the A2A Skyhawk and Cherokee. Up until now I have really never had an OOM crash, except in NYC when I had enabled HD textures. I have since reduced my max texture to 1024. Yesterday I started to get crashes with the FSUIPC VAS alarm (ding, ding, ding) going off, but FSX.EXE was using around 1.9GB according to Task Manager. Is there a way to log VAS and specifically the process using it? Does the moment of task swapping out of full screen to a window cause VAS to be reduced by close to 2GB?

It's very nice, but has nothing to do with flying an aircraft. That was my point. I guess it's just a different outlook on my part.

Very nice, but what's the point? It's called FLIGHT Simulator, not airport terminal interior simulator.

FSX is a 32 bit application, so it's limited to 4GB of virtual address space. When you add complex aircraft, mesh, detailed scenery with large HD textures, etc., with tweaks in the fsx.cfg that increase these impacts, when you get close to the ground on approach, these impacts cause the app to run out of VAS.