maredzki

I feel for everyone here... having the same problem with W7 and FSX SP2 with Acceleration Pack.Running newest video drivers for nVidia 9800 GTX+ and sound drivers for SB X-Fi Xtreme. I will also try setting the FSX.exe I also got the hotfix info, will load it and will post the results here for you guys.Thanks,Marek

Thanks guys, not sure why I posted in the PMDG forum... my mistake. Moderator, please remove the post if required. I will repost in the proper forum.Thanks so much guys!

I am having issues with high N1 percentages when starting to taxi. I have to be at about 50% N1 to barely start moving. The plane is <50% loaded.Any ideas why that is?Thanks,Marek

Michael,Sorry, it is the 737.Thanks!Marek

Hello,i have fiddled with the cockpit configuration and now cannot get it to the same as it was out of the box... i liked it and now want it back :)Please let me know if anyone can assist with restoring the default config.Thank you!Marek

>You can also enter the cruise speed on the cruise page.Did that as well and no joy...

>1. The FMC is telling you that you need to change the ALT>window .... in your case from 320 to 340>>2. If you have a cruise mach speed set up in the>initialisation it should automatically show in the legs page>as 0.78/320 I think you can just type it in also>>Peter 1) Odd thing is that I have set the new ALT in the MCP and still get that error.2) Same here; in the INIT of CRZ there is the default speed set, the only thing needs to be changed is the CRZ ALT, if I am correct.No clue what is wrong...

I guess I will have to dink around with those monitor knobs :)Thanks for the help on a great product!Marek

I have three questions:1)I have looked through the forums and did not find the solution to my problem. Tried ALT INTV but did not work. I am flying at FL320 and had VNAV disengaged (at one point during the climb it was engaged up until ATC's first altitude restriction). Then used FLCH and leveled of at FL320 and asked ATC for FL change to FL340. I have changed the FL in FMC and in ACT RTE LEGS at the next waypoint but when I click on VNAV it gives me 'CHECK MCP ALT" and MCP ALT says FL320.2) How do you set the mach speed in the FMC? Now it just says ------/FL320.3) All of my waypoints (after pressing DATA button display the following info:Waypoint nameALT Restriction-------ZAny reason why the ZULU time is not displayed there?Thanks much for any suggestions you guys may have!Marek

Mats,Even thought when the power is on and the a/c is running on both engines i have a hard time seeing the spring loaded switches (middle screen shot). Any suggestions for that?

Vin,here are the screenies:you will need to add the http header in front of those links below as that is not allowed, I guess...img329.imageshack.us/my.php?image=overhead3du8.png (day image)img329.imageshack.us/my.php?image=overhead2lc6.png (night image w/power and panel lights on"img512.imageshack.us/my.php?image=overhead1tn9.png (night image w/panel lights on)

I am using a flat panel which works well with the default MSFS 737 at night, all of the buttons and switches are visible. However, when I switch to the PDMG 737-800 I only see the labels for the switches, cannot tell if they are on or off. Is there anything else that can be done instead of adjusting the brightness/contrast on the monitor?I will try to post the image this evening.Thank you.Marek

Here is my beef with the Xpack and SP2.I've purchased the XPack early December and that is when I started getting the d3d9.dll. It was happening sporadically displaying this error when getting into the ALT menus in Full Screen mode. I uninstalled the Xpack and the d3d9.dll error went away. I also tried installing the SP2 yesterday with the same results as with the Xpack. The XPack has the SP2 already installed. I am betting that this is related to some cards that do not handle the updated DirectX.I am personally running the following and hoping for MS to fix the issue.AMD Athlon 64 X2 Dual-Core 6400+ 3.2 GHz2 GB RAM2x GeForce 7950 GX2 SLI

I had the same problem with Acceleration pack and I had to return it. Today, I downloaded the FSX SP2 and yet again I am having the same issue. I think it is related to DirectX but MS didnt want to admit to it. I hope this will get more publicity as Acceleration Pack was not free whereas SP2 is...We shall see.Take care,Marek