Jump to content

Tom Tsui

Members
  • Content Count

    46
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by Tom Tsui


  1. I found the ground texture keeps refreshing around Bern Belp (LSZB) airport when flying at low altitude.   When altitude is above 3,500 feet, the issue is gone.
    I have Orbx's LSZB addon.  The issue remains with and without it.
    https://www.dropbox.com/s/obuhe2f5cdnzqci/BernBelpTexture.MOV?dl=0

    Tried reinstallations and rebuilding rolling cache.  Doesn't help.
    Any ideas to fix it ?  Appreciate it very much.

     


  2. Not sure if it's been reported. After MSFS SU10 update, the NAV/GPS button of the C172 (above VOR1) won't toggle the status of NAV and GPS on the VORs as well as on the GNS530/430.

    In order to change the status of NAV and GPS on the VORs, one has to press the CDI buttons on the GNS530 and 430 respectively.

    The issue seems valid on the C172 only.    Tested other aircraft (either default or payware) and they don't have such issue.

     


  3. If you are running Windows 11, be careful with the recent Cumulative Update (KB5007262).

    win11-update.jpg

    My MSFS crashed to desktop after 5 to 10 minutes running in any active flight.

    I can confirm that on my system since I experienced the same situation twice in the last few days.

    The first time was last Friday, in which I mistook the CTD was caused by the motherboard drivers I updated at the same time.

    Yesterday I had the Windows Cumulative Update installed alone, which consequently led to the same MSFS CTD scenerio after less than 10 minutes running.

    Luckily, both CTDs were fixed by restoring my OS drive (just Windows, excluding MSFS) from the latest backup.

    Have reported the issue to Zendesk and got a reply saying "the issue has been tracked in our internal bug tracker".   

    Hope there will be a solution soon.

    If you are running Windows 11 and had the update installed already without any issue, Congratulations !

    If you are running Windows 11 and haven’t had the KB5007262 update installed yet, do be careful either by making a system back up first (just in case) or simply skipping it for good.

     

    • Like 2

  4. I recently wrote a utility called ShadeShifter to make the switching of Presets a lot easier and user-friendly. Anyone interested could see my post here. Note that version 2 is coming soon. However, subscribing to my blog is required in order to get a copy of it.shadeshifterv2.jpg


  5. Great work Tom. I actually have your excellent blog in my favourites. Just didn't realize you were the same Tom ;)I will checkout the particular post you've referred to. By the way, you've got a neat setup.Cheers,Sam
    Yes Sam, I am that Tom. Glad you like my blog. Actually I am thinking about upgrading to 3 monitors in PLP setup (20"+30"+20"). Still researching if this is possible. Another change being worked on is to further elaborate my flying zone setup. Hope to have that completed in a couple of months.

  6. In reading and searching this forum along with what this gentlemen says here about it: http://fsxtimes.word...mult-revisited/I am currently at a loss as to what I should use. I have been using =120 and now just went to 400. I see many people posting their cfg with it at 80 or 40. This above blogger is now using =800 on his rig. I have two 1GB HD5870 ATI cards. I know fsx does not use SLI. I am wondering if someone (Word Not Allowed?) might explain further what a good number is to use. My cfg tweaks and relevant settings are:
    Hi Eric,This is Tom of fsxtimes. As Ian pointed out, "the number tends to be very individual system dependent." I tried different numbers from 40, 80, 200, 400 to 800 on different systems and results were varied. I found 800 is good for my HD6970 card with current tweaks in fsx.CFG. If 120 is best for your current setup, stick to it. Tom
×
×
  • Create New...