Pete Dowson

I notice it says: Is yours specially wired? If you previously used it with a Game Port I would think that it isn't supported via the Quadrant. Maybe you'd be better off using it via the Game Port after all? Either way, this is a question of PFC Support I'm afraid. I've never had any information about such a device. Sorry. Regards Pete

No, WideServer is not really involved. Yes. That is almost always a result of an illegally generated Key. Really? From where? I've never issued temporary licences. If this is from Project Magenta, then possibly it was one generated by an old version of the key generator which encoded the expiry wrong. You'd need to ask PM support for assistance. Please load FS with FSUIPC registered, let it settle then close FSX, and show me the FSUIPC LOG. Regards Pete

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? Note that if the base SimConnect WinSxS folder is deleted and not repaired then FSUIPC won't run either -- it needs the base SimConnect (the one from the DVD) to get loaded. It can run with or without the SP1 updated SimConnect -- it just provides slightly lesser facilities and performance. I don't know of any case where FSX needs reinstalling, and reinstalling doesn't create or mess with DLL.XML or EXE.XML files -- they are both up to installers to handle, or users under instructions (as, for instance, in the case of MyTrafficX). Regards Pete

The repair doesn't merely recreate the folder, it sets up all the other settings in the registry to make the contents of that folder work. The reason for deleting the folder is that the repair doesn't do anything if it is there as it thinks it must be okay! I'm not sure why you were trying the SimConnect repair solution just to get an EXE automatically loaded -- that's part of the EXE.XML file (in the same folder as the FSX.CFG). Doesn't GoFlight's installer see to that? Did you try to do a GoFlight re-install? Regards Pete

I've never heard of a Cirrus yoke with a throttle! Where does it fit? How does that work when the throttles are on the Throttle quadrant? I think you probably need to direct your question on this to PFC themselves - I should think the extra throttle is superfluous. Regards Pete

There's a section in the WideFS Technical document all about that. What you list as having done seems exactly what Lee Glover (the chap who contributed that answer) said, so I don't really know why it worked. Well, except that this worries me: I've never seen such an option mentioned before. Maybe TeamSpeak no longer accepts SendInput methods? Have you tried that option unchecked? I hope someone else using TeamSpeak can help here! Regards Pete

I think the only hope would be if they abandoned the use of TCP/IP protocols for communicating internally, which is very unlikely (though I still hope as it seems very inefficient to do in-process), and certainly impossible for the external and network operations SimConnect is also intended for. I use Norton Anti-Virus, and both its firewall and Windows XP firewalls without any problems ever occurring in FSX -- and I haven't had to take any special steps. Others have said AVG and Avast (?) are okay. I thought I read that Kaspersky had fixed their problems with FSX, but I couldn't swear to that. Maybe you should try making sure your software is up to date first. Regards Pete

I've no idea what you mean by "4 parts", but since all of the radio frequencies are only 16-bit (2 byte) values, and the maximum possible number in 16bits, treating it as unsigned, is 65535, the number you are getting obviously does NOT come from reading a 16-bit frequency or any other 16-bit value for that matter). Regards Pete

You have somehow lost the base version of SimConnect. You need to repair FSX from the original DVD. Please see the FSX Help announcement. Regards Pete

Please refer to the Advanced User's Guide for FSUIPC. Near the end there's a section called Multiple Joysticks. It deals exactly with what you want to do. For a long time now FSUIPC has supported dual controls -- actually triple and quadruple if desired! Regards Pete

FSUIPC4 is a complete product. I don't supply upgrades. The special rate "upgrade" price" is referring to recent purchasers of FSUIPC3 "upgrading" to FSX and FSUIPC4. It is you who is upgrading. The program is new. Well you are the first one who has any difficulty since FSUIPC4 is released last September. What is the problem? All of my FS programs are always available on the Schiratti site, and have been now for over ten years. FSUIPC4 is what you bought. The Server for WideFS7 is built into FSUIPC4, but it won't work unless you buy that too. Why not simply read the user guide which is included in the ZIP? 4.12 is merely the current version. It changes all the time. You can (and should) update your copy when new versions are available. The Announcements in this Forum tell you which version is current, and also often provides interim updates. I cannot understand why -- you are the only one I've ever heard from who cannot download FSUIPC4.ZIP from the link provided. Surely, in order to only pay the upgrade price, you must have downloaded FSUIPC3 (FSUIPC.ZIP) from the same place? It is no different a process! :-( I would, in any case, always advise you to download the programs FIRST, before paying for them. You can then read the documentation and decide what to do. The first few pages explain everything. Pete

Really? How strangeI'll look at that directly. If it does it is a bug. Ah, a contact in Level-D. Good. Can you tell me, please, how it is that merely my intercepting axis values and re-transmitting them, even with no change, is upsetting your A/P? It must be something odd with SimConnect, as all my control operations are 100% using standard SimConnect facilities, but I need to understand it if I'm going to ask MS to fix it, and find a work-around in the interim (other than removing the whole set of intercepts). Any relevant details would be very welcome please. Are all axes affected or only elevator, or elevator trim, or aileron or aileron trim, or what? Is it perhaps a priority problem where I trap them at one priority and re-transmit them at another, and you are trying to collect them in between? If we are both trying to collect them at maximum maskable priority, maybe it is an ordering problem -- in fact, maybe FSUIPC won't get them if SimConnect sends them to you first (unlikely as aircraft will be loaded later than DLLs). I don't know how SimConnect resolves equal priorities -- it should treat them equally. Regards Pete

FSUIPC3 does intercept axes as such. There is no comparison with FSX. Hasn't the FS2004 version of the LDS aircraft been available for a long time? I am not aware of any problems with FSUIPC and the Feelthere software, other that you may need to check the THROTTLES option centre bottom on the 4 throttles calibration page, if you use it. Regards Pete

If you are using Windows XP all round you should have no need to touch that INI file. What did you change? Well, the reason for the apparent increase in the number of connections is actually explained fairly clearly in the documentation. As to what it is trying to reconnect, let's see: OkayWideClient says it is timing out waiting for data from the Server. That is why it is trying to reconnect. What did the WideServer Log show? This is only half the story! There's no need for a photo. Why not just read the explanation in the documentation? Here, I'll reproduce it for you to save you all the bother: There. That was in the early section in the WideFS User Guide called "Running WideFS". Regards Pete

No idea, sorry, but if I wanted information like that I guess I'd do some measurements and work it out. You could, for example, find out what the numbers are on each GS mark on the AI, then just refer to an aircraft text to see what the marks actually indicate. I'm sure there's a direct and probably linear (angular linearality of course) relationship. Regards Pete

No idea why that is. Maybe FS is assigning both sets to the same FS axes and is alternating values from each? Where are you observing this "going bananas"? How were you using FSUIPC with your own throttle - via axis assignment is FSUIPC or in FS itself? A standard POV is treated as 4 or 8 buttons in FSUIPC3 -- check it in the Buttons page. There are examples in the user guide on how to make it a POV, or you can assign different functions. I've no idea -- if you mean FSUIPC *axis* assignments then the only possible conflict is dual assignments - i.e. the axes you assign in FSUIPC are also assigned in FS. The same may apply even if you are only using FSUIPC calibration, not assignment. Try taking FSUIPC out of the equation. It shouldn't make any difference in the latter case. Regards Pete

Please see my reply to your original question. Pete

I don't know of any way of doing that on FS2004 or before, at least not without loading the Flight which refers to it. SimConnect does provide such an option, however. So you could do it in FSX from a SimConnect application. I could possibly add a way of accessing this via FSUIPC4, but on the whole I am expecting most new applications for FSX to use SimConnect directly. Regards Pete

No, but by editing the FSUIPC INI file you could make one button send more than one keystroke. In fact you could do it by programming, on the FSUIPC Buttons screen, one keystroke for pressing and another for releasing the button. This will work provided the "unused" keystroke clicks the mouse on a screen position which doesn't do anything, or at least nothing of consequence. However, you seem to be taking a rather roundabout course here. Are you sure that the PSS baro knob doesn't respond to normal FS controls to increase or decrease that Kollsman value? I've never actually seen any add-on which replaces the default FS action for altimeter pressure settings, as it works perfectly well as it is. The controls are called Kohlsman Dec and Kohlsman Inc -- Microsoft misspelled the inventor's name! ;-) Regards Pete

A difference in email address between FSUIPC3 + WideFS6 and FSUIPC4 + WideFS7 won't stop you registering -- the keys for FSUIPC4 and WideFS7 must have the same name and email, as must FSUIPC3 and WideFS6, but those details are only kept in the KEY file which is stored in the Modules folder for the specific version of FS. So, something else is going on which is not evident from your explanation. Perhaps you should send all the details to me at petedowson@btconnect.com (please be sure to ZIP any attachments), and explain what you do and what you see. Regards Pete

I don't know what this has to do with FSUIPC, but all versions of FS have swtched to outside view to show the crash. Then the last loaded Flight (or last Saved Flight) is reloaded so the view swityches to whatever that flight had. As always, FSUIPC provides such axis assignments if you need them. You have to purchase it though. Pete

Sorry, I've no idea what it is or how it would be referred to in MSFS. Is this something to do with that mysterious "helicopter beep"? Is it a simple on/off switch, or some sort of axis/dial? For things simulated in FS, references to specific things actually in FS would help. If it isn't simulated then you would just have to have a dummy switch. If the "Helo Governor Beep" adjustment is what you want, then the controls INCREASE HELO GOV BEEP and INCREASE HELO GOV BEEP should work, I would have thought? Searching the List of FS2004 Controls also reveals these, which may or may not be relevant: ROTOR GOV SWITCH SET ROTOR GOV SWITCH TOGGLE Regards Pete

Yes, I understood that. It is just that you were referring to specific entries within such a range so in order to cross-check I have to read through them. search through them to find out what you are talking about. A specific data reference needs a specific offset value, please. It probably works in FS2004, it's just that I haven't had time to test it and update the document. I tend to rely on feedback. Why not try it? You don't need to write a program for that, simple use FSInterrogate. Where are you referring? Originally there were some like that (all those in the second table), as they were mapped-through areas of FS memory which folks found by experimentation and consequently labelled them for me. I provided the information but could not guarantee to do the same in every version. Gradually many of those moved from that second table to the first -- the first table are all supported as far as possible in all relevant FS versions. If they don't work and folks report that I undertake to fix it. I don't undertake such for the second table, in general. Examples? I would be very very grateful if you could try to be more specific. I cannot work on generalities. Sorry. Regards Pete

No. The single byte switches in 3102 and 3103 were implemented in FSUIPC by operating the relevant FS controls (i.e. just like using FS control assignments). The 2xxx ones are mainly derived from originally unsupported mappings directly into FS2000 or 2002, direct into FS's memory. There was a whole batch labelled "not necessarily supported ..." (in fact there's still some there, in the separate table at the nd. Unfortunately (for me) quite a few folks used them directly so I had to move them into the supported table. So now I have to make them work in each subsequent release in any case. No difference. 3101, alternator switch, is listed. What else are you talking about? If you have any question about offsets it is best to actually say what the offsets are, not use "XXX" as I cannot check that. FSX offset status is provided in a separate document available in the FSX downloads. Regards Pete

TCP is a connected protocol. The process of creating a socket and getting data across involves, for the Server (with parameters omitted for now): WSAStartup(..., ...); to initialise WinSock SOCKET s = socket(..., ..., ...); to get a socket assigned a series of setsockopts according to needs bind(..., ..., ...); to associate an address with the socket listen(..., ...); wait for a connection WSAAsyncSelect(..., ..., ..., ...); to send message to window when a connection attempt is made The action on the Client is different, but equally complex. In both cases either a separate thread has to be used or a lot of trouble is taken over getting everything to operate asynchronously and thus not ruining performance. I've left out all the errors checks and clean up actions they need. And even UDP involves most of those steps. I think you just miss out the "listen" bit. Now, tell me, how do you see that as equating to your "All that needs to be done is open a Winsock socket connection to the specified port of a specified IP address."? Let me see your code (in C please), without using any fancy libraries not available or not wanted inside the FS process. I am on holiday from late tomorrow (Thursday) until Monday 25th June. Maybe you'll have some easy short source code by then? Honestly, nothing I've seen in networks is as simple as you are making it sound, so I'd really like to see this. Regards Pete