Jump to content

Shack95

Members
  • Content Count

    1,465
  • Donations

    $25.00 
  • Joined

  • Last visited

Community Reputation

2,416 Excellent

About Shack95

Profile Information

  • Gender
    Male
  • Location
    LFSB

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I agree that performance is important but I for one quite like animated people inside terminals (as long as you can see them through the windows). One „aha moment“ was when I was parked at the gate of Aerosoft‘s outstanding EBBR Brussels for the first time. The incredibly detailed scenery, the moving passengers inside the terminal, the airport vehicles moving smoothly at the correct speed, it all added immensely to the immersion. It just looked more real than anything I‘d seen in a flight sim before. Of course it’s not necessary, like so many other things we love in flightsim, but it makes it more immersive and that‘s something many of us want (and no, I‘m not „playing“ pilot). As for performance, EBBR runs pretty smoothly on my rig, better than many much smaller airports like e.g. Gaya‘s Florence for example and also better than Asobo‘s LFDG, both of which have no moving people.
  2. LIRQ Florence by Gaya Simulations has moving trams. EPKK Krakow by Drzewiecki Design has moving trains. KLAS Las Vegas by FlyTampa has moving shuttle trains, custom road traffic, including taxis and busses (that pull in and away at stops) plus loads of POIs in the city. LGAV Athens by FlyTampa has moving trains and spectacular night lighting. LOWW Vienna by Gaya Simulations has moving trains.
  3. Content.xml file.: (AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Content.xml) simulator .dat files: (AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes*.dat) They are restored when you load the sim. I haven‘t noticed any changes. I emptied my the community folder before I deleted these files. Then I started the sim once with an empty community folder. I don‘t know it this is necessary but i just wanted to be on the safe side. I‘ve done a few full flights now and the situation has much improved. I encountered some tearing and micro stutters here and there but it‘s no comparison to how it was before. Now it‘s playable again.
  4. I’ve done 3 flights with FSLTL and so far I quite like it. The only thing that’s a bit odd (apart form the usual AI quirks) is that I haven‘t seen a single AI landing yet.
  5. If I had to guess I'd say it's down to Bing Maps imagery and has nothing to do with the sim as such. It's just images taken at a different time. There's quite a few such anomalies in Illinois.
  6. Do we have to use a key every time we start FSLTL or is it active until we change it like the other settings? And another question, how do you follow an AI plane in MSFS? I saw that in a Youtube video but I couldn‘t figure out how to do it.
  7. I had serious issues after the update as well. I had CTDs every time I started the sim (in the main menu, while loading a flight or shortly after starting a flight). Reinstalling the sim solved that problem but then I got massive screen tearing problems in VR making it impossible to fly. Just today I found the solution to these problems, thanks to a user on the official forum. I deleted the Content.xml file and the simulator.dat files and all is good again. That user also posted some other tips that might be helpful (see quote below). I‘m no expert at all and maybe these solutions have nothing to do with your issues but before reinstalling everything again it might be worth giving them a try. Please note that I only had to do the first 3 steps. 1. Delete any rolling cache. 2. Delete the Content.xml file. (AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Content.xml) 3. Delete the simulator .dat files (AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes*.dat) 4. Do not add anything to the Community folder In the search bar type CMD and hit return This will bring up a menu selection . Select the option “Run as Adminstrator” A DOS window will then open. Go through each of the following steps one at a time. Copy each line, one at a time , paste it into the Dos window (crtl + V) and press return and it will then run. Wait until each runs and finishes before you move on to the next one. When you are completely finished, Restart your computer and then try to see in MS2020 will start and run properly Dism.exe /online /Cleanup-Image /checkhealth Dism.exe /online /Cleanup-Image /scanhealth Dism.exe /online /Cleanup-Image /Restorehealth sfc /scannow Please note that the line sfc /scannow will probably be where you will see a lot of corrupt files repaired. If this happens, please rerun this command again until you get the message that no corrupt files have been found. Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore Dism.exe /Online /Cleanup-Image /StartComponentCleanup RESTART your computer as the last step Please note that the line sfc /scannow will probably be where you will see a lot of corrupt files repaired. If this happens, please rerun this command again until you get the message that no corrupt files have been found. It may take 2 or more tries to fix everything.
  8. Deleting the Content.xml file and the Simulator.dat files seems to have solved the problem. Thanks to everyone who helped me sorting this out!
  9. Thanks a lot for your support @Fielder. Unfortunately that doesn‘t work either.
  10. @jmig sorry to hear that. I hope it will work out for you. That would be plan b then, I guess.
  11. Thanks a lot. You’re right, it seems to be screen tearing. Now I know what to search for. I‘ve just noticed that there‘s a new Nvidia game ready driver available. I‘m going to install that one and see how it goes. Edit: The latest driver didn‘t help either.
  12. I‘ve spend some more time trying to figure out what‘s wrong. I tried without OpenXR dev tool and I‘ve also updated all my drivers (lates Game Ready Nvidia driver). That didn‘t help. It seems that frame rates aren‘t the problem. I get constant 37-40 fps in the Fenix with relatively high settings and it feels smooth. It‘s when I move my head that things get weird. It‘s as if the image flashes up slightly offset 2-3 times per second. Especially bright objects such as lights, text or displays are affected. On my monitor I can‘t see it. I also tried other VR games and they run just fine. Really frustrating to say the least.
×
×
  • Create New...