Jump to content
The simFlight Network Forums

pccitgo

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by pccitgo

  1. I am trying to use In Cabin Browser to view my Instrument Approach charts. Once installed the browser window sits on the bottom edge of the screen. I would like to move it up a bit. I would like the browser to appear mid way between the top of the screen and the bottom and on the left side of my monitor. I would also like to make the browser screen long enough so I can see all of the chart.

    I tried setting the height in the config screen to 900 that did not help and now the browser screen config button is hidden below my screen. I cannot find a way to undo the changes so I can access the Config button. I can only now uninstall and reinstall to get back to the original " too short" screen. Can you help?

    Peter

  2. Hi Peter,

    I have installed the Dodosim Advanced 206 Jetranger sim and am experiencing a problem with the collective axis which is assigned to the Z axis in FS9. No other FS9 assignments use this axis. I have the latest Saitek throttle, stick and pedals.

    I have set the sensitivity and null zone to the correct values as per Dodosim's instructions and checked in my Saitek X52 Pro Calibration screen that all is OK with regard to range of movement.

    On starting the simulator I am unable to control the collective. The lever starts jumping up and down when I attempt to pull collective and the torque gauge fluctuates wildly.

    Obviously something else is attempting to overide my control inputs. As a troubleshooting measure I removed my FSUIPC.dll file from the Modules folder and restarted FS9. The problem disappeared.

    I have checked the Axis page in FSUIPC 3.743 (registered) and can find nothing assigned to any axis. Also under the joystick calibration screen all axis are unassigned. Not too sure how to proceed from here.

    I did try to use only the FSUIPC setup for the collective by deleting the FS9 assignment but that did not work too well as my throttle lever (collective) needed to use a third of its travel before the collective actually moved. The calibration screen, with the reverse box ticked, showed the OUT value at zero until the IN value beginning at minus 16,000 reached about plus 300 as I moved the throttle up. I could not find a way to change this.

    I am happy to continue using the FS9 only setup but would like to be able to put FSUIPC back in the Modules folder but without it causing the control conflict problem.

    Many thanks in advance,

    Peter

  3. Hi Pete,

    Just installed latest drivers of Nvidia site for 8800GTS, Vista, 32 bit and results are the same. I would be interested to see if any other users with a similar setup to mine have had the same issue. I believe there is an update to Vista due soon.

    As you might imagine it is a big job transferring all the payware stuff over from my old machine to this superdooper one. Your FSUIPC, Active Sky, Radar Contact, SSTSIM Concorde, etc etc.

    The decision to go with Vista was not taken lightly and these problems were anticipated with the hope that eventually the problems would be addressed with updates and fixes. Saitek have just issued a beta fix for their X52Pro software for example. Time will tell.

    Cheers

    Peter

  4. FSUIPC is vers 3.743

    I tried it again and same result after exacting updated version from your website link.

    and this is what Vista advises after CTD

    Problem Event Name: AppHangB1

    Application Name: fs9.exe

    Application Version: 9.1.0.40901

    Application Timestamp: 4135a208

    Hang Signature: 7348

    Hang Type: 6144

    OS Version: 6.0.6000.2.0.0.768.3

    Locale ID: 5129

    Additional Hang Signature 1: 14dfbae485370538665722fd9de48432

    Additional Hang Signature 2: bc5f

    Additional Hang Signature 3: f4e79f1080bf6e83e42d79ed5200f654

    Additional Hang Signature 4: 7348

    Additional Hang Signature 5: 14dfbae485370538665722fd9de48432

    Additional Hang Signature 6: bc5f

    Additional Hang Signature 7: f4e79f1080bf6e83e42d79ed5200f654

    Log file reads: I have xxx'ed out personal stuff

    ********* FSUIPC, Version 3.743 by Pete Dowson *********

    Running on Windows Version 5.1 Build 2600 Service Pack 2

    Verifying Certificate for "D:\Program Files\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.dll" now ...

    SUCCESS! Signature verifies okay!

    Running inside FS2004(original release)

    User Name="xxx"

    User Addr="xxx.co.nz"

    FSUIPC Key is provided

    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=1

    1045 System time = 17:14:26

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

    1045 System time = 17:14:26, FS2004 time = 12:00:00 (00:00Z)

    1716 FLIGHTS\OTHER\FLTSIM.flt

    1731 AIRCRAFT\c172\Cessna172SP.air

    7566 C:\Users\xxx\Documents\Flight Simulator Files\concorde.flt

    7613 AIRCRAFT\BAe-Concorde\Concorde.air

    8674 Clear All Weather requested: external weather discarded

    23213 Advanced Weather Interface Enabled

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

  5. I have loaded a fresh install of FS9 into my brand new computer and copied across from my old computer's flight sim 9 modules folder my key file and latest FSUIPC.dll into the new computers FS9/Modules folder. I have not copied the .ini file.

    I have selected run fs9.exe as Administrator and started a session of FS9. I go Alt, Modules and as soon as I select FSUIPC the program crashes to desktop.

    The Vista is 32 bit Home Premium.

    Any ideas how to get this working please.

    Peter

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