EnQ

Just to be sure: There are a few plugins which crash X-Plane if the number of TCAS contacts exceeds 19 or 20 until they are updated. I think I've read that SAM can react to some "AI traffic". As there is no real AI traffic in X-Plane, AFAIK it's either fully featured "network multiplayer" aircraft or just dumb 3D objects, I have to ask if SAM by any chance also uses TCAS data to support docking other aircraft? If it does, did you already test if SAM is fully compatible with more than 20 TCAS contacts at the same time? It seems that other plugins perform illegal memory access in such cases which leads to CTDs. Note that TCAS has nothing to do with Vulkan, it's just an additional change in XP 11.50 and even if a plugin already supports Vulkan it may still not have been checked for issues resulting from the TCAS API changes.

LSGG ILS 22 has its CAT 1 minima covered by the same arrow in both the Windows app and also if viewed in the browser (although rendered on server side).

Looks like there are even more font rendering issues... In both the Windows app and the browser version (Chrome) visual tracks currently appear with letter "Z" instead of the expected arrow markings, for example: LOWI "Visual after LOC DME" charts LOWS Circling 33 (but RNP V 33 shows the arrows correctly) LFMN Circling approaches Other LFMN approaches show the number "2" overlaid on the NDB NC which I can't make any sense of and don't remember having seen something like that before. It's kind of weird that both the old rendering in the Windows app (still PDF, I presume?) and the newly generated JPEGs are affected... Might be some new generic issue for AIRAC cycle 2001?

LYBE AGC is also blank using either Windows app or Chrome. Again, I can see that the downloaded PDF is empty except for meta data. Affected files have just 1.3kB which makes me think all blank charts should easily be detectable on server side by checking for charts smaller than 2kB.

Charts "AGC" and "Tempo AGC" are blank for ESGG, both in Windows app and Chrome. Using Chrome's developer tools I can see that the PDF appears to be without content (just metadata). Other charts of ESGG are fine and I didn't notice any other affected airports yet.

For EDDT charts "ILS or LOC 26R" and "ILS or LOC 08L" a part of the CAT minima is currently covered by a large black arrow. Is that arrow supposed to be there or some rendering issue with those documents? The small arrow in the right lower corner refers to "additional minima [...] on the last IAC page" (i.e. "WxMinima Overflow") according to the 2014 LIDO documentation I have at hand but it seems that the large arrow is somewhat out of place (especially since it covers numbers which I would not expect on aeronautical charts). The arrow is visible in both the Windows application and when accessing the webpage using latest Chrome. I already noticed that arrow yesterday before access to/rendering of the charts was restored. The chart pages have become effective in June and August, but I am not aware that I would have seen that arrow previously. "WxMinima Overflow" does not list Cat 2 for 08L so I don't think that arrow should mean to substitute any information.

Eigenartig, dass der Fehler so uneinheitlich ist. Bei mir funktionieren KSFO und KORD im Browser bestens, nur in der Windows-Anwendung wieder nicht. Edit: Im anderen Thread grad gesehen, dass ein Kompatibilitätsproblem zwischen den Browsern und Schriftarten der PDFs vermutet wird.

Im englischen Forum wird grad schon versucht, dem Fehler auf die Schliche zu kommen: Wenn Du die Charts dringend brauchst, versuch es mal im Browser unter http://navdatapro.aerosoft.com/ - das funktioniert zumindest bei mir erstmal ersatzweise. Bitte im anderen Thread auch nochmal posten, welche App Du benutzt oder ob Du auch auf der Webseite das Problem hast und wie sich der Fehler bei Dir äußert.

For me the issue looks the same as in yesterday's screenshot posted above: When using the Windows application I get a white screen when selecting certain charts. In such cases, "Downloading chart" is shortly visible but then simply disappears, leaving the page blank. No percentage is shown. For other charts I can observe that additional to the "Downloading chart" message a percentage appears and quickly counts towards 100% before the page appears. When using latest stable Chrome on the same machines (tried on two different PCs) the same charts work without any issues (navdatapro.aerosoft.com).

Just checked, LICJ is broken for me as well. LROP is also showing the same issue as yesterday, as is KFJK. New one: LSZH is missing APC chart for me, AGC and AFC are fine. A few weeks ago it sounded like there was a bigger issue on the server (drive defect or something like that) but that would not really explain why some clients can access the charts and some can't (even on the same PC and after all the desktop app is just nothing but an embedded Chromium browser, so why does it work with Chrome on the same machine...). I also noted that when accessing by web browser I see a "dark mode" option and a few days ago I noticed a green airplane icon (supposedly some preparation work for geo-referenced charts?). I don't have either in the installable Windows app. Could it be that the installable app versions cached some old resources (JavaScript?) which are incompatible with latest server-side API? If there's any way to open the apps up for Chrome's web developer tools I'd be glad to submit screenshots of the network and console log tabs, if insight from affected installations is needed. (TeamViewer or something similar for a developer to debug on my machine would also be an option - contact me by PM if interested but I can only offer access in the evening)

Seems to be a bit on-and-off right now. Working: EDDT, LIRN, LOWI Not working: LROP, KJFK No error shown in the NDP desktop application. Just tried again a few minutes later, now I get some more charts of the affected airports on one PC but not the other. Access through webbrowser appears to work fine. LROP AFC, AGC and APC charts appear to have the most reliably reproduceable issues for me. Also note that somehow charts have different names and appear in a different order in browser and app, is that normal?

Same here. Just in case it should be an account or ISP related issue: I got 304 days left in my subscription according to settings page (bought on 22 August 2019). App version 0.1.1; just tried reinstalling "1.0.0.1" (latest download offered) from the shop, app still shows 0.1.1. ISP: Deutsche Telekom, IPv4+IPv6 Dual Stack via VDSL (no mobile proxy) I just tried https://navdatapro.aerosoft.com/ through a web browser; connection runs via IPv4. Status code is 200 but the server says all PDF files were 0 bytes in length (content-length). Filenames in content-disposition header look correct.