Jump to content
The simFlight Network Forums

Greg Goodavish

Members
  • Posts

    35
  • Joined

  • Last visited

Posts posted by Greg Goodavish

  1. I recently purchased your Embraer 170/190 package from Simmarket.  There are no manuals that came with the package.  Where can I get them?  Also, I went to input a route into the FMS that had airways, but could not figure out how to enter airways into the FMS. Can you advise?

    --

    Mods edit subject line to reflect the questions

  2. I was flying on VATSIM today, and the controller cleared me to land on rwy 32. I tuned in the ILS freq and course (110.50/317 deg), and picked up the localizer and glideslope. However, I was to the right of the rwy, and had to leave the localizer to line up with the rwy. This could be a problem in low visibility. I don't have any other duplicate AFCAD files for KIND. Could you test your scenery, and let me know what you find for rwy 32? Thanks.

  3. OK, Pete. I opened FS9 and clicked on Fly Now. I then clicked on Help in the menu bar, and clicked on About Microsoft Flight Simulator. It showed that I have FS9.1 installed and gave a version number. However, for product ID, it said "Registry error". This might be my problem. Could you check your setup and see if you get the same? If not, should I reinstall FS9.1, and do I need to uninstall all of my scenery and aircraft addons before I do? Thanks.

  4. Pete, I do have Active Sky 6.5 on my system. I looked in the FS9 modules folder, and there is a folder in there named ASv6. Within that folder is an FSUIPC.dll (version 3.5). In my modules folder is your up to date FSUIPC. Could this cause the problem I am experiencing? Should I remove that older version from the ASv6 folder, and if so, will that cause Active Sky not to work anymore?

  5. The only error message is it says that MSFS has encountered a problem and needs to close. That is it. I just loaded up 3.932 and same thing happens. Here is the log:

    ********* FSUIPC, Version 3.932 by Pete Dowson *********

    Running on Windows Version 5.1 Build 2600 Service Pack 2

    Verifying Certificate for "C:\Program Files\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.dll" now ...

    SUCCESS! Signature verifies okay!

    Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

    User Name=""

    User Addr=""

    FSUIPC not user registered

    WIDEFS not user registered, or expired

    Module base=61000000

    ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

    WeatherOptions(Orig)=0000B027[0000B027]

    InitDelay: 0 seconds

    WeatherReadInterval=4

    LogOptions=00000001

    DebugStatus=0

    17066 System time = 16/09/2009 07:12:32

    17066 C:\Program Files\Microsoft Games\Flight Simulator 9\

    17066 System time = 16/09/2009 07:12:32, FS2004 time = 12:00:00 (00:00Z)

    51246 FLIGHTS\OTHER\FLTSIM.flt

    51402 AIRCRAFT\c172\Cessna172SP.air

    65676 System time = 16/09/2009 07:13:20, FS2004 time = 07:13:07 (14:13Z)

    65676 *** FSUIPC log file being closed

    Memory managed: 0 Allocs, 0 Freed

    ********* FSUIPC Log file closed ***********

    I also took out the FS9.cfg file, and again, same thing happens. I do not have any other addons running when this happens. The funny thing is, when this happens, it generates a FSUIPC.cfg file and a log file. If I remove those, it will start without problems the next time. But it does generate those two files again, and then the next time, unless I remove them, it closes again. I am beginning to think this might be a scenery problem.

  6. when exactly does FS crash, and is it truly what they call a "CTD" (that is a crash to desktop with no error message, no indication, nothing, just a disappearing act), or is there some information? And is there an FSUIPC.LOG to show me? And is your FSUIPC registered, or do you just have it installed to interface some of your add-ons?

    It crashes a few seconds after the intial splashscreen comes up. It says that there windows must close FS and then does. Here is the FSUIPC log that is generated:

    ********* FSUIPC, Version 3.93 by Pete Dowson *********

    Running on Windows Version 5.1 Build 2600 Service Pack 2

    Verifying Certificate for "C:\Program Files\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.DLL" now ...

    SUCCESS! Signature verifies okay!

    Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

    User Name=""

    User Addr=""

    FSUIPC not user registered

    WIDEFS not user registered, or expired

    Module base=61000000

    ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

    WeatherOptions(Orig)=0000B027[0000B027]

    InitDelay: 0 seconds

    WeatherReadInterval=4

    LogOptions=00000001

    DebugStatus=0

    60450 System time = 15/09/2009 22:32:20

    60466 C:\Program Files\Microsoft Games\Flight Simulator 9\

    60466 System time = 15/09/2009 22:32:20, FS2004 time = 12:00:00 (00:00Z)

    102773 FLIGHTS\OTHER\FLTSIM.flt

    102960 AIRCRAFT\c172\Cessna172SP.air

    124005 System time = 15/09/2009 22:33:23, FS2004 time = 22:33:08 (05:33Z)

    124005 *** FSUIPC log file being closed

    Memory managed: 0 Allocs, 0 Freed

    ********* FSUIPC Log file closed ***********

    I do not have a registered version, just use it for addon interface. I have just about every payware aircraft there is, but never had any trouble with them before. I also have Active Sky 6.5, and other addons. Again, none of them caused problems before. And I do have you latest version installed in the modules folder.

  7. I recently installed the new FSUIPC 3.93 for FS9. Now, when I start up FS9, it CTD, and it generates a FSUIPC.cgf file and text file in the modules folder. I delete those, try to start FS9 again, and it starts up OK. This happens every time. When I installed FSUIPC 3.93, this is the log file it created:

    Installer for FSUIPC.DLL version 3.93

    Looking in registry for FS9.1 install path:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1

    Parameter"EXE Path"

    Not there, so looking in:

    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1

    Parameter"EXE Path"

    ... NOT found! ...

    Looking in registry for FS9 install path:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0

    Parameter"EXE Path"

    ... >>> OK! FOUND FS9! <<< ...

    Looking in registry for FS8 install path:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\8.0

    Parameter"EXE Path"

    Not there, so looking in:

    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\8.0

    Parameter"EXE Path"

    ... NOT found! ...

    Looking in registry for FS7 install path:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\7.0

    Parameter"path"

    Not there, so looking in:

    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\7.0

    Parameter"path"

    ... NOT found! ...

    Looking in registry for FS6.1 install path:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\6.1

    Parameter"InstallDir"

    Not there, so looking in:

    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\6.1

    Parameter"InstallDir"

    ... NOT found! ...

    Looking in registry for CFS2 install path:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\2.0

    Parameter"EXE Path"

    Not there, so looking in:

    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\2.0

    Parameter"EXE Path"

    ... NOT found! ...

    Looking in registry for CFS1 install path:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\1.0

    Parameter"EXE Path"

    Not there, so looking in:

    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\1.0

    Parameter"EXE Path"

    ... NOT found! ...

    ===========================================================

    INSTALLATION FOR FS9:

    EXE Path="C:\Program Files\Microsoft Games\Flight Simulator 9\"

    Checking if there's already a version of FSUIPC installed in:

    C:\Program Files\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL

    ... Version 3.930 found.

    Okay -- installed FSUIPC into "C:\Program Files\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL"

    Now installing additional files into the Modules folder:

    Installed "FSUIPC User Guide.pdf" okay

    Installed "FSUIPC for Advanced Users.pdf" okay

    Installed "FSUIPC History.pdf" okay

    Installed "List of FS2004 controls.pdf" okay

    Installed "GlobalSign Root.exe" okay

    Installed "FSUIPC Lua Library.pdf" okay

    Installed "FSUIPC Lua Plug-Ins.pdf" okay

    Installed "Lua License.pdf" okay

    Installed "Example LUA plugins.zip" okay

    It appears it couldn't find the registry entry for FS9.1, which is installed on my machine (I use VISTA). I checked my FS9.exe file and it is version 9.1. Could this be causing the CTD and if so, how do I fix it? I don't want to reinstall FS9, as I have TONS of addons, and don't want to erase all of them again. Can you help?

  8. Hi Greg. I belong to the Midwest VA (midwestva.net). Many of us use your KMKE scenery, as that is our home hub. We also try to be realistic to load the proper amount of fuel for our flights. Several of us have found that at your KMKE scenery, for some reason, it always puts the fuel load to full in the aircraft. Even if we go in to Fuel load section on MSFS and change it, within a few seconds, it changes back to a full fuel load, which uses way to much fuel for most of our flights. This affects our VA financial performance. One of our members noticed that this doesn't happen at gate D30, but does for most of the others. Can you research and see if there might be a reason for this? It is very frustrating. Thanks.

  9. Greg, I got the email and zip file. I installed the texture files in KMKE 2006 texture folder. Still no grass around the airport and runways. And I did have the season set to summer. I tried the scenery options program again, and set all settings to max. I also indicated that I have the Milwaukee 2006 program installed. I then clicked on the apply button. Nothing seemed to happen. Is there supposed to be a message indicating the settings were applied? Maybe that is the problem, and that settings option program isn't working properly. Let me know. Thanks for helping me, Greg .

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.