July 31, 20214 yr Yes these small issues start to add up. I keep reading posts about being confident these issues will get fixed, but here we are almost a year later...
August 16, 20223 yr You can change the airline / callsign in the aircraft.cfg file... I don't put anything in the menu fields and it reads the cfg
August 16, 20223 yr On 7/31/2021 at 2:29 AM, ryanbatc said: Even though it hurts to say it...Asobo needs to stop adding features and FIX the broken parts. And do maybe 2 big updates per year....it's hard to keep up with changes...even our little VL3 Rotax 915is mod was broken by the latest update ugh. New features is what a lot of people keep playing and comming back. As soon as they stop adding new things only the diehards remain and I dont think thats what MS needs/wants. I9-14900K, Gigabyte B760 Aorus Elite AX, RTX 4080, 32 ram.1 tb nvme M.2 SSD, MSFS 2020 on 2 tb nvme m.2 SSD
August 16, 20223 yr I was under the impression that we could leave the call sign and flight number blank on the aircraft customization page and MSFS would use what was in my (exported from Simbrief) flight plan and/or whatever I put into the MCDU (Fenix or PMDG). MSFS seems to get the call sign correct, but it never uses my correct flight number. I've been entering it in the customization page, but I feel like I shouldn't have to do that. Is it working for anyone else? i9-10850K, ASUS TUF GAMING Z490-PLUS (WI-FI), 32GB G.SKILL DDR4-3603 / PC4-28800, GIGABYTE RTX5080 16GB WF OC 3 FAN running 3440x1440
August 16, 20223 yr On 7/31/2021 at 1:29 AM, ryanbatc said: Asobo needs to stop adding features and FIX the broken parts. I can almost guarantee Asobo would like a big chunk of time to do just that. Sadly it all depends on Microsoft allowing them to. And I can understand why Microsoft wouldn't want them to switch over to only bug fixing at the expense of new features for a significant period of time. Edited August 16, 20223 yr by March Hare
Archived
This topic is now archived and is closed to further replies.