mackalex

The user IS using Opus. Interestingly enough, the checkerboard system is very common in the area in which he is flying (Houston, Texas). The clouds will begin as looking thin with less condensation and water built up within them; they will look something like this photo. As the clouds begin to become more thick and filled with water, it is not as easy to realize the checkerboard pattern with the naked eye, but in reality the condensated "cores" of the clouds are still aligned with each other in a checkerboard pattern. The weather radar is able to pick up these densely precipitated cores of the cloud as the red color.

I am aware of that. But the alpha channel on the cut fuse sections does not have the window cut outs. The alpha channel is totally white on those.

Hey guys! The PMDG 777 is a fantastic plane to fly! A whole load of great work definitely shows in the systems quality and graphics! I have one problem with the paintkit though. The alpha channel that comes with the paintkit PSDs for the windows on the fuselage of the 777 does not show the black cutouts for where the windows are. So when the paint is exported into flight sim, the windows are covered in the paint and are not transparent to see inside the cabin. I am certainly not an expert when it comes to working with Photoshop, but I do know a lot. So I am unsure as to why the alpha channels for the windows are not already prepared. Any help is appreciated! Thanks! Alex Makoviecki

Hey guys! The PMDG 777 is a fantastic plane to fly! A whole load of great work definitely shows in the systems quality and graphics! I have one problem with the paintkit though. The alpha channel that comes with the paintkit PSDs for the windows on the fuselage of the 777 does not show the black cutouts for where the windows are. So when the paint is exported into flight sim, the windows are covered in the paint and are not transparent to see inside the cabin. I am certainly not an expert when it comes to working with Photoshop, but I do know a lot. So I am unsure as to why the alpha channels for the windows are not already prepared. Any help is appreciated! Thanks! Alex Makoviecki

Hey guys. After completing a fresh installation of the PMDG 777 I've noticed that I can never get the Operations Center to launch past the update check. The green loading arrows keep on spinning while it says at the bottom of the window, "Checking for online updates...", never getting to the full interface. I am unsure as to if this is a bug, or something that is screwing it up from my computer. My UAC settings are set to "never notify", and the Operations Center is running as admin. Help is appreciated! Thanks, Alex.

Looks fantastic! Another classic plane with quality that I can add to my hanger!

Thinking of creating a VA and would like to hear your thoughts on my ideas. Feel free to give me more ideas!

Hey guys, it's Alex!I have the latest Beta version of FSRecorder and have the latest service pack for the NGX. Evertime I record the NGX pushing back, taxiing, cruising, taking off, after recording it and playing the recording back the aircraft seems to have engines shutdown and basically almost a cold and dark aircraft. Even when recording a push-back and engine start I play the recording back and the aircraft moves but none of the switches turn on or off like I recorded and the engines don't start up and barely any of the systems in the whole aircraft operate normally during playback. Also when ending the playback the aircraft goes into a cold and dark stage just like it does during playback... I know confusing, right?!Please help! I am currently trying to make another episode of my "World Tour" series from Newark to Saint Maarten and I need to make another video now using the NGX, haven't made one in 4 months!Thanks!Alex.

Well, it's still not working, and since I'm flying STARS I don't want to manage the VS (vertical speed) or FL CH. On every flight I tried it happened, I got all the way up to the descent and I failed... or the plane failed. I tried every other aircraft on each STAR that I flew with the NGX and they could descend normally. Something must be up with me configuring the LEGS for the descent with the STAR, but I'm not sure because each waypoint's speed and altitude look fine with the chart compared. I think it might be the altitude between one waypoint and another.(made up waypoints): EXAMPLEBOAGA - 240/6000A ----> Speed and altitude given on the STAR chart.SANTO - 240/4543 ----> Speed and altitude calculated by FMC.SVT - 220/3354 ----> Speed and altitude calculated by FMC.CLANT - 200/2500A ----> Speed and altitude given on the STAR chart. This kind of gives you the idea of what I mean by the waypoints in between that have speeds and altitudes calculated by the FMC. What I think is maybe they have to be changed? Thanks,Alex.

Hi my name is Alex Makoviecki. I recently got the PMDG 737NGX and I really... really love it! The only problem I have with it is descending. I am about thirty miles back from the TOD (top of descent) and I set in the altitudes in the FMC that I should be at for each waypoint and VOR for the OMN.HILEY2 STAR at Miami Intl. I was using a chart that shows you the altitudes for each waypoint and VOR. I then set the altitude for descent to 5000ft which was the altitude for one of the waypoints that I would descend to and stay at for a while until descending to the glideslope intercept altitude. When I reached the top of descent the engines went to idle and the aircraft started descending but then leveled out at 37000ft (my cruising altitude was 38000ft). I noticed that the FMC had a message that said DES PATH UNACHIEVABLE, that was weird because I set the right altitudes for each waypoint and VOR for exactly what they should have been. I got the aircraft to descend a little more by copying of the speed and altitude of the first descent waypoint and pasting it again on the same waypoint. But I only got the aircraft to descend to 32000ft. I also noticed that when I am climbing above 25000ft the aircraft slows down the climb to 1000fpm, compared to 1800fpm in other payware aircraft. I would appreciate some help here!Thanks,Alex.

Thank you. I have figured it out now. I just needed to fiddle with the audio drivers and get an adapter for my headset. No worries! Thanks,Alex.

Hi this is a pretty serious and annoying problem with FS2Crew. I obviously have it for the Level-D 767 and it's the Voice Commander edition for FSX. I am running Windows Vista 32Bit and have no problems with it. On FS2Crew I can configure the 767 for the panel state and click on the vertical speed standby instrument and the FS2Crew panel pops up. It says that the voice recognition has started but I talk into my headset and nothing shows up on the upper bar where it shows what you said. I tested my built-in mic and my headset mic. They both work fine outside of FS2Crew. I also set my headset mic for sound and voice on the sound options of FSX, and installed new audio drivers. But nothing seems to work! I would appreciate some help. Thanks,Alex.

Never mind I got it to work. It was weird, it just did that for a while then stopped.

Yes many times.

I have Flight Simulator X on Windows Vista 32Bit, 4GB Ram, Core 2 Duo 2.13GHz. Whenever I'm ready to start the before start checklist I say "Before start checklist." And the copilot says "Windows." I say "Closed and locked" and he keeps saying "Wing anti ice off," multiple times. When I use the UK or EU voices it says "Wipers off," "Wipers low," "Wipers medium," or "Wipers high." I don't know how to fix this and I can't skip to the next thing in the checklist the copilot just keeps saying the same thing over and over again. Thanks,Alex.