John_Thomas

Well, hopefully you noticed I said earlier, "this is my subjective opinion". :) Nope, I sure haven't ever flown a real P-51, but by doing side by side comparisons I'm seeing practically the same roll rate between the Accusim P-51 and the Accusim P-40. If you happen to own both aircraft, I invite you to test them yourself and compare. The P-51 was legendary for it's unmatched roll rate. The P-40, I think most people were surprised it could even fly inverted. :)

I really want to like this plane - it has some tremendous modeling in the virtual cockpit, along with advanced animations and external details; truly a wonder. I have reservations about the some aspects of the flight modeling, however. The roll rate seems very slow for a P-51, and I really can't detect that the Accusim P-51 rolls any faster than the Accusim P-40. In real life there should be a very dramatic difference in roll rates between these two aircraft. I'm not sure if this is a limitation of the flawed ground friction physics modeling inherent in FSX itself, but the the way torque is modeled on takeoff seems sloppy to me. This of course is a purely subjective opinion on my part. Nevertheless, the Accusim P-51 seems to intially pull to the right initially as power in applied (this sure doesn't seem correct) before correctly causing a pull to the left as power builds. The tire friction modeling seems not right and it's quite difficult (at least for me) to maintain center-line as power is increased without wobbling from side to side. I don't know how to explain it, but the tires just don't seem to be griping the asphalt with the correct amount of friction. In real life the P-51 is reported to be quite stable on takeoff roll when correct rudder trim is applied. The Accusim P-51 just seems to me to be too unstable in this regard. Again, this observation is purely subjective. The actual Accusim engine physics are a wonder to behold though; really makes one feel like they are flying a living, breathing, oil sucking machine, so to speak. A2A are truly masters at this particular aspect of simulation. The manual has some shortcomings - there are no published takeoff or approach speeds. There is also no explanation of how to manage fuel tank switching other than the advice of using the left tank for takeoff. Perhaps the manual was a little rushed or this is simply an oversight. I'm not trying to bring A2A down in the least, believe me. I own several of their aircraft and each is among my most favorite to fly in FSX because of the precision modeling and attention to the smallest details, most especially the Accusim technology. The Accusim P-51 to me just seems a little rough around the edges here and there at present, but I'm sure A2A will address any issues down the road.

Well, with version 1.3 this too has now passed into the squashed bugs oblivion. :) I do believe things are very close to being perfect at this point! Nice job fellas, and thank you. -John Thomas

I was also wondering if a "takeoff power set" call from the F/O would be possible at some future date. Damien, you are saying that this too is a carrier-specific SOP though?

Hi Bryan, Thank you. I was going to mention also that I'm actually calling for the landing checklist myself after calling for "gear down, flaps 15", rather than calling for landing flaps and having the F/O call for the landing checklist. It would seem that FS2Crew will let you do it either way. If I personally call for the landing checklist, however, the F/O will not challenge me for the landing flap setting. Instead, if I call for the landing checklist after gear down and flaps 15, the F/O will challenge me for gear down, ignition continuous, and speedbrake armed. He will then wait for me to call for landing flaps before announcing "flaps 30, landing checklist complete". I hadn't realized that the F/O will himself call for the landing checklist and challenge me for the landing flap setting otherwise, that is if I understand correctly. Thanks again, John Thomas

Hi Bryan and Damien, I have to say that you guys, together with all of the FS2Crew Team, have done an outstanding job with the latest SP2 release of the NGX version. All of the issues I've reported thus far have now been completely fixed and resolved; indeed FS2Crew is truly one of the most satisfying and enjoyable addons I've ever purchased for Flight Simulator X. I am therefore somewhat sheepish in even possibly finding one small remaing issue, although it's certainly very possible everything is working correctly and that my current understanding of correct procedure is askew. What I have noticed though is that with Flaps 30 landings, after I call for for Flaps 30, the F/O will complete the landing checklist after he sets the correct landing flaps by announcing, "Flaps 30, landing checklist complete". However, when performing Flaps 40 landings, after I call for Flaps 40 the F/O sets landing flaps 40 correctly, but does not announce, "Flaps 40, landing checklist complete." Rather, he only announces, "landing checklist complete". I'm wondering if the F/O should therefore be making a "Flaps 40" announcement in the same way as he does with his "Flaps 30, landing checklist complete" announcment. Also, to be clear, I have a Flaps 40 landing configured correctly in the FS2Crew approach briefing panel beforehand. Again, it's very possible I'm misunderstaning the correct procedure in the above situation. Also, I'm calling for flaps 40 after gear is down and the flaps are set to 15, if this has any bearing. In other words, I'm calling directly for Flaps 40 from Flaps 15, rather than calling for Flaps 30 in between. I am not sure if this is correct procedure or not. Thank you for all of your support and tireless effort with this wonderful product, Signed, John Thomas

Yes, just the takeoff speeds portion of the before start checklist is where I'm experiencing the problem. The MCP portion of the before start checklist works fine. Bryan, I'm using Win 7 Ultimate 64 bit. Thanks, John Thomas

Hi, This isn't a huge problem, but with my installation of FS2Crew Voice (SP1) for the NGX, I cannot make the F/O recognize my reading off takeoff speeds during the before start checklist. I notice via the green bar that my voice commands are being input properly; I see "V one one two zero", "V R one three four, and "V two one four zero", etc, being correctly interpreted on the green bar. I also pause for a second between takeoff speed read outs as specified in the user manual. After reading off the V 2 speed, however, the F/O never responds. I've tried pausing longer and shorter during call outs, but there is still no response after the V2 callout. Again, my voice commands are being correctly interpreted on the green bar. I am also certain that FS2Crew is in the correct mode, i.e., the "before start checklist mode", during this time. I am only reading off Takeoff speeds when prompted by the F/O. Strangely, during my voice read outs for the MCP settings during the before start checklist, everything goes perfectly. Here too one must pause between read outs, but for whatever reason it works quite well for the V 2, Heading, and Altitude read outs during the MCP part of the before start checklist. I only have trouble with the takeoff speed callouts. Thank you, John Thomas

Ok, I am about 95 percent certain the cockpit lighting dimming out for a split seconds is related to either hard drive access times and/or scenery texture loading. I've pretty much caught this effect in the act, so to speak, after some extensive testing. When either the hard drive takes a drag :) or textures/autogen loads, I can see the lights dimming out in the cockpit. I can pretty much predict the lights will dim during such hardware stress times. I am therefore going to diagnose the lights dimming phenomenon accordingly. As such, I really don't see a fix other than optimizing one's computer for a minimum of stuttering during simming sessions with the NGX. All of this from my admittedly non-professional results, but again I would be willing to bet money that it's a hardware related thing and not some kind of special effects modeling implemented by PMDG. :) Signed, John Thomas All the time for me too, daytime or night. The LCD numeric displays on the MCP will flicker if there is no cockpit background or flood lighting activated. If background and flood lighting is activated, it too will flicker. Only for a split second. I'm now convinced this is happening when computer hardware running FSX and NGX is under high loads such as hard drive access or texture loading. Signed, John Thomas

I experience the EXACT same thing with the F/O audio volume fluctuations. I have the "do nothing" box checked in regards to Windows automatic volume control as was earlier suggested. This did not solve the problem for me. While I have a Creative XFi Soundcard for my main Windows audio, I instead use a USB headset with FS2Crew. I have to manually switch my default audio device to the USB headset before using FSX/FS2Crew, so my Creative Sound should be altogether disabled and bypassed during simming sessions. The USB Headset I'm using is a Microsoft Lifechat 3000, if this has any relevance. Bryan, if you are able to find a solution for Mr. Moe, please share it here. Thank you.

It would be interesting if PMDG could confirm or deny this (as either being a FSX glitch or a real-world 737NG electrical effect modeling). I really don't think electrical surges in a real 737 would be as prevalent as the cockpit lighting brightness fluctuations are in the PMDG sim though. Thanks for all the input so far guys! Signed, John Thomas

I don't have the ENB mod going personally, no. FWIW my system specs = AMD Phenom II (quad core) 965 @ 4.6 Ghz ATI 4870 1 GB Video 4 gb main ram Windows + FSX installed on Western Digital 300 GB HD @7200 rpm, defragged with DiskTrix Ultimate Defrag Windows 7 Ultimate 64 bit Creative XiFi Titanium 32 bit PCIe sound card FSX Acceleration PMDG NGX SP1c FS2Crew NGX EzDok FSUIPC Registered version Maybe some nice individual from PMDG will be able to offer some input. Seems a lot of people are experiencing the same thing. Thanks, John C. Thomas

Weird! This is really starting to bug me now, lol. Signed, John C. Thomas

I have the exact same random cockpit lights flickering with my installation as well. All of the interior panel lighting dims for a split second then returns to normal brightness. The primary and secondary displays do not flicker; rather, just the background panel lighting and flood lighting. I too am wondering what is going on? I'm somewhat suspicious of this phenomenon having to do with either hard drive access periods and/or texture loading, but I am not positive. I have never seen this on videos of real 737 cockpits. Is anyone else experiencing this? Thank you, Signed, John Thomas

Same here for me, unfortunately. I went through the same process described above and FSX bluescreened BIGTIME the first time I tried to start FS2Crew Voice SP1 for the NGX. I tried reinstalling but I'm still encountering CTD's left and right. Weird. For now I'm going to try installing the non-SP1 version again as it was stable on my particular setup. Gee Whiz though, I was kinda excited about the SP1 and all the new features. I'm using FSX Acceleration + W7 Ultimate 64 bit.

I appreciate everyone's replies and very good advice on this subject! I think I've exausted every possible solution to no avail. I'll next try reinstalling FSX altogether and just try starting from stratch to eliminate any kind of conflict with other addons I have.

The memory device in question has three rotary knobs on it and is fully functional in the PMDG NGX virtual cockpit. :)Signed,John C. Thomas

Hi Paul,I do always climb with VNAV engaged on the NGX. The normal VNAV climb profile for any given cost index will initially fly a constant IAS above 10,000 ft, then intercept the programmed cruise Mach number at whatever relevant altitude (depending on temps aloft), then maintain cruising Mach number until cruise altitude is reached. All things considered then, climb rate is always a resultant variable depending on weather conditions and aircraft weight; airspeed is however is a constant with normal climb profiles. Jet engines do of course safely produce more power and become much more efficient as the temperature aloft decreases, but the air is getting thinner and thinner as the aircraft is climbed to higher flight levels. The turbine engines are highly efficient at these high altitudes but the lifting bodies (wings, stabilizer) become increasingly less aerodynamically efficient. Thus, climb rate naturally diminishes in this situation. What I'm experiencing is way beyond the natural decay in climb rate using normal VNAV climb profiles. I'm seeing the aircraft level off completely sometimes during the climb, which should never happen at the aircraft weights I fly with. Signed,John C. Thomas

Yes, thinner air = less climb performance at high altitudes.

Can you possibly ever not be totally annoying when you find the irrepressible urge to barge into a thread like this on any of the numerous forums at Avsim??? You seem to manage to appear everywhere around here, ever quick to make a most unwelcome and very much unsolicited snippet of rebarbative, self-important drovel at random intervals.

Hi,I've experimented with FSUIPC completely uninstalled from FSX and yet I experience the same problem, but thank you.Signed,John C. Thomas

So, how many of you know where the memory device is in the 737 NG cockpit, and what purpose does it serve? HINT: It has three little knobs on it. Amazingly, it actually functions in the PMDG NGX simulation just as it does in the real world. Signed,John C. Thomas

Hi, I have wind smoothing enabled in both FSUPIC and ASE, but thank you. Signed,John C. Thomas

I don't have FSINN, but thanks.Signed,John C. Thomas

Hi,When using the NGX with either default FSX online weather or an external program such as AS2012 or such, I'm finding that all weather depiction in FSX has trouble interpolating temperatures aloft; at least on my setup. For example, in between the normal published reporting levels, the temperatures aloft in FSX tend to stay at the temperature of the current or lower reporting level for too long before transitioning to the temperature at the next reporting level. There isn't simply isn't enough interpolation between the weather reporting levels for a realistic, smooth temperature change as the aircraft is climbed into the higher flight levels. As a result, with the high fidelity flight and engine performance dynamics inherent in an aircraft like the PMDG NGX, the 737NGX tends to climb at a sporadic rate, rather than a realistic, predictable climb to higher altitudes. Climb rate when flying a constant IAS or MACH should of course diminish as the aircraft gains altitude, but with the NGX on my installation I experience normal climb rates that will suddenly diminish and taper off from around 2000 feet a minute at around FL240 (at standard weights) to something like 200 feet a minute. Sometimes the NGX will even level off for a few seconds during the climb as it struggles to maintain constant airspeed. It's very easy to predict when this anomaly will happen because I can monitor the true outside air temp on the FMC Progress page 2. The NGX struggles when the temperature aloft is not changing fast enough from the previous reporting level to the temperature at the next highest reporting level. When the temperature finally does begin to match that of the next higher reporting level, the NGX's climb rate shoots back up to around 2000 fpm again. I essentially experience periods of temperature induced 'climb porpoising' in any given situation and I'm not able so far to find a way around it. Again, I experience this with default FSX online weather and either AS2012 or ASE. I have a registered version of FSUIPC installed, but I've also been able to reproduce the climb behavior with FSUIPC completely uninstalled. One might suspect some kind of situation with SIMCONNECT, but since I experience the climb problem even with default FSX online weather this would seem to rule that out as well. Do any of you guys NOT experience this kind of climb behavior with the NGX and online real weather of any kind? I'm just wondering if this is a situation one has to live with given the limitations on how FSX is currrently able to depict weather or if there is something that perhaps can be fixed on my side.Thank you for any help or insight!Signed,John C. Thomas