Ray Proudfoot

Jeff, FSUIPC will only recognise the throttle if Windows can see it. I'm a bit confused because it's the first throttle quadrant that has the round connector. A second one has a standard USB plug which can plug either into the USB hub on the Pro Yoke or directly to a port on your computer. Sounds like you have the connections wrong. Swap the throttles around and start only with the one with the round plug. See if Windows recognises that and if it does plug the second throttle into the Pro Yoke. The Pro Yoke should be plugged into a powered hub. That's how I have mine and it's fine.

Ken, For info I run the VAS Monitor and RC4 on an Intel i5 desktop and have no problems with either. Neither program uses many resources so I suppose it could be down to your laptop.

Thanks Ken. :)

Ken, Can you edit your post and remove my email address please.

I use ShowText for RC. You can adjust the font size and colour and change the background colour too. That might be possible with Lua but you probably have to program it.

Timonier, If you still have FS9 and the PMDG737 from that it may interest you to know I am running it in FSX with PM and the GoFlight MCP. LNav and VNav work fine. I have removed the PMDG panel so there's no conflict and the FS9 737-900 flies very well in FSX. I'm planning to try the 737-800 next.

Alan, Yes, it can be tricky because you start by steering using the tiller and then have to seamlessly switch to rudder control. And of course I don't get to fly on Pete's setup that often so I am always a bit rusty. That take-off roll was on the slow side as you may have noticed but the Honiley SID out of EGCC involves negotiating around the town of Knutsford so speed has to be curtailed in order to negotiate the turns. I'm not hugely impressed with my landing. Too low for too long! But my excuse is there was a lot going on and I got distracted! ;-) It's a fantastic setup Pete has. It's always a pleasure to visit him and to enjoy his and June's company.

Thanks for that Pete. Lefteris or anyone in the beta team can raise a bug report on this so it's addressed formally. As you are copying him in on this I'll leave it to him to decide and monitor the situation. Hopefully as it's so easily reproducable it will be equally easy to fix! :D

Hi Pete, I've reproduced this problem but I have no idea which bit of software is causing it. I disengaged AT1 whilst the AP is on and retracted the 4 throttle levers back to idle. Pushing them forward does not result in the engines spooling up. I don't have filtering enabled. I have posted this in the FS Labs ConcordeX Forum too. I know you don't have much spare time in the next few weeks so this is just to confirm quarterback's problem is reproducable.

quarterback85, As a beta tester for Concorde-X and a user of Saitek throttles I haven't experienced this particular problem. I'm wondering if it might be related to USB power saving. If the OS doesn't detect any use from a USB connected device for a certain period of time it will put that connection into sleep mode. Check if you have "Allow the computer to turn off this device to save power" checked for the USB hubs that your throttles are connected to. You can find this as follows:- Right-click "My Computer" - Manage - Device Manager. Highlight the relevant USB Hub entry and right-click to see Properties. Look at the Power Management tab. If the option is checked switch it off and see if that solves the problem.

Good. Marvellous! They talk to each other? Odd. Don't you mean they both happily talk to FSX? ;-) Yes. I don't know my ASX from my FSX!:lol: No. From the last logs you posted, these are the salient bits: From the Installer (which worked fine, but was done on 16th June, presumably before this mess?): That was the day I bought ASX and started all of this. Without a time it's difficult to know what was done when but given my WinSxS folders are okay and ASX and GoFlight work with FSX I think I can draw a line under this. Thanks for the lesson on SimConnect. As you may have gathered I'm on leave this week and next. Are you open for visitors? Regards, Ray.

Hi again Pete, I've deleted the two SimConnect folders in WinSxS, run the repair option and the SimConnect.msi in the following folder: C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\Core Utilities Kit\SimConnect SDK\lib I now have two SimConnect folders in WinSxS. Partial names are 60905 which contains 10.0.60905.0 and in 61242 I have 10.0.61355. I have also run SimConnect.msi on my laptop where ASX is installed. ASX and GoFlight are talking to one another fine. Do you need to see any logs to confirm all is well? Cheers, Ray.

It's not complicated to ordinary users who never need to know what is going on in the background. The most complex parts for add-on installation is getting those XML files correct, and really installer programs should do all that. This is why FSUIPC has, for the first time, got an installer. I've never made an installer for any of my add-ons before! Well I suspect most 'ordinary users' don't have GoFlight hardware. Up to your post last night I didn't even know FSUIPC even talked to simconnect or the installer created those xml files. I wouldn't have thought running FS-related apps on a networked PC was unusual. More and more people have networked setups these days and running ASX, Radar Contact etc. on a separate PC is quite widespread I would guess. Couldn't agree more! Because the two are different. Microsoft invented the Side-by-Side installation system so that their updates (to Windows, FS, or any system including add-ons) don't cause application compatibility problems as facilities change and evolve. The old method for ensuring compatibility was to always support all the old things whilst adding new ones. This grows into a right Royal mess as changes occur, and this is good for nobody, being inefficient, confusing, and very costly to maintain. With the Side-by-Side library system, old programs will still work as they use the older library, whilst newer ones, or later versions, will use the new one, and so on. FSUIPC4 actively checks the SimConnect versions available, and uses the latest one it recognises (SP1 at present). But it will still work when SP2 comes out, even without me changing anything, as it will still use the SP1 version. However, to actually get itself loaded -- and thus in a position where it can check versions -- it needs the Base version to also be there, as this is the only one always guaranteed. I hope this is clear. In summary, the side-by-side system is good as is provides ongoing compatibility in a most efficient manner without restricting changes for the better in future updates and versions. It's a way of having your cake and eating it. ;-) That makes perfect sense. Thanks Pete. I hadn't realised this until you described it all. I'm currently runing the repair utility on the FSX DVD. I checked a couple of things before I started. Ihave two FlightSimulator folders in WinSxS. Both contain the same version of simconnect.dll - 10.0.61355.0. That, I'm guessing, is not good. I had a look at the two logs for FSUIPC and it's installer. I'm attaching for info. Any comments? More to follow later :D Cheers, Ray. RayLogs.zip

Hi Pete, Yes, that is where the original base edition of SimConnect.DLL is stored, and it is that which should be repaired by using the repair from the original DVDs. The "FSX Help" announcement above, which you insist on calling my "locked post" (most Announcements are locked) is exactly about this. Without that the base version of SimConnect FSUIPC will not load either. Ah, so I need two instances of simconnect. The original plus a later one. I was under the mistaken impression only one would suffice. I'll run the repair option from the DVD. I'll check the version prior to running the repair - just for info. Okay, understood. You have to remember that whilst you're an expert on all this I am most certainly not. I did what I did because it was the only way I could get the GoFlight program running. I knew nothing at al about simconnect and xml files before all this! It was running fine prior to the installation of the simconnect and exe xml files. It was only the creation of those (perhaps by the GoFlight setup) that caused that initialisation problem with GFDEVFSX.EXE. I don't knowingly create problems for myself.:wink: My simconnect.xml has both local and global sections. But I did run the repair. I didn't cherry-pick the instructions. You're speaking from a position of someone who knows the system inside out. I didn't and still don't but I do now have a better understanding of how it works. Okay, I'll do that and report back. Thanks for the background. I had no idea it was so complicated. Why can't we have just one instance of simconnect.dll? :roll: Cheers. Ray.

And what was the posted solution, please? This thread seems to indicate you still have problems? What was the reason for the GoFlight stuff not working which you identified and fixed? I posted the problem in the FSX forum. Here it is http://forums.simflight.com/viewtopic.php?t=62929. Tim's second reply gave me the vital information relating to the WinSxS folder name which the GoFlight program seems to need. The problem was solved last Monday. The folder apparently needed by the GF program is C:\WINDOWS\WinSxS\x86_Microsoft.FlightSimulator.SimConnect_67c7c14424d61b5b_10.0.60905.0_x-ww_429211e9 FSUIPC certainly runs but how would I know if it's running at full efficiency? Whilst I had to name that WinSxS folder with a specific name I placed the most recent SimConnect.dll in it. I don't have that PC running at present so can't quote you the version number but from memory it was from the SDK SP1. I only mentioned a reinstall as it seemed to be the only option left. When I was installing ASX I didn't initially find the detailed installation instructions for loading on a different PC to FSX. When I did find them there were references to both EXE.XML and SimConnect.xml and I had neither in the specified folders on the FSX PC. What I did have was that specifically named folder containing an older simconnect.dll. When I encountered problems trying to get ASX to talk to FSX I scoured the web and found the posted topic on your forum advising to delete that folder. I deleted it and then went through the remaining ASX instructions and on completing them I was finally able to get ASX working. But whilst doing this I'd messed GF up. It was only by asking around and getting Tim's second reply I fathomed out what was causing the problem. Now whether any of this is right or wrong I really couldn't say but as I have both ASX talking to FSX and my GF software works I'm happy. Cheers.

Hi Pete, Welcome back! Hope you had a nice time. I ran the repair amongst a multitude of other things over several hours and that also included reinstalling the GoFlight software several times. I was just about at my wits end. Nothing would convince that exe to run. The posted solution was the only way I could get the GF program to run. During all this I did become quite familiar with how those XML files work. I have no idea why the repair didn't work for me. Maybe a reinstall of FSX might have done it but that was something I couldn't face.

Just to bring everyone up to date on the original problem. I received a reply from GoFlight support pointing me to Pete's locked topic on deleting the folder in WinSxS. When I later pointed out to them that deleting this folder was the cause of the problem I never heard back from them despite sending a second message a couple of days later. GoFlight might excel in certain areas. Technical support isn't one of them. :roll:

Ian, Why do I need to run it again when I have everything working? I thought I made that clear in my original message. Leave well alone is my motto! :D It seems to me that GoFlight need that folder to have a specific name for their GFDEVFSX.EXE to work. If it's named anything else their program fails. And because of their abysmal support I don't know if they intend fixing that issue.

Yes, I did but I also had to install the SP1 version of simconnect.dll from the SDK. But if running the repair just recreates the original folder what is the point? I don't doubt it worked for you but it didn't for me. I should add that although I had one reply from GoFlight support pointing me to Pete's locked topic suggesting that folder be deleted they never came back to me when I said that the non-existence of that folder was the cause of all my problems. I find their lack of any further response veru disappointing given they don't respond whatsoever in their own forums.

Hi, I believe L and R are denoted with a 1 or 2 after the runway ID. So 0031 would be 03L and 0032 03R. W, I guess stands for Water. Maybe when Pete returns from holiday next Monday he can fill in any gaps. Cheers,

Hi Pete, I know you're still on holiday but I wanted to post this asap in case anyone else has problems with GoFlight modules in FSX. On Saturday I bought and installed ASX on my laptop. I had a lot of problems getting it to talk to my FSX PC but eventually I got the two working. However, during those few hours I happened upon this locked topic http://forums.simflight.com/viewtopic.php?t=58095 in which you advise deleting a folder in WinSxS. Unfortunately deleting this folder caused the GoFlight GFDexFSX.EXE to fail to run when I started FSX. I only found the reason after receiving a reply from someone who did have ASX installed on his PC and who had GoFlight modules. Despite having other FlightSimulator folders in WinSxS it seems the GoFlight program requires that specific folder to exist. I have been in touch with their tech support and I'm awaiting their response. I'm sure you wouldn't have advised deleting this folder unless you had good reason to but I just wanted to advise you and others it could cause problems with GoFlght software. Cheers.

I never knew that! Great tip - thanks Pete. I now have accurate tower views at EGCC and my latest scenery - LEPA which I'm sure you have already :D Regards, Ray.