Jump to content
The simFlight Network Forums
muppi

"ILH_TCAS.GAU"

Recommended Posts

Greetings all, This is my first post on this illustrious forum, I have a slight problem with the "ILH_TCAS.GAU" as it appears to be a none registered gau, and an error message pops up.

Also trying to do a trawl through the search picked out 3 pages so the simplest way to resolve this is to possibly ask the question again so I'm sorry if this is a repeat question.

2000 D:\Program Files\Microsoft Games\Flight Simulator 9\

2000 System time = 11:12:00, FS2004 time = 12:00:00 (00:00Z)

97468 FLIGHTS\OTHER\FLTSIM.flt

97500 AIRCRAFT\c172\Cessna172SP.air

97890 Aircraft="Cessna Skyhawk 172SP"

182109 Advanced Weather Interface Enabled

195734 C:\Documents and Settings\DAVID\My Documents\Flight Simulator Files\UI generated flight.flt

196922 Clear All Weather requested: external weather discarded

223375 Traffic File #17 = "scenery\world\scenery\traffic"

224297 Traffic File #33 = "scenery\world\scenery\traffic_fred_su05_philippineairlines"

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

397312 Traffic File #79 = "scenery\world\scenery\traffic_paf"

505781 AIRCRAFT\gmaxF1\gmaxF1.air

506156 Aircraft="gmaxF1 clean a"

508062 Module [M1] identified = "SuperEtendard.GAU"

591625 Traffic File #81 = "scenery\world\scenery\traffic_pai"

913672 AIRCRAFT\Lipad Nuwebe DC-9-32\lipad9.air

914047 Aircraft="DC-9-32 Cebu Pacific"

914922 Module [M1] identified = "SuperEtendard.GAU"

917390 Module [M2] identified = "Sem.GAU"

925218 Module [M2] "ILH_TCAS.gau" access registration is okay

1168734 Traffic File #73 = "scenery\world\scenery\traffic_mrai_su05_thaiairways"

2011859 AIRCRAFT\Airbus A320-214 Cebu Pacific Air (F-WWID)\Airbus320-200CFM.air

2012297 Aircraft="A320-200 Cebu Pacific Air (F-WWID)"

2016797 Module [M2] identified = "ILH_TCAS.GAU"

2016828 Illegal read attempt: offset 7B90, size 1 [P-2]

2016828Program or module not accredited for use with this unregistered FSUIPC

2022750 ### IPC Message processed in 5985mSecs ###

2140797 System time = 11:47:39, FS2004 time = 13:02:48 (05:02Z)

2140797 *** FSUIPC log file being closed

Memory managed: 2 Allocs, 8532 Freed

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

Here it's... ok 925218 Module [M2] "ILH_TCAS.gau" access registration is okay

1168734 Traffic File #73.

Next time I fly with this gau it spikes up an error guys any help with this will be very much appreciated.

Cheers,

Dave.

Share this post


Link to post
Share on other sites
Greetings all, This is my first post on this illustrious forum, I have a slight problem with the "ILH_TCAS.GAU" as it appears to be a none registered gau, and an error message pops up.

On the contrary, the ILH_TCAS gauge is confirmed as registered, thus:

925218 Module [M2] "ILH_TCAS.gau" access registration is okay

The problem appears to be with Sem.GAU, which I'm afraid I've never heard of and which certainly does not have an access key granted:

917390 Module [M2] identified = "Sem.GAU"

The odd thing here is that the this appears to be Module 2, which is the same module number as the ILH_TCAS gauge.

Could the gauge called "Sem.GAU" actually be a copy of ILH_TCAS renamed? If so, then that would be the problem -- renaming the gauge causes the identification of its calls to go wrong (obviously, FSUIPC trusts Windows to tell it the names of the gauges in memory).

Check your PANELS.CFG file, see if it loads both ILH_TCAS and SEM, or only one. If it is SEM only, change it (rename it) back to ILH_TCAS -- the GAU itself will probably be in the Gauges folder.

BTW, please always give the version number of FSUIPC in such reports. If not the latest it is always wisest to check with that first, too.

Regards,

Pete

Share this post


Link to post
Share on other sites

Hi Pete, Thanks for the reply sorry I should of put the version FSUIPC, Version 3.48, I have been unable to locate the sem.gau in my gauges folder.

There is also an error spike now and this is the cpt_F16.gau and this is a TCAS gauge and is on the A340 panel.

Cheers Pete and Thanks,

Dave.

Share this post


Link to post
Share on other sites
Hi Pete, Thanks for the reply sorry I should of put the version FSUIPC, Version 3.48

Could you update to 3.50 (or even the 3.507 available in the top announcement here) please? I doubt that it will make much difference, but it is supportable in case I need to ask you for more information.

I have been unable to locate the sem.gau in my gauges folder.

Gauges don't actually have to be in the Gauges folder, though that is most usual. The way to find them is by looking at the PANEL.CFG file (in your aircraft's Panel folder). Any editor can be used to look at it.

If the PANEL.CFG file is not loading a SEM.GAU, then there's some problem with renamed gauges there, somewhere.

There is also an error spike now and this is the cpt_F16.gau and this is a TCAS gauge and is on the A340 panel.

Not sure what you mean by "error spike"? But there's no "cpt_F16.gau" listed here that's ever had an access key.

Regards,

Pete

Share this post


Link to post
Share on other sites

Hi Pete, I have installed , version 3.50 and none of the previous errors have appeared all types of TCAS gauges are ok, so that looks good now.

Sorry about my jargon a spike is just another name for an error that pops up.

Cheers Pete and thanks,

Dave.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • 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.