Jump to content

C. Schaffhausen

Member
  • Posts

    155
  • Joined

  • Last visited

  • Days Won

    7

C. Schaffhausen last won the day on March 15

C. Schaffhausen had the most liked content!

Recent Profile Visitors

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

C. Schaffhausen's Achievements

63

Reputation

1

Community Answers

  1. Another flight freeze, this time on 1.0.11. The sim was minimized in the task bar and I was not able to open the window again. I disabled auto import step climb and entered them manually, auto step climb enabled, navigraph navdata used.
  2. Agreed, if the sim has issue it would have affected much more than just Inibuild's products.
  3. The aircraft does not recognize the route "MOLKA M750 MUKEP", and probably onwards. When entering M750 after MOLKA, the page did not respond; whereas with the scenery off, it will recognize M750 MUKEP. Really strange to see other aircraft working without issue too. It is very easy to recreate, install the Kai Tak scenery, load the A350 onto RCTP, ensure in-sim navdata is selected, enter a MOLKA SID, then from MOLKA, you shouldn't be able to enter M750 MUKEP. Then, load into the same scenario with a default 737, programme the same route, you will be able to enter M750 MUKEP.
  4. Aircraft: A350-900/-1000 Version: 1.2.4 Simulator: FS2024 SU5 1.7.17.0 Navdata Method: In-sim OFP: route provided WASM Error: Not related Specs: 9800X3D, RX 9070 XT 16G, 64G RAM Autosave File: Not related I've been using this Kai Tak scenery from flishtsim.to for a while, but I noticed an issue with the navdata. I use in-sim navdata on the A350 to prevent WASM crashes and flight path deviation/flight freeze. I planned a flight from RCTP to RJAA which the SID lead me to MOLKA M750 MUKEP. I entered the route into the FMS but it didn't recognize the route. While I understand that the Kai Tak scenery does have its approaches and navdata, which in my sim appears to override the jeppesen data. When I disable the Kai Tak scenery, the FMS recognize the route correctly. Up to this point, the problem seems to be the scenery, until I enable the scenery again and tried the same route on the default 737, as well as the FBW A380, which they all recognize the route correctly. Only the default aircrafts made by Inibuilds, as well as the A340/A350 does not recognize the route correctly. It looks like there is an issue on Inibuilds' aircraft when it comes to reading the default navdata, can the team please take a look? The Kai Tak scenery: https://flightsim.to/addon/51332/vhhx-kai-tak-enhancement-for-asobo-gaya-su11 Route: RCTP MOLKA M750 MUKEP Y891 AGIMO Y89 GUPER Y81 RUTAS RJAA
  5. Understood, looks like I have a different problem then you do. Then perhaps it's worth getting Navigraph. However even with that I had to change to in-sim navdata to avoid wasm crash, which lead to a different problem for me.
  6. @Rodolfo Becerra Vargas I had the same issues as you do. Try to use the package reorder tool to move the two navigraph entries to as low as you can, with navigraph-nav-base higher than navigraph-nav-app (I think being lower loads it last, therefore overwriting any entries that might have interfered with the jeppesen navdata.). Do that and clear wasm again.
  7. Votes for this as well, as I have to use default navdata to avoid the wasm crashes and sim freeze. I have recently unable to use inbuilt navdata as well, looking for a solution.
  8. Looking at the Tristar previews, with the steam gauges cockpit and such a vintage look, I can't help but imagine what if, what if Inibuilds make a Concorde? The only one in the market is working but not stunning, while the lab probably need 10 more years. 🤔
  9. Hello team, any updates? I just flew there and notices the issues there, including the flags and inaccurate lat long of the airport. I understand this is freeware, but hopefully we can see an update to make things right. Thank you.
  10. I've recorded a video showing the error, this also involves a premature rotation without any stick input during takeoff roll.
  11. I've stopped my flight and made a video to demonstrate here. I did not apply any back pressure to pitch up during the takeoff roll, it took off by itself. This also demonstrate the VNAV fault which shift to DES phase after passing 1000ft
  12. Aircraft: A350-900 Version: 1.2.3 Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: Attached WASM Error: Not related Specs: 9800X3D, RX 9070 XT 16G, 64G RAM Autosave File: Not related As titled, I encountered 2 consistent premature rotation during takeoff roll. I did not record both flights but I have the aircraft loading available here. Takeoff performance calculated by the built-in tool. I can confirm that the load is correct and that no weight disagree message was shown. TOW: 194710kg ZFW: 173696kg 2026031501_VHHHRJFF_PDF_1773578058.6d60e72d.pdf
  13. Had the exact issue, come on Inibuilds, fly it at least once before an update. Hotfix needed.
  14. I have not encounter the issue in 1.0.10, but now I do. The sim was minimized in the task bar and I was not able to open the window again. I disabled auto import step climb and entered them manually, auto step climb enabled, navigraph navdata used.
  15. No I'm not, I used the custom view setting to save wing views which are in the cabin. I also do that for the A350 and did not notice any cockpit warnings in the A350.
×
×
  • Create New...