JohnSmith

Before I say anything else, let me just say that I seriously respect the work that PMDG does for the community. I own the majority of their products and think that they're almost incomparable to other addons at the moment. With that said, I am very disappointed to learn about the pricing for the P3D version of the 777. I know the different licensing structure makes it difficult to price these products competitively, but I just don't understand why other developers can release free or heavily discounted P3D versions of their aircraft, yet PMDG cannot. With the price as high as it is, I fear that PMDG will put too much work into a product that nobody will be able to afford. 

If I had ANY authority on the subject, I'd say that if there is a similar pricing structure for the 737, 747, and J41, switching to P3D will not only be a serious financial burden on us simmers, but it will also negatively effect PMDG in terms of financial success.

You've missed something. Despite being an option on the REF page of the FMC, the selection is non-normal (there are a few situations in which it is specified by Boeing, but as part of non-normal procedures), thus the warning.

 

If, for whatever reason, you want to land with non-normal (other than 25 or 30) flaps, note the FLAP OVRD switch above the gear handle.

Interesting how the option would still be included in the FMS. Oh well. Thanks for the reply.

Afternoon everyone. I would like to ask the frequent flyers of the PMDG 777 a brief question about approach flap selection. Yesterday, I was just about to start my approach into Frankfurt. I selected flaps 20 in the FMS and verified the selection when I went through the landing checklist on final. However, just a few hundred feet above the ground, the GPWS began to shout at me, "Too low! Flaps!" Of course, this warning prevented the altitude callouts and my landing was quite rough. I've never had this issue when using flaps 25 or 30. Is this a bug or have I missed something?

Hello all,

I'm in the process of planning an IFR flight from KATL to KFLL. In the route that I obtained from FlightAware (shown below), there is a short section where, according to the semicircular rule, I should be cruising at a different altitude. I'm wondering how this situation might be handled in the real world. Would a plane be asked to change their altitude after a turn in order to remain in constant compliance with the semicircular rule? Or, if there is no presence of traffic, would the plane simply stay at their original altitude?

Route: https://i.imgur.com/WO9ESvv.png

After a bit of reading, I have made a few discoveries. Here's a section from the 777 FCOM under "Fuel Operations". I have excluded irrelevant details.

Before start, the main tank pump switches should all be pushed ON.

 

[Option - English Units, 777-200, with pump logic revision]

Before start, with center tank quantity more than 7,500 pounds, the center tank pump switches should be pushed ON.

 

[Option - Metric Units, 777-200, with pump logic revision]

Before start, with center tank quantity more than 3,400 kilograms, the center tank pump switches should be pushed ON.

 

[All models]

During flight, when the FUEL IN CENTER message displays the center tank pump switches should be pushed ON, when the FUEL LOW CENTER message displays the center tank pump switches should be pushed off.

This is section 12.20.3 in Volume 2 of the PMDG 777 FCOM if anyone wants to have a look at the entire page.

Hi Stephen,

 

I'm not 100% this is correct as I haven't seen any info it, but I'm guessing you'd do a random route until 40W, and from 40W you'd join a track, and your clearance would consist of a random route and a track.

 

NAT means North Atlantic, not North Atlantic Track as many people think. Check the glossary of terms in ICAO NAT document 007 (page 14). It's sufficient to refer to them as a "track", e.g Track A

 

 

Hopefully that'll help you out a bit. If anyone have any info on how they do this real life (clearance wise), that'd be lovely so we could use it on Vatsim as well

 

 

Anders

I did a lot of research but couldn't find any information as to how this situation is handled in the real world, but that makes the most sense. Though, I don't really see the point of having a track start in the middle of the ocean. Oh well.

Fellow 777 pilots,

I've recently started flying longer routes since the release of the 300ER. However, I am somewhat perplexed when it comes to the operation of the center fuel tank. On some routes, there is barely any in the center tank. Maybe 4000 kilograms. In this situation, using the center pumps on the ground produces a "Fuel Low Center" EICAS warning. However, if I leave them off, a "Fuel In Center" EICAS warning is displayed once I am established in my climb.

Does anyone have any information on how to properly operate the center fuel tank when in this situation? I know the 737 center tanks are meant to be switched on after 10,000 feet if there is less than 5,000 pounds or something like that. Does the 777 operate using similar rules?

Thanks

Hello. I am currently in the process of planning a flight from EGKK to KMCO in PFPX. However, I noticed that the airlines use a NAT that is pretty far south. I'm currently looking at NAT J. This track starts in the middle of the Atlantic. An airliner that recently flew this route actually used the first two waypoints of NAT F before deviating to the south to cross via NAT J. This is shown in the image below. 

How is a clearance obtained from ATC to fly these half NATs? Is it normal to simply hop straight to the middle of the Atlantic and then join a NAT? I am many well confused.

Hello everyone. I am aware of the infamous joystick disconnect issue that has plagued the majority of Windows 8 users. Well, I'm experiencing a rather unique variation of this issue that I have yet to see other users of the PMDG 777 discuss.

My controls only disconnect when using the PMDG 777. This is usually a result of switching to another window and switching back to FSX. The only way I am able to fix this is to launch the task manager and quickly switch back to FSX. This usually works, but can also result in FSX crashing. I know there are several proposed remedies to this issue, but I'm trying to figure out if they actually apply to me.

Has anyone else experienced the joystick disconnect bug with the PMDG 777 only? Did you fix it? How?

Any assistance would be greatly appreciated.

Damian recently posted a promising update to the support thread on the HiFi forums.

We were finally able to duplicate this, and have things mostly narrowed down and believe this is due to current data where certain METAR stations are reporting/vs not reporting and affecting interpolation source computations. We are also able to confirm that SP1 has indeed solved this issue through the various adjustments/improvements/fixes we have made. 

 

We are working hard now to expedite SP1 for release, most likely as an open beta, sometime around Monday next week. We could do an HF for this, but internal testing and releasing this would likely not occur any quicker, and would only further delay SP1.

 

We apologize for the inconvenience this issue has caused and we will do our absolute best to get this resolution in your hands ASAP.

I have been receiving these errors as well. This has been a pretty common issue as of recently. Considering how widespread the problem is, I suspect the program is being given bad data by the ASN servers. There's a support thread on the HiFi forums. One of the developers has been suggesting potential fixes.

http://www.hifitechinc.com/forums/showthread.php?3438-ASN-Error

To all: Please try the following to help isolate:

- Reset your databases to default (tools, Edit Station Database, Reset to default - for weather stations and airports)
- Turn off VATSIM option in ASN settings
- Try without a flight plan (if this is caused by the flight plan, please attach .PLN)
- If using PMDG 777SP1, make sure you have auto load simulator flight plan off in ASN settings
- Please make sure to post your entire error report here if you continue having the issue


Thank you! Hope to get to the bottom of this soon.

Lot's of people have been getting errors like this throughout the past couple of days. There hasn't been much of a response from the HiFi team. I suspect it's the ASN servers feeding the program corrupt data or something like that.

It's out!

http://www.precisionmanuals.com/ProductCart/pc/viewPrd.asp?idproduct=101&idcategory=

My calender says it's Junetober 32nd. Hope it's released soon.

Yeah I'm seeing the same thing on my calendar.

Fantastic news! Glad you're back in action, Robert. Really looking forward to SP1 and the 300ER. Still have plenty of summer left to enjoy the two products.

All these flight simulation forums are so pessimistic and full of argumentative users with the exception of a few. It makes me sad. :(

Just to get back to the OP.

 

I think what we would like to know is, based on the beta testers systems, is there any difference in performance from running the original T7 to running the T7 SP1.  

 

Simply - have any of you found there to be improvements in performance on what you HAD to what you have now.

 

Hirdy

Yeah I came back and noticed there was an entire debate about VAS. I feel like I'm at fault haha.

Have you tried no frame rate lock Stephen? No internal limiter and no external limiter, no limiter of any kind.

 

Huge frame rate increase for me and others. No stutters.

 

Seems some set-ups can handle it and some can't.

 

I get very high frame rate, but that's because I keep sliders at a sensible level and run with only GEX, UTX and ASN.

Yes I've discovered the luxury of setting the FPS limiter to unlimited. Made a huge difference for me as well, even in the 777.

Are there additional options for configuring the performance of the PMDG 777? For example, you could alter the resolution of the VC etc in the NGX.

I would love having this option. My PC is fairly beefy so I don't understand why I'm receiving the performance issues that I am, but I certainly need more frames in the T7.

It seems like it's running better, but it all depends on how you've configured your own system, honestly...

Heh. I've never understood FSX performance. All other PMDG addons work quite well. I guess I'll just have to wait and see how things play out with the update. Thanks for the reply!

Afternoon everyone. I would like to ask the beta testers of the 777 SP1 if they have noticed any performance improvements compared to the current release of the 777. I've always encountered performance issues with this addon and hope that the said issues are remedied with the upcoming update. Let me know. :)

Thanks,

Stephen Hobson

There must be something wrong with your installation of the airbus as hundreds have no problems running it.  It does use a lot more resources than normal though.  You probably should check with Aerosoft and submit a ticket.

 

I would run Process Monitor first though and make sure it is the airbus causing the problems.  You can download Process Monitor from the Internet.  I fixed a major problem with my system by using this program.  I would start it up just before takeoff (you have to turn it on after FSX is at least at the Startup screen so it can "see" it).  Once open, you need to click on Filter.  Change Architecture to Process Name and then go to the blank space and scroll down to FSX.exe then click on Add and then OK.  Process Monitor should now be showing only FSX stuff loading.  Now go to full screen and go fly.  During the flight I wrote down the time I saw a "glitch" in the flight, like a one or two second stutter.  Of course, if it freezes or CTD's, write down the time then you need to get to the Process Monitor and click Ctrl+E.  This will capture all the events that occurred during your flight session.  Now you can scroll through to the time(s) you saw a glitch or FSX froze up or crashed.  Just remember this program is not going to tell you "here's the glitch".  You have to figure that out yourself.  When I saw my fps going from 50-60 fps to suddenly 6 fps, I wrote the time down.  I think you'll be able to see what's a major glitch and what is not. 

 

Best regards,

It turns out the issue was far easier to solve than I had originally anticipated. All I had to do was run FSX in compatibility mode. Thanks for the help.

That's probably the problem then.  You need to download and run NvidiaInspector and set the settings as shown in the AVSIM FSX Configuration guide (see link in my signature).

 

If your FSX graphics are set "conservatively" with nothing to the max, then it is a problem with your Fsx.cfg.  Rename or delete it, restart fsx and let the config rebuild.

 

Best regards,

I just tried both Nvidia Inspector (using recommended settings) and let FSX re-compile an fsx.cfg file. Unfortunately, the problem persists.

Is it possible that this is simply a hardware problem? Maybe something in my case will simply not run the Airbus properly. That would rather odd considering the fact that all other addon aircraft run flawlessly.

Edit: I did look at CPU activity while the stuttering took place. No jump. All seemed normal.

Is FSX freezing or stuttering?  Sounds to me like it's stuttering which means you might have your AA Supersampling setting turned off or it is set too high.  You cannot have your FSX settings set with all sliders to the right (max).  Your system is not good enough as FSX will bring the best most powerful systems down.  I have a Haswell i7 4770K with a GTX 780 video card.  FSX freezes (locks up) if I turn all of my FSX settings to the max including high Autogen.  FSX was not made to have all sliders moved to the right.  Tweaks will also destroy your enjoyment of FSX.  I have none but have tweaked the LOD_Radius and set it to 6.5 and set my Texture_Max_Load to 2048.  If I had all of my fsx settings set to max with those two "tweaks", fsx would be a slide show especially if I had real weather and a high demanding resource killer aircraft like PMDG or Aerosoft.  Nice eye-candy but you have to modify your settings to use them.  I don't know what Aerosoft recommended for settings but I would follow those as closely as possible. 

 

You might want to check out your Event Viewer for any errors too and get those fixed (see the AVSIM CTD Guide for procedures on how to do that).  I would also check out the section for fixing freezes in the CTD Guide too.  Excellent advice!

 

Best regards,

I don't use any external tweaking tools so I don't have the ability to modify the supersampling value. My graphics in FSX are set fairly conservatively. Nothing is set to the max. Most sliders are in the middle area.

Auto-save is disabled is FSUIPC. The issue persists.