Jump to content
The simFlight Network Forums

Jonahbird

Members
  • Posts

    60
  • Joined

  • Last visited

Posts posted by Jonahbird

  1. Hi Pete

    I hope you had a good holiday. LAN stands for Local Area Network, so I should perhaps have referred to 'Local Area Connection' (LAC).

    I use Vista32 on this machine and in the 'Network & Sharing Center' you can select 'View Status' of the LAC. This takes you to 'Windows Network Diagnostic'. Click on 'Diagnose' and you get 2 options. One is 'Reset the network adapter for Local Area Connection'. This corrects my problem. It shouldn't be necessary to do that, and I don't know why it is happening - yet!

    I do know that WideFS is not at fault. It worked fine before I chose to switch anti-virus protection from McAfee to AVG Internet Security (the full version of AVG free).

    Best regards

    Frank

  2. For some years, I have been successfully using WideFS (included with my FSUIPC4 licence) with AVG Free on my 'flying' PC and McAfee on my general PC. This is to enable use of FSCommander on my general PC.

    A few days ago, my McAfee licence expired and I decided to switch to the full version of AVG on both machines. Now I cannot get WideFS to work. Has anyone else experienced this? I did not install AVG's firewall, as I use a Netgear router. Windows firewall is on, as it always has been. I have excluded WideClient.exe and WideServer.dll in AVG's Resident Shield options.

    Any other suggestions, please?

    Frank

  3. Hi Jean-Jacques

    I hope you are still reading this thread. Volker has solved my problem and I suspect it could prove to be the answer for you too.

    You are correct in deducing that the scenery.cfg file is at fault. As I don't know what knowledge you have already I will try to give a simple answer, and stand willing to clarify if asked for further detail. Remember, I use Vista64 and run FSC on a separate networked computer, linked by WideFS. This problem is peculiar to network structures.

    The active scenery.cfg file entry for any airfield (or batch of airfields as in UK2000's VFR Airfields Vols. 1 & 2 ) must have a last line written in the following format:

    Local=UK2000 scenery\UK2000 Belfast Xtreme. I went through the file and altered all the wrong ones. Then ran the special exec file and then the DataBase Manager. Booting into FSX did the rest. And - that's it.

    I hope this helps you

    All the best

    Frank

  4. Hi Sascha & Volker

    Many thanks for that information. I am already well versed in the way scenery.cfg files are written and where they are stored, but the rest of what you say is very helpful. May I ask some questions?

    1) Does the special tool (scenerycfg.fsc) have to be renewed when new addons are installed?

    2) You say >>if the add-on scenery has been installed under FSX/Scenery together with the original Microsoft files, because as a consequence the Database Manager will find two conflicting *.bgl files under the same directory. Therefore, an add-on scenery should NEVER BE INSTALLED under FSX/Scenery, but rather in ANY other location.<<

    Does this mean 'in the scenery folder' or in another folder within FSX? Because Addon Scenery, Aerosoft, UK2000 Scenery and MyTraffic are in their individual folders within the FSX folder. Should they be elsewhere? They are not in FSX/Scenery.

    Regards

    Frank

  5. Hi Sascha & Volker

    I apologise for omitting from my recent submission the details necessary to get a response from you. Here they are:

    1. FSX

    2. FSUIPC/WideFS version 4.53

    3. FSC & DBM version 8.6 build 101209

    4. Download

    5. OS is Vista64 on dedicated flight sim computer

    Vista32 on networked general computer - FSC & DBM are on this computer.

    My question is why does FSC choose to base the airports on MyTrafficX BGLs? I believe the runway difference I see for Manchester is because the UK2 BGL is not selected.

    I am unused to writing in this forum. In other places, I frequently praise FSC as a better program than the much missed FSNavigator. Thank you for producing FSC.

    Best regards

    Frank Jones

  6. Hi Jean-Jacques

    Well, I'm up (04.45 - an earlybird!). Trying a wide global selection, I find that all my airports in FSC are based on BR2 files. Files prefixed in that way are My Traffic files. As you are seeing the stock file for Manchester my guess is that all yours are based on the stock files. Do you have My Traffic, or any other AI addon?

    I can't see anything here to suggest that my FSX's scenery cfg file is involved with FSC's selection of files on which it bases its program. What has caused you to conclude that?

    Regards

    Frank

  7. Hi Jean-Jacques

    Thank you for your input, and my apologies for not complying with the forum posting guidelines. I will sign off with my name; it was rude of me not to do so.

    I have been thinking about what might be the problem. I use Vista64 on 3 monitors TH2G linked. FSC is on another networked computer and is linked as directed. I only use FSX and FSUIPC4 is the full version and is up-to-date.

    I see that FSC bases Manchester on BR2_EGCC.BGL which is clearly not the right file. My guess is that I have to try and direct the DBM to the appropriate UKScenery file.

    It is late now, so I will try that tomorrow.

    Regards

    Frank

  8. Pete

    FSUIPC for setting buttons on Yoke and Avionics is easy to use and very flexible. I will now ignore PFCFSX for that job.

    Also using the PFC software I have succeeded in retuning the ailerons. You were very kind not to tell me to RFM. It is quite a while since I read the User Guides in full. I am now going to do that to discover what else I should be using FSUIPC for.

    Your headsup on the chip led me to email support at PFC. They responded immediately and I am purchasing the latest chip for install in the Avionics box. Ivan at PFC has been very helpful. He confirms that the flickering LDG GEAR lights will be put right by the new chip.

    Once again, many thanks for all your help.

    Frank

  9. Pete

    Sorry - after I sent the last reply I thought that last bit was not clear. The PFC one still does not work. I was talking about the one in FSUIPC. That dropdown contains many other possibilities I don't recall seeing before. As I said FSUIPC is quite brilliant. I like the 'workaround'. I can understand why you use that method.

    You are right, my console does not have an aileron trim on it. I now understand what you are recommending. I'll give it a try.

    Regards

    Frank

  10. Thanks again, Pete. I've learned a lot today - and at 75 I'm glad to still be learning anything!

    I found the "Trim/shaker motors fitted" and that wasn't ticked. So I can forget that.

    As to the banking problem, when you say "it is almost certainly the aileron trim out of whack, etc" are you referring to the hardware?

    I will "check both" - but where?

    The major breakthrough (for me!) in your answer was the final para. That is a truly great way to set PFC. It will take a little time but to make it aircraft specific seems to be a great advantage. I am trying it on a Cessna for the moment, and it really does work. Brilliant.

    The surprise to me was that after gingerly choosing the FS Controls dropdown all choices were there.

    Warmest regards

    Frank

  11. Pete

    Thank you for that helpful and informative reply. I will answer the questions seriatim:

    - FSUIPC4 is registered, and both that and PFCFSX are versions 4.30

    - Yes, I have "used the same facility" with these versions

    - CONTROLS.DLL is dated and timed 10.12.2007 22:29 (incidentally, is there any way I could read that?)

    All DLLs are dated and timed the same, except the following:

    GameuxInstallHelper 5.7.2006 22:13

    Gauge Sound 4.2.2008 15:16

    TCAS2v7 5.7.2008 10:11

    WaveLIB 5.7.2008 10:11

    - FSUIPC4 doesn't crash when I try to drop down, etc

    - I can't find the "Motor Trim" option.

    - I have tried re-calibrating the yoke with no success, but will try that again when the main problem is sorted.

    - I think you were right about the aileron trim. I was using a saved flight and have deleted that now. The fault didn't show on the default flight.

    But the main problem remains.

    Frank

  12. Hi Pete

    I've been using your software for about 15 years. It's indispensable; thank you for all your hard work.

    I have a dedicated high spec PC, and use only FSX. I do have the latest FSUIPC4 and PFCFSX.dll installed. My PFC console is 7 years old, and I know that product quite well. A few days ago I encountered an unfamiliar problem. When I tick 'List all FS Controls' and try to drop down the choices, nothing happens and after a few seconds FSX shuts down. Without the tick I can operate PFC's buttons OK, but when I seek the greater choice this failure occurs.

    Immediately before I noticed this problem I had installed a trial for Vox ATC and done a major defrag using Ultimate Defrag. Thinking it may have highjacked the FS Controls I have uninstalled Vox ATC, but the problem remains. I did notice that Vox ATC contains a file called FSUIPCInt.dll and wondered if that could have caused a corruption.

    I suspect a corrupted file somewhere, possibly in FSX, and I fear a complete reinstall. But before I do that I am seeking your experienced input. On the hardware there two faults evident - the green LDG Gear lights flicker on and off occasionally and the yoke needs to be held down left to prevent banking to the right. So hardware may be the cause.

    I will be most grateful for your help.

    Frank

  13. Hi Pete

    Are you absolutely sure that file is there, in that folder?

    I was!!!! but you've hit the nail right on the head. A full search reveals several copies in different places!! - none of them in that folder!!! I think I'm losing it.

    Thanks for your patience and help. I will now sort out the various folders and get the correct instruction into FSUIPC4.ini

    Best regards

    Frank

  14. Hi Pete

    Old age strikes again! You are, of course, right - that log was after I had removed the "runif1" line.

    My use of the word 'tablet' is meant to describe a small window. It appears when FSX has opened to the point where I have the panel of the aircraft on screen. It is headed FSUIPC INI FILE and, after an ! in a yellow triangle, it says - FSUIPC couldn't run: "D:\FSX\Modules\FS_COM.exe"[Error=2]. It stutters on and off then FSX closes.

    FSUIPC4.ini says

    [General]

    History=19L88OBAVJAWBYLGA1VGF

    TCASid=Flight

    TCASrange=40

    AxisCalibration=No

    DirectAxesToCalibs=No

    ShowMultilineWindow=Yes

    SuppressSingleline=No

    SuppressMultilineFS=No

    WeatherReadFactor=2

    SimConnectStallTime=1

    GraduatedVisibility=No

    LowerVisAltitude=0

    UpperVisAltitude=25000

    UpperVisibility=10000

    MinimumVisibility=0

    MaximumVisibilityFewClouds=0

    MaximumVisibility=0

    MaximumVisibilityOvercast=0

    MaximumVisibilityRainy=0

    SetVisUpperAlt=No

    VisUpperAltLimit=0

    ExtendMetarMaxVis=No

    OneCloudLayer=No

    ThinClouds=No

    ThinThunderClouds=No

    CloudThinness=1000

    ThunderCloudThinness=10000

    CloudTurbulence=No

    CloudIcing=No

    GenerateCirrus=No

    SuppressCloudTurbulence=No

    MaxIce=3

    MinIce=-1

    ExtendTopWind=No

    UpperWindGusts=No

    SuppressWindTurbulence=No

    WindTurbulence=No

    SuppressAllGusts=No

    MaxSurfaceWind=0

    WindLimitLevel=200

    WindDiscardLevel=400

    WindAjustAltitude=No

    WindAjustAltitudeBy=2000

    DisconnTrimForAP=No

    ZeroElevForAPAlt=No

    ThrottleSyncAll=No

    WhiteMessages=No

    ShowPMcontrols=No

    MagicBattery=No

    RudderSpikeRemoval=No

    ElevatorSpikeRemoval=No

    AileronSpikeRemoval=No

    ReversedElevatorTrim=No

    ClockSync=No

    ClockSyncMins=5

    ClearWeatherDynamics=No

    FixWindows=No

    OwnWeatherChanges=No

    TimeForSelect=4

    LoadFlightMenu=No

    LoadPlanMenu=No

    PauseAfterCrash=No

    ShortAircraftNameOk=No

    NoAxisIntercepts=No

    [WideServer]

    WideFSenabled=Yes

    [GPSout]

    Port=

    Speed=4800

    Interval=1000

    PosTo6Decimal=Yes

    Sentences=

    GPSoutEnabled=No

    [AutoSave]

    AutoSaveEnabled=No

    [Programs]

    runif1=HIDE,READY,CLOSE,D:\FSX\Modules\FS_COM.exe

    and the FSUIPC4.log says

    ********* FSUIPC4, Version 4.103 by Pete Dowson *********

    User Name="FRANK JONES"

    User Addr="jonesfrn8@aol.com"

    FSUIPC4 Key is provided

    WIDEFS7 not user registered, or expired

    Running inside FSX (SimConnect SP1 May07)

    Module base=61000000

    DebugStatus=15

    219 System time = 15:13:40

    219 FLT UNC path = "C:\Documents and Settings\Frank\My Documents\Flight Simulator X Files\"

    219 FS UNC path = "D:\FSX\"

    2047 LogOptions=00000001

    2062 SimConnect_Open succeeded: waiting to check version okay

    11453 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0)

    130141 SimStart Event: Initialising SimConnect data requests

    130141 FSUIPC Menu entry added

    130281 C:\Documents and Settings\Frank\Application Data\Microsoft\FSX\Previous flight.FLT

    130281 D:\FSX\SimObjects\Airplanes\beech_baron_58\Beech_Baron_58.AIR

    Best regards

    Frank

  15. Hi Pete

    The version is 4.103 and the latest Log file says

    ********* FSUIPC4, Version 4.103 by Pete Dowson *********

    User Name="FRANK JONES"

    User Addr="jonesfrn8@aol.com"

    FSUIPC4 Key is provided

    WIDEFS7 not user registered, or expired

    Running inside FSX (SimConnect SP1 May07)

    Module base=61000000

    DebugStatus=15

    62 System time = 13:29:41

    62 FLT UNC path = "C:\Documents and Settings\Frank\My Documents\Flight Simulator X Files\"

    62 FS UNC path = "D:\FSX\"

    2109 LogOptions=00000001

    2125 SimConnect_Open succeeded: waiting to check version okay

    5422 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0)

    30015 SimStart Event: Initialising SimConnect data requests

    30015 FSUIPC Menu entry added

    30187 C:\Documents and Settings\Frank\Application Data\Microsoft\FSX\Previous flight.FLT

    30187 D:\FSX\SimObjects\Airplanes\beech_baron_58\Beech_Baron_58.AIR

    133984 PFC Menu entry added

    135125 System time = 13:31:56, FSX time = 11:45:01 (10:45Z)

    135281 Aircraft="Beech Baron 58 Paint1"

    136500 Advanced Weather Interface Enabled

    774000 System time = 13:42:35, FSX time = 11:54:57 (10:54Z)

    774000 *** FSUIPC log file being closed

    Memory managed: 383 Allocs, 383 Freed

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

    Thanks you for responding so quickly.

    Frank

  16. I have upgraded FSX with its SP1. To do this I first did a complete uninstall and am gradually re-installing addons - hardware and software.

    After many trials and errors I still can't get the "runif1" line to connect FS_COM automatically on start up. I have added the prescribed line to FSUIPC4.ini under [Programs] but an error tablet prevents FSX from opening. FS_COM can be opened manually to operate the MCP.

    It did work before SP1 and FSUIPC4.

    Am I missing something?

    Frank Jones

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