Jump to content

lufthansi

Members
  • Content Count

    13
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    IVAO
  • Virtual Airlines
    No
  1. Hi Mark! I've had this issue as well. The grinding sound could be the compass in some of the default aircrafts like the Carenado A-36. When I switched into other aircrafts - beeing it a PMDG one or for example the F-22 - this grinding noise kept on annoying me. I tried to set up a new default scenario in an aircraft not containing this old compass. It didn't work. Solution was to delete my saved scenario to force P3D to load the "real default flight". The one with the F-22 at Eglin Airbase. This solved the problem for me. Looks like a P3D bug as it effects both, PMDG and P3D included aircraft. Greetings,
  2. Hello folks! I recently got a real world 777 mechanics rating and used the PMDG 777 to learn at home. I came across the same issue with the backup generators (referred to as BUGs). Also at my P3D PMDG 777 the BUGs show green on the synoptics page when the IDGs are switched off. But they don't supply power as they should. After I landed the BUGs also worked fine on ground. Conclusion: The BUGs only work as supposed after the aircraft has been set to flight mode. Once the aircraft was in flight, the BUGs also work ok on ground. That seems to me like a fault in the PMDG 777 because I don't see any reason why the BUGs should work different in air than on ground. I have access to real world, up to date Boeing documentation including AMM, SDS and training docs. According to these documents the BUGs supply their onside AC transfer bus if the IDG is not delivering power (switched off, disconnected, faulty, etc.). If both IDGs don't supply power the right BUG supplies both AC transfer buses. The BUGs deliver their power to the backup generator converter in the main equipment center. This converter is necessary as the BUGs don't include a transmission that keeps the frequency constant with varying engine speeds. The main generators are called IDGs because they have an internal gearbox that regulate the varying input speed to a constant 115V AC / 400Hz output. The BUGs can't do this (they're much smaller because of the missing transmission). As there is only one BUG converter installed on the 777 only one BUG can deliver power at a time. They can not be paralleled within the BUG converter. That's why the right BUG supplies power to both AC transfer buses if power is lost on both sides. If the right BUG is faulty the left one can replace it to power both AC transfer buses. But only one BUG can be active at a time. If only one engine is running of course one IDG can supply both AC transfer buses (APU and external power off). The BUG needs a running engine just like the normal IDG. So if the engine doesn't turn the installed IDG and BUG are not delivering power. Nowhere Boeing mentions that the system behavior differs between air and ground mode. And as I said the P3D PMDG 777 system behavior on ground changes after the aircraft has been set to air. This can't be normal. After engine start the BUGs are checked automatically. You can see this also on the PMDG 777 if you monitor the ELEC synoptics page. The BUGs come online green for 15sec after ENG start. So after every engine start the aircraft checks its BUGs by itself. Quite cool. The function that the right BUG (or the left one if the right one failed) supplies power to both AC transfer buses on the PMDG 777 only works when the IFE and cabin supplies have been switched off. I couldn't find any info about this on the Boeing docs. But maybe PMDG knows even more than mechanics do. Nobody knows everything about an airplane like this. If the IFE and cabin supplies are switched on the BUGs only supply their onside bus on the PMDG 777. As I said I just made my rating. I'm not saying that I know everything. But this is how I understood it. If something is wrong or you have further questions I can try to find out. Maybe PMDG staff can look into this as well. Greetings, Stephan
  3. Thank you for your replies! Got the message. The FD are necessary to enable the entire "TO/GA mode" shown on the PFD by the FD. I was just wondering because most people, who are having trouble with TO/GA can't get the throttles moving and every time they're told to switch the FDs on.
  4. Good day! I figured out that my throttles advance without arming either of the 2 flight directors. The manual correctly states that TO/GA is only available when both FD are engaged. What could be the cause that my TO/GA mode can be activated without any FD or only 1 FD active? It doesn't matter if I'm using the TO/GA buttons on the throttles or the hidden one on the MCP. I'm using Prepar3D V3.2, the latest PMDG 737NGX updates (via the PMDG Updater -> no self caused finger trouble) and only liveries downloaded via the PMDG livery manager (again no finger trouble). I'm running P3D on my iMac using Bootcamp and Windows 7 (also latest updates installed). Everything works wonderful btw. Maybe I just got something wrong here understanding the system. Even though I read a lot in the forum using the advanced search function. Therefore I'd be delighted getting answers from the pros! Have a nice weekend everybody!
  5. Hi matt! Thank you! I did what you said and it worked immediately! Thank you very much for your replies!
  6. Hi Matt! Thanks for helping me again. I really appreciate your time. I did what you said and flattened the pink PSD, saved it as JPEG and converted it into a DDS DXT5 file. As I only have a Photoshop version for iMac I can not install the Nvidia DDS Plug-In (works for Windows only). I have to use a stand-alone program to convert my files into the DDS DXT5 format. It worked very well on all other fuselage sections. The only thing I experienced is, that I have to save the night lighting files as JPEG to get the correct result after converting these files into the DXT5 format. At the "day time" PSDs it doesn't matter if I convert to DXT5 from a JPEG, PSD or BMP file. It's only the night files where I have to make sure to go from PSD to JPEG and then to DDS DXT5. I still have the bright tail and inboard engine cowlings. Tomorrow I'll try to make a (white) tail file from the paint kit without adding any paint layer. If that doesn't work there might be a mistake in to paint kit PSD file that I don't know and therefore can't fix. But as you mentioned there're freeware paints available without these problems. So if anyone knows how they did it, please let me know. Take care!
  7. Hi Matt! Thank you for your help. I also deleted the tailnight file and it had no impact at all. You are right on this. But I still have the bright engine parts and tail. I looked in the PSD file of the paint kit again. 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. 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. Thanks for your help everybody!
  8. Hello fellow PMDG riders! I tried to do my 1st repaint of the PMDG 737-800NGX (non winglet version). I managed to get the livery on the aircraft but I still struggle with the night lighting. I searched about 40 pages of topics in the forum but couldn't find a thread with this issue. The original PMDG (re)paint that comes with the 737NGX when bought contains a file called "pmdg_737NGX_tailnight". The repaint kit does not include a file with this name. After searching the internet I found some guys who created their own night lighting file for the tail. They adjusted the alpha layer of the "pmdg_737NGX_tail" file and saved it as "pmdg_737NGX_tailnight". Here's their description: http://forum.avsim.net/topic/348802-paintkit-tail-night-textures-psd-file/ Just like them I can't fix the issue. My repaint still shows with bright tail and inboard engine fairings during night. Maybe someone from PMDG or any repainter who has had more success could tell me what I'm doing wrong? I repainted the tail file. What is the layer 60 for? When I enable it, it it covers my entire tail repaint. By default it is disabled and that's how I left it. Next I flattened all the layers. I accessed the channel section to enable the alpha layer. In order to do so I selected Alpha 1. As the color looks strange I deselect the RGB channels so that only Alpha 1 is left active. But this deactivates my repaint and I only get the white tail with the light beams from the logo lights. I managed to create a PSD file by following the instructions in the other thread posted above. The result looks like it does on the PMDG demonstrator livery that comes along with the product. But even with this file the tail and the engine inboard cowlings appear in bright condition. What is my mistake? Greetings!
×
×
  • Create New...