Jump to content
The simFlight Network Forums

FSUIPC and payware aircraft


Recommended Posts

Hi Peter! I hope you can help me; I am having a hecka a time attempting to get FS9 and my payware aircrafts to run with the FSUIPC v. 3.53 installed. FS9 will run all aircraft w/o the module which I carefully read thru your docs to comfirm it's proper install, but with it installed in the modules folder only with the default aircraft will FS9 load and run. I become frustrated because the payware had initially run, but when a new payware aircraft is loaded it porks them all and ASv.6 as well. Plz review FSUIPC logs and list of payware aircraft I really need a clue as to what to do. I use payware support forums and they point to this forum. I've attempted clearing prefetch and temp folders w/ no avail.

Thanks in advance!!

System specs:

WinXP

AMD 3000

1056mg RAM

ATI 9800 128

80gig HDD

Payware:

*Eaglesoft Cirrus SR22

*PMDG B1900C

*Aeroworx KingAir B200

*PSS Airbus Base

*Dreamfleet Baron 58

********* FSUIPC, Version 3.53 by Pete Dowson *********

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

6531 System time = 20:35:05

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

6531 System time = 20:35:05, FS2004 time = 12:00:00 (00:00Z)

11343 FLIGHTS\OTHER\FLTSIM.flt

11437 AIRCRAFT\c172\Cessna172SP.air

12093 Aircraft="Cessna Skyhawk 172SP"

17843 Client Application: "ASv6" (Id=3212)

17843 C:\Program Files\Microsoft Games\Flight Simulator 9\Modules\ASv6\ASv6.exe

17843 Product="ActiveSky 6"

17843 Company="HiFi Simulation Software"

39062 Program [3212] "ASv6" access registration is okay

40828 Module [M1] identified = "sb3gaugebridge.dll"

40828 Module [M1] "sb3gaugebridge.dll" access registration is okay

40890 Module [M2] identified = "ActiveRadar.dll"

40906 Module [M2] "ActiveRadar.dll" access registration is okay

42734 Advanced Weather Interface Enabled

56031 NWI weather clear actioned

56031 External weather discarded

56031 WeatherOptions set, now 0000B12F (timer=255)

70468 AIRCRAFT\Aeroworx Super King Air B200\awxb200.air

71125 Aircraft="Aeroworx Super King Air B200 - 2D EFIS Cockpit & VC"

84156 Module [M1] identified = "sb3gaugebridge.dll"

288890 C:\Documents and Settings\xxxxx\My Documents\Flight Simulator Files\UI generated flight.flt

293125 Clear All Weather requested: external weather discarded

Link to comment
Share on other sites

I am having a hecka a time attempting to get FS9 and my payware aircrafts to run with the FSUIPC v. 3.53 installed. FS9 will run all aircraft w/o the module which I carefully read thru your docs to comfirm it's proper install, but with it installed in the modules folder only with the default aircraft will FS9 load and run.

FSUIPC doesn't do anything with any aircraft. Some aircraft use it, but even then only usually for stuff like TCAS displays. You have something else wrong with your system.

17843 Client Application: "ASv6" (Id=3212)

17843 C:\Program Files\Microsoft Games\Flight Simulator 9\Modules\ASv6\ASv6.exe

17843 Product="ActiveSky 6"

17843 Company="HiFi Simulation Software"

39062 Program [3212] "ASv6" access registration is okay

40828 Module [M1] identified = "sb3gaugebridge.dll"

40828 Module [M1] "sb3gaugebridge.dll" access registration is okay

40890 Module [M2] identified = "ActiveRadar.dll"

40906 Module [M2] "ActiveRadar.dll" access registration is okay

42734 Advanced Weather Interface Enabled

56031 NWI weather clear actioned

56031 External weather discarded

56031 WeatherOptions set, now 0000B12F (timer=255)

This shows ASv6 has connected okay, and has cleared the weather and set the FSUIPC weather options. It also shows some Squawkbox stuff running okay.

I really have no idea what your odd term "porks" means, but this shows ASv6 is working with FSUIPC okay. The log also shows that no aircraft (loaded in this part) are using FSUIPC, so it won't have any affect on them whatsoever.

Next time you show me a log please make sure it is a complete log -- i.e. close FS first.

Regards,

Pete

Link to comment
Share on other sites

Pete, by "porks" he means a complete CTD.

For the record, the Eaglesoft Cirrus SR20/22 a/c don't use FSUIPC at all for any reason. Our transponder does use the sb3gaugebridge.dll interface, but then only when SB3 is loaded.

Link to comment
Share on other sites

Pete, by "porks" he means a complete CTD.

Ah. How quaint!

If he's getting ASv6 CTDing he most certainly needs to deal with their support. There's no way I can get inside someone else's program even if it was something I should be doing. The ActiveSky folks should be able to get to the bottom of it with enough information. It obviously connects to FSUIPC okay as his log shows.

Pete

Link to comment
Share on other sites

Hi All,

I saw his log last night here and thought the same thing, nothing wrong. It looks like a system problem because he states that it only happens with a payware plane and it closes down both FS and ASv6. Now, for a plane to shut down both programs is pretty unique.

To the first poster: How much free space is on your HD?

At what point does FS04 crash?

Have you tried with Render to Texture set the opposite it is now?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.