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.

TacomaSailor

Members
  • Joined

  • Last visited

  1. I think I remember several updates ago that I could ask MarketPlace (in My Library ?) to show me all items with a state of "update". I have a lot of marketplace stuff and none of it has been updated for many months. All I want to do is ensure all my marketplace stuff is kept current. Am I mis-remembering or mis-understanding?
  2. Sim is at Latest Beta but this problem has been inconsistently present for over a year Navigraph up to date, GTN is up to date, and all other nav stuff seems to be up to date. flying at 8000' Nearest VOR shows JLI OCN TRM MZB PGY. I tune JLI (113.75) in GTN750Xi - in some planes the JLI letters appear on the screen next to the frequency in others, during the same sim session, the JLI does not appear. In both cases the other instruments (HSI, RMI, LOC, DME) do NOT "see" or respond to the JLI signal. JLI was 10 miles distant. I then tuned OCN and TRM (both within 25 miles) and again the instruments do not sense a signal. I then tune MZB at 30 miles and PGY at 35 miles and all the instruments react properly. During other sim sessions everything works perfectly and all VORs are sensed. The same inconsistency occurs with WayPoints. I try to do a Direct to Julian and the GPS finds a "JLI" waypoint but it is thousands of miles distant and no report of "Duplicate" occurs. I use navigraph to go to the Lat/Lon shown and there is no JLI at that location. Some sessions I can only go direct to Chinese waypoints and other times I can do Chinese and Russian waypoints but not any Western Hemisphere waypoints. Again, this is independent of airplane or GPS/Nav instrument. During many sim sessions the waypoints work perfectly. Those problems occur in many different ASOBO, MS, and add-on planes. It is also inconsistent with which VORs or Waypoints are a problem. I have seen the problem in dozens of sessions anywhere from Canada to Mexico west of the Great Plains. Both problems also occur when I am building a flight plan in the sim on the GPS. If I then download the identical flight plan from Simbrief or other planning software - the VORs and Waypoints are found and used correctly during the flight. Do I have a corrupted database somewhere. The problem has survived to major release updates and all the recent updates. Where do I start looking? The problems are occurring more and more frequently.
  3. Overall - this update has improved many aspects of my flightsim experience. I have experienced several problems, none of which make me want to drop out of the beta but all point to a need for some problem solving: One CTD at the 2-hour point in a long distance flight. One transition to a totally black screen while saving changes to settings. Alt-F4 killed the process which was not responding. One frozen screen for 30-seconds and then when the sim starting working again my plane, which had just landed, was a mile from the TDZ and not even on the airport grounds. After an hour flying at FL420 in the Lear 35A the sim performance went from a steady 30 FPS locked in the sim with FG 2x, to 12 FPS in the sim. The frame time went from a steady 25ms to a steady 82 ms. This was at FL420 over the south Nevada mountains. I was running System Informer and nothing in the GPU and CPU and Memory measurements changed. No new processes were noted. The CPU was at 64% idle before and after the change. I unlocked the FPS in Settings and the FPS jumped up to 60 and stayed there. I noted no changes after the unlocking other than an increase in frame rate and decrease in frame time. GPU load and memory usage did not change. FPS stays as I wish while starting cold and dark until the instant the plane starts to move. The FPS then drops to 2 to 4 and stays that way until the plane is at 100-feet AGL when FPS suddenly jumps back up to the desired levels. This only happens with 3-party airports such as KSEE or KMYF.
  4. I touchdown on the main gear in the Baron Pro at 83-knots, with a VS of -193 ft/min and the landing analyzer says 1.0G with no yaw or roll. Why does the plane shake so hard and the a wing drop so far as to almost touch the runway? The landing is stable and on the centerline but the landing jolt knocks the fillings in my teeth loose. I am using a Moza AY10 yoke and FF-Bridge with a profile for the Baron. The same sensation occurs in the C-172 and the P-38. Landings seem to be very smooth but the yoke and visual presentation shows a huge impact. I've not flown GA in real life - are landings impactful?
  5. I understand how to set an attitude and airspeed and then trim out stick inputs so the stick stays neutral in both pitch and roll. I can make that happen... BUT within 10-seconds the plane is changing it's pitch and roll. And, the change becomes exponentially greater. Sometimes it is positive and sometimes negative. Aileron trim is incredibly sensitive - I hover the cursor over the roll trim and it shows 0 - if I click it once it shows 0.1 and if I leave it there the plane completes an aileron roll in about 30-seconds. The pitch trim is not as sensitive but the following is way to common: Straight and level with -3% elevator trim - 540 knots IAS at FL250. I change the pitch trim to -2.5% and within 20 seconds I see a climb of 4000 fpm. The same happens going down ward. I am using a Bravo trim wheel for the pitch and have it set so one-button click is 0.2% - or it takes five clicks to change the trim by 1%. I have spent a dozen hours trying to work this out - with no luck. I am quite proficient with the Lear 35, the L39, the BAE Hawk, and the A-10 - but can't keep the T-38A stable. What am I doing wrong?
  6. I flew 75-minutes in VR (HP Reverb G2) at very low level up to 10,000 feet and did three landings and takeoffs from VBCorp airports in San Diego County. Using AutoFPS with a 30 FPS target I seldom saw less than 45 FPS and TOD > 200. I had high VR settings with ULTRA clouds. It was all just as I wanted. I was running Navigraph on a 2nd monitor and using it consistently. The VRAM usage stayed at a consistent 10.9 GB with an additional 1.1GB shared in RAM. GPU utilization seldom exceeded 75% RTX 4070S 12GB Landed for a fourth time at KCRQ ILS28, taxied to the GA ramp and parked. This was my 2nd trip into KCRQ this session. Sitting on the ramp outside the BlkSq Baron Pro I could spin in a circle while maintaining 40 FPS. I moved the mouse pointer to the 2nd monitor and clicked on the Navigraph KCRQ name to bring up an airport info chart. The in plane GTN 750 did show the chart but I wanted to see a bigger image. When I clicked on the chart in the 2nd monitor - VRAM usage jumped up to 13.5GB with 5.5GB shared in RAM and GPU usage settled at a steady 99%. Frame rate dropped below 2/second. I closed Navigraph and returned to the in cockpit view. The FPS stayed at 1 or 2 and VRAM stayed way over allocated. When I "ended flight" the VRAM usage stayed over committed and the GPU stayed at 99%. Restarting the flight from the Main Menu resulted in the Baron sitting on the KCRQ GA ramp with VRAM still over committed and GPU at 99% with FPS<4. This problem has been occurring randomly for the last week. Once VRAM is overcommitted the only way I can free it is to shut the sim session and then restart it. Will VRAM usage ever be stabilized?
  7. I am very long time flight simulator addict and, like others here, own a vast library of ORBX products. I guess I am naive, or maybe just word not allowed, about piracy of individual addons to streamed games. How much of that kind of thing occurs. How many sales of ATL or any other Orbx product are lost to people buying "prirated" or being "gifted" addons? What is the scale of the problem?
  8. Benjamin - thanks for reminding me. You were correct. I used to have a little batch file with a desktop icon for resetting the host file. I'll have to find it and put it back on the desktop.
  9. FS2024 (1.7.27.0) was running perfectly in the latest Beta. Flow Pro was working as expected. I decided I would reinstall ChasePlane (experimental). Chase Plane had been working well several months ago but I uninstalled it so I could work on native controller profiles. Before I installed Chase Plane I used the MFS Cleaner Fixer app to clear all the shader caches and my rolling cache. I then installed Chase Plane and started FS2024. Loaded at normal speed to 87% (about 90 seconds) and then stalled. During the next five-minutes loading got to 96% but never progressed from there. I verified there was no rolling cache, I deleted all the steamed packages, installed the latest nVidia driver, rebooted the system.' Started FS2024 (1.7.27.0) and it stalled at 89% and then never got past 97%. Same result with FS2020 (1.39.12.0) The programs seem to be stuck trying to find Default_Global_XEN_Supperresolution and Default_Global_XEN_TrueHDR in the registry. They just keeping trying to read the key and not finding it. Apparently I deleted something somewhere but have no idea how to fix it. Supperresolution seems to be an AMD thing. I have an AMD 9800X3D but neither monitor is connected to it. TrueHDR seems to be a downloaded thing to give more control of the HDR process. I turned all HDR references off but the sims still try to load it. What to do?
  10. Sitting on ramp cold and dark. I had just updated a control profile and hit save & back - got the screen I expected but on the entire left side was a mystery box with all kinds of performance and usage measures. What app or process is producing the mystery box ? How do I kill it? I could move the cursor but clicking or scrolling with mouse did nothing. ALT + F4 did not kill anything. I had to use task manager to kill FS2024. Win 11 / Beta 2024
  11. It has happened to me twice but not in the last couple weeks.
  12. win 11 25H2 Sim 1.6.34.0 I am having very poor performance at an airport (any airport) which in the prior sim session (same day) I had excellent performance. For example empty Community folder KBFI (Boeing Field, Seattle) with Asobo Baron G58 cold and dark on a GA medium ramp. Sim starts at 60 FPS (FG and sim locked at 30). If I stay out of cockpit and pan around I see a steady 60FPS. Enter cockpit, turn on systems, start engine, CTRL+Z and pan - the frame rate drops to 1 or 2 and sometimes freezes for 15-seconds. Return to cockpit and frame rate slowly climbs to 60. Move view outside again and poof! back to one or NO FPS. If I let the sim sit for several minutes the frame rate climbs to 60 and stays there. But, as soon as I try to start taxing - FR goes to 1 again. Changing sim settings to LOW - no increase in frame rate. The VRAM usage stays below 95% (~11 GB) and the CPU usage, for each processor, never exceeds 30%. When the frame rates is less than three I find every thread in the sim is in a wait except for Main which is using about 1% of the CPU. Stop sim and restart it, with the exact same scenario as above - FPS never deviates from 60. This happens at many airports and makes SU4 less than enjoyable or even useable. Did not have this problem in the last couple SU 4 Beta updates
  13. On Dec 12 I received an email reply from AeroDynamics support that said: "Currently, the manual is being created, but not complete. " Where did you find a bundled manual?
  14. I am very disappointed in the reliability of SU4! I've not had a single problem and now must cope with flying airplanes rather than dealing with computer issues. I am much better and happier with computer problems than airplane stuff. OH - Woe is me.
  15. I can't remember in detail what I did. I tried several of the ZenDesk suggestions and they fixed the problem for a day or so then it would reappear, eventually changing from 1047 to 2047. I know I tried a complete Steam deletion of FS2024 and reinstall. That fixed the problem for a week or so but the next Beta update brought the problem back. Eventually I deleted anything to do with Clouds, Saves, Caches, Indexes in various orders. That helped for a while but then problem reappeared. I reverted back to plain vanilla SU3 after deleting everything. I think that solved the problem am not sure. All I really know is the 2047 error occured after reinstalling SU3. I got word not allowed off and quit the sim, turned off the PC and went off to saulk. When I next started FS 2024 SU3 - no error messages and none since, about three weeks I think.

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.