Pmdg 737 Hud
Ceola Roefaro
Do we know the real answer why the 777 is delayed over and over. When Rob was speaking on you tube video he was very confident it will be release within 2 weeks and 2 months and he said around one month I believe. Now, it seems like there is no date in sight. I know they are adding polishes apparently but the whole 777 hype is dead for me. It was an overkill with the promised "oh its coming very soon, not too long now, its on approach", etc...
- I also *think* he said during the stream that RF legs may be a close follow on to release. They changed that to a launch feature. This is the right move since the whole RF legs thing isn't something they can go live with a second time.
- The delay of SU 15. Now, yeah. Mattijs said SU15 didn't impact their release date. Now, most things Mattijs posts about he is wrong (see, the two mentions of a "secret project" that got swept away). Now, it's also true that it didn't matter since their original schedule was after SU15 anyway. But when that got pushed.
- They are in a fun position now that they want to get the "free" advertising from the streamers, but in a few weeks most of them are closing up business to go to Expo. They are going to want the Q8 Pilot, CptCanada, Jeff Favignano etc to do their own hype streams to get viewers. Does this matter to any of us? No. But little of these things target us.
- It's also likely they've just hit enough weird bugs and things on the polish pass and they want this to be in good shape. They have a lot on the table with this release. Fenix has upped the game for what people expect from a study-level sim. Plus, I imagine PMDG wants to show they release a similar product.
- It also amazes me that after all the flack Fenix got for missing two deadlines, and the whole "weeks not months" but, that another dev won't learn from that mistake and give their version of "weeks not months."
Also, after how bad the launch of the Ini a300 was, with frequent hot fixes, patches, overloaded support, I have zero desire to go through that again. I'm ok with them releasing a plane that just works whenever it is ready. It's not like I am bereft of choices to fly.
To be quite frank, there is no "delay" here as PMDG never promised any dates.. RSR might've given guesstimates earlier, but they've always maintained it'll release when they feel it's ready. Only thing they've promised is an announcement two weeks before release.
Hype is ultimately what me make of it and let ourselves get caught up in or not, so sure it can come alive or become dead for whoever. IMO it's some in the user base (and flight sim media) who've whipped themselves into too much of a frenzy when awaiting new releases, especially from top tier developers like PMDG.
Now iniBuilds, they're masters at building hype and anticipation, and they own that ? PMDG on the other hand is now going out of its way to tell people to not read too much into every little thing (including facebook photos changes which some users immediately took to mean "on approach"). PMDG just naturally draws intense attention, anticipation, scrutiny, and everything else under the sun from users, and ultimately it just goes to show how much of a player they are in the add-on scene.
Latest example of PMDG trying to mitigate hype in advance:
-forum/general-discussion-news-and-announcements/297690-29may24-system-service-notice-not-a-777-release-indicator
In preparation for the upcoming 777 release, we have had our infrastructure partners doing some audit and preparation to manage the expected operational tempo for our public facing functions.
We are about to roll in some upgrades, and that will necessitate taking down some back-end systems temporarily as we migrate them across mirrors and other systems. There will also be short outages of a minute or two occasionally as we test various mechanisms to ensure everything is working as expected.
We will experience down-time for all license and distribution related functions at random intervals during the period of 30MAY24/0000Z to 31MAY24/2359Z.
Outages should last anywhere from a few moments to a few hours as systems are brought into conformity and tested for appropriate response.
Please do not construe this as a sign that we are about to release the PMDG 777-300ER. I promised we'd give you two weeks advance notice and that promise remains.
If they are seeing this problem with the 777 on their test systems, or even if there's a chance they could have this problem, then I'm sure they'd concentrate on isolating the error and fixing it before release. Can you imagine the PR nightmare if they release the eagerly-anticipated 777 only to have large numbers of people not even able to authenticate the product after purchasing it?
In 20 years dealing with their development cycles I can't remember a single time where they released even closely to his estimates. He is ALWAYS at least 6 Months off. And on avarage something like 8 months.
At this point I will almost certainly wait for MSFS2024 for the 777. It is summer now and I am out and about quite a bit with less time focused on simulation. With the new release likely only three to four months away, it seems to me to be a good time to hold off on purchases now and see what the future holds, let the dust settle and then pick up again in the fall.
And yes those of us who have been around for a long time know that release talk from PMDG is really just water cooler talk and should be roundly ignored. Until they put a firm, very specific date out there it is just talk.
PMDG on the other hand is now going out of its way to tell people to not read too much into every little thing (including facebook photos changes which some users immediately took to mean "on approach")
This is after they realized they completely screwed up the beta announcement and the expectations game. They're backpedaling because the development timeline has slipped. By the time this gets released, it will have been at least half a year since the beta announcement in December 2023. I doubt they intended that.
My guess is ita feature creep. They tested the waters by dropping a few pics and videos, those did not get the response they had hoped for. Then the whole rf leg drama happened, they conceded and added the fix to the release. Then fenix released their external engine simulation and graphics updates, blew pmdgs engine simulation away, maybe they are tweaking that too. (Did you know the 737 egt behavior is totally fake and unrealistic, and backwards? Maybe they will fix that in the 777). Inibuilds included visible tire and brake wear on their a300, now all of the sudden the 777 will magically have that too. I think they are starting to realise the competition is catching up and dont want to miss the mark with the 777. I think that is a good choice on their part, its too bad it took them so long to catch on that it blew their time line away.
So after messing with this for a few hours, I went into the working folder in the MSFS packages folder, and there was a nav folder in there. C:\Users\XXXX\AppData\Local\Packages\Microsoft.FlightSimulator\LocalState\packages\pmdg-aircraft-737\work\NavData.
Funny you mention this fix as I found it posted somewhere else not long after posting this - and indeed deleting/removing RWY DATA file fixed my issue immediately. Not sure why it went from working to not - but I will keep this in mind for future Airac updates. Cheers!
So I have build a homecockpit using old controllers and desktop aviator circuit boards. The problem I am having is that Fsuipc7 recognizes all the buttons and switches but when I assign a preset from the list, it will not actuate the assigned switch.
For instance, I assigned the battery on/off preset from the drop down menu for buttons and switches using the preset pmdg 737 list. Fsuipc sees the switch and assigns it the correct controller ID. Yet nothing happens in the cockpit.
The presets use calculator code, and much of the calculator code uses the custom events, as well as lvars. The custom events/controls for the PMSG 737 in MSFS use the Rotor Brake control, with the parameter indicating the actual control/event. You can see the parameters used by looking at the calculator code for the presets (in the events.txt file, or, better, on the MF HubHob site ). PMDG have not published the SDK yet - this should come in the next update, due any day now.
I don't know. You need to work out if its not configured properly (i.e. the preset calculator code is not being sent to the FS) or if it is the preset/calculator code that isn't working correctly. For the former, I need to see your FSUIPC7.ini and FSUIPC7.log files, the latter with Event and Extras logging activated, and with Debug logging enabled in the WAPI (add the line LogLevel=Debug to the [WAPI] section of your FSUIPC7.ini file). If its the latter, you need to ask about this on the MF Discord server.
Layman's term procedure...in button and switches, select the rotor brake option in the dropdown list. Have the log window open and see what it logs when you click on the switch you want to manipulate in the cockpit. The log will show you the name of the switch (I.e. yaw damper) and it will show a 6 digit number such as 26502. That's the number you put in the "parameter" box underneath the drop down list.
Logging is one way to determine the parameter, otherwise you can use the SDK header file. This has not been published yet, but you can use the P3D737 header file if you have that. The SDK for the MSFS PMDG 737 should be published in the next update. There is a guide in the FAQ section on how yo calculate the Rotor Brake parameter codes:
4a15465005