Jump to content
The simFlight Network Forums

Newbie with FSUIC


Recommended Posts

Hi there

As a newbie to this topic could anyone help.

Running FS 2004 with the Viper

I am trying to make the radar panel work and get the following log file.

If I register the FSUIPC will that solve the problem?

********* FSUIPC, Version 3.14 by Pete Dowson *********

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

DebugStatus=0

2219 System time = 23:34:56

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

2250 F:\fs2004\fsuic\TrafficLook.exe

2469 System time = 23:34:56, FS2004 time = 12:00:00 (00:00Z)

6391 FLIGHTS\OTHER\FLTSIM.flt

6437 AIRCRAFT\c172\Cessna172SP.air

9297 Client Application: "TrafficLook" (Id=3476)

9297 F:\fs2004\fsuic\TrafficLook.exe

9297 Product="FS A.I. Traffic Display"

9297 Company="Peter L. Dowson"

9297 Key is provided

13328 FLIGHTS\other\FLTSIM.flt

13594 Clear All Weather requested: external weather discarded

14641 Advanced Weather Interface Enabled

32625 Traffic File #14 = "scenery\world\scenery\traffic030528"

49516 AIRCRAFT\VIPER\VIPER.air

54203 C:\Program Files\Microsoft Games\Flight Simulator\GAUGES\F16.GAU

54203 not listed in Key file

192484 READ1 02A0, 2 bytes: 34 0E

192484 READ1 0560, 24 bytes: 00 00 92 DB 31 6E 50 00 00 00

--------------------------------------------------------------------- etc----

Link to comment
Share on other sites

Running FS 2004 with the Viper

I am trying to make the radar panel work and get the following log file.

If I register the FSUIPC will that solve the problem?

There's no problem actually shown in the Log extract you provide. The section

49516 AIRCRAFT\VIPER\VIPER.air

54203 C:\Program Files\Microsoft Games\Flight Simulator\GAUGES\F16.GAU

54203 not listed in Key file

192484 READ1 02A0, 2 bytes: 34 0E

192484 READ1 0560, 24 bytes: 00 00 92 DB 31 6E 50 00 00 00

merely says that the F16.GAU isn't listed in the FSUIPC.KEY file. That doesn't mean it doesn't have access. It may be supplying its key automatically. I could tell if you enabled IPC write logging, instead of read (why DID you enable IPC read logging anyway?).

If it was being refused entry there should be an error message in the log saying so -- there isn't one. In fact there's nothing for over two minutes after it starts. Did you suddenly decide to turn the IPC read logging on after 2 minutes? That doesn't help.

The gauge may simply be reading the FS version and deciding it doesn't like FS2004, so it isn't running. Have you checked with the author, (Eric Marciano?), to see if it is supposed to work in FS2004? Many of the FS2002 gauges have such checks. I do have a fiddle which you can try if that's the case, but let's get more information first.

It looks most unlikely that this is anything to do with registration or accridatation. Don't run TrafficLook, that confuses the issue, and enable IPC read and write logging BEFORE loading the aircraft. If it's your default, enable that logging then close down and restart FS.

Regards,

Pete

Link to comment
Share on other sites

Hi Peter

Thank you for such a fast reply.

Re your question as to why I set the program up as I did..

I was trying everything to get a handle on how it all worked..

This whole topic is new to me I come from the pure business area

with relational databases and wizards and a bit of VB!

So I have a steep learning curve here.

I have reset the system as you advised.

I received an error on loading the Viper.

FSUIPC Acces Error

one of your programs is not accredited for accsess

to an unregistered copy of FSUIPC...etc

Below is the first few lines of the log.

Dick B

********* FSUIPC, Version 3.14 by Pete Dowson *********

User Name=""

User Addr=""

FSUIPC not user registered

WIDEFS not user registered, or expired

[Continuation log requested by user]

Module base=61000000

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

WeatherOptions(Orig)=0000B027[0000B027]

InitDelay: 0 seconds

WeatherReadInterval=4

83860 System time = 12:21:45, FS2004 time = 10:15:16 (17:15Z)

83860 WeatherOptions set, now 0000B027 (timer=0)

104485 AIRCRAFT\VIPER\VIPER.air

109594 Searching for IPC module user ...

109625 C:\Program Files\Microsoft Games\Flight Simulator 9\GAUGES\F16.GAU

109625 not listed in Key file

109625 READ0 3304, 4 bytes: 00 00 40 31

109625 READ0 3308, 4 bytes: 07 00 DE FA

109625 WRITE0 (failed, read-only!) 330A, 2 bytes: 4C 04

109625 Illegal read attempt: offset F000, size 2

189641 ### IPC Message processed in 80016mSecs ###

189641 Searching for IPC module user ...

189641 C:\Program Files\Microsoft Games\Flight Simulator 9\GAUGES\F16.GAU

189641 Illegal read attempt: offset F002, size 2

189641 READ0 3304, 4 bytes: 00 00 40 31

189641 READ0 3308, 4 bytes: 07 00 DE FA

189641 WRITE0 (failed, read-only!) 330A, 2 bytes: 4C 04

189891 READ0 3304, 4 bytes: 00 00 40 31

189891 READ0 3308, 4 bytes: 07 00 DE FA

189891 WRITE0 (failed, read-only!) 330A, 2 bytes: 4C 04

189891 Illegal read attempt: offset F000, size 2

189891 Illegal read attempt: offset F002, size 2

189891 READ0 3304, 4 bytes: 00 00 40 31

189891 READ0 3308, 4 bytes: 07 00 DE FA

--------------------------------------------------------------------------

Link to comment
Share on other sites

I have reset the system as you advised.

I received an error on loading the Viper.

FSUIPC Acces Error

one of your programs is not accredited for accsess

to an unregistered copy of FSUIPC...etc

Ah, that's better. You should have got that the first time.

Yes, the Log shows that the F16 Gauge is not accredited and is not providing the key. That's odd because I did supply a Key for this, to the author Eric Marciano. Or is this a different aircraft? Can you confirm that it is freeware and by Eric? If so I can give the the Key I gave him. If not, then your only alternative is to register FSUIPC as a paid-up user.

Regards,

Pete

Link to comment
Share on other sites

Pete

Thanks again.

I got the Viper from SImAviations site see below

I assume its freeware as there is no other info.

If you can send me the code.. how do I insert it?

FS2002/FS2004 PAF F-16 VIPER. This is an all NEW Gmax model of the F-16 Fighting Falcon, in a Pakistani air force paint scheme.Features include multiple loadouts, Max animation, dynamic shine, wing vapor effect, and a Virtual Cockpit. There is no 2D panel, but the panel.cfg I have included is made to work seamlessly with Eric Marciano's freeware F-16 panel. I strongly recommend you get this panel. As my Virtual Cockpit requires several of the gauges from it. View the Text Documents I've included for detail's on where and how to get this panel. GMAX F-16 model by Kirk Olsson. 6.7 MG Author: Kirk Olsson File: pafVIPER.ZIP. 6.7MB

Link to comment
Share on other sites

I got the Viper from SImAviations site see below

I assume its freeware as there is no other info.

Yes, it looks to be freeware. But more importantly it is not Eric Marciano's aircraft but it is supplied with Eric's panel. That is probably why Eric is not willing or bothered to issue the Keys I gave him -- he presumably assumes it is then the responsibility of the author who "borrowed" his work and put it in their own.

If you can send me the code.. how do I insert it?

As described, and illustrated, in the FSUIPC user guide. Enter the complete gauge name, i.e. F16.gau, and the Key which is DSVT JE5S 6DUO

Regards,

Pete

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.