Jump to content
The simFlight Network Forums

jordanal

Members
  • Posts

    158
  • Joined

  • Last visited

Everything posted by jordanal

  1. Hi again, Well, the guys over at CH believe the Yoke, TQ, and rudder pedal devices are working properly becuase they seem to properly populate the game contolers GUI in the Control panel and they are in the registry in their normal place. Also the fact that both FS9 and FSX see the devices as well. I have since completely uninstalled all FSX addons, FSX, and FSUIPC4. Rinstalled FSX, SP1, and FSUIPC4 v4.104 and still get the same affect. I can still see buttons in the bottons tab, but not axis in the axis assignments tab. Axis still work if I enable controllers from the FS menu. dxdiag continues to indicate all devices are working properly, including directinput devices. I am back to the conclusion that it has something to do with the SP1 patch and FSUIPC4. :? I look forward to further deugging this issue with you upon your return from vacation. I hope you had a good rest because this issue has me perplexed and I am not about to give up. v/r, AL
  2. OK, let's wait until you get back. Besides, I want to try something else while you're out of town. I did a bit more reading today and I discovered that the CH Control Manager v4.2 software and drivers were not ready for Vista and I had them installed up until I started troubleshooting this issue, yesterday afternoon. I really don't need it anyway as I'm not running any customized CH maps for my CH devices. But, I now think my devices might be mixed up in the registry and I need to get them cleaned out. For that I will visit the CH forums for their assistance. My hope is, I will have a working system by the time you return. If not, I will meet you back here around the 7th of June. Thanks again, 8) AL
  3. Oh, sorry, I should have read that more carefully. Understand now, I'll have an answer for you the minute I get home. Hi Pete, The answer is YES, I can see the numbers move in the Calibration tab when I have Controls enabled on the FS menu. But I still don't understand what this means. Thanks AL
  4. Oh, sorry, I should have read that more carefully. Understand now, I'll have an answer for you the minute I get home. I see, I was just curious having seen the word "Airleron" while having axis issues. I just arrived at work this morning, so will continue to troubleshoot this as soon as I get home later this afternoon, EST. Meanwhile, I'm sure I'll be burning a few brain cells thinking about this during the day today. Honestly Pete, Thanks again. I know you're terribly busy these days. AL
  5. Darn Pete, don't you ever go to sleep? What is it, 4am over there now? Do you have an alarm or something every time you get a post in this forum? :D I have never, ever not seen you quickly answer a question here. Amazing... Obviously, you know what I meant, LOL Nope, no change; still can't see axis numbers in the assignemnts tab even with FS controls enabled or disabled. Yes, button assignments have been working flawlessly in my original, more elaborate ini file. Joystick #'s continue to appear on the buttons tab while I'm troubleshooting with my fairly empty, newly generated ini file. Makes sense. I redownloaded the latest DirextX redistributable (4/07) and let it update any nesseccary files and rebooted. Dxdiag indicates all devices are nominal and functioning properly but it did not solve the issue unfortunitly. Understood, I just do far too much geeking to constantly be switching permissions and roles. I'll keep lookin around or make additional logs if it'll help. BTW, from the previous log above, what does this mean? I don't see anything similar in my FSUIPC3.log file. 49468 SimRead: 0BB6="AILERON POSITION" FLT64: -6.10388817677e-005 Thanks again, AL
  6. Hi Pete, Sorry to bother you but I'm a bit stumped. Using FSX-SP1 and FSUIPC4 v4.10 & v4.104, I seemed to have lost my axis assignments and calibration inputs to FSUIPC4. In other words, no device or axis numbers ever show up on either the assignments tab or the calibration tab. This was working up until very recently and SP1 and FSUIPC4 are the only things I can think of that have recently changed. Clean install of FSX prior to SP1, then FSUIPC4/WideServer7 (registered). This is on Vista-Ultimate x86 rig by the way with my account having administrator priviledges and UAC is turned off. Here is what I do know or have tried so far: Both FS9 (still installed) and FSX-SP1 have joysticks disabled in FS menu My CH Yoke, Throttle & Pedals calibrate fine in Windows game controllers all axis are still seen using FSUIPC3 and FS9 in assisngment and calibration tabs FSUIPC4 can see the buttons of these CH devices, but not axis If I temporarily enable joysticks in the FSX menu, then axis movement is seen on aircraft Have tried newly created FSUIPC4.ini file by renaming my original copy and restarting FSX Wideserver7 is connecting properly to my wideclient I'm sure I'm missing something simple that I've probably overlooked. :roll: As always, I appreciate any thoughts you might have... AL Copy of most recent FSCUIPC4 log file follows: ********* FSUIPC4, Version 4.104 by Pete Dowson ********* User Name="" User Addr="" FSUIPC4 Key is provided WideFS7 Key is provided Running inside FSX (SimConnect SP1 May07) Module base=61000000 DebugStatus=255 63 System time = 19:53:55 63 FLT UNC path = "\\ALCOMP\C\Users\jordana\Documents\Flight Simulator X Files\" 63 FS UNC path = "\\ALCOMP\I\Microsoft Flight Simulator X\" 1123 LogOptions=00000001 1123 SimConnect_Open succeeded: waiting to check version okay 4384 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0) 49374 SimStart Event: Initialising SimConnect data requests 49374 FSUIPC Menu entry added 49406 C:\Users\jordana\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 49406 I:\Microsoft Flight Simulator X\SimObjects\Airplanes\beech_baron_58\Beech_Baron_58.AIR 49468 SimRead: 0BB6="AILERON POSITION" FLT64: -6.10388817677e-005 49920 System time = 19:54:45, FSX time = 19:54:00 (23:54Z) 50061 Aircraft="Beech Baron 58 Paint3" 50451 Advanced Weather Interface Enabled 102025 System time = 19:55:37, FSX time = 19:54:10 (23:54Z) 102025 *** FSUIPC log file being closed Memory managed: 10 Allocs, 10 Freed ********* FSUIPC Log file closed ***********
  7. Nevermind, been still using FS9 until today and I forgot WideFS is included in FSUIPC4. Help, I need some version control! To much to do using both FS9 & 10! LOL... :D AL
  8. Pete, Does the current version of WideFS on the download page work with FSX-SP1 or is there a new version coming for it as well? Thanks for your timely update of FSUIPC4! AL
  9. I'm sure the docs do explain it but I'm lacking the time this evening. I"ll figure it out in the coming days. No big deal at the moment, and like I said, everything else seems to work well. AL :)
  10. He he he, works like a champ! :D I don't know why I didn't try GPSOut sooner! With MS Streets & Trips 2007 on the WideClient PC, "Sentences=RMC,GGA,GSA" @ 19200/COM7 seems to work fine. All GPS sensor fields (Spd, Alt, Brg, Lat/Long, etc) are filed in with the exception of one, "Num Stats:", whatever that is; doesn't seem important. Thanks Pete, this is cooool... v/r, AL
  11. Hi Pete & Thomas, EDIT: Oh, I think I just found the answer to my question below. I think I need to add something similar to the following to my WideClient.ini file: [GPSout] Port=COM3 Speed=4800 Original Post: I've been thinking of using MS Street & Trips 2007 (U.S. equivilent to AutoRoute) on my WideClient PC for sometime now. Having come across this thread, I now think I'll give it shot after work tonight. I breifely looked through the readme.txt files for GPSout and MixW but I need some clarification. My setup is FS2004/WideServer PC and a WindowsXP WideClient PC which has been working flawlessly for some time now. I understand that the GPSOut.dll and .ini file will go in the FS9\modules and that I set the port= paramenter to "WideFS". I also understand that on the WideClient PC, I would install MS Steets & Trips and the MixW driver, but my question is, how do I tell the data to flow from the WideClient process into a set COM port for MixW to see? Do I need to add a GPSOut config-section in my WideCient.ini file or something to tell it to also output data on a virtual COM port for MixW? From there I undestand the MixW driver will translate the data onto another COM port for input to the GPS portion of MS Streets & Trips; or at least in theory at this point. :) I think the only piece I don't understand yet, is how to get the data out of WideClient to MixW. Thanks for any front-end help you have to get me started. v/r, AL
  12. Hi Pete, FWIW, I hope to validate your 3.715 fix on my WinXP x64 installation tonight after work (EST). Will advise... Al
  13. Hi Pete, I'm now ungregistered too (FSUIPC3 & WideFS6) after installing v3.712 & v3.714. I'm using Windows XP x64 (64-bit). I've never had a problem with Keys until these two beta versions of FSUIPC3. Simply dropping back to v3.711 and restarting FS9 appears to restore my registration. WinTrust.dll (C:\windows\system32) = v5.131.3790.1830 / March 25, 2005 The following is from my FSUIPC.log when running v3.714. Al Jordan ******** FSUIPC, Version 3.714 by Pete Dowson ********* Verifying Certificate for "E:\Flight Simulator 9\MODULES\FSUIPC.dll" now ... FAILURE! "WinVerifyTrustEx" error 0x80092003: This return is non-standard, possibly specific to trust provider Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="correct / edited for posting" User Addr="correct / edited for posting" FSUIPC Key is provided WideFS Key is provided Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E
  14. Thanks Pete. Just as you recommended, it worked like a champ. You 'da man ! :D
  15. Thank you Sir! That makes perfect sense! How come I didn't think of that! LOL :idea: I can't believe I was even close with the flag and virtual butoon theory. I can't wait to get home from work and try this. I'll let you know either way. Regard, Al Jordan
  16. Hi Pete, FYI, FSUIPC4 and WideFS7 seem to be running great here. Nice job and congrats on another successful launch. I know you're busy but I'm a bit stumped. Since installing FSUIPC4, I've decided to refine my FSUIPC.ini file and button (control) assignemnts for my CH Throttle Quad & Yoke. I've decided that I need more buttons so I've been attempting to use a keyboard-key as a compound modifier to existing button assignment. I spent most of last evening trying various syntax's (and reading the advanced user's guide) but nothing so far seems to work. I'd prefer a key to do this as I'm out of real buttons available to assign at the moment. For example pressing j2,b0 is Heading_inc and j2,b1 is Heading_dec. I want to hold down the keyboard "control" key for example, while using these same buttons and have its assignement shift to Heading_inc_fast and Heading_dec_fast respectivly. My first attempt (below) seemed logical at first but didn't make a difference when the control key was held down. Although the guide specifically stated that you could mix keys and controls, I didn't see this type combination exampled anywhere. [buttons] 24=R2,0,C65879,0 ;Heading_Inc 25=R2,1,C65880,0 ;Heading_Dec 26=CR(+K0,10)2,0,1024,0 ;Heading_Inc_Fast 27=CR(+K0,10)2,1,1025,0 ;Heading_Dec_Fast Then it seemed that maybe a virtual button set by my keyboard control key. Then the virtual button and its flag status could be used to compound the real buttons. But my first shot at this last night didn't seem to work either. Found this in the guide: 1003 Set button flag (param = 256*joy + btn) 1004 Clear button flag (ditto) So I tried it with an imaginary (virtual) joystck 10, button 1 and programmed it something like: [buttons] 24=R2,0,C65879,0 ;Heading_Inc 25=R2,1,C65880,0 ;Heading_Dec 26=CR(F+10,1)2,0,1024,0 ;Heading_Inc_Fast 27=CR(F+10,1)2,1,1025,0 ;Heading_Dec_Fast [Keys] 0=0,10,1003,2561,1004,2561 I don't know if this is even feasable (to use key-press to compound a button) but I always appreciate your mentoring. AL Jordan
  17. Well, I should probably be accused of crying-wolf as can't seem to duplicate this issue on v3.708 with all my add-ons running. I appologize to PMDG and Pete for prematurely raising the red-flag. After having the issue in three consective flights I now can't seem to duplicate it. Maybe it was a flakey copy-process when copying the dll into my modules folder the first time, sun-spots, or even the celestial alignment of the stars. Who knows and again appologies for creating this thread in the first place. :cry: v/r, AL Jordan
  18. Lefteris has asked for more information in the PMDG forum on this same topic and I have provided a scenerio in which it has happened three time now. Also, another user has reported that rolling-back to v3.7 final does fix the issue. The PMDG thread can be found here: http://forums.avsim.net/dcboard.php?az=0288&page= v/r, AL
  19. I now believe both the v3.707 and still in the 3.708 have issus wit the PMDG FMC and the radios. While using these betas, the PMDG FMC will not tansition from LNAV to ILS guidance much as it did perfectly well up and through FSUPC v3.7 final. I have posted this issue in a new thread here on Pete's forum as well as in the PMDG forum.
  20. Pete, I've posted the following over in PMDG's forum as well. I believe the last couple of FSUIPC Betas have issues with the PMDG FMC probably due to some unique coding they did under the hood. FSUIPC 3.3707 Broke VOR2 DME (~3200nm) seems fixed with 3.708 FSUIPC 3.708 Broke FMC transistion from LNAV to ILS guidance on final I have yet to roll back to v3.7 final due to the fact that I have a lot of aircraft-specific maps that from what I understand are not backward compatible after using 3.70x beta. I recomend that you and PMDG chat about the latest beta before they go final. I believe there are underlying issues involved the may create a headache for us users, PMDG and yourself. Posted in the PMDG forum on AVSIM: I'm pretty sure the latest beta versions of Pete's wonderful FSUIPC utility is breaking the PMDG 747 (and maybe the 737) FMC. In version 3.707 Beta, we noted that the VOR2 DME distance was permenently set ~3200nm. Pete didn't understand why that was but managed to fix it with v3.708 Beta. Now, when transitioning from LNAV to ILS approach guidance, the FMC vector gets all messed up. I have to swich to HDG until I'm right on top of the ILS approach path. I suspect that due to some unique PMDG coding under the hood, Pete is making changes that may adversely affect the PMDG FMC in the coming release. I would like to recommend that PMDG formally get in touch with Pete before he formally releases this version. FWIW, I have not tried to roll back to v3.7 (Final) because his new betas fixed some issues with the aircraft-specific maps that are rummored to not be backward compatible. AL | KCHS - Charleston AFB/Intl | USAF 437AW (~53 C-17's) FS9/Game Rig: AMD64-4000+ SanDiego OC=210/420/2520 | Asus A8N-SLI Deluxe | Corsair TwinX2048-3200C2PT (2x1GB) 2.5-3-3-8/1T@2.8v | Evga NV 7900GT v91.47 (1280x1024x32/4xAA/16xAF/High-Quality) | Enermax 550W PSU | Thermalright XP-120(mm) HSF | NV 1GB LAN | NV SATA-I Raid-0 223GB (3x80GB Samsung) (WinXPx64/Games) | NV SATA-II WD 320GB (Backups) | IDE-0 80GB Samsung (Archive) | Realtek AC'97 5.1 Surround | CH Yoke, TQ, & Pedals | FS9.1 (Settings max'd/60-50Vis/No-Shadows/20FPS) | WideFS v6.7 | FSUIPC v3.7 | FSGenesis Mesh (All) | PMDG (All) | PAI (All) | FSPassengers | FSBuild2 | Etc FS9 Support Rig: AMD3200+ | Gigabyte GA-7NNXP | Leadtek NV 5900 | Corsair TwinX1024-3200 (2x512MB) | Intel 1GB LAN | SiI3112 SATA-I 80GB Samsung | IDE-0 80GB IBM | JustCom 4port KVM | WideClient | GE-Pro v2 | ActiveSky v6 (512x32bit/Wx Influanced)| Radar Contact v4.2 | FS Real Time | FS Flight Keeper | FS Commander | AI Smooth
  21. Well, I think I've solved my checksum errors. The problem was a newly installed McAfee Personal Firewall Plus application on the 32bit WideClient PC only. Comcast, a major U.S. broadband cable provider here on the East coast of the US recently started offering free subscriptions to McAfee antivirus, personal security, and personal firewall. After swapping LAN cables, reseting My Netgear Router/switch, uninstalling and reinstalling my NForce2 MB chipset/Ethernet drivers, I discovered that when I reinstalled all three of the McAfee products mentioned above, my ASv6 station writing slows down and I start getting the checksum errors as noted in the WideFS server log again. I then uninstalled only the Personal Firewall Plus product and my problems and log events disappeared. Comcast is a major provider and it won't surprise me if others start seeing similar problems using this firewall product. I hope my findings here benefit anyone else who start having these checksum errors. v/r, AL
  22. Nope, WinXP x64 went final in March of '05 and has been running great for almost a year now on my rig. Checkout the Hardware forums on Avism under the FS general discussion. This is not new, or beta, but quickly becomeing routine for the AMD64 product line. You are correct that WinXP 64 does require specific driviers but that's it. This OS includes a Windows-on-Windows32 subsystem (WoW32) which allows most 32 bit applications to run fine on the 64bit OS. Anyway, all my drivers inlcuding the Nvidia NForce and Geforce drivers have been final for a while now and have already gone through several itteraions. FS actually runs a bit smoother on the Win64 OS as noted by several others on the AVSIM hadware forum. 1GB RAM is fine even for AMD64. No difference noted. Just as with the 32bit version more RAM is always better. Anyway, my AMD64 system, which is quite standard now, is not the issue here. I'll try changing the LAN cable tonight. I appreciate you taking the time to look through my logs. Al
  23. Thanks Pete; I'm at work right now so I can't provide answers. To everything right now. Sorry about not posting the WideClient Log. You were correct that was my intention, but a couple of beers and sleepy-eyes messed-up my copy-&-past abilities. When you mentioned network issues, it did jar my memory a bit. A couple of weeks ago, I physically relocated my WideFS PC which ment undoing all the cables. One thing I do explicitly remember was changing the LAN cable from the switch to the WideFS PC. I hoping that cable I used might be slightly faulty. Now I have to wait all-day before I can get home and test my theory. I remoted home and gathered all the log files and ini files for you and ziped them up for you as an attachment below. WideFS PC: WinXP x64-bit Pro | AMD-64 3500+ | Corsair XMS 1GB RAM (2x512) | Asus A8N-SLI Deluxe MB | Nvidia NF4 SATA Raid-0 x3 80GB) | EVGA Nvidia 6800GT PCI-x | NF4 Chipset LAN 100MB | FS9.1 FR 25 FPS | FS9.1 Joysitcks disabled | FSUIPC v3.537 AXIS & Buttons Enable w/Aircraft specfic settings. WideClient PC: WinXP Pro (32bit) | AMD 3200+ | Corsair XMS 1GB RAM (2x512) | Gigabyte A7NNXP MB | 2 x 80GB IDE | EVGA Nvidia 5900 | NF2 100MB LAN jordanal - WideFS Checksum Error logs.zip
  24. Hi Pete, I've been using your latest beta of FSUIPC v3.536/7 and recently noticed how slow my ASv6 sessions have been updating FS9 weather. ASv6 is on my Wideclient PC and I've retried the last two versions of the ASv6 updates. I do know for a fact that my network is solid and have no problems. All Windows shares work fine and no network event-log entries noted. I've been running this same 100MB LAN for several years with WideFS and nothing has recently changed as far as the network itself is concerned. I should also mention that a few times, Flightsim Flightkeeper, also in the WideClient PC, has also thrown an error saying that FS9 was not properly initialized when in fact, FS9 was up and running fine on the WideFS server. Anyway, I've tried reinstaling ASv6 several times and I've tried different FS9 startup situations. Can you point me in a good direction as to what to troubleshoot next? I'm starting to think that there's something going on here between the FSUIPC beta 3.536 and WideFS. I've put a lot of work into configuring my new AXIS facilites in the FSUIPC.ini file so dropping back to v3.53 or earlier really isn't an option if I can avoid it, even for troubleshooting. Thanks for your help. Al BTW, I removed many of the duplicate line errors to save space in this post. ********* WideServer.DLL Log [version 6.51] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 27/02/06, Time 21:04:42.549: Server name is XPGAMER 98937 Initialising TCP/IP server 98953 Initialising IPX/SPX server 98953 IPX/SPX socket() failed [Error=10044] Socket type not supported 98953 Failed to start IPX/SPX Server 99031 Incoming connection Accepted ok (skt=7928) 99109 Connected to computer "XPSERVER" running WideClient version 6.510 (skt=7928) 99109 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=1246 (time=0) 99266 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=384 (time=533406) 99797 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=1491 (time=533906) 99906 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=162 (time=534015) 100031 Broadcasting service every 1 mSecs 100391 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=189 (time=534500) 101969 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=371 (time=536062) 103047 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=175 (time=537140) 103172 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=1306 (time=537250) 103734 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=298 (time=537828) 105094 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=973 (time=539219) 105172 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=259 (time=539281) 106219 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=259 (time=540312) 268750 Closing down now ... Memory managed: Offset records: 39 alloc, 39 free Total number of received blocks having sumcheck errors = 248 Throughput maximum achieved: 26 frames/sec, 1802 bytes/sec Throughput average achieved for complete session: 7 frames/sec, 315 bytes/sec Average receive rate from "XPSERVER": 2 frames/sec, 3153 bytes/sec ********* Log file closed ********* FSUIPC v3.537 LOG: ********* FSUIPC, Version 3.537 by Pete Dowson ********* Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="Removed For POST" User Addr="Removed For POST" FSUIPC Key is provided WideFS Key is provided Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=4000B7AF[4000B7AF] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=255 3859 System time = 21:04:42 3859 \\XPGAMER\E\Flight Simulator 9\ 3875 C:\Program Files (x86)\ScreenGrab\ScreenGrab.exe 3922 System time = 21:04:42, FS2004 time = 12:00:00 (00:00Z) 13765 C:\Documents and Settings\jordana\My Documents\Flight Simulator Files\KIPT - Default.flt 13765 AIRCRAFT\beech_baron_58\FSD_B58TC.air 13968 Aircraft="Beech Baron 58" 19015 Module [M1] identified = "sb3gaugebridge.dll" 19015 Module [M1] "sb3gaugebridge.dll" access registration is okay 19015 Module [M2] identified = "ActiveRadar.dll" 19015 Module [M2] "ActiveRadar.dll" access registration is okay 67765 C:\Documents and Settings\jordana\My Documents\Flight Simulator Files\UI generated flight.flt 67968 Clear All Weather requested: external weather discarded 69625 Advanced Weather Interface Enabled 98172 Traffic File #18 = "projectai flightplans\scenery\traffic_mrai_wi04-05_federalexpress" 98172 Traffic File #17 = "scenery\world\scenery\traffic-ga" 98781 Traffic File #224 = "projectai flightplans\scenery\traffic_pai_vir" 98875 Traffic File #22 = "projectai flightplans\scenery\traffic_pai_aal" 98875 Traffic File #74 = "projectai flightplans\scenery\traffic_pai_dal" 99000 Traffic File #159 = "projectai flightplans\scenery\traffic_pai_nwa" 99047 Traffic File #210 = "projectai flightplans\scenery\traffic_pai_usa" 99640 Traffic File #25 = "projectai flightplans\scenery\traffic_pai_aca" 99750 Traffic File #48 = "projectai flightplans\scenery\traffic_pai_aza" 99875 Traffic File #67 = "projectai flightplans\scenery\traffic_pai_coa" 100000 Traffic File #192 = "projectai flightplans\scenery\traffic_pai_swa" 100234 Traffic File #209 = "projectai flightplans\scenery\traffic_pai_ups" 100484 Traffic File #75 = "projectai flightplans\scenery\traffic_pai_dals" 100609 Traffic File #79 = "projectai flightplans\scenery\traffic_pai_dlh" 100718 Traffic File #86 = "projectai flightplans\scenery\traffic_pai_egf" 101000 Traffic File #193 = "projectai flightplans\scenery\traffic_pai_swr" 101047 Traffic File #208 = "projectai flightplans\scenery\traffic_pai_ual" 107843 NWI weather clear actioned 107843 External weather discarded 271609 System time = 21:09:06, FS2004 time = 14:29:21 (19:29Z) 271609 *** FSUIPC log file being closed Memory managed: 1257 Allocs, 1834 Freed ********* FSUIPC Log file closed **** WideClient LOG: ********* FSUIPC, Version 3.537 by Pete Dowson ********* Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="Removed For POST" User Addr="Removed For POST" FSUIPC Key is provided WideFS Key is provided Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=4000B7AF[4000B7AF] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=255 3859 System time = 21:04:42 3859 \\XPGAMER\E\Flight Simulator 9\ 3875 C:\Program Files (x86)\ScreenGrab\ScreenGrab.exe 3922 System time = 21:04:42, FS2004 time = 12:00:00 (00:00Z) 13765 C:\Documents and Settings\jordana\My Documents\Flight Simulator Files\KIPT - Default.flt 13765 AIRCRAFT\beech_baron_58\FSD_B58TC.air 13968 Aircraft="Beech Baron 58" 19015 Module [M1] identified = "sb3gaugebridge.dll" 19015 Module [M1] "sb3gaugebridge.dll" access registration is okay 19015 Module [M2] identified = "ActiveRadar.dll" 19015 Module [M2] "ActiveRadar.dll" access registration is okay 67765 C:\Documents and Settings\jordana\My Documents\Flight Simulator Files\UI generated flight.flt 67968 Clear All Weather requested: external weather discarded 69625 Advanced Weather Interface Enabled 98172 Traffic File #18 = "projectai flightplans\scenery\traffic_mrai_wi04-05_federalexpress" 98172 Traffic File #17 = "scenery\world\scenery\traffic-ga" 98781 Traffic File #224 = "projectai flightplans\scenery\traffic_pai_vir" 98875 Traffic File #22 = "projectai flightplans\scenery\traffic_pai_aal" 98875 Traffic File #74 = "projectai flightplans\scenery\traffic_pai_dal" 99000 Traffic File #159 = "projectai flightplans\scenery\traffic_pai_nwa" 99047 Traffic File #210 = "projectai flightplans\scenery\traffic_pai_usa" 99640 Traffic File #25 = "projectai flightplans\scenery\traffic_pai_aca" 99750 Traffic File #48 = "projectai flightplans\scenery\traffic_pai_aza" 99875 Traffic File #67 = "projectai flightplans\scenery\traffic_pai_coa" 100000 Traffic File #192 = "projectai flightplans\scenery\traffic_pai_swa" 100234 Traffic File #209 = "projectai flightplans\scenery\traffic_pai_ups" 100484 Traffic File #75 = "projectai flightplans\scenery\traffic_pai_dals" 100609 Traffic File #79 = "projectai flightplans\scenery\traffic_pai_dlh" 100718 Traffic File #86 = "projectai flightplans\scenery\traffic_pai_egf" 101000 Traffic File #193 = "projectai flightplans\scenery\traffic_pai_swr" 101047 Traffic File #208 = "projectai flightplans\scenery\traffic_pai_ual" 107843 NWI weather clear actioned 107843 External weather discarded 271609 System time = 21:09:06, FS2004 time = 14:29:21 (19:29Z) 271609 *** FSUIPC log file being closed Memory managed: 1257 Allocs, 1834 Freed ********* FSUIPC Log file closed ****
  25. Well this time I did as you suggested, unassigned axis, disabled joystick and then removed the joysticks from the fs9.cfg file. So far the devices have stayed gone. As for the numerous times I have to hit the "ignore axis" button, this hasn't improved much. No, I'm not using raw mode. In the CH-Products calibartion utility, the raw numbers 0-255 look solid so I think it might be too sensitive in FSUIPC. Maybe something we can adjust ourselvs with an added option to the axis assignemtns tab? BTW, so far it appears that you can't add comments to the end of axis assignment. I tried to use the same commenting method used in the buttons and keys sections but FSUIPC wipes the axis comments clean after every save. Will this be added? v/r, AL
×
×
  • 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.