Pete Dowson

Er ... the log would be in the FSX modules folder if you'd put the path to it where it clearly says "path to FSX\Modules". As it is that path is invalid so no log will be generated. Pete

If you want different assignments for each profile you have to assign in FSUIPC because FSX doesn't offer different assignments for different aircraft. But if you assign in FSUIPC you can't have your FS Force working you said. So you have to make a choice it seems. As I keep saying, the calibration options are completely and utterly independent of how you assign! vHow many more times must I say this. assign in whatever way you like. The calibration options work on the controls in FS, not on the axes at all! And the right-hand side of the assignment is to assign different functions to different parts of the range of an axis. it is not relevant to anything you want at all! The thing you are missing is what i keep repeating. CALIBRATION IN FSUIPC IS INDEPENDENT OF ASSIGNMENT. FULL STOP! Sorry ot have to shout but I don't seem to be getting through to you at all. :-( Just assign in whatever method suits you. Calibrate using whatever options you want. There's nothing magic, it is all as easy as that! Pete

That looks fine. So it is a puzzle. SimConnect is ignoring the entry in the DLL.XML file? Do the other modules load -- eg the one before FSUIPC, "RAASPRO"? Maybe we need a SimConnect log to see what it says. There's a thread in the FAQ subforum which tells you how to get one of those. Pete

Okat, all that looks okay. So, two more files to check: First, is there an FSUIPC4.LOG file in that Modules folder? If so then FSUIPC4 is being loaded -- please paste its contents here. Second, the DLL.XML file is responsible for telling SimConnect which modules to load. Maybe it is corrupt, so please let me see that. You can find it here: C:\Users\Dougies\AppData\Roaming\Microsoft\FSX Finally, take a look in the FSX.CFG file in the same folder. No need to post it here. If there are any entries referring to FSUIPC in the [Trusted] section, delete them. Pete

FSUIPC uses the exact same identical Windows facilities for reading joystick axes and buttons as FSX does, no difference at all. I've no idea why folks sometimes say they behave differently -- though these is one difference. FSUIPC will re-scan for devices each time you enter one of its assignment Tabs in its options. It also rescans devices if it sees a USB disconnection and reconnection, unlike FSX which only ever scans for devices when first loaded. Maybe that little difference sometimes helps -- I really don't know, nor do I know why Windows 8 users suffer these problems so much. Your experience, where even going into FSUIPC and seeing no reaction to buttons, means that, in your case at least, rescanning devices doesn't solve the problem, whatever it is. Maybe it is more related to the devices themselves, so I suppose you could try unplugging and re-plugging in the USBs then checking in FSUIPC. Regards Pete

Is there a Modules folder in the main FSX folder? If so, please find the FSUIPC4 Install log file, and paste its contents into a reply here. Pete

Please download FSUIPC4934a.zip. You will find instructions inside. Please give it a good bashing and let me know how you get on. Bast to make a backup copy of your INI (the auto conversion also does this, but just to be safe for now). Then if you want to do different tests you'd only need to restore that and delete or rename the new Profiles sub-folder I'm not a user of Profiles myself (I only fly one aircraft each on two different hardware sims), so whatever I do here with the facilities would be completely artificial. I have tested the logic of the code and everything works as I have documented it for me, in my simple test cases. Thanks & Regards Pete

Why 4 bytes when you are told it is one byte and you are reading and writing one byte? Isn't that a bit obtuse? ;-) And when testing things involving offsets, please use the tools available to see what is going on: FSUIPC logging tab, right-hand side. monitor offset 66C0 as type U8 and offset 94DE also as type U8. Select "Normal log" below. FSUIPC will then log all changes to those two offsets. I'm afraid I'm no help with either iFly2FSUIPC or FS2Phidget, so if the offsets are working correctly, you'll need help elsewhere I think. Like a value which can be on or off is a "LogicVar"? Maybe? Pete

The Auto Assign option just does initial assignment for controllers not yet assigned a letter. You can't undo letter assignment without going through editing every line in every section where a button or joystick axis is referenced! Why on Earth would you want to disuse a facility which is designed solely to safeguard your assignments? You really should always use joystick letters unless you only ever have one joystick, and the same one never changing. Without the lettering any temporary disconnection of the USBs or even some Windows updates or repairs, will reassign all of your buttons and axes. Then you will have a hell of a job sorting the mess out! This is because you still have assignments in your Axes or Buttons sections to F, A, E and B. It will always report the problem because it cannot use those assignments when it doesn't know which controller they refer to. They are just wasting time and space. Pete

Okay. I didn't know that -- best, then, to assign in FS. There's really no problem with that provided you don't need different assignments for different aircraft -- you can only do that in FSUIPC. FSUIPC calibration operates on the final values for the controls, just before they go into FS's sim engine (SIM1). FS itself doesn't offer axis calibration -- that's done in Windows which uses the drivers from the installed controllers or the default Windows ones. You should certainly calibrate in Windows properly first. The FS calibration is to do with matching the controller inputs to the desired effect in FS, it is NOT hardware calibration. The only thing to ensure in FS is that the null zone slider is off (full left) and the sensitivity slider is full on (full right). Either of these will otherwise just limit the range of numbers the hardware axis provides to FSUIPC. Pete

No, I got back a few days ago and caught up with the support backlog. Best not to delete any assignments in FS but simply to disable controllers. If you don't do this you can sometimes find that FS has re-made its automatic assignments because it sometimes sees the controller as newly connected. The full name of that option is "direct to FSUIPC calibration". ALL of the controls which CAN be calibrated are listed. There's no point in sending ones which can't be calibrated or they'll just go no where! The normal FS control assignment option lists all of the controls including those not calibrated. Yes, of course. Calibration in FSUIPC works on FS controls not on "axes" as such. When you assign in FSUIPC or in FS then all you are doing is matching an external device axis to an FS control. FSUIPC intercepts controls for calibration whether assigned in FSUIPC (by any method, not just "direct") or in FS. In fact the calibration facilities existed in FSUIPC long before any assignment facilities were added. The "direct to calibration" method of assignment is just more efficient, because instead of the assignment to a control it sends the input value directly to the appropriate calibration function which then sends the control to FS. All other methods go indirectly -- to FS first then to FSUIPC for calibration then back to FS. Each of that involves extra messages in the Windows message queue, or via SimConnect. The only drawback to the direct method is that it can defeat the programming in some add-on aircraft, notably those by PMDG, where you generally need to assign to the normal FS controls (in FSUIPC or in FS, it doesn't matter). What? Assigning an axis to a control? Just in the normal way, either in FSUIPC (all of the FS controls are available in the dropdown, not just those provided by FS itself in its assignments), or in FS if you don't want to assign in FSUIPC. Calibration is independent of assignment, as I said. So why are you questioning the way of assigning? It's what happens to the control after assignment which is important. FS itself does not offer any assignable controls for throttle which include the reverse range. There are such controls but just not assignable in FS. FSUIPC provides the reverse zones in its calibration facilities. There are whole sections of the User Guide about this so I'm not reprinting it all here. Please refer to the calibration chapter. Suffice to say that you can assign throttles however you like then use the calibration options to get your reverse zones. Those occur in the 4 throttles tab, but you can map a single throttle to the 4 if you wish. It is all there, and all documented. Well it is all explained in the documentation I assure you. Have you looked in the User Guide? It really does sound like you have not. There are separate chapters on Axes and on Calibration. they are separate subjects for the reasons i state above, and as also explained in the User Guide. Pete

Well, turned out to be nearly June before I found time, and then, once I knuckled down to it, I had a working solution ready in a few days! ;-) However it needs a good testing before I let it out generally. If either or both of you (xcorez and aua668), or anyone else for that matter, are still interested in pursuing this and can do some testing, let me know and I'll provide the updated version of FSUIPC4. The facilities are based around having separate INI files per Profile, saved in a separate subfolder. The main INI file still contains the list of aircraft in each profile, and you can, if you really wish, have a mix -- some profiles in the main INI, others separate in their own file -- but a single Profile can't be split. I've even implemented an automatic conversion. I just now need to do a little write up, by way of documentation, and it'll be ready to try -- over the weekend for sure. So, let me know. Regards Pete

No. Lua plug-ins paced in the same folder as WideClient are run automatically -- there's no need to do anything in the WideClient.INI file, and the FSUIPC.INI file is only relevant to the FS PC, FSUIPC knows and cares nothing about Client plug-ins. If it doesn't appear to be working, check the WideClient folder for a Log file with the plug-in name. That will detail any errors found. Pete

I've no idea what you are talking about here. "cut and paste" is simply a way of copying text from one place to another. It is nothing of mine, but a standard way of editing. If you can type your name exactly as it should be, and your email, and your key, then do so, but evidently you've not been able to so far. The name, email and key MUST be exactly correct. That is all that is required. How you achieve that is up to you, but the sure way and the way generally recommended is to copy the text directly using the tools all Windsows editors provide. Well, see, you CAN do it!!! Now do it in the correct places in the Registration dialogue. Do NOT spell your name "l:arry mintz" as you did the first time, nor "Larry Mintz" as you did the second time! What do you mean by "key for 'Cmd'?" That makes no sense to me! I can't tutor you in how to use an editor. They are all different. Certainly there are standard ways in Windows -- I'm sure any Windows help will tell you. Or use the menus in an editor, they are in English in an English or American system! The directions have not changed for the 12 years that FSUIPC has had a registration system, and you've had one registered copy of FSUIPC3 and four of FSUIPC4, yet you still don't know how to Register? It is explained in both the Installation and Registration document and in the User Guide, and both emphasise, as I have done repeatedly here, that you must enter things CORRECTLY! If you enter them correctly it works, if not it doesn't. Pete

Well, that's all it would do -- Debug=Please simply enables more logging options, it doesn't change the FSUIPC behaviour. Without those entries the only other ways of auto-starting Lua plug-ins are: 1. Assigning a button or keypress to "Lua <name>" in the drop-downs, and having another Lua or initial button action sending the right button or keypress, or 2. Having a program running which starts the Lua via offsets provided to do this. Maybe one of those was previously in use? Glad it's sorted now. Pete

Never Ever publish your private key! I shall have to disable that one now! :sad: There is no purchased registration with the name "Larry Mintz", only "larry mintz". I told you everything muct be exact! If you can't enter it afresh correctly, use cut and paste, as I said! 5/24/2010 is a way of saying May 2010, one of the 4 I listed! Did you think there were 24 months in a year? 5 = May! Obviously you entered it into the dialogue. A slip of the finger on the keyboard perhaps. Nevertheless, that's what you told the computer! Do NOT use that key you just published for all the world's pirates to use. I will be disabling that one now. Use one of the other three. And please enter everything exactly, no variations! Pete

The registration information appears very strange. Is your SimMarket user name really "l;arry mintz". I've never seen a name with a ';' before! Either way, one of the three parts of the registration you have entered is most definitely wrong, and that is the reason, plain and simple, why the installation appears unregistered. Please go to your SimMarket account and retrieve the correct user name, email and key, and use cut-and-paste from that so you make no more mistakes. [LATER] I just checked, and in fact you've been very very good to me, having purchased FSUIPC4 no less than 4 (FOUR) times -- in October 06, May 07, April 10 and May 10! And every time you used the name "larry mintz" never "l;arry mintz"! BTW my name is "Dowson" rather than "Dawson". Pete

Ah, good. Then all you need now to be aware of is that offsets are hexadecimal (but you can convert them to decimal if you must), and FS likes strings for display only in "ASCIIZ", which is a series of ASCII 8-bit characters terminated by a zero byte. Pete

You won't be able to do this easily with the same buttons for both because they are different controls. One way to do that would be to have a Lua plug-in which switched between the two -- but it may not be possible for it to detect the state of the NAV/COM switch, so you'd need to program that too. You might be able to do it with conditional button actions, as described in the advanced user's guide for FSUIPC, but again you'd need to work out how to tell where the switch is set. Maybe there's a L:var which will tell you, but they can only be read in Lua in any case. Where do offsets come into it? You need to find the control name or number, as I said above. "Console Log" is an option in the Logging tab of FSUIPC. Please do look at the assorted options in FSUIPC some time. In the FS Modules folder. That's where everything to do with FSUIPC is found. The Installation document for FSUIPC, which you should have read before installing FSUIPC (it is in the same ZIP as the Installer) tells you what is installed and where. Maybe, if you've never looked in the FSUIPC Documents folder, you've never even read any of the documentation for FSUIPC? I don't know. Sorry. I've never used any of the GPS's for FS. No, sorry, I have no interest in X-Plane at all. Pete

Yes, Apart from the application interface, WideClient will perform its normal functions, and run Lua plug-ins, on a PC also running FS. You will need to change the "ClassInstance" parameter in the WideClient INI file to other than 0, or it won't run -- FS is the first "instance" (to do with Window class names being used). Such a configuration will not support most FSUIPC applications -- only those very few who also allow the ClassInstance change -- but you don't need FSUIPC applications for your needs. You may or may not need to specify the ServerName (or ServerIPaddr) and Protocol parameters as well, depending on your network configuration. You program your PC1 buttons to send "KeySend" numbers, and edit the [user] section of the WideClient.INI file to equate these KeySend numbers to the keystrokes. You need to be sure they get sent to the program you wish -- in this case FS. This is easier if you arrange for WideClient to load FS on PC2 (using a Run parameter), but you could also try using the FS Window Classname ("FS98MAIN" -- don't ask ;-) ). Pete

I don't know how different the 796 is from 695/696, but check this thread: http://forum.simflight.com/topic/69295-garmin-695696-to-fsx/?hl=garmin Pete

Well, if that's your complete INI file, then, apart from this spurious rubbish: [Profile.pmdg] 1= which you should most certainly delete, there's nothing really there to go wrong. The axis assignments seem odd though: 0=0X,256,D,1,0,0,0 =Aileron, assigned direct 1=0Z,256,D,4,0,0,0 =Generic throttle, assigned direct 2=0R,256,D,3,0,0,0 =Rudder, assigned direct 3=0S,256,D,22,0,0,0 =Spoilers/speed brake, assigned direct How do you get by with no elevator? Are you sure you haven't got axes also assigned in FS? If assigning axes in FSUIPC you should really disable the controller altogether in FS. Pete

Why did you reinstall FSX? Are you sure FSUIPC is even working? Best to show me the Install log and the FSUIPC4 log files from the Modules folder. Pete

Oh dear. No. It isn't hard, and the names do describe what they are! Both 3380 and 32FA are offsets (effectively addresses in a large data area), and they are hexadecimal so must be expressed as such. Sorry, but I have no idea how Java represents a hex number. Maybe 0x preceding or maybe $ like VB? A "count" is a number giving the size of the data to be written: in this case the number of BYTES. In FS each character in a string is a BYTE and strings are ended with a zero BYTE. A byte is 8 bits. Data is the data - i.e. the stuff you want to write. Normally this is a pointer to the data, but I've no idea how or if Java even works with pointers. You evidently have not referred to the offsets list at all to see what these should be written with? I did suggest you look these things up. And don't forget you need to connect to FSUIPC first. Do you know any Java at all? If not I suggest you learn some first. I'm afraid I cannot help with Java. Pete

Well, by default FSUIPC will, if GFDev.DLL is installed, load any GoFlight devices it sees, but not all HID devices -- else everyone's logs would show keyboards, mice and cameras as well as all joysticks as HID devices. Just run HidScanner to see what it would see. Certain types of HID devices can be logged with a debugging option. You have to set Debug=Please LogExtras=512 into the [General] section of the INI file. Just placing a Lua file in the Modules folder only lists it in the FSUIPC4.INI file, in the [LuaFiles] section. It won't run it. Only ipcInit.lua and ipcReady.lua are auto run unless you have appropriate entries in an [Auto] section, or assign a button or key to run them. Without some more information, like an explanation of your actual steps and some logs and INI files to show, I really can't help. There is absolutely no difference in FSUIPC or Lua between FSX and P3D nor with different PCs. Try the HID logging I just mentioned (add those lines BEFORE running FS/P3D), and also enable button/key logging so I can see the Lua file being started. Pete