From the Reality XP website I understand using this forum is how to seek technical support:

Below is a condensed version of an ongoing going thread I had contributed to on the X-Plane.org forum regarding the UDP network IPv6 message.  This should be of great interest to you as I discovered this specific crash issue of X-Plane related to the XP Reality GTN plugin.  If at all possible it would be sincerely appreciated to get a support fix for this issue causing X-Plane 11 to crash & stay in memory when changing views creating the UDP network input message which in turn leads folks in the wrong direction when troubleshooting.?

I started getting the following message after trying to restart X-Plane 11 after it crashed when I did a view switch from interior to exterior view using the Shift+8 key combination.  This started in December (2019) after I had purchased the Reality XP plugin to use with the "vFlyteAir Cherokee 140 Modern" also purchased in December.  Thank you kindly.  Cheers

Thread starts:

BE ADVISED

Failed to initialize UDP network input.  (legacy RECEIVE)

This is almost certainly because you are already running 
another copy of X-Plane on the same computer.

Another possibility is that you turned off IPv6 support in your 
operating system.  X-Plane requires at least link-local IPv6
connectivity.

Be sure that IPv6 support is on, and restart your computer to
be sure that no other instance of X-Plane is running in the
background.  If it still fails, please check the Log.txt file for
entries of type E/NET and W/NET for details.

By pressing "I understand" X-Plane closes itself.  There is no instance of X-Plane running per the Task Master main page.  The only way I can get X-Plane to load correctly thereafter is by a hardboot of the computer.  This is a major annoyance to say the least.  The next course of action will be to turn off & isolate each "plug-in" one at a time to that I have installed since last November to rule out whether or not the issue is related to a "plug-in".

Running on Windows 10 pro platform desktop

Version XP11.41r1

Reality XP GTN 750/650 2.5.22.1

Update:

Confirmed the issue being generated by the Reality XP GTN plugin for the GTN650/750 (latest version installed 2.5.22.1) when used as a secondary gps.  When I switch between interior view to exterior view using the shift+8 key combination X-Plane 11 crashes.  When doing a restart the "Failed to initialize UDP network connectivity......." message is generated.  After selecting "Understood" X-Plane closes however when looking at Task Manager underneath the "Processes" tab X-Plane is still in memory.  I will contact Reality XP support and advise.  Thank you to the community for your input and support. 

Hi,

thank you for the detailed report and explanations. We'll try to repro and analyse and report back once we find something.

update: the UDP warning you are getting is most likely solely related to the XP11 crashed instance still in memory while trying to run the 2nd instance.

As for the external/internal view switching causing the CTD, do you confirm this happens only if you choose "Popout Window" to 'detach' the GTN window from the X-Plane window and make it a regular Windows window?

We can repro this only when selecting outside view with a popout window and 'auto hide' is enable (the feature which hides the popout window in external view and displays it back when in internal view).

This seems to be a bug in X-Plane 10.41 compared to previous versions. We're investigating further and will report to X-Plane devs. 

In the meantime, you might want to disable 'auto hide' feature.

Edited January 25, 20206 yr by RXP

Thank you for the great feed back.  I didn't realize I had the auto hide feature enabled (actually I didn't even know what that feature was for) but yes, confirming I did choose the "Popout Window" to 'detach' the GTN window from the X-Plane window and make it a regular Windows window.  I'll try the disable feature in the "Auto Hide" in the meantime.

Cheers

757FTB

Upon further investigation I confirm this is a bug/limitation of XP11 but we can't pinpoint from which specific XP11 version this is happening. We're looking at different ways to workaround this but with XP11.50 a moving target right now, we might wait for an official 11.50 release prior committing a fix.