Matt2218

NZAA uploaded just now. KBOS too for all those Patriots/Red Sox fans out there!

That's as far as I understand it. Every time I have encountered the problem it's been due to a helipad (or water runway in the case of KBOS!) that is its own airport in the sim.

I actually fixed NZAA already but forgot to upload it...will do that soon as I get a minute!

I'm not sure TBH...let me know the ICAO and when I get a minute I can see if I can kill it.

As crazy as it sounds, the problem is caused by nearby helipads that are their own "airport" in the sim...for some reason they conflict with the command to operate the jetway. So the solution is to just create a new airport OF THAT HELIPAD and click the 'delete all helipads' command in the properties, then build. It actually takes less time to do than it took me to describe it. The result is that with the helipad deleted, the jetway command works normally at the main airport, whether it's a default or addon. Good news is, if you check Flightsim.to (MattS2218 is my username there) you'll see that I've already uploaded fixes for KBDL, KJFK, KMCO, KMIA, KORD, LEBL, LEMD, LIRF, and SVMI. Somebody mentioned SBGR and I'm going to look at that tonight. If you find any airports that aren't working for you, let me know and I can probably fix it quickly!

I figured out how to disable the helipads in the scenery using Dev Mode. Copying a simple scenery folder into Community solves the problem! Check Flightsim.to for my upload of LEMD...I'll check out LFPG and fix that too if I can. Edit: I just tried a few gates at Charles De Gaulle and the jetways appeared to be working OK. If you have a specific terminal or gate that you want me to check, let me know.

I'm late to join this thread, but for such an overall brilliant series of simulators it seems like the people at Asobo don't actually play their own game sometimes.

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!

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. You are correct...the tail in the master PSD is just for lining up.

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: WITHOUT tailnight:

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.

No problem! Easiest thing to do is add your name to the "Signature" block at the bottom. I think I did the same thing in the past :angry: :( :blink:

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.

LOL. The story of my (virtual) life. Spent hours trying to figure out why Ray Smith's KJFK scenery wasn't working right only to discover that I had failed to copy over the relevant OBJECT file. "Operator Error" is real. And I am the operator.

My pleasure, Bob - enjoy!

I put together this fictional repaint of the Q in Delta Connection colors - uploading to AVSIM tonight: Note: these 'work in progress' screenshots show a glitch on the engine paint (white spot above the intake) that I've already fixed.

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.

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.

I thought I was going crazy - noticed the same phenomenon! Not a complaint, just an observation...for a 4 year old product to get an update is amazing and if that is the worst thing... (Heads out to fire up the Poseidon).

Probably, but I found it by chance Ken! Have a happy (and quieter) new year

Gents; Go into the FMC... Click "PMDG Setup" Then "Options" Then "Sound" Then, where it says "Volume Levels", click "Adjust" This will bring up your options. Set the "Ambience" to a lower number and see how you like it. Even with Ambience of "0" you can hear the engines and alarms.

The alpha channel controls where 'holes' will appear in the fuselage. You need to make the alpha channel 'black' in the places where you have windows. Then you can see through the window. You also need to make the alpha channel white where there are window blanks or you will have extra holes in the side of the plane.

The "alpha channel" of the texture controls where the window openings appear on the model in the sim. In Photoshop (or whatever program you are using) you need to make sure the alpha channel is 'black' where there are windows and 'white' where there are blanks. You can always use the alpha channel from a forward fuselage texture of another -900 paint as a place to start.

FSX is crazy. I have another addon where every once in awhile you end up flying around with the ground power cart attached. LOL

Here's the -200LR version: Will do a final quality check and try to upload to AVSIM tomorrow.