Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

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

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

Noel

Members
  • Joined

  • Last visited

  1. I'm seeing a fair amount of GA aircraft parked and have seen some taxiing as well...in my three flights using default RT traffic.
  2. It's true but to be honest though I haven't used SI ATC I find BATC's audio is too good to pass up, and that is why I'm doing this it's great to not have all of the BATC<>controller chatter (I use LiveATC instead) which can be annoying but worse still it uses Premium characters, and not having to wait for comms to settle down so the controller responds to my request, and odd has heck BATC's ground traffic management has actually been WORSE than was FSLTLs and so far, default RealTime traffic has been great. I just have to pay attention to moving ground traffic to avoid conflict but it's easy to do. On my maiden flight from SKRG to MROC was impressed by the parked traffic as well, and same here at the small rural airport, KPGA. Plenty of GA aircraft and a few regional jets or turboprops.
  3. This belonged in the recent thread that was locked: try default RealTime traffic. I'm first trying this now at SKRG and I couldn't tell the difference between it and FSLTL. I do use BATC but sometimes avoid using its injector and this seems to work fine as a sub for FSLTL.
  4. The simple adjustment is NVCP's Digital Vibrance, where you can easily dial back color saturation to the point of black and white if you so desire, and everything in between. I'm set at 44 (default is 50%). And of course, minor adjustments in contrast, gamma, brightness. I do use HDR as well.
  5. This is a statement I can totally related to--it's really become photorealistic in so many ways.
  6. Howard, your issues are all software setup as what you describe is not 2024 it's absolutely stunning here, textures, weather and all. My default TBH is to panic after spending all of that effort moving only to experience what you describe, but that is a mistake because, once again, you have the hardware. You also are new to Win 11? Do you have all of the usual settings configured for HAGS? Chipset drivers all current, audio drivers all current, etc? To panic now would be a sad mistake because once again you have everything required to make this sim sing which is why you see well more users now in 2024 than in 2020 (Steam survey). Given you description I would start with this if you haven't already: 1. Delete all Nvidia software from Add/Rem programs, but retain NV Control Panel 2. Go to System > Recovery > Advanced Startup > Restart Now, then select Safe Mode w/o network. 3. Now go to Search, Disk Cleanup, and clear the DX shader cache option. 3. Next, run DDU and do the full clean up of the GPU software, except NVCP 4. Now install the current NV driver, however DO NOT install either the NV App, nor HD Audio Driver. Reboot, and see how things go from there.
  7. Yes you would hope but it's not guaranteed at all, as you should well know if you spend any time here.
  8. As you may recall I first noticed a significant improvement in smoothness, not freedom from stuttering per se, but smoothness, when tried using RTSS w/ front edge sync passive waiting I think it's called in RTSS setup. I was not using CFX at that point in time and only later after learning about CFX that I noticed that subjective sense of smoothness at some level does correlate w/ low FTV captures. At some level it's presumably the difference between this: __ __ __ __ __ __ __ __ __ __ and this: __ _ __ __ __ _ __ __ __ _ __ Of course real stuttering from whatever cause is going to adversely impact FTV too, so it's perhaps a fair way to assess if you are setup well for the rate you're trying to maintain.
  9. That is bizarre for sure. The good news is you *should* be able to fix it (i.e., you have the hardware) so it's in the software domain, but finding out how is another story good luck! I'm not on a Beta either so that could a big reason. FWIW, I do not install the NV HD audio driver, and found the NV App to be troublesome for the frame time variance, but that could be an artifact of how CapFrameX captures video. Your recurrent regularly spaced pauses point to some polling/saving feature. In fact THAT was what prompted me to dig deeper into what impacted animation quality as I was getting recurrent regularly spaced pauses as well, and it turned out to be the windows background was set to change periodically, like every minute? (if I recall correctly, in Win 10) and once I saw that and disabled the pauses ceased. That led me to learn about RTSS to control rate which is when I discovered the best path to lowet frame time variance and I've been stuck there ever since. A very nice benefit to RTSS is one can change the rate lock during flight so comes in handy if I need to go from 60FPS-fg to 90FPS-fg. I try to stick w/ multiples of 30FPS which Simconnect is confined to I believe, hence helps with GSX Pro.
  10. Yep same old same old and it still holds up for me. Refresh is at 120 or 144 and it doesn't matter really except the lower the refresh the more visible can be rate-related visual aberrations w/ FG. Vsync off. Gsync on. For a long time I stuck w/ native rendering but after a long hiatus from I tried FG many months ago now and was delighted to discover the 2nd screen judder was gone which was a fair part of the problems I had w/ FG as I'm always going back and forth between screens. And, now that performance is as good as it is can bump up to 90FPS-fg when conditions demand due to rate-related visual aberrations. TLOD is always 100-150 on the ground, all else Ultra, and Render Scaling is at 130 along with the NVCP sharpening feature can't really do any better image quality wise. There are times when this doesn't happen of course and I like many chalk it up to server/net issues. It does help to refresh the GPU install periodically which I do maybe every 2-3 months or so as it seems things slowly get garbled a little over time where I will see some stutters return, but it's rarely much unless as I say something outside the box is in play. I just did this refresh a few days ago, same NV driver, a recent but not current one.
  11. Pardon me but I remain so impressed by 2024 and had to share this. Not a hint of a stutter anywhere for this 2h+ flight from departure involving taxi/TO in the Fenix 320 at LIPZ to EGLL involving landing and taxi to the gate w/ ample FSLTL traffic, just pure perfection! As I've always maintained when you have flawless frame time variance this correlates very well with subjective perception of super smooth animation. This was from the landing at EGLL. Yes, it's a modest 60FPS-fg but no significant rate-related visual aberration that can happen in certain types of lighting and textures in which case I will bump the native rate up to 45/90FPS-fg.
  12. Why not create a subscription fee for FSLTL users who wish to stay with FSLTL, at least to cover FT24's cost, that is if FBW would be willing to create the interface for that? It's been great to use for years now and I would pay a reasonable sub fee to continue on.
  13. Mainly because of the comments by some! I might look into it if Plan A fails. Or perhaps FSLTL will find a work around. I will even go back and have a look at default ATC for traffic and run BATC alongside like I do now w/ FSLTL. Okay, what software do I need from AIG, exactly?
  14. I think I'll just move back to BATC's injection w/ FSLTL models, and put BATC's parked traffic to zero and let FSLTL populate static aircraft. Thanks for your reply on this...
  15. Sounds like a PIA compared to FSLTL's automated everything.

Account

Navigation

Search

Search

Configure browser push notifications

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