jordanal

Nope, no concerns here as FSUIPC v4.104 seems to be wokring here so far. Just wanted to bring the application-log to your attention. If I'm not concerned about and you're not too concenred about it then it sounds like it's no big deal. Again, glad you're back and thanks again for your help with the axis issues. Your support always has been and continues to be top notch.

Pete, I don't even know what side-by-side is, or means. I am simply reporting an observation that in my MS Windows Vista Event - Application log, that when I run the FSCUIPC v4.104 installer.exe, I notice this error in the Vista "Application" log viewer. I wasn't trying to uninstall anythig at the time. No, I have never see any error indications in the FSUIPC installation log located in the modules folder nor does it appear to be affecting FSCUIP v1.04 performance in any way. I just thought you'd like to know that I see this error when I install FSCUIPC v1.04. You said you had Vista Premium and FSUIPC v1.04 running on box. Look in the Vista Event log viewer under application, do you see this side-by-side error around the time you had installed FSCUIPC v1.04? Al

Well hello Pete, welcome back! I trust your daughter got some useful work out of you? :lol: As for repairing simconnect in Vista, I think you are correct. The simconnect.cat, simconnect.manifest, and simconnect folder were owned by "TrustedInstaller" which is non-visable account. To remove these files and folder for both FSX RTM & SP1, I had to change the ownerships to me (admin). Well, when I put these back after fixing the axis issue, with me still as the owner, simconnect was non-functioning. Becuase the TrustedInstaller is not a selectable account to apply to a file or folder, I could not force the owneship back to the way I originally found it. So yes, I think you would have to uninstall and re-install FSX in its entirety. I was reluctant to do this becuase I had just built a new PC and had alreay installed and registered FSX several time in the last few weeks. Vista-U's "save previous versions of files" saved my keaster though. I'm not exactly sure what the specific circumstances are when v1.04 generates the side-by-side error in Vista's system log, but it seemed to happen every time in installed it. Meaning, it happened with FSX RTM & SP1, and both with and without the simmconnect folder. v4.072 never exibited this error in the system log at anytime. Glad you're back...

Well, I seemed to have fixed my lost axis issues mostly through persaverance, trial-an-error, and reading forums. :D This thread http://forums.simflight.com/viewtopic.pvista+axis is what helped me the most. First, I rolled back (uninstalled SP1) and repair-installed FSX when I noticed I continued to have the same problem. Hmm, I could have sworn I had FSUIPC axis functionality in FSX RTM. It looked identical to what Peter Hayes saw above, with the rescan button greyed-out on the axis tab. At this point, I thought it a good idea to roll-back FSUIPC as well to a known good starting point, or so I thought. The only other FSUIPC version I had was 4.072 which I though I must have been previously using with FSX RTM. I then "properly" uninstalled my CH devices and manually cleaned out the remaining stale CH DirectInput Devices under HKCU. The only two DirectInput devices I now had were for my keyboard and mouse. Good to go I thought. Re-enabled my CH devices and I was shocked to see I still could not get CH devices to show up on the axis tab. For the next six hours I tried everthing under the friggin sun except a complete re-install of Vista-Ultimate which was not going to happen becuase FS9 is still perfect. After coming across the aforemention thread, it was then shocked to see that the axis assignemnts tab was broke up until v4.08 which is the earliest version that worked with Vista (six hours wasted by a version difference of 0.008). Damn if I didn't install 4.104 with my current FSX RTM installation and bam, all CH devices worked on the first try. Instaled SP1 and the axis assigments continue to work like a champ with both SP1 and FSUIPC v4.104. Also, as mention in Pete's sticky at the top of this forum, do not attempt to delete any simconnect dll or Wxsx folder under Windows in Vista. If you do manage to change the permissions enough on this and the parent folders and get them deleted, then guess what? A repair-install of FSX and or SP1 does not recreate the cat files or folders for the simconnect dll becuase only the "TrustedInstaller" account can put these back and it only does that on a clean install of FSX or SP1. Oh, and I had cleaned out my recycle-bin don't you know! :evil: I did manage to utilize Vista's new revert to older file version function whereby it saves older copies of files, and there I found a copy of each of the simconnect dlls and cat files for the Wxsx folder. Whew, time to fly!.

Pete, Was does the following mean regarding this issue? This "side-by-side" error is generated in my Vista Event Log (Application) each time I install FSUIPC4 v1.04. I downloaded and installed the Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) from Microsoft thinking there's an extraneous dependacy, but I still get the side-by-side error. Log Name: Application Source: SideBySide Date: 5/25/2007 6:37:01 AM Event ID: 33 Task Category: None Level: Error Keywords: Classic User: N/A Computer: AlComp Description: Activation context generation failed for "F:\Install Queue\Pete Dowson - FSUIPC v4.104 Beta\Install FSUIPC4.exe". Dependent Assembly Microsoft.FlightSimulator.SimConnect ,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.61234.0" could not be found. Please use sxstrace.exe for detailed diagnosis. Event Xml: 33 2 0 0x80000000000000 5344 Application AlComp Microsoft.FlightSimulator.SimConnect ,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.61234.0" F:\Install Queue\Pete Dowson - FSUIPC v4.104 Beta\Install FSUIPC4.exe

Yup, I figured out copying aircraft specific sections of the ini file the week FSX came out. Agreed much easier. I have been using aircraft-specific settings for several years now as well. Right now I'm using a very simple ini file for troubleshooting purposes of this issue. Thanks again for checking the issue this weekend. Much appreciated...

Thank you so much Peter for replying. You're the very first person to indicate similar issues. I am seeing the exact same thing only with SP1 and FSUIPC v4.1+. Yes, I can see axis in FSUIPC if I enable cotrollers within FS, but up until SP1, I always had that unchecked so I didn't have to mess around with conflicting axis assignemsnts within FS. I would just disable all of them with the checkbox. I have an elaborate multi aircraft-specific FSCUIPC ini file which I have used for years, and continue to use in FS9/FSUPIC3 to this day. Again, the fact that I can see buttons in FSUIPC4 indicates that some part of FSUIPC4 is working, so it has to be something with FSUIPC4 axis detection and perhaps simconnect. Maybe by uncheckecking the controllers in FS, it prevents controllers from going out simconnect to FSUIPC, or however it works. I'm sure Pete has that all figured and will try to explain it to me and I probably won't understand the low-level driver stuff, again, :lol: You did give me temporay fix, at least for the long 4-day holiday weekend (starting today :D ) to just enable and assign some axis within FS and use my existing calibrations within FSUIPC4 until Pete gets back. Thanks again, I'm sorry, but misery really dooes love company! :twisted: v/r, AL

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

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

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

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

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

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 ***********

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

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

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 :)

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

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

Hi Pete, FWIW, I hope to validate your 3.715 fix on my WinXP x64 installation tonight after work (EST). Will advise... Al

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

Thanks Pete. Just as you recommended, it worked like a champ. You 'da man ! :D

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

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

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

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