8 hours ago, Stearmandriver said:

Well to be fair, I never said it was "across the board superior", I said "comparable", which was in response to you suggesting that if anyone thought the iFly approached the level of PMDG, they must not know what makes a good 737 sim.  Bit of hyperbole in both your posts there, right?

For every particular detail you can give that PMDG models better than the iFly, I'm pretty sure I can give you at least one the iFly wins at. I've been having fun discovering all these little touches, after years of seeing PMDG ignore them, despite quite a few tickets and forum input from myself and others. 

Engine spool and control interference are really the two big ticket items, and they're coming in the upcoming update.  I suppose we all remember how long, and how many updates, it took PMDG to fix the exact same engine spool behavior we current see on the iFly 😉.

VNAV is actually better on the iFly, as it's not a weird blend of common and basic.  Does it experience a bug occasionally? Yup, but honestly I haven't seen anything worse than the PMDG bugs.  As far as LNAV goes, I've seen bugs in how the route is drawn occasionally, but what I've found interesting is that it flies the correct routing even if it drew a weird loop or something.  So for the most part I think the important stuff is there, it's just drawing bugs. I definitely give the iFly the edge here...pmdg draws AND flies things strangely sometimes. 

Etc.  Point is they're both top-tier sim aircraft.  There is a narrative that the iFly is all about cosmetics and lacks systems depth and that's 100% false.  It is at LEAST as detailed as the PMDG, that's all.

Most unbiased real Boeing pilots and particularly 737 pilots I’ve spoken to prefer the ifly max for the reasons you give above. Looks like PMDG have finally after 15 years, improved their old lnav though which is a plus. Great to see some competition in the Boeing flightsim market also. 

1 hour ago, StoneDoor said:

Except that they did not. Just follow the steps in their manual and you have the "PMDG-mouse" behavior back.

I suggest you read the thread I posted from the pmdg forums earlier, and this one actually, the xml has not been updated for this update so using it kills the EFB and MK states for final build they will almost certainly scrub that option from existence. 

Of COURSE I've done the PMDG mouse option in the mouse manual... 🙄

I am reluctant to update my 737 until I see fluffy rabbits running around happily in the meadows again.

Please stick to the topic title. Discussion is about the PMDG 737. Other offerings should be discussed in their own topic.

1 hour ago, sloppysmusic said:

I suggest you read the thread I posted from the pmdg forums earlier, and this one actually, the xml has not been updated for this update so using it kills the EFB and MK states for final build they will almost certainly scrub that option from existence. 

Of COURSE I've done the PMDG mouse option in the mouse manual... 🙄

Edit... Oops, I quoted the wrong reply.

 

PMDG have quickly replied to my support ticket.

"We have identified the issue with the Mouse settings and it will be updated in the next day or so.  If you return to the default MS it should work again."

As mentioned previously, returning to the MS mouse templates didn't fix my blank EFB, I had to remove and re-install. If I'd kept the original files installed with the update rather than overwriting them, I could have restored those.

But the good news is that they will update the mouse settings 🙂

Edited October 26, 20241 yr by flyingscampi

3 hours ago, StoneDoor said:

Except that they did not. Just follow the steps in their manual and you have the "PMDG-mouse" behavior back.

I'm surprised that worked for you. You didn't get a blank EFB?

9 hours ago, vonmar said:

Thanks for the follow up.

I only have the -600 and -700.

Both had stopped updating Navdata at 80%. Many reporting the same problem.

Uninstall / reinstall did not fix the problem.

Currently I have both Uninstalled / Installed to the basic level (fresh PMDG downloads) without Updating via the Ops Center.

Both work ok but the Navdata is back to Cycle 2204 and naturally do not have the current Update.

Stuck right there.

This is the process I use to remove PMDG 737, Ops Center, Liveries, everything... (also likely to kill 777 if you have it.)

1. Uninstall 'PMDG 737-800 for MSFS' from Windows Control Panel

2. Delete these folders (if you have different models -600, -700 adjust folder names accordingly):

C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-738
C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator\SimObjects\Airplanes\PMDG 737-800
C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator\SimObjects\Airplanes\PMDG 737-800BBJ2
C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator\SimObjects\Airplanes\PMDG 737-800BCF
C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator\SimObjects\Airplanes\PMDG 737-800BDSF
C:\Users\<username>\AppData\Roaming\PMDG
C:\Users\<username>\AppData\Local\PMDG
C:\Users\<username>\AppData\Local\Temp
C:\Windows\Prefetch\PMDG 737-800 FOR MSFS.EXE-<xxxxxxxx>.pf
C:\Windows\Prefetch\PMDG OPERATIONS CENTER.EXE-<xxxxxxxx>.pf
C:\Windows\Temp

3. Delete these folders (your MSFS folder will be in a different location)
D:\MSFS\Packages\Community\pmdg-aircraft-738
D:\MSFS\Packages\Community\pmdg-aircraft-738-liveries

 

9 hours ago, vonmar said:

Thanks for the follow up.

I only have the -600 and -700.

Both had stopped updating Navdata at 80%. Many reporting the same problem.

Uninstall / reinstall did not fix the problem.

Currently I have both Uninstalled / Installed to the basic level (fresh PMDG downloads) without Updating via the Ops Center.

Both work ok but the Navdata is back to Cycle 2204 and naturally do not have the current Update.

Stuck right there.

what does  the  nav hub  cycle  say if its the latest  than update  the pmdg 600  and  700   using  the  update  nav  hub not  the efb  way,  see  if  that  updates  you 600  and  700  to the latest.  or  you can  wait  for  the  latest  fix  from pmdg

26 minutes ago, flyingscampi said:

This is the process I use to remove PMDG 737, Ops Center, Liveries, everything... (also likely to kill 777 if you have it.)

1. Uninstall 'PMDG 737-800 for MSFS' from Windows Control Panel

2. Delete these folders (if you have different models -600, -700 adjust folder names accordingly):

C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-738
C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator\SimObjects\Airplanes\PMDG 737-800
C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator\SimObjects\Airplanes\PMDG 737-800BBJ2
C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator\SimObjects\Airplanes\PMDG 737-800BCF
C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator\SimObjects\Airplanes\PMDG 737-800BDSF
C:\Users\<username>\AppData\Roaming\PMDG
C:\Users\<username>\AppData\Local\PMDG
C:\Users\<username>\AppData\Local\Temp
C:\Windows\Prefetch\PMDG 737-800 FOR MSFS.EXE-<xxxxxxxx>.pf
C:\Windows\Prefetch\PMDG OPERATIONS CENTER.EXE-<xxxxxxxx>.pf
C:\Windows\Temp

3. Delete these folders (your MSFS folder will be in a different location)
D:\MSFS\Packages\Community\pmdg-aircraft-738
D:\MSFS\Packages\Community\pmdg-aircraft-738-liveries

 

Not necessary.

56 minutes ago, flyingscampi said:

Edit... Oops, I quoted the wrong reply.

Ah no worries!

There have been several people worried about the mouse settings issue on the PMDG forums. Kyle R has been very understanding even if he is no longer involved in development there. A post from MK 'almost' confirmed that the mouse settings would be retained and the EFB issue fixed, not one at the cost of the other.

I say 'almost' because his statement could be taken either way:

ahh he has now clarified it will stay the same in 2020 but not guaranteed for 2024. This is a fair and acceptable policy IMO. If we want to buy a sim/plane it's our choice rather than taking away what we've already purchased and enjoyed:

MK: Keep in mind that things might change for MSFS2024. The SDK for VC interactions has changed, and it is not clear if non-standard mouse interaction is possible. We dropped the PMDG mouse thing for the 777 and it is unlikely it will be implemented in any new product.

 

2 hours ago, pete_auau said:

what does  the  nav hub  cycle  say if its the latest  than update  the pmdg 600  and  700   using  the  update  nav  hub not  the efb  way,  see  if  that  updates  you 600  and  700  to the latest.  or  you can  wait  for  the  latest  fix  from pmdg

Thanks for the follow up.

There is no longer a Nav Hub for the PMDG737-600 or -700.

 

Edit:

I see now PMDG asked NG to put PMDG back in the NG Hub.

I will give that a try.

 

 

Edited October 26, 20241 yr by vonmar

Back to Normal..

 

 

3 hours ago, Bobsk8 said:

Not necessary.

Unless you can't make the plane work any other way.

I've used it to fix a stuck cockpit (post last update), and the mouse problem (post this update), and it takes 5 minutes to delete the files.

 

51 minutes ago, Bobsk8 said:

Back to Normal..

 

 

Yes  , nice but might be a silly one but now i have the spinning PMDG thing on my tablet FO ? 🙂

Michael Moe

I have just noticed something. The version number of the PMDG 737 stated in my Navigraph Hub is v3.0.105 (which I believe is the updated version). However, I have not yet installed the update for the plane. Does the Navigraph Hub automatically state the latest version, or should it read the version number of the plane that is installed on the user's PC?