davetfc

OK. Thanks for the information. Will give it a try.Regards,Dave TchangAntwerp, Belgium

Hi,I'm using Win7 Home premium 64 bit. I don't have any desktop icons! I want to keep my desktop clean. I only have a couple of icons pinned to the taskbar (for instance FireFox and Windows Media Player). I start most programs using the Windows key. This automatiscally opens the Start menu. I type in the first few letters of the program I want to start (for instance vrou for vroute program) in the dialogue box. Win7 automatically presents a list of the programs and files found with the letter combinations typed. In my example the program vroute is presented 2nd on the list. You can either use the keyboard (arrow keys and enter) or the mouse to start the program. Other programs which I use very often (for instance a text editor) I would pin it to the Start menu.Regards,Dave TchangAntwerp, Belgium

Hi,Thanks for the quick reply. So if I set the flag in FS9.EXE then I'm set to go, or do I still need to configure something in Win7?RegardsDaveAntwerp, Belgium

Hi,Just one question on this. If one is running a 64 bit OS (ie Windows 7 Home Premium 64 bit) does one still need to set the LARGEADDRESSAWARE flag in the FS9.EXE file header?RegardsDaveAntwerp, Belgium

Hi everyone,Just wondering. Has anyone been able to get the iFLY B747 working in FS9 under Windows 7? Thanks.RegardsDaveAntwerp, Belgium

Hi digitalfil,I would like to suggest that you check your energy power savings scheme in W7 configuration. Make sure you are using the "Maximum performance" scheme.I'm running W7-64 Home Premium with FS9 and in the beginning I was also experiencing a lot of fluctuations in the frame rates, until I changed my energy savings scheme to maximum. In my case it was with all aircraft and not specifically with 1 type. Hope this helps.RegardsDaveAntwerp, Belgium

Hi Colfmedion,I'm not sure if this is going to help you out in your case, but check your energy savings settings in W7. I was having fluctuating frame rates using FS9 on W7 64 bits and couldn't figure out why. Eventually I tried the high performance scheme in the energy savings settings and that did the trick for me.RegardsDave TchangAntwerp, Belgium

Hi,I can only tell you my experience. I've upgraded from a Vista 64 bit Home Premium to a W7 64 bit Home Premium (RTM).I installed FS9 by first configuring the following properties of the FS9 setup program: compatibility mode = WinXP (SP2); deactivate visual themes; deactivate desktop composition; deactivate DPI adjustment (sorry I'm not sure if these are the correct names of these options in an English version of W7 as I'm translating from a Dutch version); activate run the program as Administrator.I then installed 737 v1.3, then the model 800/900 and the model update + service update for 800/900. Each time I first configured the setup programs as I did with the setup program of FS9 (see above).I also configured the FS9 startup shortcut with the same compatibility settings. I'm having no problems in running FS9 or the PMDG 737. Neither model 700 nor model 800 has the problems you encountered. FMC works perfectly. I have not turned off UAC, nor did I run the setup programs in safe mode.Initially I did encounter problems of fluctuating frame rates, but this was due to the configured energy savings scheme on the laptop. Since I configured it to maximum performance, I'm having no issues anymore with the frame rates.I can therefore only suggest that you configure the compatibilty mode settings when running the setup programs as well as when starting FS9.RegardsDaveAntwerp, Belgium

Hi,Yes indeed! Put me in also for a pre-order for a FS9 version of the new 737NG2.RegardsDaveAntwerp, Belgium

Hi,Just to let you all know that I found the solution to my fluctuating frame rates! It was due to the configured energy savings scheme on my laptop. I changed this to the highest performance setting and now I have my FS9 frame rate locked at 25 with all the display sliders maxed out. Activesky (running on another network PC) is also configured to display maximum quality. The frame rates are great. They stay at 25 most of the time, only on occaision (when flying into thick clouds) does it drop to the mid teens.So if any of you are running W7-64 (RTM) with FS9 and experiencing fluctuating frame rates, especially on laptops, check you energy savings settings.RegardsDaveAntwerp, Belgium

Hi,I have a laptop with a GT130M graphics card onboard. I've installed the NVidia drivers 195.62 under Win7 64 Home premium. I'm running FS9 and I have the frame rate locked at 35. What I'm experiencing is a lot of fluctuating frame rates. FS9 runs at 35 frame rates and then it suddenly drops to below 10, after a short while (anything from 5 to 10 seconds) it will pop up again to the upper 20's and then go back up to 35 frame rates.I've tried to play around with the TEXTURE_BANDWIDTH_MULT and TextureMaxLoad settings in FS9.cfg. This does influence the fluctuations somewhat, but doesn't make them go away completely. I tried with TEXT_BANDWIDTH_MULT setting at 400 and 600 and TextureMaxLoad at 10.Can anyone tell me what are the maximums for both these settings? Is there anything else I can try?Regards,DaveAntwerp, Belgium

Hi everyone,I've just recently purchased a new HP laptop with a NVidia GeForce GT130M graphics card onboard. This is a notebook version of the graphics card, not the GT130. I've installed NVidia WHQL driver software version 195.62. I've also installed the NVidia system tools software. The OS is Win7-64bit Home Premium edition (RTM).Now I've noticed in the NVidia settings that I have the option of changing up to 3 clock settings: Core clock; Memory clock; and Shader clock. The settings to change the cooling are grayed out, so I would assume that there is no separate cooling installed for the GPU itself.Now I was wondering which of these settings should I change to achieve better frame rates in FS9? At the moment these are still at the "Factory shipped frequencies" (Core = 600 Mhz, Memory = 500 Mhz and Shader = 1500 Mhz). Is there a risk of irrevocably damaging the hardware when changing these settings? What should I watch for when changing these settings so that I don't damage the hardware? Logically I would assume that increasing these values would mean that the GPU would attain a higher temperature. As there is no separate cooling provided for, what precautions should I take in this area when changing the clock settings.So you see I'm a bit apprehensive in changing these settings, as I certainly don't want to irrevocably damage the hardware of this new laptop. Any pieces of advice would be much appreciated! I would also like to know from those who have modified these settings what gains in frame rates did you manage to get out of the system in FS9?Many thanks for taking the time to read this message.RegardsDaveAntwerp, Belgium

Hi everyone,I've just recently purchased a new HP laptop with a NVidia GeForce GT130M graphics card onboard. This is a notebook version of the graphics card, not the GT130. I've installed NVidia WHQL driver software version 195.62. I've also installed the NVidia system tools software. The OS is Win7-64bit Home Premium edition (RTM).Now I've noticed in the NVidia settings that I have the option of changing up to 3 clock settings: Core clock; Memory clock; and Shader clock. The settings to change the cooling are grayed out, so I would assume that there is no separate cooling installed for the GPU itself.Now I was wondering which of these settings should I change to achieve better frame rates in FS9? At the moment these are still at the "Factory shipped frequencies" (Core = 600 Mhz, Memory = 500 Mhz and Shader = 1500 Mhz). Is there a risk of irrevocably damaging the hardware when changing these settings? What should I watch for when changing these settings so that I don't damage the hardware? Logically I would assume that increasing these values would mean that the GPU would attain a higher temperature. As there is no separate cooling provided for, what precautions should I take in this area when changing the clock settings.So you see I'm a bit apprehensive in changing these settings, as I certainly don't want to irrevocably damage the hardware of this new laptop. Any pieces of advice would be much appreciated! I would also like to know from those who have modified these settings what gains in frame rates did you manage to get out of the system in FS9?Many thanks for taking the time to read this message.RegardsDaveAntwerp, Belgium

Hi,I've recently upgraded my laptop PC from Windows Vista 64 to Windows 7 64 Home Premium. I've done a completely new installation of my FS9 without any problems. I also have Active Sky 6.5 installed, up and running. I also installed the PMDG 737 NG ver 1.3 and here I encountered the following symptoms. I can set up a flight and program the FMC with a route and SIDS. Everything works fine. I can start the engines, taxi and take off without any problems. Once airbourne I activate VNAV & LNAV and here is the problem. The auto pilot does not do anything. The aircraft just keeps flying straight ahead and does not follow the flight plan programmed into the FMC. The route is visible on the navigational display, but the a/c is not following the displayed route. I tried clicking on the HDG button and changing the heading with the dial, but although the change in heading is visible in the navigational display, the a/c does not turn! It just flies on on the current heading. What also weird is that if I click on the auto pilot disconnect bar (or push Z) I see the disconnect button move, but the auto pilot disconnect sound is not played.This problem persists even after I have installed the 800/900 add-on and the 800/900 model + service updates. I have tried completely removing PMDG 737 with the removal tool and reinstalling serveral times without any success. Every time the same symptoms occurs. Can fly around manually, but auto pilot does not function. Every installation of FS9 and PMDG has been done under compatibility mode (Win XP SP2 - visual themes deactivated - desktop features deactivated - screen adjustment for higher DPI deactivated - run as administrator selected). I've even completely de-installed PMDG 737 and FS9 and started from scratch with the same results each time.The auto pilot does function normally with the other aircraft in FS9. Up till now the disfunctional auto pilot symptom occurs only in PMDG 737!In my last attempt I even followed the advice, which I found in another post in this forum, from Ryan Maziarz (PMDG support) by re-installing FS9 in another folder other than the standard "Program Files (x86)" folder. FS9 is now installed in its own folder "C:\Flight Sim\Microsoft Games\Flight Simulator 9". I am now completely at a loss as this last attempt did not resolve the problem either. I've now run out of ideas and I'm hoping someone here on the forum can shed some light and point me in the right direction.RegardsDave

Hi Bob,Thanks for your quick reply. Which PE resource editor do you recommend and where can I find it?In anycase, it doesn't seem to be a simple process. 8-( Before the updates one could just modify the bitmap & panel.cfg files and it was done. Any idea why they made this change?RegardsDave >Just get yourself a PE resource editor, extract the bitmaps>from the PMDG gauge file(s), mod 'em to your heart's content,>then reinsert them back into the gauge.>>Make good backups, of course, and make sure the new bitmap>matches the old one exactly in size and resolution. Also good>to always re-write the bitmap with MS ImageTool (from the SDK)>before reinserting it into the gauge file.>>Cheers>>Bob Scott>ATP IMEL Gulfstream II-III-IV-V>Santiago de Chile

Hello all,I've been told that after installing the 800/900 model & service update that it is no longer possible to change the panel bitmaps (for example the bitmap of the radio stack). Before the update one could "repaint" the radio stack bitmap. Is this true? Does this mean that all panel bitmaps are now hard-coded into the PMDG737NG?RegardsDave