Fsbuild-2 Flight Planner

I have recently purchased the ISG1 gauges and love every aspect of them. I even updated the NavData to Cycle 1401. However, I am having a bit of trouble with the Smiths FMC and will do my best to describe the problem as accurately as possible as well as give as much information as possible.

First, I have installed the gauges and they are working correctly with the exception of the Smith's FMC as described below. In all instances, I am using panel.cfg files which were downloaded directly from the ISG website. I have not modified the files in any other way. I am using the FSX King Air 350 file, the Posky CRJ700 file, and the FSX A321 file. I am willing to try other files but don't believe it will make any difference.

Here is the exact situation in which I have created the problem. I was enroute from KSNA to KPHX in the CRJ700 and had loaded the Geela6 arrival, BLH transition, and ILS runway 8. About halfway through the arrival, I noticed the RNAV points were wrong. Instead of showing the final six points of the arrival correctly, the MCU indicated only two points as "DISCO" and "WAZUP" - neither of which is an actual point in the arrival or anywhere close to PHX for that matter. The FMC legs menu show the same points but immediately prior to Disco indicated "route discontinuity." The points prior to the route discontinuity were correct. The points after were DISCO and WAZUP. Secondly, upon arriving into PHX area, I was told Runway 8 was not active and would need to land on Runway 26. When I updated this through the FMC, instead of changing the arrival with the correct points, it simply added the entire arrival AFTER the already entered (now incorrect) arrival points. In other words, the FMC would have had my fly the original arrival, then return to the beginning of the entire STAR and refly the entire route with the new points. However, as before, the final six or so points of the STAR were omitted and instead "DISCO" and "WAZUP" were the final two (still incorrect) points. No correct transition to the runway was listed. The only way to remove the previous arrival points was to manually delete them one by one.

Frustrated, I flew the route with one of the planes which uses the GNSLXS. When I entered the desired STAR, all the points displayed correctly with no route discontinuity of any kind and the final waypoints for the runway transition were listed correctly and completely and did not include DISCO or WAZUP. When I attempted to change the STAR to a different runway, the STAR was updated correctly and the runway desired correctly changed. The inactive portion of the STAR was removed and replaced with the correct waypoints. In short, the GNSLXS behaved correctly and as intended.

Bottom line: the GNSLXS handled the changes perfectly while the same changes made with the Smiths' FMS only created the problems described. Since the GNSLXS had all of the correct Navdata, I know I don't have a data problem. All related gauges behave correctly with the GNSLXS and incorrectly with the Smith's.

One final note: I did manually change out the Smiths' in the CRJ700 with the GNSLXS in the panel.cfg file and the GNSLXS worked perfectly again. So, I know the problem is entirely with the Smith's

Any ideas what needs to be done to correct the issue? I like the Smith's but if it's not going to handle the STARs correctly, I can't use it.

Thanks for your help looking into this matter.