Pete Dowson

The TQ6 is recognised in FS as a set of axes, so you can assign them just like any other joystick axes. OR you can assign in FSUIPC, just as with any other axes. The buttons and switches on all GoFlight units are recognised in FSUIPC just like any other buttons and switches, providing you have "GFDev.DLL" installed in the same place as your GFConfig program (which is where it usually is) or, for FSX only, in the FSX Modules folder. So, there's no difference really using GoFlight devices from any others. Just go ahead and assign as you wish. Regards Pete

They are not seeing each other, then. Did you check and make sure that both computers are in the same Workgroup? Or if you prefer to have them in a separate workgroup, did you tell WideClient the name of the Server and the Protocol you want to use? This elementary part of the setup is described at the beginning of the section in the WideFS User Guide entitled thus: Configure your Network IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS! If you've checked that or attended to it and it still fails to connect, it may simply be the firewall at one end or the other. If you've disabled that or attended to it to allow FS and WideClient through, please show me the WideServer.log file from the FS Modules folder, and the WideClient.log file from the client folder. These might show the details of the problem. Pete

Both "G" and clicking the mouse generate a GEAR TOGGLE control, as you would see if you enabled FSUIPC's event logging. What are you assigning the Button to? If it is to Gear Tooggle there cannot be a difference. If the gear changing sound occurs then most certainly FS things the gear is moving. Have you looked on the outside view to check? Pete

Hey Pete. Could you explain what you mean by this a little more? Simple: use frequencies which FS won't recognise as ATIS in the vicinity. Yes, but if everyone knows that and uses the same off-frequencies that would work, right? You all want to avoid FS's ATC voice, correct? You will all be using your application, whatever it is, right? Maybe I'm not understanding what it is you are trying to do. what will you be using the COM frequencies for if not for your own ATC and ATIS? Regards Pete

Of course not, because you've deleted the lines which tell FSUIPC which joystick names equate to which Windows ID number. You are supposed to ADD those letter-defining names, not replace the originals!! Doing that destroys any chance FSUIPC has of tying them up again for you. If the numbers change the names will still tie up, but FSUIPC has to have both number and letter references in that section, as the example in the documentation clearly shows. It remakes the numeric lines when it loads so it can tie them up. Regards PEte

To edit and recompile BGLs you'd need the FSX SDK to start with. There are some useful, even freeware, programs around too like Airport Design Editor (ADE), but I don't know if they deal with ATIS frequencies as well as those specific to airport functions. No. There appear to be no provisions for doing anything with sound in SimConnect. You'd be better off simply using non-ATIS frequencies, maybe just automatically adding .05 or something to de-tune them. It really depends on what you are substituting for the transmitter, doesn't it? If you are writing a program to read the frequencies, just re-adjust them internally. Or simply choose arbitrarily different frequencies in the first place. Regards Pete

There are two ways around this. One is simply to use the "ShortAircraftNameOk" facilities as described in an Appendix to the Advanced Users guide: APPENDIX 2: About the Aircraft Specific option and “ShortAircraftNameOK” Those facilities have been available and documented with examples supplied by users for several years. The tidier and more modern facilities to cover this in a much nice way are those for aircraft Profiles. Those facilities are described in their very own chapter in the Main User Guide: User profiles for all control settings Take a browse through the documentation provided some time. You may be surprised at the range of facilities provided. This is the problem with such a multi-purpose tool, folks miss too many of the useful bits. :-( Regards Pete

First, if you really do mean "FSUIPC 4.1", please update to at least 4.53. Version 4.1 is very old and totally unsupported. it is also not taking advantage of the SimConnect pipe protocol added in FSX SP2/Acceleration, which make FSUIPC's operation more efficient. Try again after updating FSUIPC. Two seconds lag is not good. If there's no problems shown in either WideServer nor WideClient log files then it shouldn't won't be the Network -- though you could try specifying "Protocol=UDP" in the WideClient INI file to see if that helps -- it is a faster option for a reliable connection. Also check the FSUIPC4.LOG file for errors or SimConnect problems. You could also try running the program on the same PC as FSX in order to eliminate the Network entirely. Other possibilities include anti-virus or firewall checking. Some packages can slow things down noticeably. I'm afraid Network problems are really not something I can help with easily. It's often a matter of trial and error. I was adding lots of hints to the wideFS documentation, but Vista and Windows 7 sem to have added a whole raft of new and different problems. Make sure all your PCs are in the same Workgroup. Make sure each can see the other, via Windows Explorer, for instance. Make sure the firewall isn't blocking anything - try with it disabled on all three as a test. Regards Pete

That is correct. In fact it is even more restrictive -- only the SimConnect client which added the WX station can remove it. In any case, I'm not sure that removing a "real" weather station (if it were possible) would remove the ATIS -- the ATIS is a radio aid built into the BGLs, so if you tuned it in it would try, at least, to tell you the weather. Maybe it would get an error when it asked for the specific WX ICAO weather and crash FSX. The FS weather stations are listed in files in FSX folders. You could try deleting (or renaming) those. They are icao_pos.bin, wxmapping.bin, and wxstationlist.bin in the Weather folder, and wxstationlist.BIN in the same folder as the FSX.CFG file. I suspect you'd crash things if they aren't there at all, so experimentation might be needed. You could start with the one in the FSX.CFG folder, as I think that is a dynamically created subset of the one in the Weather folder, being updated from the MS/Jeppeson website when & if you download FSX "real weather". If you delete that and don't download weather, maybe it will remove those stations. However, none of that defeats the ATIS radio frequencies and worrying what FSX might do when you tune into a station. If there's no current weather for a station (which can happen), it probably just gets either the default ("global") or the interpolated weather. Thus defeating your object. In the end probably the only way is to remove the ATIS frequencies from the BGLs. You could probably write a BGL which did that using the "delete frequency" codes, and have it running at the top layer, so processed last. Same way, turn the voice slider down and/or uncheck it. Regards Pete

Don't test them on the ground. As soon as the value is in the region of the "Arm" detente on the lever, with the gear compressed through being on the ground, they deploy as in landing. There's no such range on the spoilers. The Arm position is around value 4800 (29%). Below that is full down (0%), above that the speed brake range applies from control values 5619 (34%) to full 16383 (100%), though you shouldn't extend to more than the flight detente when in flight. that's around 60-65% I believe. Regards Pete

Does it really? That's a bit of an oversight on Microsoft's part. Apart from the normal response controls (for the dialogue selections), there's no ATC control whatsoever exported from FS. I've always replaced it by Radar Contact, and some folks prefer VoxATC. Of course if you fly on-line (not "multiplayer", but on-line ATC) then you have real ATC voices anyway. FSX allows additional weather stations to be created, through SimConnect. Programs like ASA uses the facility to create weather stations in the Atlantic, for example, so the weather can vary on transatlantic flights. FS only sets weather at WX stations -- everywhere else it is interpolated. The facility to remove the created stations just does the reverse. WX stations are of course completely to do with ATIS as it is the weather stations which supply the weather being reported by ATIS. Regards Pete

By "not seeing it reversed" do you mean the numbers increase when you push the lever forward, and decrease when pulled back? If not, then you need to use the REV checkbox. If default aircraft, used on their own, via a mouse not a joystick, operate with the throttle lever going forward giving reverse thrust, something very very odd is going on in your system. I would uninstall and reinstall FS completely if such weird things are happening. It certainly cannot be down to any addons if it affects FS on its own. You might want to transfer your questions about such odd things to the FSX forum, near here, see if others have experienced such odd behaviour in FSX. Regards Pete

Yes, sorry! I am fixing that now. Through an oversight on my part, the Registration check in FSUIPC doesn't like 2010. It was meant to be updated for 2010 registrations long ago, but I've been working on so many new facilities of late that the new User Release which was intended to go out in October or so isn't yet released. I will be making a full update later this month. Meanwhile, look out for FSUIPC version 3.957 which I shall make available via the Updates & Other Goodies Announcement at the top of this Forum in a short while ... (It's there now!) Apologies, again, Regards Pete

I would normally say that the reason was that your throttle lever axis is reversed, so, before calibrating it, you need to select the "REV" option to put it the right way round. There's one in FSX assignments and also in FSUIPC calibrations -- but don't use both. However, the fact that your pictorial throttle quadrant in FSX is also working in reverse is completely inexplicable unless you have a practical joke of an aircraft add-on. Try one of the default aircraft instead. Regards Pete

This isn't an error log, it is a successful Install log, with a successful registration, as it clearly states. Why do you think there's any error? And, yes, it shows FSX.CFG was found in "C:\Users\Marc\AppData\Roaming\Microsoft\FSX\FSX.CFG". Not sure what "benutzer" is -- I assume that's the translation of "Users" presented to you in the user interface? What do you mean by "FSUIPC doesn't show up"? Regards Pete

Sorry, I don't really know the PMDG 747X. I know that the GoFlight TQ6 is a generic throttle quadrant, assignable in FSX in any case, so I don't think that will be a problem. Radio modules should be okay I think -- I doubt that PMDG do their own radio emulation. As for anything else, sorry, i don't know. Regards Pete

Thank you. The same to you and yours! Best Regards Pete

Sorry, you misunderstand I think. The mouse macro facility isn't a mouse position and click emulator. It replaces the action of the mouse on a mouse-sensitive switch by a direct call to the underlying software which obeys the click. It never does any mouse clicking at all. Regards Pete

Yes. Happy New Year! Pete

It is pointing to the PMDG installation then, for sure. The "FSUIPC Installation" is simply the presence of FSUIPC.DLL in the Modules folder, nothing more, nothing less. If it's there, it is "installed", if it isn't, it isn't. It has no feelers, no changes, no parts placed anywhere else. Try putting FSUIPC.DLL back and instead removing the PMDG DLL from the Modules folder -- PMDGOptions.dll is the one, I think. Regards Pete

Thanks. That would enable me to stop folks going outside the LAN -- assuming I wanted to, and also assuming I knew how to get hold of the sub-net mask! ;-) Regards Pete

Strange indeed. Something seems to have got corrupted in FS itself somehow, but what could cause the conditions you mention I've really no idea. I suspect your quickest remedy would be an uninstall and re-install. Though you could start by simply uininstalling one add-on at a time, checking each time. Start with FSUIPC by all means -- it is so easy to uninstall in any case, merely remove it from the Modules folder. No, it is very strange I agree. If it were a proper crash, with details, I would possibly suspect a memory fault -- hardware errors are always unexpected and need not of course coincide with any other change you make. I suppose corruption of files on disc could also account for unpredictable results, but the only way to find that out would be the reinstall path. You did say it was a new PC, so perhaps something's not right with it. If things fail they often do when new or very old, not so much in between (in my experience). If you have enough disk space, why not do as I do in these cases? Just rename the folder containing FS (eg "Flight Simulator 9" to "Old Flight Simulator 9") then install FS9 again, in the same place as you did before. Check that is works, then gradually add one thing at a time ...even copying stuff from the "old" folders if need be. Check at each stage. Regards Pete

0BC4 and 0BC6 are the brake axes. The 0C00 and 0C01 bytes are a remnant from FS98 days, emulated by FSUIPC since FS2002 at least, and operate the brake pressure decay when using a Brakes button or key control, rather than an axis. Without that decay time, braking would be only on or off with those controls instead of increasing when held/repeated and reducing when not. 3416 and 3418 are merely the copies for Fly-by-Wire operation, when the brakes are disconnected by using 341A. They are not control offsets, just copies for application's information. FSUIPC doesn't use them -- an FBW application would use them, or one doing its own sophisticated braking system (taking into account wet, sloping, icy runways for instance, like the Thomas Richter braking utilities). They might modify the value before writing it to 0BC4 or 0BC6 Yes, as just described and documented for those offsets. disconnect the brakes via 341A, read those values at 3416/8, change them, and write them to 0BC4/6, as described. Regards Pete

Okay. so it isn't relevant to the problem. Okay -- the first thing FSUIPC does when run is start the Log. So if no new one is being produced it appears FS isn't getting that far even. It is probably failing with a bad CFG file of its own. I know corrupted LogBooks can do this for FSX, but I'm not sure about FS9. I don't think it's a problem for those. Looking at your last successful log, I notice that you have the PMDG 737 loading as your default, in the default flight. I have known a number of problems folks have had with loading a complex aircraft as default -- something could have become screwed up there somewhere. Unless you can find a place to click to get more information on the error from Windows (there's usually a "details" clcik sdpot or somesuch and I'm surprised you cannot find anything), then I think your best procedure, at least as a test, if to find and rename your FS9.CFG file, so that it isn't used and FS9 makes a new one. This will revert FS to its default settings. If that works, then you can use a process of elimination between the old renamed one and the new defaults, gradually moving to the same result. I suspect, though, that it is tied up with that initial flight, which of course won't be loaded by the default CFG. That won't do any harm. Regards Pete

It isn't as simple as that because those settings will be in the parameter file sections for that profile, not in the general / global sections, and cannot simply be re-classified because of possible clashes. You would need to edit the FSUIPC INI file -- load it into any ordinary text editor, like NotePad (not WordPad). You'll find it in the FS Modules folder. There are sections for [Axes], [buttons], [Keys] and [JoystickCalibration]. These names, without additions, are the global sections. The sections applicable to a Profile have the Profile name appended, for example: [Axes.MyJets], [buttons.MyJets], [Keys.MyJets] and [JoystickCalibration.MyJets], for a profile called "MyJets". If you simply want to make this "MyJets" set of assignments global, replacing any pre-existing global settings, then simply delete the entire global sections and then edit the titles in the Profile ones to remove the ".MyJets" part of the name. If you want to merge in the profile settings with the global settings, it isn't so easy -- there may be clashes (dual assignments), and you'd need to deal with those, deleting whichever is not required first. Then add the contents of the profiles part to the global part, renumbering the lines to be in sequence again. The line numbers (before the "=" sign) have no significant other than imposing order. If you want to remove specific aircraft from a Profile assignment, look for the [Profile.MyJets] section (or whatever yours is named). There's a list of aircraft names in that section. Delete those you don't want profiled in that way, renumbering any remaining lines in sequence. Hope this helps, Regards Pete