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.

cjk28

Members
  • Joined

  • Last visited

Everything posted by cjk28

  1. Nice! re. the gpu-usage thing, the video encoder is separate dedicated hardware, hence why GPUZ reporting 99% can be misleading. obviously a bit of an edge case as only applies to meta quest users, but thought worth mentioning in case theres an easy to use API that gives the 3d GPU usage % that task manager shows
  2. working nicely, thanks so much! i have my FPS set to 37 in autoFPS (with system cap at 40 (virtual desktop set to 80Hz with forced spacewarp) as otherwise i find TLOD seems to decrease unnecessarily (presumably due to occasional frame drop) - hopefully this doesn't invalidate the testing of this test version. I tried launching from a demanding airport and TLOD dropped nice and quickly. the 30s wait before considering to increasing TLOD again doesn't feel ideal but not sure if there are better options available. i got the feeling that AutoFPS is a overly keen to reduce TLOD in response to a small frame drop, I guess the Sens and target FPS settings can be used to tune this. Other than that, being able to open up the range so i can set my min to something lower (e.g. 20) without limiting my top max would be perfect N.B. I noticed that the app reports GPU usage values similar to GPUZ/MSI, but I found that these values are misleading, as they are some kind of aggregated value of 3D GPU%, GPU Video encode etc, so GPU 3D 80% and GPU Video Encode of 20% (for VR users) can get reported as GPU 99%, so could adversely affect places where gpu usage is used in the app.
  3. hm i get the error here changing base extra from 3x to 4x, so still seems wrong to me
  4. hi again, i think the calculation for this warning might be wrong (screenshot below). 42*4 is less than 100*2 i'm still not quite where i'd like to be with the app, which would be: single set+forget config where my TLOD is set between my ideal min for heavy cities (~30 TLOD), and my ideal max for all other scenarios (~165 TLOD), regardless of altitude, based on delta from target FPS. The current extra multipliers are a bit limiting as i'd need a mult of ~5.5x to achieve that range, so supporting other mults might help me with one part, and i assume if i set base min*extra to be the same as top min * extra, then i should achieve the "regardless of altitude" part too also not sure if its intentional for the performance optimiser to be quite hidden in the UI? It took me a while to find
  5. wow thanks so much, seems to work nicely! currently have set tlod base alt to 10ft as i dont really want to couple tlod to altitude, bit of a bodge but seems to work. i'll spend some more time comparing fps cap vs fps sensitivity, the latter seems to be working fine though... one thing i found trying fps cap mode, i can easily get the app to crash and require config delete to fix as follows: fresh config click expert user 1 select fps cap base min 42 base extra 4x top extra 1.5x -crash
  6. my approach is to get 40fps (spacewarp in vr brings it to 80) at 90% of situations (including at start of flight on ground), which i have with my upper desired tlod of 165, but was hoping autofps could step in when things get extra heavy (built up cities seems to be where its needed). I forgot to mention i'm on msfs2020 so no dynamic settings. hence the desire for an option for autoFPS to start from max (i.e. TLOD Base Min x Extra mult, or from my configured setting in MSFS gfx settings), and decrease if needed after the settle time (i.e. start high and reduce if needed, rather than start low and increase if possible.) anyways i don't mean to nag, just thought i'd explain further as i figured it would be a fairly common approach to configuring settings so might be something others would find useful
  7. Ah thanks I wasn't aware of the test versions. I guess i was hoping to either: be able to override the initial settle time to something shorter or have an alternate mode not considering altitude, where you start at your preferred max TLOD and only decrease towards the min TLOD based on delta from target FPS, that feels like a more catch all approach that accounts for variance in system demand caused by different environments, planes etc.
  8. hi, thanks for the app, works nicely, can anyone advise if its possible to configure it to start a session with your preferred top TLOD, and to only decrease TLOD if below target FPS? atm i've configured in FPS sensitivity, base min 42@1000, extra x4, top max 168@2000 which works nicely apart from the first 30sec during FPS settle will always have the min TLOD, so for things like landing challenges the terrain looks bad to start with.

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.