Paraso

Hi ini Team, I (and many others) would be highly interested in seeing a high quality rendition of GMMN (Mohammed V International Airport) done by inibuilds for MSFS 2024. As you know, this airport serves as the hub for Royal Air Maroc, is among the busiest airports in the African continent and serves countless destinations in Europe, Africa, the Middle East & North America including ini's own LHR, LGW, MAN, JFK, LAX, DOH, AUH and DXB (serviced by Emirates' A380, wink wink). The two current renditions of Casablanca in MSFS are really quite poor and outdated so a well crafted rendition is needed in my opinion. Thanks for reading!

Hello! Thanks for binging functionality to the SND! I have noticed multiple issues during my first flight using it. (2024) In this case, I was performing a flight from the new Heathrow to Kennedy, and inserted my NAT waypoints into the SND during initial cruise. 1 -> Attempting to modify an existing waypoint in the SND actually ended up creating a fix with the updated coordinates I had inserted. 2 -> In every following attempt to modify a waypoint, each depression of the set/select knob would skip the next portion of the coordinate being edited. For example: Pressing knob would jump the selection from N -> Minutes (skipping degrees) or Degrees -> Decimal minutes (skipping minutes). Essentially I could only edit every other portion of a coordinate. 3 (WASM Crash) -> Cockpit freeze occured when clearing out the last waypoint in sequence in the SND. Otherwise, nice addition. As a side inquiry, are you planning on implementing the "mode" pb in a future update?

Recently had a similar issue with the a300 (which I posted in the wrong thread). KJFK - KLAX descending via ANJLL4 @ ~FL240. Freeze occurred after activating the secondary flight plan (which was loaded with ILS25L+transition as opposed to the primary flight plan which had ILS24L+transition loaded). The freeze didn't occur immediately after activation of the secondary flight plan, rather it happened only after a few seconds. Everything in the cockpit froze barring the EFBs (none of the preset aircraft state buttons had any effect) and external light switches (which weren't functional). All else I noticed was that the altimeter was stuck in a continuous descent from about 24,200 down to 24,000 after which it would return 24,200 and continue on an endless loop. Flaps and landing gear doors had no animation, though flaps themselves appeared to be aerodynamically functional. Plane handled normally, throttles were functional but with a lack of animation.

Just had this same issue with the a300. KJFK - KLAX descending via ANJLL4 @ ~FL240. Freeze occurred after activating the secondary flight plan (which was loaded with ILS25L+transition as opposed to the primary flight plan which had ILS24L+transition loaded). The freeze didn't occur immediately after activation of the secondary flight plan, rather it happened only after a few seconds. Everything in the cockpit froze barring the EFBs (none of the preset aircraft state buttons had any effect) and external light switches (which weren't functional). All else I noticed was that the altimeter was stuck in a continuous descent from about 24,200 down to 24,000 after which it would return 24,200 and continue on an endless loop. Flaps and landing gear doors had no animation, though flaps themselves appeared to be aerodynamically functional. Plane handled normally, throttles were functional but with a lack of animation. Happy to provide additional information if needed.