by WebbPA » Tue Aug 17, 2004 12:32 pm
Interesting. Yes, it can be fixed.
What the designer has done is taken an old F16.gau and renamed it to CPT.F16.gau. There is more than one way to skin a cat but this is how I fixed it.
Follow the instructions above to get the latest F16.gau and FSUIPC, register, etc. You probably want to put F16.gau into your main gauges folder (fs9/gauges) because you may want to use with other aircraft.
Then make a copy of panel.cfg because you are going to need to edit it. Open the original panel.cfg with notepad and make these changes:
In (Window01), change these entries
gauge00=CPT.F16!Radar, 31,44,333,271
gauge01=CPT.F16!Radar Mode, 106,374,76,20
gauge02=CPT.F16!Radar Range, 229,375,74,20
to this
gauge00=F16!Radar, 31,44,333,271
gauge01=F16!Radar Mode, 106,374,76,20
gauge02=F16!Radar Range, 229,375,74,20
This tells FS to use your new, registered F16.gau instead of the old CPT.F16.gau. Of course you will need to make the change in both panel.cfg files.
If it doesn't look right click on the range or mode buttons. If you get an error message look at the modules/fsuipc.log file to make sure the gauge is properly registered.