[SOLVED on future 1.1 version] Bug with FMS Duplicate Waypoint Selection

[Dhruv]

I'm looking forward to flying the CRJ successfully, but so far the FMS has deemed itself somewhat unpredictable on my end. Unfortunately, it didn't take long for this one to rear its ugly head.

Entering KMSP-KGFK into the FMS via the BRD (Brainerd) VOR revealed a number of bugs in the FMC, culminating with a crash to desktop.

Part 1:

The multiple VOR selection screen that appears when the database has more than one navaid with the same identifier is slightly off - it displays all the VOR frequencies as ending in .00. Therefore, the list shows as such:

BRD (Brindisi), actual frequency 113.2 displays on the FMC as 113.00

BRD (Bojnord), actual frequency 114.8 displays on the FMC as 114.00

So on and so forth throughout page 1/2, which leads me to the next part of the problem.

Part 2:

In fact, BRD (Brainerd) - the VOR I need - isn't even displayed. It's on page 2/2, which comes up blank when I hit next page. Taking a shot in the dark, I hit LSK L1 on page 2 of the selection menu, which inserted Brainerd into my flight plan with a bearing of 339 and 94nm from KMSP, which is correct. At this time, X-Plane beachballed and crashed to desktop.

System specs:

MacBook Pro 4,1. 2.5 GHz C2D T9300

4GB RAM

nV 8600M GT, 512MB

OS X 10.6.7

X-Plane 9.68

Operative Part of the crashlog:

Process:         X-Plane [40297]
Path:            /Volumes/Paine Field/XPJ and FreeWorld/X-Plane 9.67/X-Plane.app/Contents/MacOS/X-Plane
Identifier:      com.laminar_research.X-Plane
Version:         9.68 (398)
Code Type:       X86 (Native)
Parent Process:  launchd [113]

Date/Time:       2011-05-08 14:38:12.168 -0500
OS Version:      Mac OS X 10.6.7 (10J869)
Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000000000c
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   mac.xpl                       	0x3650cb80 CDUPanel::getWaypointLegs(int) + 256
1   mac.xpl                       	0x36512a21 CDUPanel::updatePageLegs() + 161
2   mac.xpl                       	0x3651dc79 CDUPanel::update() + 457
3   mac.xpl                       	0x364959df MediumLoop(float, float, int, void*) + 63
4   XPLM                          	0x1d4ac6af XPLMDoFlightLoopProcessing(float) + 165
5   XPLM                          	0x1d4a6c8c XPLMEventHook + 110
6   com.laminar_research.X-Plane  	0x004c832c flit_per_frame() + 60
7   com.laminar_research.X-Plane  	0x00248b70 APP_update() + 7440
8   com.laminar_research.X-Plane  	0x00066baa MACIBM_event_proc() + 1450
9   com.laminar_research.X-Plane  	0x006d0a76 main + 518
10  com.laminar_research.X-Plane  	0x006128d2 _start + 216
11  com.laminar_research.X-Plane  	0x006127f9 start + 41

[philipp]

Bug is confirmed. Thanks very much for the detailed report.