Jump to content

Matt2218

Members
  • Content Count

    312
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by Matt2218


  1. On 2/23/2019 at 6:01 PM, rsrandazzo said:

     

    With you saying "NG3" and "Beta" in the same sentence now, I'm feeling kind of silly for re-buying the NGX for Prepar3D last week.

    Considering how good the 747 is, I will grab the NG3 too as long as you promise not to tell my wife what I've done here LOL.

     


  2. 18 hours ago, SierraHotel said:

    I use ToPs, and gives everything I need for a derated takeoff.

    https://secure.simmarket.com/tops-takeoff-performance-system-fsx-p3d.phtml

     

    3 hours ago, sosuflyer said:

    Can't believe I've never heard of that tool before.  Does it work pretty well,  and do the takeoffs feel realistic (flight deck angle, v1 stop distance and such). It's cheap enough I'll get it anyway.  Just never heard of it before 

     

    28 minutes ago, pracines said:

    QSim only gives you a choice (a wide range - a wild guess) of assume temps - no derates. I think the OP is looking for a utility that TELLS them derates and assumed temps like topcat does.   

    Paul is correct - I was looking for something that would just spit out a temp for me. Since it was only about $7, I went ahead and grabbed that TOPS utility from simmarket.

    It seems pretty basic and TBH that is what I was after...something better than just firewalling full TOGA all the time or blindly guessing. I think it is very clever how it reads location and weather data from the sim and provides the answer without much need for manual intervention.

    Thanks for the replies and tips!


  3. On 2/17/2019 at 12:11 PM, berts said:

    Simon has already mentioned the Final Approach Fix (FAF) in his earlier post. This position is particularly important on a non-ILS (i.e. non-precision) approach, because it is often the last opportunity a pilot has of ensuring their altimeter subscale reading is set correctly.  Assuming it is set correctly then the aircraft's altitude should agree with that shown on the published procedure.  However, if the altimeter reading disagrees by a significant amount then it could be potentially very dangerous to continue the approach, because you could be starting the final descent at a much lower (or higher) altitude than you think. 

    Sorry if I'm a little dense, but I know nothing about RNAV approaches yet. Are you talking about comparing the Radar Altimeter to the baro Altimeter here? How does one "ensur[e] their altimeter subscale reading is set correctly."?


  4. 32 minutes ago, Stearmandriver said:

    Nah, the -900ER does not fly like a straight -900.  There's grumbling when you pull paperwork and see you're in an old -900, especially if it's windy ;-).

    Therein lies the biggest difference - approach speeds are significantly inflated on the -900 for tail strike protection, so with flaps 30 + wind additive on a gusty day, target speed can be well into the 150s, which puts you close to flap overspeed/blow back. 

    The ER fixes this mostly artificially, with a two-position tailskid that extends with the gear, but there are definitely aerodynamic changes too... the straight -900 flies like a truck, the -ER has a much nicer feel. 

     

    Thanks Andrew, good to know but also kind of disappointing.

    After spending $120 to get effectively the same FSX product I already had for this new sim, I wouldn't be offended if PMDG threw in the -900ER or the raindrops etc. as a bennie for loyal customers, even this late in the game.


  5. Hello!

    I recently made the jump from FSX to P3D and bought the NGX (again, LOL).

    Are you guys flying the -900 much? If so, do you have any rules of thumb for setting assumed temperature for derated takeoffs? I have TOPCAT...any way to use that (ie extrapolate downward from 737-800 results or something?).

    Also, I recognize that the 900ER has greater capability due to higher weights and more exits, but otherwise the 900 flies like a 900ER (assuming the short field package option is selected), right?

    I'm not obsessed with 100% fidelity with the 900 model, just looking to fly it like a 900ER on shorter routes with some degree of realism. Welcome your thoughts...

     

    Matt Smith

     


  6. 1 hour ago, Tony747-400 said:

    Hi.

    According to the FCOM page 10.2 Limitations Section the passenger variant Max Take Off Weight is 394.625KGS

    On the Payload screen of the FMC it shows a Max T/O weight of 385.6 KGS a shortfall of 9000 KGS.

    Also there is a small difference in the  MAX ZFW. FCOM says 244.9 KGS and the max you can enter via the FMC is 242.7 KGS.

    If anyone knows why this is, especially the 9000KGS difference in Max T/O weight I would be interested to know.

     

    Do you have a fuel tank in your horizontal stabilizer?


  7. Stephan;

     

    I think the problem with your method is that when you save that pmdg_737ngx_tail.psd as .jpg or as a 24-bit .bmp you are losing the alpha channel altogether. That is why you are continuing to see a bright tail and engine at night. The pmdg_737ngx_tail.dds is different from the fuselage textures because the alpha channel controls the night lighting, whereas on the fuselage it controls the transparency of the window openings.

     

    That is why there is no need for pmdg_737ngx_tailnight.dds.

     

    Once you are done editing pmdg_737ngx_tail.psd in photoshop...just 'save as' a 32-bit bitmap (dont need to flatten)...this will preserve the alpha channel that should already be in place. Then you can use whatever other program you like (dxtbmp?) to convert the 32-bit pmdg_737ngx_tail.bmp to .dds dxt5 on your windows machine.

     

    If you want to confirm what I am saying, use dxtbmp or something to look at the alpha on your current pmdg_737ngx_tail.dds...I'd bet money that it is all white, which is allowing all of the light and color to shine through at night.

     

    As a last resort I'd be happy to just make the .dds for you if you want to upload the .psd somewhere :)

     

    Good luck!


  8.  

    Maybe some developers can explain why this file has a layer 91 in the Paint Layer Group and what this Layer 60 in the vertical tail group is about.

     

     

    I don't think layers 60 and 91 matter at all.

     

    I think what you need to do is get back to the point where your photoshop looked like this:

     

    http://postimg.org/image/rt6t4kbuf/

     

    Then, save the .dds DXT5 file and it should look fine in the simulator. When you display the alpha channel in Photoshop it makes everything look pink and crazy but that is OK. The final paint will not be pink.

     

     

    Next to that I discovered that there is a vertical stabilizer group in the fuselage master PSD file. What is this for? Should I apply the tail livery there to get a better result with the night lighting? But this couldn't fix the issue on the engines. I assume the vertical tail group in the fuselage master PSD file is just for proper location of the paint if it continues on the tail coming from the fuselage.

     

     

    You are correct...the tail in the master PSD is just for lining up.


  9. Stephan;

     

    I don't have the answer to your specific question regarding the layers...but I suggest that you look at your repaint at night with no "pmdg_737NGX_tailnight.dds" at all. As far as I can tell it adds no value, and few if any of the repaints that I have seen (PMDG liveries from the Operations Center, Goldstar Textures etc.) even have it in the texture folder.

     

    I pulled 'tailnight' out of one of the default liveries for comparison:

     

    WITH tailnight:

     

    WithTailnight_zpseb5yt3bx.jpg

     

     

    WITHOUT tailnight:

     

    WiithoutTailnight_zpsob7n4lke.jpg

     


  10. I'm not an expert, but as I understand it when you select either sids or stars the FMC will leave a discontinuity between that and your core route on purpose...forces you to look at how they link up and make an intentional action to clear it. Google "clear discontinuity" for descriptions/tutorials on how to clear it.


  11.  

     


    Hello Matt,

    My full name? Oh! sorry, I don't want to be hidden behind a Pseudo or avatar, but as I am French, my name is Jean-Jacques BLIN, and as it's very long, all my friends write JJ my initials. So, I did not mean it , because I 'm used to sign like that. So now, I will write Jean-Jacques. But I am sure the next time, it wil be you who will answer JJ And EMI350 is my callsign in my virtual company on IVAO.

     

    No problem! Easiest thing to do is add your name to the "Signature" block at the bottom.

     

     

     


    For the paintkit, I agree with you, the best soluce is to export the Alpha channel from the default plane. But I did not tkink do do like that and I have painted my own, window, by window...

     

    I think I did the same thing in the past :angry:  :(  :blink:


  12. Hello,

    I download the Paitnkit of the 777-200 and all seems to be fine except there is no thing un the Alpha channel layer. No cabin window!

    The Paintkit of the 737-700 is ok. The Alpha channel is good.

    Can you explain me?

     

    JJ EMI350

     

     

    JJ - just a heads up, we have to put our full names in these forums.

     

     

    I'm not at my flight simulator computer right now to check my -200LR kit, but something you could do to solve the problem is export the alpha channel from the default PMDG 200LR .dds textures and copy that into your paint kit alpha channel.


  13. If you have the registered version of FSUIPC you can configure keys or joystick buttons to access the various camera views (I have mine keyed to a hat switch on my yoke). I don't know if it is possible using the standard FSX controls setup.


  14. Also, have you configured the NGX FMC to automatically detect and set the FSX Localizer course? You can find that option under 'Simulation' settings.

     

    I believe that having the wrong ILS Course set in the MCP (due to the FSX airport data not matching the charts and/or Navigraph update) will cause this problem for the PMDG planes.

×
×
  • Create New...