by mobiusfix » Tue Jun 25, 2019 11:08 pm
I played around in the sim a bit more tonight. Once again had a (software) crash just as I started rolling down the runway. Bugsplat reported. My second load-up worked just fine, and once I get going I don't experience any crashes, hiccups, or streaming lag. Super smooth FPS as always, which is why FIFS is my always my go-to VR flight sim.
Aside from some elevation mapping issues which don't bother me that much, I noticed a couple things that are a bit more bothersome:
1) Sometimes when I load an airport, my plane is either below the runway or off to the side of the runway. At Honolulu I actually started on the surface of the lagoon next to the airport. Luckily the sim didn't recognize it as a water landing.
2) The airport search function needs to be more robust (and accurate). As in the example above, if I actually search for "Honolulu", nothing comes up. If I search for the full airport name starting with "Daniel", nothing comes up. I have to enter the airport code or "Inouye" to find it. Similarly with Aeroporto Internazionale di Napoli. None of those words brings up a result. Instead, I have to type in "Capodichino" which is simply the district of Naples where the airport resides. In short, a bit of a pain.
3) Most sims add-ons that use satellite imagery fade out the imagery at the coastline. At the moment, FlyInside appears to just be using entire chunks of imagery off the coastline that end abruptly.
I'm sure this is all on your to-do list, but I just wanted to share my impressions after using the new build a couple times. Thanks!