PMDG 777 texture question

[flyinpilot212121 724]

Interesting ..first time I hear that in regards to a PMDG aircraft, they make fantastic add-ons

[micstatic 4,319]

I'm very happy with their depth of systems and such.  Love the 747 and the 737.  But fact of the matter is, their textures out of the cockpit and somewhat in it are lower quality compared to others.  The QW787 (minus the FMS) is way higher quality when it comes to the graphics department.  I say minus the FMS for 787, because I feel that is still slightly cartoonish.  Although, with the coming update it could be updated.  

[swiesma 625]

I am also surprised by this thread.

I own almost all PMDG stuff and the 777-300ER is still my favourite.

[F737MAX 5,601]

I bought the QualityWings 787 and used it extensively, then bought the PMDG 777. To say I was disappointed is an understatement.

It feels like a massive backwards step and much less immersive than the 787. Higher quality textures, checklists, moving map, EFB, PBR textures and more, means I find myself flying the QW product 10 times more frequently than PMDG's 777. How I interact and what I see when flying matters.

[eslader 1,783]

The QW787 is a real gem, especially at its price point. But it only models normal operations. You will not experience any failures in the 787. And it's not quite as complete in the systems modeling either. Every switch in the PMDG planes, save a very few unclickable ones like circuit breakers, works and does what it's supposed to do. If you want to connect the left and right APU buses, you have to press both buttons. In the QW, both buses are slaved together - press one and you phantom-press the other. In the PMDG planes, the dimmer knobs work. In the QW, they're stepped rotaries with maybe 2 brightness settings, and often they're just on or off.

That's not to say the QW is lacking. Especially for what they charge, it's an amazingly well-done plane, and I find myself flying it more than I ever thought I would.

 

As to the "cartoonish"  nature of the FMS, take a look at the real one. The QW version is closer than perhaps you thought:

 

[micstatic 4,319]

eslader.  Spot on.  I have to admit.  That picture really makes me realize I was being too hard on them calling it cartoonish.  I don't currently fly with any failures on, however the dimmers and function-less switches can be a slight annoyance. But like you I fly that plane far more than I thought I would. 

 

Back to the PMDG 777.  I can't help but feel ripped off considering their no refund policy.  I mean their website describes the airplane:

PMDG has once again raised the bar on visual quality with an incredibly detailed, accurate and functional virtual cockpit, hundreds of switch animations along with their accompanying sounds, a visually stunning exterior model accurate to the finest detail.

Nothing visually here could be considered raising the bar.  Does the 777-300 expansion package have the same quality textures, or was that redone?

 

[eslader 1,783]

You know, I'm not sure on the -300 question. I have both packages, and haven't noticed a marked difference in textures. But then I also only have HD monitors, not 4k, so that could be part of it.

As to the advertising copy, at the time it was written that was entirely true. They did raise the bar. That others (mostly them, but also Leonardo) have subsequently raised the bar higher doesn't change the fact that they raised it. The cockpit is, as they say, detailed, accurate, and functional.

Where I think you might be getting hung up is on that "visually stunning exterior model," but that, in marketing circles, is subjective. What's visually stunning to me might be junk to you. After all, at one time this was considered to be a really gorgeous house:

😉

At any rate, I sympathize with your disappointment, but I think it'd be hard to justify a refund based on false premises given that there are hundreds of pictures of the graphics online, not to mention pictures of it on the sales website. I would like to see PMDG go to a try-before-you-buy model where you get maybe 20 minutes of time in the plane to check it out. I actually think that would increase sales for them - it took me a LONG time to pull the trigger on the 747 because despite all the people here and elsewhere saying it's awesome, that's a boatload of money to spend on pixelcrack that you don't have first-hand experience as to its quality. If they'd had a demo model, they'd have gotten my money much sooner.

 

But all that's irrelevant - they don't and we know when we buy that all sales are final. We accept those terms and have to live with them even if we end up regretting our purchase. Sometimes that sucks.  Were I you, I'd fly it more. I do notice a step down in visual quality from the 747, but not as big of a step down as the 737 is. And I enjoy flying all 3 of those products. Sometimes the visuals can take a back seat when the simulation is good enough, and I think the -37 and -77, for me anyway, fits that description.

 

[Mace 1,926]

7 hours ago, F737NG said:

I bought the QualityWings 787 and used it extensively, then bought the PMDG 777. To say I was disappointed is an understatement.

It feels like a massive backwards step and much less immersive than the 787. Higher quality textures, checklists, moving map, EFB, PBR textures and more, means I find myself flying the QW product 10 times more frequently than PMDG's 777. How I interact and what I see when flying matters.

 

Well, the PMDG 777 is about 5 years older than the QW787 -- I hope you realize that the 777 is a 2014 add-on.

[F737MAX 5,601]

1 hour ago, Mace said:

Well, the PMDG 777 is about 5 years older than the QW787 -- I hope you realize that the 777 is a 2014 add-on.

Other developers seem to be well able to continually improve their products to keep them fresh. FSLabs keep updating their A32x series, QW doing likewise with their multiple aircraft offerings. Disappointing that PMDG chose not to allocate resources to do likewise.

Just my opinion. I don't expect it to be a popular one.

[Evros 310]

If your 777 looks worse than NGX, then something is wrong. NGX is a lot older and uglier. Maybe you should grab a picture so we can see if there is anything wrong with it. I also have 737-787, and I fly 777 the most. Systems are incredible and it still looks plenty good.

[Kilo60 660]

Are there any texture upgrade mods for the PMDG 777...?

[Mace 1,926]

1 hour ago, F737NG said:

Other developers seem to be well able to continually improve their products to keep them fresh. FSLabs keep updating their A32x series, QW doing likewise with their multiple aircraft offerings. Disappointing that PMDG chose not to allocate resources to do likewise.

You might want to check on PMDG's website, 777 subforum, before casting such aspersions.

[micstatic 4,319]

When I'm back I'll take a few shots.  I'm not sure why the 777 stood out as far worse than the 737 to me.  WHo knows.  But I'm also of the camp that they should be updating their products.  For the price they charge, one would expect them to be best in class in most to all aspects.  At the very least the expansion package should be updated.  

[F737MAX 5,601]

40 minutes ago, Mace said:

You might want to check on PMDG's website, 777 subforum, before casting such aspersions.

And you might want to realise that other developers manage to do more to update their aircraft in a shorter time frame. 

Below is the full changelog since P3D v4 compatibility.

Apart from making the 777 compatible with 64-bit P3D, the only other changes of note are the implementation of a rolling friction model and the creation of a dynamic lighting model.

Everything else is bug fixes and stability-related.

Hardly the stuff to go weak at the knees for. I find the texturing to be a weak point - I'm not the only person that thinks so.

BUILD 1.10.8886 (Released 30JUL18)

=====================================================
- 0000000: [FREEZES - All Types] Insertion of SID after selecting APPR that shares a common starting FIX (emvaos) - resolved.

BUILD 1.10.8871 (Released 27JUL18)
=====================================================
- 0006565: [FREEZES - All Types] CTD doing specific steps on route loading (emvaos) - resolved.
- 0006559: [FMS - Route/Legs Pages] Bearing /Distance on Fix page misaligned (mfrantzeskakis) - resolved.
- 0005062: [AFDS - Pitch Modes] Go around with a single float alt in missed approach (emvaos) - resolved.
- 0006554: [AFDS - General] Potential CTD on G/A Activation with float alt only waypoint in route (emvaos) - resolved.

BUILD 1.10.8448 (Released 12OCT17) 
=====================================================
- 0006507: [General - 2D Panels] Radio 2D panel memory leak (mfrantzeskakis) - resolved.
- 0006504: [Main Panel - General/Unsure] Manual date not advancing on chronometer (mfrantzeskakis) - resolved.
- 0006503: [Main Panel - General/Unsure] Chronometer date is local instead of UTC (mfrantzeskakis) - resolved.

BUILD 1.10.8443 (Released 12SEP17) 
=====================================================
- 0006364: [FMS - Functionality Problems(General)] Floating altitude waypoint disrupts behavior of A/P and A/T in some instances.
- 0004667: [AFDS] HDG REF suspend in polar regions and AFS mode changes on select - various issues resolved.
- 0004764: [FMS] CTD when deleting hold on active route from RTE page.
- 0000000: [AFDS] New, dedicated Mach climb mode routine for FLCH and VNAV SPD modes

BUILD 1.10.8414 (Released 27JUL17) 
=====================================================
- 0000000: [General] - Added CA PFD Pop-Up CTD Opt-In protection.
- 0000000: [General] - Improved protections against force exit CTD.
- 0000000: [Installers] - Installation stability improvements.

BUILD 1.10.8395 (Released 14JUL17) 
=====================================================
- 0000000: [Wheels-Brakes] - corrected broken reflexive latch on autobrake knob.

BUILD 1.10.8386 (Released 11JUL17) 
=====================================================
- 0000000: [Installers] - Updated installer to better handle run prerequisites, repair and modification capability. (rsrandazzo)
- 0000000: [General] - Eliminated a potential CTD based on drive location and pathing data (abashkatov)
- 0000000: [General] - Optimization.
- 0000000: [General] - Improvements to dynamic lighting.

BUILD 1.10.8378 (Released 01JUL17) 
=====================================================
- 0000000: [Performance] - Reverted exterior lighting to build 8333 due to performance/appearance problems. (jbrown)
- 0000000: [Installers] - Updated installer to better handle run prerequisites, repair and modification capability. (rsrandazzo)
- 0000000: [Sound] - Eliminated a potential CTD if no sound device is present (abashkatov)

BUILD 1.10.8363 (Released 20JUN17) 
=====================================================
- 0000000: Various improvements for Prepar3D v4
- 0000000: Implementation of rolling friction model
- 0000000: Updated braking logic to correct overtemp conditions error
- 0000000: Improvements to dynamic lighting model in Prepar3D v4

BUILD 1.10.8333 (Released 10JUN17) 
=====================================================
- 0000000: Compatibility update for Prepar3D v4
- 0000000: Rest of change list pending, please check back.

[Mace 1,926]

14 minutes ago, F737NG said:

And you might want to realise that other developers manage to do more to update their aircraft in a shorter time frame. 

Below is the full changelog since P3D v4 compatibility.

Apart from making the 777 compatible with 64-bit P3D, the only other changes of note are the implementation of a rolling friction model and the creation of a dynamic lighting model.

Everything else is bug fixes and stability-related.

Hardly the stuff to go weak at the knees for. I find the texturing to be a weak point - I'm not the only person that thinks so.

 

  Reveal hidden contents

BUILD 1.10.8886 (Released 30JUL18)

=====================================================
- 0000000: [FREEZES - All Types] Insertion of SID after selecting APPR that shares a common starting FIX (emvaos) - resolved.

BUILD 1.10.8871 (Released 27JUL18)
=====================================================
- 0006565: [FREEZES - All Types] CTD doing specific steps on route loading (emvaos) - resolved.
- 0006559: [FMS - Route/Legs Pages] Bearing /Distance on Fix page misaligned (mfrantzeskakis) - resolved.
- 0005062: [AFDS - Pitch Modes] Go around with a single float alt in missed approach (emvaos) - resolved.
- 0006554: [AFDS - General] Potential CTD on G/A Activation with float alt only waypoint in route (emvaos) - resolved.

BUILD 1.10.8448 (Released 12OCT17) 
=====================================================
- 0006507: [General - 2D Panels] Radio 2D panel memory leak (mfrantzeskakis) - resolved.
- 0006504: [Main Panel - General/Unsure] Manual date not advancing on chronometer (mfrantzeskakis) - resolved.
- 0006503: [Main Panel - General/Unsure] Chronometer date is local instead of UTC (mfrantzeskakis) - resolved.

BUILD 1.10.8443 (Released 12SEP17) 
=====================================================
- 0006364: [FMS - Functionality Problems(General)] Floating altitude waypoint disrupts behavior of A/P and A/T in some instances.
- 0004667: [AFDS] HDG REF suspend in polar regions and AFS mode changes on select - various issues resolved.
- 0004764: [FMS] CTD when deleting hold on active route from RTE page.
- 0000000: [AFDS] New, dedicated Mach climb mode routine for FLCH and VNAV SPD modes

BUILD 1.10.8414 (Released 27JUL17) 
=====================================================
- 0000000: [General] - Added CA PFD Pop-Up CTD Opt-In protection.
- 0000000: [General] - Improved protections against force exit CTD.
- 0000000: [Installers] - Installation stability improvements.

BUILD 1.10.8395 (Released 14JUL17) 
=====================================================
- 0000000: [Wheels-Brakes] - corrected broken reflexive latch on autobrake knob.

BUILD 1.10.8386 (Released 11JUL17) 
=====================================================
- 0000000: [Installers] - Updated installer to better handle run prerequisites, repair and modification capability. (rsrandazzo)
- 0000000: [General] - Eliminated a potential CTD based on drive location and pathing data (abashkatov)
- 0000000: [General] - Optimization.
- 0000000: [General] - Improvements to dynamic lighting.

BUILD 1.10.8378 (Released 01JUL17) 
=====================================================
- 0000000: [Performance] - Reverted exterior lighting to build 8333 due to performance/appearance problems. (jbrown)
- 0000000: [Installers] - Updated installer to better handle run prerequisites, repair and modification capability. (rsrandazzo)
- 0000000: [Sound] - Eliminated a potential CTD if no sound device is present (abashkatov)

BUILD 1.10.8363 (Released 20JUN17) 
=====================================================
- 0000000: Various improvements for Prepar3D v4
- 0000000: Implementation of rolling friction model
- 0000000: Updated braking logic to correct overtemp conditions error
- 0000000: Improvements to dynamic lighting model in Prepar3D v4

BUILD 1.10.8333 (Released 10JUN17) 
=====================================================
- 0000000: Compatibility update for Prepar3D v4
- 0000000: Rest of change list pending, please check back.

 

All factual, and all in agreement.  But I think your issue is with them, not me. 

I was merely pointing out that PMDG has an update in the works per their site, and therefore, your statement that they "are not allocating resources" is not fact.   Now, if they never deliver on said update, THEN you can go there.