Jump to content
The simFlight Network Forums

paulcroft

Members
  • Posts

    43
  • Joined

  • Last visited

About paulcroft

  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

paulcroft's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Peter Thank you for the speedy reply, and the justified admonishment. I've downloaded the beta and will try it tonight. You ask why I didn't check the announcements. Firstly, I did look at the announcements but, because I was looking for something specific - and it wasn't specifically mentioned in the subject titles of any of the announcements - I wrongly assumed it wasn't covered. I did open a couple of announcements and have a brief look at their contents but the reality is that I didn't think it was an fsuipc fault so didn't search all of them. I've not been using the flightsim for a couple of years now but, because fsuipc has been around for so long, and win7's beta and OEM have been around for a while too, I rather thought the fault was probably mine and was simply hoping for some advice. After your response I also did another search of your forum but this time, and with the 20/20 vision that comes with the benefit of hindsight, used the right search terms. Of course, the answer now leaped out at me. Please accept my apologies for not checking more thoroughly before posting my unnecessary query. Regards as ever Paul
  2. Hi Pete I have a new system with win 7 64 bit OS. FS9 is installed on the root drive, outside of the Program Files (x86) folder. My CH pro yoke and pedals work fine outside of fsuipc. If I disable the yoke and pedals and try to set them up through fsuipc the controls are timing out, preventing me from programming them. Attached is the latest fsuipc.log file. When this happens, if I check the joystick functionality through the OS's Control Panel>Devices and Printers they are still working fine. Any suggestions as to where the fault may lie - and how to fix it - would be appreciated. Below is the text of the log file - it is not accepted as an attachment. ********* FSUIPC, Version 3.96 by Pete Dowson ********* Running on Windows Version 5.1 Build 2600 Service Pack 2 Verifying Certificate for "C:\FS9\MODULES\FSUIPC.DLL" now ... SUCCESS! Signature verifies okay! Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="Paul Croft" User Addr="paulcroft@dsl.pipex.com" FSUIPC Key is provided WideFS Key is provided Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=40003605[40003605] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=255 765 System time = 24/02/2010 21:13:44 765 \\I7\FS9\ 796 System time = 24/02/2010 21:13:44, FS2004 time = 12:00:00 (00:00Z) 7020 \\I7\Users\Paul\Documents\Flight Simulator Files\Cessna at Biggin.flt 7020 AIRCRAFT\c172\Cessna172SP.air 7036 Aircraft="Cessna Skyhawk 172SP" 22558 \\I7\Users\Paul\Documents\Flight Simulator Files\Cessna at Biggin.flt 22636 Clear All Weather requested: external weather discarded 22948 Advanced Weather Interface Enabled 29765 Traffic File #14 = "scenery\world\scenery\traffic030528" 29796 Traffic File #20 = "uk2000 scenery\uk2000 part 4\scenery\traffic_part4" 30030 Traffic File #19 = "uk2000 scenery\uk2000 part 3\scenery\traffic_part3" 221600 WeatherOptions set, now 40003605 (timer=0) 249727 Joy 0 taking too long to respond (> 15 mSecs). Removed from scan 323016 Joy 9 taking too long to respond (> 15 mSecs). Removed from scan 323032 Joy 3 taking too long to respond (> 15 mSecs). Removed from scan 323063 Joy 8 taking too long to respond (> 15 mSecs). Removed from scan 323094 Joy 2 taking too long to respond (> 15 mSecs). Removed from scan 323110 Joy 15 taking too long to respond (> 15 mSecs). Removed from scan 323141 Joy 14 taking too long to respond (> 15 mSecs). Removed from scan 323188 Joy 6 taking too long to respond (> 15 mSecs). Removed from scan 323219 Joy 11 taking too long to respond (> 15 mSecs). Removed from scan 323266 Joy 5 taking too long to respond (> 15 mSecs). Removed from scan 323328 Joy 10 taking too long to respond (> 15 mSecs). Removed from scan 323344 Joy 13 taking too long to respond (> 15 mSecs). Removed from scan 323484 Joy 4 taking too long to respond (> 15 mSecs). Removed from scan 323562 Joy 12 taking too long to respond (> 15 mSecs). Removed from scan 323609 Joy 7 taking too long to respond (> 15 mSecs). Removed from scan 336214 Joy 1 taking too long to respond (> 15 mSecs). Removed from scan 343858 System time = 24/02/2010 21:19:27, FS2004 time = 12:37:50 (11:37Z) 343858 *** FSUIPC log file being closed Memory managed: 0 Allocs, 356 Freed ********* FSUIPC Log file closed *********** Thanks Paul
  3. Logic? Without being told otherwise one train of logic might suggest this is the right thing to do, in the same way that FS requires you to choose whether or not to repeat an action when assigning actions to keys as, e.g., trim up and trim down. Unless the 'repeat' function is requested you can hold the key down for ever but it will still only send the one initial keypress. Besides, it works fine until you need the button press to send more than one command, so the error would not have been apparent to the author under 'normal' test. Given my own comments above might it be worth reinforcing that by also adding a comment to NOT check the box? Just a thought. Regards as ever,
  4. Yes, finger slip. As for the R and P problem, I was checking the "control to repeat while held" option because that is what the instructions say to do in the included document "How to set up Push To Talk.doc" that comes with widefs.zip :? You are right though, if I uncheck this option I get a P, not an R. Regards as ever
  5. Hi Pete I'm using 6.48 and mine produces a Repeat. And glad we are that you did . At least that explains why it doesn't work using the same key for all. Regards as ever,
  6. Hi Pete All working OK now. As suggested, it was the P instead of the R which rectified matters. I'd used the R because that is the value which gets set when the button values are set via Modules>FSUIPC>Buttons but, on reading the literature, it all makes sense. Interestingly, I thought afterwards that it would make sense simply to set one key (e.g. F12) as the PTT key for RW/AVC/SB3 and Teamspeak to obviate this added complexity but, when I did this, I couldn't transmit on RW/AVC/SB3. As soon as I set the wideclient.ini value back to Rwon/Rwoff it worked fine. Ho hum ... Anyway, all up and running fine now. Thanks very much for your help.
  7. Hi Pete Am I having a senior moment? I've read the Advanced User Guide and tried this but with no success. If you can spot what I've done wrong I'd appreciate it. Currently the [user] section of wideclient.ini reads: ================ Actionkeys=Yes ; The below values are for VatSim: KeySend1=Rwon KeySend2=Rwoff ; The below values are for TeamSpeak: UseSendInput=Yes KeySend3=123,16 KeySend4=123,24 ================ and the [buttons] section of fsuipc.ini reads as follows: ============== 1=R0,0,C1006,1 2=U0,0,C1006,2 3=R0,0,C1006,3 4=U0,0,C1006,4 ============== Using this configuration PTT only works for KeySend1 and 2. It may send Keysends 3/4 at the same time but either widefs isn't translating them or TeamSpeak isn't recognising them. The only way I can get this to half work at the moment is to leave wideclient.ini as it is, delete the values 3=R0,0,C1006,3 and 4=U0,0,C1006,4 from fsuipc.ini and change the button's KeySend values from within FS (via Modules>FSUIPC>Buttons) as and when required. Your advice, as ever, is greatly appreciated.
  8. Hi Pete I fly online with both VATSIM and IVAO. I have a 2 pc setup and use PTT through a CH Pro yoke. As you are aware, at the moment SB3 and Teamspeak require different keysend parameters and the way I deal with this is to have two different wideclient.ini files and swap them around as necessary. Is there a switch I can use when starting widefs with which I can specify a specific ini file to be used? I envisage using two desktop shortcuts for starting widefs, labelled appropriately, so that I can start widefs using the shortcuts without the need to manually swap ini files around first. Or am I missing something blindingly obvious ... Best regards
  9. How high should I go to see this Pete? I cannot see it at 10,000'. Not that I want to see it you understand ( :) ) but I'd rather like to find out if it really has gone now.
  10. Hi Pete Thanks so much for taking the time to explain what's going on. As it happens, in the meantime I've been experimenting with different video drivers and the latest nVidia WHQL set seem to have fixed it. I hadn't actually expected this to work because (a) I was certain that the problem preceded my last driver change, and (b) I rarely change video drivers since it's my experience they're usually 2 steps forward and 1 step back :). Nonetheless it seems to be fixed now and I've learnt something more about how FS works into the bargain. Thanks again for taking the time to explain and best regards
  11. Hi Pete When I have visibility limits enabled (virtually all the time) I can see translucent white 'diamonds' being formed on the ground beneath me. They appear to be possibly the tiles of the underlying textures. These only extend for a defined area underneath where the aircraft is flying, not all the way to the horizon. The degree of transparency increases or decreases with the range I set, i.e. if I set vis limits to 60 miles on a clear day the tiles are more transparent than when the vis limit is set to 30 miles. These translucent diamonds are present whether or not there are any clouds in the sky. I use the FSW clouds. I have tested and the problem also exists with the default clouds. I know FSUIPC is not the cause but I wondered if you or any of your readers might have come across this before and be able to guide me in the right direction. Thanks in advance
  12. Many, many congrats Peter. Thoroughly well deserved. http://awards.simflight.com/winners2003.htm
×
×
  • 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.