FSUIPC Betas breaking PMDG FMC

[jordanal]

Pete,

I've posted the following over in PMDG's forum as well. I believe the last couple of FSUIPC Betas have issues with the PMDG FMC probably due to some unique coding they did under the hood.

FSUIPC 3.3707 Broke VOR2 DME (~3200nm) seems fixed with 3.708

FSUIPC 3.708 Broke FMC transistion from LNAV to ILS guidance on final

I have yet to roll back to v3.7 final due to the fact that I have a lot of aircraft-specific maps that from what I understand are not backward compatible after using 3.70x beta.

I recomend that you and PMDG chat about the latest beta before they go final. I believe there are underlying issues involved the may create a headache for us users, PMDG and yourself.

Posted in the PMDG forum on AVSIM:

I'm pretty sure the latest beta versions of Pete's wonderful FSUIPC utility is breaking the PMDG 747 (and maybe the 737) FMC. In version 3.707 Beta, we noted that the VOR2 DME distance was permenently set ~3200nm. Pete didn't understand why that was but managed to fix it with v3.708 Beta. Now, when transitioning from LNAV to ILS approach guidance, the FMC vector gets all messed up. I have to swich to HDG until I'm right on top of the ILS approach path. I suspect that due to some unique PMDG coding under the hood, Pete is making changes that may adversely affect the PMDG FMC in the coming release.

I would like to recommend that PMDG formally get in touch with Pete before he formally releases this version. FWIW, I have not tried to roll back to v3.7 (Final) because his new betas fixed some issues with the aircraft-specific maps that are rummored to not be backward compatible.

AL | KCHS - Charleston AFB/Intl | USAF 437AW (~53 C-17's)

FS9/Game Rig:

AMD64-4000+ SanDiego OC=210/420/2520 | Asus A8N-SLI Deluxe | Corsair TwinX2048-3200C2PT (2x1GB) 2.5-3-3-8/1T@2.8v | Evga NV 7900GT v91.47 (1280x1024x32/4xAA/16xAF/High-Quality) | Enermax 550W PSU | Thermalright XP-120(mm) HSF | NV 1GB LAN | NV SATA-I Raid-0 223GB (3x80GB Samsung) (WinXPx64/Games) | NV SATA-II WD 320GB (Backups) | IDE-0 80GB Samsung (Archive) | Realtek AC'97 5.1 Surround | CH Yoke, TQ, & Pedals | FS9.1 (Settings max'd/60-50Vis/No-Shadows/20FPS) | WideFS v6.7 | FSUIPC v3.7 | FSGenesis Mesh (All) | PMDG (All) | PAI (All) | FSPassengers | FSBuild2 | Etc

FS9 Support Rig:

AMD3200+ | Gigabyte GA-7NNXP | Leadtek NV 5900 | Corsair TwinX1024-3200 (2x512MB) | Intel 1GB LAN | SiI3112 SATA-I 80GB Samsung | IDE-0 80GB IBM | JustCom 4port KVM | WideClient | GE-Pro v2 | ActiveSky v6 (512x32bit/Wx Influanced)| Radar Contact v4.2 | FS Real Time | FS Flight Keeper | FS Commander | AI Smooth

[Pete Dowson]

FSUIPC 3.3707 Broke VOR2 DME (~3200nm) seems fixed with 3.708

FSUIPC 3.708 Broke FMC transistion from LNAV to ILS guidance on final

The *only* change from 3.707 to 3.708 is the provision of the VOR2 latitude/longitude and altitude values.

I have absolutely no idea what PMDG would be using for LNAV to ILS, but according to a note from Lefteris (in another thread here ) the PMDG ILS is operated using FS's VOR1 information, which is still fine in 3.708 just as it was in 3.707 9and, yes, I have re-checked all possible VOR1 values provided by FSUIPC).

Maybe you can persuade Lefteris to look at this.

Regards,

Pete

[jordanal]

Lefteris has asked for more information in the PMDG forum on this same topic and I have provided a scenerio in which it has happened three time now. Also, another user has reported that rolling-back to v3.7 final does fix the issue. The PMDG thread can be found here:

http://forums.avsim.net/dcboard.php?az=0288&page=

v/r,

AL

[Pete Dowson]

Lefteris has asked for more information in the PMDG forum on this same topic and I have provided a scenerio in which it has happened three time now. Also, another user has reported that rolling-back to v3.7 final does fix the issue. The PMDG thread can be found here

It's okay. All I can do is wait until Lefteris has identified the problem.

Regards,

Pete

[lefteris]

Gents-

I flew Jordan's scenario with no problems whatsoever. I can't reproduce this issue he noticed at all. In my mind, 3.708 runs fine.

[Pete Dowson]

I flew Jordan's scenario with no problems whatsoever. I can't reproduce this issue he noticed at all. In my mind, 3.708 runs fine.

Thanks Lefteris.

I actually compared my source code in the few areas which may have affected NAV data between 3.70 and 3.708, and the only changes I found were all for the added HSI data. The fix I made between 3.707 and 3.708 most definitely eradicated the problem I accidentally introduced with VOR2.

There's a puzzle there somewhere, I assume, but I suspect it is down to something else in the sufferer's system.

Best regards

Pete

[jordanal]

Well, I should probably be accused of crying-wolf as can't seem to duplicate this issue on v3.708 with all my add-ons running. I appologize to PMDG and Pete for prematurely raising the red-flag. After having the issue in three consective flights I now can't seem to duplicate it. Maybe it was a flakey copy-process when copying the dll into my modules folder the first time, sun-spots, or even the celestial alignment of the stars. Who knows and again appologies for creating this thread in the first place.

:cry:

v/r,

AL Jordan

[Pete Dowson]

Well, I should probably be accused of crying-wolf as can't seem to duplicate this issue on v3.708 with all my add-ons running. I appologize to PMDG and Pete for prematurely raising the red-flag. After having the issue in three consective flights I now can't seem to duplicate it. Maybe it was a flakey copy-process when copying the dll into my modules folder the first time, sun-spots, or even the celestial alignment of the stars. Who knows and again appologies for creating this thread in the first place.

No worries about crying out about problems. It could have been a real problem, after all. Thanks for confirming all is well with 3.708, and please don't worry about reporting things in future. I don't give out black marks! ;-)

Oh, please make sure you left Lefteris know too, it was he looking to reproduce it.

Regards,

Pete

[vhm3]

And here I was wondering what I'd messed up... :shock:

Thanks gentlemen,

Chip