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.

driotinto

Members
  • Joined

  • Last visited

  1. Hi Daniel, This is the only thread I find on the entire internet describing the same problem I am having. The behaviour of the issue I am having is exactly the same as you are, and I find the same conclusions that you do. The issue is not related to FSX.cfg config, nor to hardware. I have a high end computer (4770K, GTX760Ti - runs Arma 3 all maxxed out without even sweating) and I am experiencing the same issues as you in NY. I tried three different scenery sets and all of them show the same behaviour, including the 'all default configuration' (default scenery + default aircraft). This doesn't happen in any other airport (that I have noticed so far), even in the most demanding sceneries available in the market, used with the most demanding aircraft on the market. Only thing that actually fixes it is bringing scenery complexity to 'Sparse' or 'Very Sparse', which basically causes us to see no buildings whatsoever. More over, changing from DX10 to DX9 doesn't change anything. Rebuilding FSX.cfg doesn't do anything at all either, nor does any FSX tweaking configuration. I also tried pretty much every possible configuration of available freeware scenery and FS Display adjustments. I'm convinced that there is some issue with KJFK default scenery in conjunction with something else. If one flies from KTEB to KEWR, even seeing Manhattan's buildings but not approaching them so much, thus keeping far from KJFK, the simulator runs normally. However, approaching KJFK or KLGA makes the stutter happen immediately. We're talking about a five to ten seconds total stop of FS every 15 to 20 seconds of game play. FS X has specific scenery library entry for some default cities scenery (Rio de Janeiro, Berlin, Oshkosh, etc.), but doesn't have one for New York, which would make it much easier to fix, I guess. It's a no go for flying in New York. People keep saying this is the same for every big city, but that's also not true, in my machine Chicago and London, for example, see a decrease in FPS but no full FS stutter as in New York. Also the situation in NY does not compare to what happens in Seattle (another example). Heavy sceneries induce FPS to go lower, which is OK, understandable, expected and acceptable. But it is totally impossible to fly in JFK for example, if FS locks for five seconds every fifteen seconds. And when I say 'locks' it is total lock. Hopefully anyone also having this can share information so we can find out what to do. I recently migrated from FS9 to FSX and it would be my first time flying in NY in the new sim, as I fly mostly in Europe, but it won't be happening any time soon unless this gets fixed. It would be good to know if anyone that actually reinstalled the whole FSX to fix this problem had success or not, because otherwise is not worthy do it. Thanks an all the best, Daniel

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.