Pete Dowson

Windows assigns IDs according to connections it sees. These will alwmost always change if you unplug devices and plug them in to different USB sockets, or sometimes even to the same. I also have suspicions that it may do so if there's a Windows update performed whilst the devices are unplugged. However, it is okay if you never unplug them. Does Windows7-FSX-FSUIPC enumerate axes the same way every time all the time? FSUIPC can deal with this, but you need to use Letters fror devices instead of the numerical IDs. When everything is working okay, just close FS, and edit the FSUIPC4.INI file to automatically assign letters. That's all that is needed. There's a whole chapter about this problem and its solution in the FSUIPC4 User Guide. Regards Pete

No, I did not CHANGE the lines. The lines I showed you should be ADDED. You can of course copy the existing ones and change the copies, but if the numbered lines aren't there then FSUIPC cannot match the numbers for existing assignments to the correct joysticks! The whole point of all these lines is to declare the equality between the numbers (which might change next time) and the letters. After you edit that section you must run FS once in order for the existing assignments to be converted! I realised you didn't understand any of this, despite documentation which hasn't been so questioned since published, which is why i suggested that you take the easier course of letting it all happen automatically. Anyway, sorry, but I won't be able to help any more until 22nd july because I'm off on holiday soon. I'm sorry you find the documentation so obscure. Pete

I can't tell you exactly because I don't know the full EXACT names of anything but the two you showed. As the user guide tells you, the name must be EXACTLY as shown, as it needs to be matched. If there's a GUID, match that tooo. So, for example, for the two you have shown so far, using perhaps Y and R: Y=Saitek Pro Flight Yoke Y.GUID={8951F010-E9BF-11E2-8001-444553540000} R=Saitek Pro Flight Combat Rudder Pedals (USB) R.GUID={D015B190-EA1D-11E2-8001-444553540000} Strictly you probably don't need to add the GUID lines too, but it is safer in case you have two or more joysticks with the same name. The GUID is always unique. Pete

Is that when assigning the hat in the Axis Assignments to 2Pan View". It is smooth here. Er, why's that different to the manual? The example in the manual looks exactly like your example except, obviously, differet devices and GUID numbers! Er, no! Didn't you actually read the text? You need to ADD lines to assign with the letters if you want to do it manually. If you don't understand what you are doing, or don't want to read it, just change "AutoAssignLetters" to "Yes" before running FS, as suggested. Pete

Really? This is even with it assigned as an Axis to "Pan view"? You aren't thinking of unplugging and re-plugging things each time, were you? Because if you have not disabled controllers altogether in FSX it will re-assigned axes and buttons each time. If you weren't thinking of doing that then I don't understand how the question arises. I don't know how you create 'profiles' in FSX. Maybe you mean FSUIPC? Nothing will mess up FSUIPC assignments and profiles unless you delete or corrupt the settings stored in its INI file. However, the numbers used to identify devices may change, and that will get all the assignments mixed up. The way to avoid that, before unplugging anything, is to change FSUIPC to use Joy Letters instead of numbers. There's a chapter in the user guide about that. See the contents list near the front. But, as I said, unplugging and replugging in joysticks will wreak havoc in FSX because it will make automatic assignments -- UNLESS you disable controllers there. Axis assignments and calibrations, when made in a Profile, are profile specific. No other axis movements will be applied by FSUIPC other than those belonging to this profile. Button and Keypress assignments can be global, applying to all profiles, and profile specific. If both the latter override the former, but usually you have a mix. This isn't done for axes for obvious reasons. Regards Pete

As already stated, WideFS is for linking FSUIPC applications on one PC to an FS running on a different PC. Nothing like what you are after. WidevieW is also for separate PCs, but instead it links multiple working copies of FS. If all you want is one wide view on a single PC across 2 monitors, just check your video driver and enable the mode in which the entire width of the two monitors gives you a stretched view, as one screen. Alternatively, if your video driver doesn't support such a mode, run FS in windowed mode and stretch that window over both screens. For difdferent views on dfferent screens, just undock the views (right-click and select undock), and drag them to where you want them. Pete

The PMDG 737NGX provides data which FSUIPC does make available through a set of offsets, but ALL of that data is READ ONLY. It is the values for displays and so on. There are NO offsets available to send switch changes or other settings TO the NGX, none at all. The whole of the NGX control input is via special controls which are documented in the PMDG SDK documents (particularly the.h file). FSUIPC allows the assignment of those specifial controls, by number, to buttons and keys. Pete

What exactly are you looking for in the drop-down assignments list? They'll be added as entries like lua <name> luaclear <name> luakill <name> luaset <name> luatoggle <name> luavalue <name> where <name> is the name of the Lua file, without the .lua part. That name must be no more than 16 characters. Pete

Reinstalling FSX usually makes things worse, not better, because it messes up the SimConnect module connections. Without more information I'm afraid it isn't possible to help further. Please see the FAQ on problems after initial installation. Pete

I can't create Forums or even Subforums by myself, but I do think at least a Subforum here would be worthy. I can ask SimFlight to set that up if Paul agrees, and transfer this complete thread over when done. However, I am leaving for a 10 day break in a few hours and don't have time. Maybe Ian, if he ses this, can do the necessary. Best Regards Pete

I hope someone comes to your assistance, as I really don't have a clue. I only suggested it because we have had reports here previously of folks eventually finding some setting or other which was wrecking their network communications, but folks never really explain what, and in any case each router seems different. And it may well not be the router, of course. In fact you never actually confirmed whether your network was working at all, eg for file sharing or exchange of files. I've never ever heard of a network which takes up to 4 hours for programs to start talking to each other after the connection has been outright refused many hundreds of times. BTW, when you said this: I'm pretty sure SuperTrafficBoard does NOT use Simconnect for its network connection. It does it itself, with a program called something like "STBserver" on the FS PC. So you've actually got three different programs, all doing their networking differently, all taking 3-4 hours to get a connections That is really bizarre!. If Windows Explorer works, exchanging files etcetera, across the network, (it uses UDP protocol), you could try putting WideFS into UDP mode instead of TCP. That's done by adding "Protocol=UDP" ito the first section of the WideClient.INI file. I don't hold out a lot of hope, though, because I think SimConnect might be usung UDP too. There might be better forums to seek help with this, as it doesn't appear anyone else here is coming to assist. I'm afraid i'm no good with Windows networking at all, and in any case i'm away from tomorrow for 12 days. Pete

If the values in axis assignments page are changing rapidly, there is most certainly input from the joystick -- it is jittering for some reason. The values shown there are read directly from DirectInput the Windows joystick interface. If it is only the values in the calibration then it may be down to conflicting assignments to the same FS controls, but even then some input much be changing because both FSUIPC and FS do nothing if input values don't change. Pete

What instructions?

Weird language, C#, since a BYTE is already just an 8 bit integer. I would imagine that under the skin all the conversion does is provide the byte as it is. No conversion is really necessary. Ah well. Regards Pete

Correct. But only once instance is used by each SimConnect client. FSUIPC4 chooses the latest which it can find -- SP2/Accel if there. But many programs are written specifically to interface to one -- quite often the SP1 version. If you've deleted them from the WinSxS folder it shouldn't be a problem if you've not messed with the Registry too. Just go find the Core Utilities folder in the FSX SDK. All three SimConnect msi files should be there somewhere -- the older ones in "legacy" folders or something similar. If you run those then hopefully it will reinstall them. It SimConnect is really and truly hosed i've found it's a Windows re-install job, especialliy with Vista or later. I seem to remember that it was just about possible to sort it by registry editing etc in Win XP. Regards Pete

Sorry, I don't understand how, if you are reading a byte value (which is only 8 bits, range 0-255 if unsigned), how you can get a weird string like " FSUIPC.Offset`1[system.Int16].". Are you perhaps mistaking an error message for a value? I don't know C# at all, but the following seems odd: As documented, offset 0B6B is a one byte, or 'BYTE' value (8 bits). I don't know about C#, but in C/C++ "short" is a 16 bit or 2-byte value. I think you would get wrong results in any case even without whatever error string you seem to get. You don't mention which version of FS you are talking about, as this may be different. But i'll assume FSX for now. Internally, as a Simulation variable, it's really read-only, but if you write to it a different value to its current value, FSUIPC interprets that as a request to send the TOGGLE_ENGINEn_FAILURE control to FS, where n depends on which bit(s) you change. The read-back value will then change when FS accepts and obeys that control. Pete

Neither FS nor FSUIPC use .Net Frameworks in any case, so it sounds like you have something else going on there. Why is the title of tyour thread "FSUIPC not found"? What does that really mean, or is it irrelevant? What version of FS are you using? What version of FSUIPC? What exactly is the "error when starting", and when starting what -- FSUIPC or FS? Pete

Just go to the FSX assignments page (Options-Settings-Controls) and uncheck the option top left of the Calibration tab labelled "Enable controllers". If you don't do this FSX will sometimes automatically re-assign things. Pete

That's a network driver or hardware problem. Last time i had one of those I just uninstalled the Network connection and associated hardware (in device manager) and re-booted so that Windows would find it again and reinstall. Regards Pete

It's a mystery then. Maybe check the router, or whatever it is connecting your PCs. Sorry, I've no way at all of diagnosing such an odd occurrence. Pete

I don't really understand the question. Are you saying your joystick is operating the rudder? If so you have something on the joystick assigned to the rudder. Just delete that assignment. Again, I'm not sure what the question is, but if your brakes are coming on without you using them, it is an assignment somewhere. It rather sounds like you have dual assignments. Either assign everything in FS or everything in FSUIPC. In the latter case disable controllers altogether in FS to prevent it reassigning automatically. Er, steering with the rudder moves the rudder, of course. if you want to steer on the ground you have to use the rudder -- unless you are using FSX in which case you can assign an axis to FSX's steering axis. That is new in FSX, it doesn't exist in FS9. Not sure where landing gear comes into this. Sorry. Regards Pete

Am I being that? Sorry, if so it isn't intended. I only try to state the facts. Which part upsets you? Naming the files, or saying something is blocking? The "product" which is complicated is windows and its networking, not WideFS. There is almost nothing you should need to do with or to WideFs if the network is set up and working. And I do not find Networking easy at all, far from it. If I get a Networking problem I have to find advice and experts to help me, as I haven't the foggiest. I can see nothing in what I've said which should upset anyone, but apologies if you think so. And I won't reply any more, as i really haven't any more I can say. Regards Pete

Well, strangely, the WideServer.log is the file called "WideServer.log". The other is the normal FSUIPC log and it is called FSUIPC4 log. The names differentiate them. The Server is not seeing anything of the Client, so the latter is being blocked for sure. Well, all Windows is saying is that it is refusing the connection, so something is blocking it for sure. If not a Windows firewall some other software you have running or maybe your router. I'm sorry, but there are no other clues. Is the network working for anything else? You do need a working network first. Regards Pete

Okay, it is done. Version 4.908 of FSUIPC4 includes full support for Lua plug-ins to see mouse events and act upon them. Please download and install 4.908, and also get the latest Lua plug-ins package. You'll find them in the Download Links subforum. The example I've done is especially aimed at your requirement. It is the plug-in called 'mrudder.lua' inside the Examples zip file. Just put that into your FS Modules folder then edit your FSUIPC4.INI file adding: [Auto] 1=Lua mrudder (or a later number if you already have this section with entries). Then load up FS. When everything is up and ready, go into FSUIPC options and assign a button or keypress to "LuaToggle mrudder" in the dropdown. This button or key will switch the whole action on or off. With it off you can use all facilities of the mouse as usual. When it is on, the right mouse button will turn the mouse into a rudder control. It will move the mouse pointer to the current rudder position (left/right position on screen -- centre screen = centred rudder), and movement of the mouse left and right will move the rudder and the mouse pointer to match. The up/own movement isn't relevant. When you release the right button, the mouse pointer will go back to its position before you pressed it. If you look at the mrudder.lua file in a text ditor you will see how it works and can change it to more suit your needs if you like. Have fun! Regards Pete

But it must be very hard not to observe that it is very very repetetive, even if it is merely like looking at a wallpaper pattern to you! One section of pattern is enough to know what the rest looks like! ;-) No, that's not the WideServer.log file at all. It looks like the default copy of the Wideclient.INI file supplied in the WideFS zip file. The Server log will of course be on the Server PC, in the Modules folder necxt to FSUIPC4 etc. Pete