PMDG Forum Rules

1) SIGN YOUR POSTS. Since 1997, we have asked users to sign their real name, first and last, to all posts in the PMDG forum. We do this in order to keep conversations personal and familiar. You took the time to be here, we want to get to know you. This is one of the few rigid rules that we enforce regularly. We do so because we feel that forums in which users must engage one another personally are generally warmer, more collegial and friendly. Posts that are unsigned will be quietly removed without comment by the moderators, so to make your life easy- we recommend enabling your forum signature so that you never need to remember. Do this by clicking the username pull-down at the top right, then selecting "User Settings." You will find the signature editor on the ACCOUNT tab, about half way down the page. Look for "Edit Post Signature." Be sure to click the "Show Signatures" box.

2) BE NICE. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Treat everyone else in the forum with respect even when you disagree. If someone frustrates you, walk away from the conversation or ask for a moderator to get involved. Speaking of Moderators, they prefer not to be treated as "The Thought Police" but if any behavior infringes on the enjoyment of another user or is otherwise considered to be unacceptable in the moderator's judgment, it will be addressed in keeping with our view of ensuring that this forum remains a healthy environment for all simmers.

3) BE LAWFUL: Any behavior that infringes upon the law, such as discussion or solicitation of piracy, threats, intimidation or abuse will be handled unsympathetically by the moderators. Threats and intimidation may, at the moderator's discretion, be provided to law enforcement for handling.

4) BE FACTUAL: When you post, always be factual. Moderators will remove posts that are determined not to be factually accurate.

5) RESPECT COPYRIGHTS: Posting of copyrighted material such as flight manuals owned by Boeing or various airlines is not allowed in this forum. If you have questions related to copyrighted material, please contact a forum moderator for clarification.

6) RESPECT PMDG: We love to hear what you like about our products. We also like to hear what you think can be improved, or what isn't working. Please do tell us and we will always treat your feedback with value. Just be sure to treat the team respectfully, as they do put a significant amount of effort into building and maintaining these great simulation products for you.

7) RESPECT PMDG DEVELOPERS: All of the developers will spend some time here. Given the ratio of developers-to-users, it simply isn't possible for us to answer every post and private message individually. Please know that we do try to read everything, but developer workload is simply too high to manage personal contact with tens-of-thousands of users simultaneously. In most cases, members of the development team will stick to conversations in the forum and will not answer private messages.

8) RESPECT OTHER DEVELOPERS: PMDG has always advocated for a strong development community and we have many friends within this community. Every developer offers something unique that helps to make the simming community larger and more vibrant. We insist that you treat our friends respectfully.

9) RESPECT MODERATORS: Moderators have a tough job, and none of them enjoy having to stomp out negativity. If a moderator has to weigh in to keep a thread peaceful, please respect that effort and refrain from giving the moderator any grief.

10) If you require official support for any of our products please open a support ticket through the support portal,

11) This forum is designed primarily as a vehicle for the PMDG development team to interact with our customers, and for customers to interact with one another in a manner that is positive, supportive and assists in the general advancement of understanding the simulation and helping to make this and future simulations better. Any other use of this forum is not permitted, including but not limited to discussion of pricing policies, business practices, forum moderating policies, advertising of non-PMDG products, promotion of events, services or products that are not approved in advance by PMDG or any other topic deemed unacceptable by any forum administrator

12) HAVE FUN: This is the whole point of it all.
See more
See less

[03JUN22] PMDG 737 for MSFS Update to 3.00.0020 is released

This topic is closed.
  • Filter
  • Time
  • Show
Clear All
new posts

    [03JUN22] PMDG 737 for MSFS Update to 3.00.0020 is released


    Back in March as we began to introduce you to our new PMDG 737 for MSFS product line, I mentioned that we were going to fundamentally change the way we approach product rollouts by bringing the 737 to you as a rolling development cycle. The idea came about because all of us (well- nearly all of us!) at PMDG are DCS addicts, and DCS has done a very nice job of managing the challenges that come from having to manage multiple project profiles simultaneously. While there are many things to admire about the DCS team, one of their more admirable traits is being candid about the the pieces of things they are working on, the things they have planned, and giving regular progress updates along the way.

    Personally one of my favorite Friday morning emails comes from DCS. It has been a regular thing for a long time. Something to emulate.

    Starting back in March, we began to communicate to you our intent to take a similar approach and while many of you caputred the spirit of what we are after- some clearly have not. Obviously we need to try and communicate that a bit harder over the background noise. Still others have questioned "can PMDG do it?" The only thing to do is demonstrate by action. So we shall.

    The exciting thing about this change in how PMDG operates is that we realized early in our design process that some things in the MSFS world were just going to need to be done differently and that would take some experimentation, some learning and frankly, some mistakes along the way. In P3D world we could assign a single developer to a piece of the project and let him run. In MSFS world, this is highly inefficient, and greater progress is made by multi-disciplinary task teams working on specific threads at one time. It has taken some time to get the mix right- but two years later, we find this gives us the freedom to do things much more quickly. We think you will be interested to see what gets rolled into the entire 737 product line in the weeks ahead. Some things you are expecting, some perhaps you aren't.

    We anticipate this period will continue for the 737 product line through, at least October, and likely well into the 777 beta period that will start up after the first four 737 bodies are rolled out. Our plan during this period is to continue packing details and features into the airplane based upon user feedback, our own design goals and of course your comments and suggestions. That work continues apace- and I have a few updates on some of those things when we unveil the 737-600 a bit later on Friday- so check that post for some fun info! (It will go live in a bit)

    So lets talk about update cycles! Our original plan calls for bi-weekly updates that will bring in various bug fixes, corrections, improvements and new features as they clear testing and become available for public consumption. (I acknowledge that we are a week behind on that first update cycle, due to illness on the team. Some things just are what they are.) Beginning today, we anticipate some shifting back and forth between weekly and bi-weekly updates as we work through various details that we want to roll out to you. The goal is to give ourselves the flexibility to keep you up to date with the very latest without locking ourselves into a two week cycle "just because we said two weeks."

    To kick the process off: Today we have just released Build 3.00.0020 for the PMDG 737-700.

    This update comes with a number of changes and improvements, including updated models and associated textures, a significant update to the sound engine and dozens upon dozens of small tweaks, adjustments and improvements. The change list is as follows:

    PMDG 737 for MSFS - 3.00.0020

    0011282: [General - Documentation] Documentation - Remove mention of Keyboard command option in FMC until function restored. (hvanrensburg)
    0011289: [External Model - Liveries] Decal Mapping Error on engine cowlings (jbrown)
    0011336: [General - Documentation] Various Corrections in the Tutorial Flight Document (hvanrensburg)
    0011360: [External Model - Geometry] Touchdown Landing Gear Effect reversed laterally. (jbrown)
    0011327: [Systems - Electrical] External Airstairs should be allowed to receive power from ship batteries. (hvanrensburg)
    0011280: [Virtual Cockpit - Geometry/Textures] Various geometry and texture gaps reported by one very eagle-eyed customer. (vscimone)
    0011341: [Virtual Cockpit - Geometry/Textures] OFF text on GEN Panel incorrect (vscimone)
    0011354: [Virtual Cockpit - Geometry/Textures] Overhead Panel separation lines missing (vscimone)
    0011368: [External Model - Geometry] plug door pressure relief flaps appear doubled in some instances. (jbrown)
    0011307: [Virtual Cockpit - View Presets] View Preset zooms need adjusting (jbrown)
    0011249: [External Model - Geometry] N1 Disk transparent, when Rain/Snow WX (jbrown)
    0011292: [Virtual Cockpit - Geometry/Textures] Missing textures along base of windshield frame covers (vscimone)
    0011276: [Virtual Cockpit - Geometry/Textures] Triangle punch out in area over master caution creates a light gap in panel (vscimone)
    0011251: [General - Ground Operations] Fuel truck connecting function and transparent fuel panel when fueling door is open. (hvanrensburg)
    0011227: [AFDS - General] AP constantly micro trimming (emvaos)
    0011232: [External Model - Geometry] PIP options incorrectly connected to selection of LED lights option. (jbrown)
    0010547: [Sounds - External] External engine start bleed hiss sound loops incorrectly and causes other start sound layers to fail. (acholakian)
    0011350: [Virtual Cockpit - Geometry/Textures] VC Yoke clipping and backfacing geometry needs attention (vscimone)
    0011283: [General - Suggested/Missing Features] Displays should be able to function as pop-up 2D displays (vscimone)
    0011225: [Virtual Cockpit - Geometry/Textures] Trim wheel animation fails under certain circumstances (not related to rotation speed) (vscimone)
    0011312: [Virtual Cockpit - Functionality/Click-Spots] Alternate gear extention cords can be pulled throught the closed Alternate Gear door (abashkatov)
    0011194: [Main Panel - PFD] "Single CH" indication has green frame instead of yellow (abashkatov)
    0011302: [Main Panel - Aural/Visual Warning Systems] A/P disconnect light not operational when disconnection A/P (abashkatov)
    0011352: [Virtual Cockpit - Functionality/Click-Spots] LED Landing Lights not turning ON with clickspot (vscimone)
    0011325: [Virtual Cockpit - Functionality/Click-Spots] Flickering on various Instruments (vscimone)
    0011340: [Virtual Cockpit - Geometry/Textures] Missing Arrows Ovd and CB Light selector (vscimone)
    0011339: [Virtual Cockpit - Geometry/Textures] ALT CUTOUT missing part of a letter (vscimone)
    0011361: [Virtual Cockpit - Geometry/Textures] Pedestal ADF panel no backlighting. (hvanrensburg)
    0011338: [Virtual Cockpit - Geometry/Textures] CVR Light Plate missing text (vscimone)
    0011358: [Virtual Cockpit - Geometry/Textures] Screw alignment rudder floor panels (vscimone)
    0011367: [Virtual Cockpit - Functionality/Click-Spots] Wrong animation on Captain FMC Key (vscimone)
    0011369: [FMS - Route/Legs Pages] RTE page should show in the scratchpad the airport entered in REF page (emvaos)
    0011326: [General - Unsure] Loading Approach State on BDSF load the planes with blank screens and yoke hard over (rsrandazzo)
    0011366: [Systems - Electrical] Provisiom for APU auto shutdown if loading a panel state with APU online after loading C && D (emvaos)
    0011273: [Docs - Other General Observations] Typo in readme included with the Release candidate (rsrandazzo)
    0011279: [General - Documentation] Incorrect work folder paths in Intro (hvanrensburg)
    0011286: [General - Ground Operations] Air Start Unit is able to be called when Stairs 1L is connected (hvanrensburg)
    0011304: [General - Documentation] Introduction document Amendment - TO/GA (hvanrensburg)
    0011308: [General - Documentation] Introduction Document references to P3D license (hvanrensburg)
    0011319: [General - Unsure] ILS DME readout not correct (emvaos)
    0011353: [Docs - Need to Tell Customers This] Introduction refers to cabin light page in FMC. (hvanrensburg)
    0011357: [FREEZES - All Types] Sim freeze when using EBBR CIV5C (emvaos)
    0011315: [External Model - Geometry] Texture Mapping Issues MSFS 737-700 (jbrown)
    0011356: [External Model - Geometry] APU exhaust textures needs touch up (jbrown)
    0011363: [External Model - Geometry] Wing gap during flexing (jbrown)
    0011364: [External Model - Geometry] FWD Cargo hold gap (jbrown)
    0011343: [Systems - Flight Controls] Reduced AoA for stick shaker onset (emvaos)
    0011248: [FMS/AFDS - LNAV] Provision for successive DTO's and adding airways to start of STAR after STAR is defined(!!) (emvaos)
    0011196: [Main Panel - Aural/Visual Warning Systems] Below G/S warning should be inhibited below 200ft RA (abashkatov)
    0011051: [General - Unsure] Pane state save - When master lights switch is saved in DIM, lights still load BRT (abashkatov)
    0011337: [General - Documentation] Erroneous reference to 2D popup in tutorial (hvanrensburg)
    0011313: [External Model - Geometry] Need thumbnail for MSFS "content manager" screen (cbpowell)
    0011301: [External Model - Geometry] BBJ SSW - Missing tailpipe component R ENG (jbrown)
    0011291: [External Model - Geometry] Texture gaps engines (jbrown)
    0011266: [External Model - Liveries] negative pressure relief valve cut (jbrown)
    0011267: [External Model - Liveries] Strange texture on the left MLG door. (jbrown)
    0011076: [External Model - Liveries] Engine Texture Mapping Anomaly (jbrown)
    0011274: [AFDS - Roll Modes] Disable mouse wheel scrolling for HDG SEL Bank Angle limiter (hvanrensburg)
    0011277: [General - Documentation] Sound settings - Default volume levels and Active Spatial Sound should be set to NO in the documentation (hvanrensburg)
    0011270: [FMS - Setup/Options Pages] DISPLAY Options page 9/9 FUEL/CTRLS empty (abashkatov)
    0011263: [FMS - Setup/Options Pages] Change display order to options back to original (hvanrensburg)
    0011252: [General - Ground Operations] Air Start Unit colliding with Airstairs (hvanrensburg)
    0010749: [Sounds - Internal/Cockpit] Trim sound keeps getting triggered inflight (emvaos)
    0010840: [General - Engines] FS Engine takes way too long to start at high altitude (emvaos)
    0011216: [External Model - Liveries] Delta Livery Blue is too light (psterling)
    0011228: [External Model - Liveries] Fuse3 Mapping Anomaly (jbrown)
    0011180: [Sounds - External] Hydraulic Pump sound missing (acholakian)
    0011328: [Virtual Cockpit - Functionality/Click-Spots] Clickspots on FMC do not align correctly after change to PMDG mouse logic (hvanrensburg)
    0010678: [General - Engines] MSFS side - Engines take too long to stabilise to idle after engine start (emvaos)
    69 issues

    HOW TO UPDATE YOUR PMDG 737: The update is available via the PMDG Operations Center on the AIRCRAFT AND LIVERIES//PRODUCT UPDATES page. Click the update button and it will pull the update down and install it for you locally.

    IMPORTANT NOTAMS: There are two things we want you to know: First, this is a big update. Run it when you have a few moments to let it do it's thing. Second, our beta team found that for a few of them, the first time they ran the 737 after installing the update, the aircraft sounds did not play properly. We have traced this to the manner in which the sim caches sounds, and it can be easily corrected by simply running the airplane, then exiting back to the world menu and launching the aircraft a second time. For reasons we don't yet understand, the sim does not update the cache on the first run, but it does on the second launch and from then on you will be fine without further need to tinker. (We'll bring this up with Asobo to see if they have ideas to mitigate that problem in the future. It is a very minor nuisance but we'd still like to avoid it if that is possible on the developer end.)

    IMPORTANT NOTAM 2: The update is truly huge. It is out on a wide distribution cloud network and should give good speed to most users, no matter where you are geographically. If you find it gives you trouble, sit and watch it a bit. A few of the files are huge. If that doesn't work, you can always grab the installer from your account again. Not that updating via the Operations Center will normally be faster, but obviously internet connections around the globe vary quite dramatically- so we wanted to be sure you had options available to suit your needs.

    IMPORTANT NOTAM 3: One of our testers reminded me (in thread below) to remind you: The first time you run a C++/WASM project in MSFS, the sim goes through a ton of compilation process that takes some time. Not all updates will trigger this recompilation, but this one certainly will. Don't think that the sim failed, just let it do it's thing- and you'll be rewarded with a nice, optimized refresh on your 737. (Thanks, Steve- I owe you a bonus cookie at FSExpo...)

    Okay- that is all for this update... Time to build the next beta for the test team to look at so that we can hand it to you next week. And so the journey begins!

    Robert S. Randazzo
    PMDG Simulations

    Exciting! Thank you very much for all the work, that's one meaty update!

    Luke Carter | Flight Sim Content Creator & PPL Student Pilot


      I love this company. Thank you!!!

      Jeff Soule


      • rsrandazzo
        rsrandazzo commented
        Editing a comment
        Jeff- We love you too. :-) - RSR

      Thank you, sir! Nice meaty list of updates and tweaks. πŸ‘
      Herb Schaltegger - Father, husband, lawyer, engineer & getting too old for this $#!t. Do Not Taunt Happy Fun Ball!TM.


        Thanks for the update. Will the Optional Mouse Behavior have to be reinstalled or does the update not touch it?
        Dan Moore


        • rsrandazzo
          rsrandazzo commented
          Editing a comment
          Dan- Oh. Uh. Jeez. Can you maybe come back to me with a question I know the answer to? <flips a coin> It will work without needing to be redone. (If you find I'm wrong come back and shout... The guy I'd normally ask is away on his anniversary with his wife and as much as I'd love to pester him, it is likely that Mrs. Henning will reach out to The Lovely Dr. Randazzo and then I'd really be in trouble... - RSR

        • Wise87
          Wise87 commented
          Editing a comment
          Robert - I can confirm all the Behavior Mouse files are overwritten to MSFS default. I'll go back and replace them with the ones you provided for the left/right click option. Thanks Again.

        Also downloaded the update in about 2.5 minutes. Amazing.

        Jeff Soule


          Another note to consider with this Update.
          This update has updated many items, and as such, the INITIAL load into MSFS to sitting on the ramp will take a while....about 15mins for me. This will happen for each model the FIRST time you load it...including the 737 Pax, BDSF and BBJ. Do NOT think the load has stalled and quit the the progress, please.

          You guys are not used to installing many builds and having to remember this...the PMDG team and beta team however, we have it engrained in our brains, hehe.
          Regards, Steve Dra
          Click here to download my P3D, FSX, 2004 paints at Avsim
          Get my paints for MSFS planes at here


          • rsrandazzo
            rsrandazzo commented
            Editing a comment
            Steve- AH. Thanks for covering my six. Yes- you are indeed correct. This is a down-side to C++/WASM is that the sim feels compelled to rebuild the whole thing on you... Thanks for the memory job, Steve. Like you I'm so used to it that I don't think of it any longer. - RSR

          • Want2BFlyin
            Want2BFlyin commented
            Editing a comment
            I was just about to ask about this exact thing. Thanks for the heads-up.

          • Steve Dra
            Steve Dra commented
            Editing a comment
            No Problem Rob rsrandazzo! Its a scary memory much so that I've actually identified the exact location of the blue progress line where it pauses when it's doing its WASM thingy.
            Should my memory item be "flushed" as's been a few days since a new beta build, seeing the stalled blue line right there refreshes the memory location (34A45FFF in my particular cerebral memory container) instantly and then I take that time to grab another cup of coffee.

          Exciting! Thank you very much


            Super Robert .Thank you.
            Tomas Zima Prague


              thanks for the update robert.

              just a question, how about the gear switch (and the noise with right mouse click)
              and that the gear leaver stays stuck on a thrustmaster tca boeing and airbus pack?
              Harm Hartsuiker


              • rsrandazzo
                rsrandazzo commented
                Editing a comment
                Harm- Not fixed yet. It is in my workflow plan though. I will come up with something- just not sure how to make a 3 position lever listen to a two position switch while preserving the important fidelity of the system. If I could convince Asobo that pinging the sim 200x / second with the gear position switch is somehow affecting french wine production, I might stand a chance- but so far no luck. Gimme time- I'll think of something. - RSR

              • matrosov
                matrosov commented
                Editing a comment
                Not sure the right mouse click, the one in the beginning was related to sim command not really retracting gear and soundpack giving you gear noise at random points because it was confused. but if you abandon the half baked ingame controll UI and go with bridge like SPAD and start addressing plane specific events and variables gear thing with two position switch is easily resolvable. Gear up wait x milliseconds gear off PMDG specific events and you're done. Lever on stick stays up lever in VC stays off. It was plenty tedious for me to start playing with SPAD but now I'm very happy I did because I don't have to bother with UI profiles anymore and interaction is super smooth and effortless.
                Last edited by matrosov; 04Jun2022, 00:05.

              To clarify there is no fix for FPV or AIII runway alignment in the HUD?
              I'm sure it's a tough one, and maybe asobo's fault πŸ˜€

              William Bomfrein


              • rsrandazzo
                rsrandazzo commented
                Editing a comment
                William- We have tuned it a bit, but we don't find it sufficient to call it fixed. We continue to reach out to Asobo on the topic. No reply. We continue to envision new ideas to get around limitations. - RSR

              • bf03
                bf03 commented
                Editing a comment
                Thanks Robert, no reply is par for the course, huh? I believe your creativeness will emerge victorious, you might be missing some hair though.
                William Bomfrein

              Thanks, but what about the missing PPG paint sticker on the top left corner of the pilot's side window?

              Shoko Cho


              • asyncawait
                asyncawait commented
                Editing a comment
                As someone from Pittsburgh, I agree.

              Thanks for the update, Rob!!! I'm about to go fly right now!
              Jason Ellis
              Instrument Pilot wishing I was more.


                Originally posted by winglady View Post
                Thanks, but what about the missing PPG paint sticker on the top left corner of the pilot's side window?

                Was this reported to support?
                Chris Makris (Olympic260)
                PMDG Technical Support


                • JWarner32
                  JWarner32 commented
                  Editing a comment
                  I made a post about this within an hour of purchasing the aircraft...

                • Ralgh
                  Ralgh commented
                  Editing a comment
                  The only way to ensure the proper people are notified of an issue it to make a report at the support portal here:



                • rsrandazzo
                  rsrandazzo commented
                  Editing a comment
                  Either you posted just your name, or you shouted mine and failed to sign your post. Don't make me come in here with a hammer. I WILL YOU KNOW! LOL - RSR

                • jcoops
                  jcoops commented
                  Editing a comment
                  It's a sicilian thing

                Indeed a large changelog - thank you! Maybe I missed it, but I thought the pop-up screens would be in this update. Is it?
                Michael Leung


                  Originally posted by flightjunkie View Post
                  Indeed a large changelog - thank you! Maybe I missed it, but I thought the pop-up screens would be in this update. Is it?
                  It is

                  0011283: [General - Suggested/Missing Features] Displays should be able to function as pop-up 2D displays (vscimone)
                  Chris Makris (Olympic260)
                  PMDG Technical Support


                  • Jd_jay
                    Jd_jay commented
                    Editing a comment
                    Its something I tried, and they didn't pop out, do you have to be in windowed mode for them to work?

                  • Crabby
                    Crabby commented
                    Editing a comment
                    If the popups work as others do, you have to mouse over and then hit one of the ctrl buttons while clicking the mouse. Don't remember which.

                  What about the weak pitch/power ratio and the plane does not respect altitude restrictions in some auto pilot modes?
                  Pedro Guedes


                  • rsrandazzo
                    rsrandazzo commented
                    Editing a comment
                    Pedro- Take a read through the change list. If you find it there- then it was addressed. If you didn't, it is likely to appear in a future update. The whole point of the change list is so that you can see what was addressed. - RSR

                  RSR & Co. -- Very pleased to see that my many edits, comments, and just plain old nits and picks of the Tutorial Flight PDF made it into the new version!! Just let me know when you want me to scour the next document.

                  EFB? Too soon?
                  Dan Jaffe


                  • rsrandazzo
                    rsrandazzo commented
                    Editing a comment
                    Dan- Thanks for sending them in- and for the bits of humor that came along with them. Henning is on vacation or he'd thank you himself. - RSR

                  • Iadbound
                    Iadbound commented
                    Editing a comment
                    My pleasure.

                  Thank you so much - amazing work as usual team PMDG!


                    I'm just blown away by what PMDG accomplished with this aircraft and really appreciate the commitment to improving the product going forward. I do need to report, however, that I'm still getting the flickering PFD on the FO side after the update.
                    Jim Herrod
                    PMDG 737-700BDSF


                      Absolute pleasure already this machine, and now it's even better. Thanks alot, Randazzo & co! This is fantastic.
                      Christoph Linden


                        Great to see these fixes, liking the new PMDG develop and release cycles, great move.
                        Iain Colledge


                          Thanks very much for this update Robert, nice job.
                          Sergio Naiberg


                            Many thanks for the update Robert.

                            Nice to see the PMDG gang jumping on to the "two weeks" band waggon to!! it's a big thing on the DCS forums/discord as you are probably well aware!....has been for years!

                            Looking forward to the big reveal later.
                            Pete Simpson


                              Originally posted by JH2022 View Post
                              I'm just blown away by what PMDG accomplished with this aircraft and really appreciate the commitment to improving the product going forward. I do need to report, however, that I'm still getting the flickering PFD on the FO side after the update.
                              This is pending Asobo fix as it’s from their side
                              Chris Makris (Olympic260)
                              PMDG Technical Support


                                Now if this product had been released to the general public a year ago as I suggested, these extensive modifications and enhancements would have been discovered and implemented last year already! A huge "testing" team out there! Jokes aside, great update and thanks for the continued development..
                                Peter Webber

                                Prepar3D v5 & MSFS / Windows 10 Home Edition / CPU i7-7700K / MSI Z270 XPower Gaming Titanium / Samsung 960 EVO M.2 500GB / Corsair Vengeance DDR4 32GB 3000MHz / MSI Geforce GTX 1080Ti Gaming X


                                  Thank you Captain, see you tomorrow for some -600 action, (and nice to see an timeframe for the 777)
                                  Joe Colehouse


                                    Wow, someone has been busy at work πŸ‘
                                    Andrew Bolton


                                      Originally posted by cmakris View Post

                                      It is

                                      0011283: [General - Suggested/Missing Features] Displays should be able to function as pop-up 2D displays (vscimone)
                                      If the Pop-ups were included I can't get them to work. Please confirm.
                                      Harry Schraishuhn - System Builder

                                      I7-9700K @ 5Ghz, AORUS Z390 Master Motherboard, Corsair H100i AIO, AORUS 1080ti Xtreme, HyperX Predator 32GB, Samsung 1TB NVMe + 2 x 1TB SSD's, 27" LG 27GL850-B QHD Display, Cooler Master MasterCase H500, Cooler Master 1000 Watt PSU, Win10, Logitech X52 Pro


                                      • Jd_jay
                                        Jd_jay commented
                                        Editing a comment
                                        Did you try them in windowed mode?