Quick wording fix SetupRootDialog
macOS: new app icon, update files
That does appear to be the case, and from this the only explanation is that for whatever reason the build on the nightlies webpage is out of date, even though it says it was updated with the latest from today (??) which is what I am using. The log looks the same whether I let it overwrite the files in bin/ and when I went to manually delete them and tried again just now. If someone else can confirm this on their end, then this would all make sense.
NavCache aborting on Windows nightly
Hello! I am on 1.5 GB VRAM integrated intel (so far less powerful than ASR's rig) yet I can confirm the exact same behavior on my end – while the fps and overall performance is as would be expected on 2020.3, on the latest nightly I had switched to that same fps became absolutely abysmal, barely cracking 7-10 fps even in light areas like the vicinity of EDDM where I don't even have osm2city. Playing around with my typical LOD ranges vs default, ALS on/off, all shaders, shadows on/off – none of that...
I don't think this is even on Canvas, if I'm not mistaken, though one of our goals is to port over all the cockpit instruments to Canvas at some point. As mentioned earlier, this is most likely an issue that lies internally in FG with not adopting/recognizing UTF-8 only. I'm really not sure how to go about isolating only the parts of the aircraft where the issue lies? It could (and probably does) go far beyond the scope of just that anyway, if it is like Megaf said and the symbols like ° have the...
Hello James! First off, big up for all the great work you've done/are doing for FG. Despite Megaf's message, it isn't that we've lost interest – just that we've been busy with some things irl lately. I can confirm to you that using LiberationSans instead of B612 as we were using earlier (even though really I aim to use Nunito but I wasn't able to get it to work through a custom font directory path (Aircraft/787-family/Fonts) , only through FGdata for some reason so I might propose for it to be added...
Hello James! First off, big up for all the great work you've done/are doing for FG. Despite Megaf's message, it isn't that we've lost interest – just that we've been busy with some things irl lately. I can confirm to you that using LiberationSans instead of B612 as we were using earlier (even though really I aim to use Nunito but I wasn't able to get it to work through a custom font directory path (Aircraft/787-family/Fonts) , only through FGdata for some reason so I might propose for it to be added...