Pete Dowson

Can you be a little more specific? What aircraft panel is this with? Does it do the same with default aircraft? If not then doesn't it also do the same with FS's own default assignments? It's hard to tell from the little information you provide, but it sounds rather like the control acceleration which occurs on some complex aircraft panels because of the way they wastefully send controls to FS many times per second. If this is the case, then try checking the "fix control accelerations" option on FSUIPC's Technical page. Regards Pete

You don't mention it, but I assume you are using my GPSout DLL? If so, which NMEA sentences have you enabled? The RMC and RMA sentences don't carry the altitude. I think you need the GGA sentence, or the proprietary Garmin PGRMZ sentence. The non-NMEA protocol AV400 also carries it. The origin of NMEA protocols lies with marine applications, where I suppose altitude had a low priority! :wink: Maybe the documentation for PocketFMS says what it accepts? Regards, Pete

It is "supposed to work" with any Moving Map program which accepts NMEA 0183 standard messages from a normal RS232 serial comms port, running on any type of PC or device which has such a facility, using a cable which connects the correct output lines from the FS PC to the correct input lines on the target computer or device. I have no idea whether the Garmin program and your connection meets any of those criteria, but from my experience with two Garmin units (an Etrex and an iQue 3600) I don't think Garmin supports such a facility in any case except on their aviation-equipped units, and then it seems the protocol it requres is AV400 (which I added specifically because of this), not NMEA at all. Regards, Pete

It's just based on the units used in FS. In this case, I think it's the number of metres from the equator (10001750 metres is about 6215 statute miles). So dividing by that and multiplying by 90 gives you degrees. The reference used by those editing FSInterrogate's FSI files is the Programmer's Guide document. Regards, Pete

The FSUIPC interface for adding airraft to the TCAS tables is only a means of adding data to those tables, for other programs to read (for TCAS displays and the like). It doesn't create any aircraft in the simulation. That's done through the Multiplayer interface. This is how Squawkbox and the other on-line programs work -- those EXTERNAL programs do exactly what you say. So, with that understanding, except for pitch and bank, yes. Those two particular items are in the TCAS_DATA2 part of the information structure, and that part is not available for externally injected MP data. As you will notice, most of the data there was relevant to AI aircraft only in any case -- I only used spare fields there for pitch and roll for use by the AIsmooth program. No, they are not "AI aircraft". They are "Multiplayer aircraft". But given that, if you injected the aircraft through the FS multiplayer interface, yes, that's what it is for. Note that FSUIPC has absolutely nothing to do with multiplayer -- that is entirely a Microsoft documented interface. The FSUIPC interface to which you refer is merely to allow aircraft injected via the MP interface to also be seen on 3rd party TCAS displays. This should all be clear from the description of the facilities in the Programmer's guide documentation in the SDK! Regards, Pete

Good flying then! Regards, Pete

Where did you get those parameter values from? I've never heard of them and they most certainly will not be recognised! Please refer to the section in the WideFS documentation entitled "PTT (push to talk) for Roger Wilco, AVC and TeamSpeak", and use the parameters as shown. There's also a separate document inside the WideFS package called "How to setup Push To Talk". That one has pictures in it and the correct parameters. I am afraid that computer programs do not work just by making up your own values for things. They have to be fed things they are programmed to understand. Regards, Pete

If you mean you want to use FSUIPC to enable reverse thrust, then the instructions are included in the FSUIPC documentation. It does get slightly more complicated for the CH quadrant if you are using their Manager. You then have two ways of doing it, as far as I understand. I don't have any CH gear, but Bob "Sticky" Church has written about how to sort this out, either way. Check for this on http://www.stickworks.com. Regards, Pete

If you re-install Windows, or move to another PC, you need to re-enter the codes into FSUIPC, as you did when you first got them. If you have copied the FSUIPC.KEY file over, all you should need to do is re-enter the Keys. If you cannot find them you can cut-and-paste them from the KEY file, which is a simple text file you can view with Notepad. Please note that you are out of date with both of these, so they are both effectively unsupported. Current supported versions are FSUIPC 3.48 and WideFS 6.47. Regards, Pete

There's nothing I know of which would cause that, and I've certainly never noticed it. Sounds like some poor modelling -- are you using add-on aircraft models? If so, look for better ones. Or are you trying to turn with extreme bank? Limit your rolls into turns to 30 degrees max. Since I don't know the cause I can't see how FSUIPC could help in doing anything about it. Maybe others here have some ideas... Regards, Pete

WideClient can be run alongside FS, but only by setting it up with a different Class name. Please see the ClassInstance parameter documented in the WideFS documentation. It needs to have a different class name because the way client applications link to the IPC interface in FSUIPC is by finding the program with the classname FS98MAIN, which is FS's own. You can't have two running in the same PC and expect the application to link correctly, so this circumstance is prevented. In fact FS itself won't load if WideClient is running, and vice versa. The ClassInstance parameter does get around that problem, but then you have another. You now need to get the application programs to link to the new Class name instead of FS98MAIN. That requires a change in them. I don't think that there are any programs being distributed at present which offer such an option. It would be something you'd need to request from the author(s). Regards, Pete

Via FSUIPC, you mean? No, sorry. That's a part of FS I never found out much about, at least since FS2000. For FS98 I did find a way to intercept, redirect and change sound values for some sound sources in FS, but it all changed in FS2000 and I couldn't repeat the exercise. Regards, Pete

You missed it then? Near the end there's a section entitled "The PFC.INI file" which lists those parameters which can be changed there rather than in the options dialogue. The last three cover these limits individually for each axis type. Regards, Pete

Great! Good flying! Pete

I'm afraid I've never heard of Matlab, Simulink or MFSUIPC before, but merely entering "MFSUIPC" in the Google search bar finds me just this link: http://web.mit.edu/aeroastro/flightsimlab/flightsim_appendix.htm Maybe there will be a clue there? At least you should be able to email the folks who made it? Regards, Pete

Okay. Thanks for letting me know. Good luck! Regards, Pete

FSUIPC doesn't replace FS assignments, nor does it do the basic initial calibration you should do in Windows Game Controllers. FSUIPC offers refinements to the results -- more accurate centres, null zones, response curves and some rudimentary jitter filtering. You also want to find the [Controls] section in your FS9.CFG file and add "stick_sensitivity_mode=0". This makes it deal linearly with axes instead of using a strange time-related response (something which was introduced, to my mind inexplicably, in FS2000). And check that the FS Sensitivity setting is at max and the null zone at min before using FSUIPC. These settings are in the Options-Controls menu in FS I think. Buttons are a different matter. FSUIPC offsers more controls you can assign to, and also keystrokes. But de-assign the same buttons in FS if you program them in FSUIPC. Regards, Pete

Well, that was contributed by someone else. The WideFS document covers it in a section called "PTT (push to talk) for Roger Wilco, AVC and TeamSpeak". It's near the end so perhaps you never got that far? :wink: The contributed document to which you refer may be more understandable for you -- it does have pictures too! I clean forgot it was there. However, it will only apply if SB3 does support that method. Otherwise you have to set up the KeySends in the INI file to send the keystroke instead, as described for TeamSpeak. Regards, Pete

Well, it's IPX/SPX, and, yes, of course. WideFS was always IPX/SPX only -- for over 4 years -- before I added TCP/IP. The latter's only advantage is that it is easier to set up and is installed by default. Microsoft don't seem to care too much for IPX/SPX. Incidentally, WideFS uses SPX (Sequential Protocol), because things need to be done in order. IPX, as used by WidevieW, is used for broadcasting and doesn't guarantee sequence. Not as much as TCP/IP, which has far more red tape and software levels to handle it. IPX/SPX was designed for small local Networks. TCP/IP is designed for the whole Internet. The latter needs a whole lot of stuff which is not needed at all when talking to the PC two feet away. See how IPX/SPX goes first. Check the documentation. Your WideClient INI files don't work with ServerName and ServerIPAddr then, you need the ServerNode, which will be listed for you in the WideServer.LOG. Regards Pete

Are you sure they don't also support the Roger Wilco / AVC commands. I seem to remember someone in the team saying they would. If so, it is much easier and more reliable than programming keystrokes. Regards, Pete

I don't know anything about SB3, but presumably it either uses the same commands for PTT as Roger Wilco and AVC, or it needs a Keystroke. Try the former first. All this is documented in the WideFS documentation, though admittedly not yet for SB3 which I know nohing about. BTW, I would have hoped that SB3 had their own Support forum where there must be loads of folks who know the answers to questions like these. Regards, Pete

Well, you must have changed something -- installed an add-on which updated FSUIPC from a version 2.xxx to a version 3.xxx perhaps? I assume your 747-400 is not the default FS one -- that would need to access permissions. After this occurs, look in the FSUIPC.LOG file -- it is an ordinary text file and you will find it in the FS Modules folder. It will tell you which gauge is trying to access FSUIPC. If it is a freeware one there may well be a Key already listed above. If you don't understand what you see, show it here. Please note that I always need to know the Version number of FSUIPC in any query of this sort. You can find that either by going to the FSUIPC options in FS (ALT M F), or right-clicking on the DLL and selecting Properties-Version. If you are not using 3.48 (or even the 3.481 provided here for testing), then please update -- you'll find the package on http://www.schiratti.com/dowson. Regards, Pete

Reply by clicking the "quote" button. That's okay. Yes, ICS. I never got on with that. I don't know why -- something for a Windows XP/Network expert I think. In that case, couldn't you do without ICS and just have the Modem connected to the PC running Squawkbox? You could also firewall and virus check on that PC. without internet access on all the others they should be safe. There certainly shouldn't be any. I know nothing much at all about Networks, so, to write WideFS, I just used Microaoft example code -- literally, straight out of their SDK. Since you have IPX/SPX up and running everywhere, why aren't you using that for WideFS? It is much more efficient -- less load on the Network, less interference with anything else. Have you tried it? It varies from Ethernet card to Ethernet card, but as an example see the section in the WideFS documentation entitled "Other Notes for Trouble-Shooting". There's even a picture there of what you might see. One of the entries in the list illustrated is "Line speed & Duplex" which by default gets set to "Auto" -- it is better at 100 Full Duplex. The list on your hardware may be different, but it should be there in some form or other. You could check some of the other entries in the list too -- make the number of sockets much higher for instance. As soon as you get a new connection working, WideServer will list it so that it can allocate unique numbers to any joystick or Goflight buttons coming from that Client. WideFS does not use the Internet so it doesn't care where it is. It doesn't use file sharing either. Regards, Pete

I've never heard of "Matlab/Simulink", but you should realise that FSInterrogate is only an investigative tool, an example of a program written to obtain information from FS via FSUIPC. If you want to read data from FSUIPC, interface to it directly. The FSUIPC SDK is available from http://www.schiratti.com/dowson. Take a look. Regards, Pete

How strange. I really do have no idea. How are the other PCs getting their internet connection? Are you using Windows "ICS" (Internet Connection Service) for this, or a third party program like Sygate? I never got on at all well with any type of ICS -- eventually I gave up and got a cheap router -- which really is better as it acts as a firewall as well and effectively isolates your entire Network from the outside world. If it is ICS, I wonder if somehow both the ICS and WideFS are attempting to use the same sockets -- I don't know how that would be possible. Otherwise, possibly the traffic is clashing so much that neither is successful. But for that it must be a rather poor Network. Is it the same if you try it the other way round -- i.e. get WideFS going before enabling the Internet connection on the other PC? File sharing might matter to Squawkbox, I don't know, but it isn't used or needed for WideFS. Equally, just because Windows Explorer can see other PCs it doesn't mean other programs can do the same. Yes, it's clear enough, thank you, but I really don't know enough about Networks to answer. I would proceed with a series of experiments to try to nail down the cause. For example, what if WidevieW isn't running? Maybe that is contributing. Try the Internet PC without running FS on that one. With WidevieW traffic, Internet traffic, and WideFS traffic all attempting to use the Network simultaneously, I do hope you have a good fast Network with a switching hub, or even a Firewire daisy chain. Switches rather than Hubs help quite a lot because then every PC only gets traffic destined for it. This certainly helps WideFS and Internet traffic as they use point-to-point exchanges. WidevieW uses broadcasts I think, so that will still tend to flood things a bit. As far as Network speed is concerned, the fastest at present is the Gigabit (1000 mbps) Ethernet connections, followed by Firewire (1394 or I-link) which is roughly equivalent to 400 mbps, then the ubiquitous 100 mbps. Do not use 10 mbps at all. Also check all the settings on each Ethernet device. You don't really want auto-negotiation of anything, as that takes extra time on every exchange. Set the mode to the fastest common speed, full duplex, on all. Finally, I'm a little surprised you were sent here from the FS2004 Forum. I assume this wasn't by Katy Pluta, who is one of the moderators there and is the person I tend to ask whenever I have a Network problem. It may be a good idea to ask for her advice over there, specifically. Please let me know what you find. Regards, Pete