Pete Dowson

Well, you have so far for certain. I think you are still talking about Mouse Macros when I strongly advised using the facilities PMDG supplied for everything you might want to do, instead. But: Well, that's a bit better. But rather than "apu-start" of something like that" I need you to say EXACTLY what it was assigned to. Tell you what, don't bother telling me anything. Just show me your settings -- the FSUIPC4.INI file (or in your case the FSUIPC file described as Configuration settings. I will see what you have assigned and to what. If it's addressing a macro file, show me that as well. It will have the name XXXX.mcro where XXXX is whatever you called it when you started making macros. For your attempt to use the PMDG controls, I do need you to tell me exactly what yuou did -- what <custom control> you assigned and how you derived that number. Also, use the Logging facilities to see if your assignments actually send what you thought. Enable Key/Button logging, and also Event logging, in the Logging tab. Meanwhile, did you bother to look through the User Contributions to see if there was anything useful there? If so, how is it you didn't find this one? which is rather old, I know -- and maybe you have a later version of the 737NGX (?), in which case these would need re-making, but there are certainly a whole list of Overhead mouse Macros there. Worth a try, and also an example of what to do. [Note: please read through that whole thread. Apparently PMDG issued a HOTFIX soon after those mactos were made, which rendered them useless. (This will be because the numbers in the macros are actually memory addresses, and they change when the DLL being accessed is recompiled -- another reason it is much better to use the PMDG controls instead).] I shouldn't really have to go and look for you when I did advise you to check. And you say you follow my advice? Hmm. Oh, I re-titled this thread to make it more meaningful, and possibly attract other users who are actually using the PMDG 737NGX (unlke me). Next time you post a question on a subject, it would be a good idea to make the title more related to what you actually want to do. Okay? Pete

When you said you couldn't write the Latitude/Longitude, did you mean that literally? Or did you mean you tried writing to them and they didn't change? How do you tell that they didn't change? If by watching where the aircraft is, try first putting the Sim into SLEW mode. (I really cannot remember if that is necessary or not. but i don't think so). Oh, try logging ipc writes (option in FSUIPC Logging tab), thenshow the Log file to see what it thinks is happening. Sorry, I don't have time to write programs for people. Why not show me what you've written and I'll see if I can spot the error? Or, if you are having difficulty with the example in the SDK, why not use Paul Henty's .Net DLL? Please see the subforum above about that. It aimes to make programming the FSUIPC interface easier. To demonstrate that, indeed, you can do exactly what you want, please see the Example LUA plugins ZIP file in your FSUIPC Documents folder. The pair "MasterClient.lua" and "SlaveServer.lua" are a demonstration of linking two PCs running FS by LAN, and having one mimic the other. The line in SlaveServer: -- now write it all in one structure write ipc.writeStruct(0x0560,"3DD", lat, lon, alt, "2SD", pitch, bank, "1UD", hdgT) writes Lat, Lon, Alt, Pitch, Bank and Heading all in one go, as you should be able to do. And that's a simple script! Pete

The mouse macro you created may well work, but as you NEVER told me exactly what you then did, despite me asking several times, I've given up. I Just do not understand why you are so secretive about it! And now it is the same with the PMDG supplied controls. So you obviously have no idea of what are doing and since you don't explain yourself at all, I've really no way of helping, have I? Good night. Pete

What was that for? Most take advice. Why not you? USE THE PMDG CONTROLS. That is what they are for! Mouse macros are not the best solution in every case. In fact their use in FSX and later is very limited, and they work infrequently due to the way add-on aircraft are made these days. They were great in FS2002 and FS2004, and will still work for the same old aircraft they worked in back then. They do work on a lot of the switches in the PMDG aircraft, but i can't tell you which. And they are not needed for an aircraft which is supplied with a full complement of assignable controls in any case. So why not read what i keep telling you, and take that route? Pete

Yes you can. Many programs do it quite successfully. I cannot debug your program from here. I've no idea what you are doing wrong. Pete

I never sent any such thing. For every device there will be two lines defining the LETTER, with name in onne and "GUID" in the other, and another pair telling FSUIPC what ID NUMBERthat device now has in the Registry. The latter is needed internally. Please do check the User Guide chapter on Joy Letters. Pete

Again, as everytime before, you are not explaining what you are doing. just saying "set the letter q to taxi light", what are you actually assigning to. How? I cannot help you if you persist in not actually saying exactly what you are doing! I'm out now till later tomorrow. Why don't you ask in the PMDG forums, or doing your own searches as I suggested, for instance in the User Contributions above? I have spent a lot of time trying to explain things to you and asking you to be more exact, all to no avail! Pete

On the contrary! It is clearly shown in your picture. The FSUIPC file with the hidden filetype (so you have NOT changed that Windows Explorer option!), and description in your language saying it is a text documnet. The other one with the missing type and clearly described as the configuration settings is the INI. Both exactly as I said to you. Why post a picture of a screen you evidently didn't actually look at? You haven't told me what you are doing afterwards! I did ask. And why are you ignoring my advice to use the PMDG controls? That ewould be a far easier and more reliable method. that's why PMDG provided them, so why ignore them? Pete

The file is in the sim's Modules folder, alongside FSUIPC4 itself!!! Pete

It is FSUIPC4.LOG file, not FSUIPC.LOG! And you probably still have Windows hiding file types from you if you didn't turn that off as advised in the FSUIPC documentation, right near the beginning. If so then you will see just "FSUIPC" with no type and something like "Text file" and "Configuration file" in the type column. The text file will be the Log and the config file the INI, with all your settings! BTW It would have been better to have asked this question in your thread, rather than start a new thread just for this. Pete

Yes, I understood that. Yes, but not a "viewpoint". You set the user aircraft to those values. you simply do not have the user aircraft cockpit displayed, so you only get scenery! As I said, Lockheed-Martin do provide methods for you to do exactly as you wish, and using that interface might be more efficient than using a middle-man like FSUIPC. But if you want to use FSUIPC, please refer to the Offsets Status document, part of both the SDK and the documentation installed for you in the FSUIPC documents subfolder in"Modules". Check offsets 0x0560 to 0x0580 inclusive. Write to those as frequently as necessary for smooth movement. Pete

That's not right. There are many PMDG 737NGX users also using FSUIPC. But PMDG use of lot of non-standard "tricks", including all of their own systems which don't respond to the normal Sim controls. That's why they provide a large set of "custom controls" which CAN be assigned in FSUIPC oce you've derived the control number. The axes on your joystick and throttle can also be programmed and calibrated in FSUIPC, but probably not the throttles, because for those PMDG read them differently, not through the Sim's set values. If using FSUIPC for joystick axes it is best to assign throttles to the "Axis throttle ..." controls and NOT calibrating, as this ensures that the NGX receives the values as it would from assignment in the Sim. You should press the "Tab" key before bothering to enter a name to see if the mouse macro will work. If it doesn't then there's no point in continuing for that switch. Please clarify this. What do you mean by "combine"? Are you using a hardware overhead switch? Or do you mean assigning the key "Q" to a mouse macro you've called .... what, "737:taxi". Tell me what you are actually doing please. FSUIPC4 is the same for FSX, FSX-SE and the 32-bit versions of P3D (up to 3). Only FSUIPC5 is different. That's 64-bit and is for P3D4 only. They won't install into the wrong sim. No: either the macro doesn't work for whatever switch you've tried, or you are making a mistake assigning. i can't tell unless you describe what you actually did. I really would recommend using the PMDG contorls rather than mouse Macros, as they are much more reliable and easier to program once you work out how to get the numbers. I can help with that. BTW I am in England (Stoke-on-Trent in fact, as it says on the left under my picture). and at 75 I am a little oder than you and definitely have to be in bed long before 01:30! 😉 Pete

Yes. This IS the Forum. The other bits above are what are called "subforums" and contain either reference material, updates and details of them, and special interest areas. Where you are now is where all requests for advice or assistance should first be posted, UNLESS it is a clear matter for a special interest section -- the only one of which at present is for programmers using or interested in using Paul Henty's .NET interface. Before P3D version 4, mouse macros only worked on gauges programmed using the original gauges SDK from Microsoft -- the one supplied with FS2002 or FS2004 (not sure which). Even then they didn't even work on many of microsoft's own default aircraft because they didn't follow their own rules1 Many, or even most, modern add-on aircraft these days use XML gauges. they tend to use Local Panel Variables (LVars) for control. Consequently, as things developed, special facilities were added to FSUIPC to allow these to be discovered, logged, read and written. So, maybe the aircraft you are trying to use the Mouse Macro facility on simply cannot support them? I don't see any information (yet -- but see later! 😉 ) in your post about which simulator version you are using, nor what aircraft, nor indeed what version of FSUIPC. Such information is obviously essential to one trying to provide help. The fact that the text is changing colour indicates two things: 1. You are not using P3D4, and 2. The gauge is somehow continuing to think it is being clicked. Are you holding the mouse button down? Just click it once and move the mouse away. Please check the FSUIPC4.LOG file, which you'll find in the simulator's Modules folder. You can post it here if you like. It probably contains information about what is happening. If not i can suggest ways of making it so. Ah! Now i see it: "fsxse"! And then, later ... Is that the aircraft used in the case of the problem you mention? You should know that, whilst many folks have successfully used Mouse Macros on PMDG aircraft, the Boeing range does have a full set of assignable "custom controls". These are listed in a file in the SDK folder of your PMDG aircraft, at the end of the one with filetype ".h" (sorry, I don't remember the name itself -- I don't use PMDG aircraft). Take a look and see if you can find what you need. There may also be lots of help in the subforum called "User Contributions", as there are lots of PMDG users. Yes. either to macros handling "LVars (not useful with PMDG aircraft though), or to macros created using the Mouse Macro facility -- which you'd tried already. Certainly don't let failure on one switch deter you from trying others, as I definitely know folks have used this method okay. AND more reliably using the controls supplied by PMDG themselves, as just mentioned. Note that to use their controls you need to compute a control number (just adding two values, in fact). Then you can assign in the FSUIPC drop-down assignments list to <custom control> and enter that number, and any parameter it may need. Again, i think quite a few of these might be found within User Contributions. It's a matter of searching. Try "737NGX" or "PMDG", or even just "NGX". Also, for Saitek controls there's a program called SPAD (or maybe SPAD.Next) which used to be freeware, but there may be a fee now. It was written specifically for Saitek Panels. worth checking out at least. LINDA is another program, or rather suite of programs, designed to help too, but I'm not sure how applicable it is to Saitek and PMDG. Worth looking into, though. Pete

You've posted this in different forms all over the place. And the answer is: None. Why a "viewpoint"? A viewpoint is detached from the aircraft! You can control those things for the aircraft -- the user aircraft! Surely that is what you want really? That's what other programs using DSX/P3D visuals do for an external simulator. But really I think you ought to investigate the provisions made by Lockheed-Martin for just such operations, through their software Development Kits (SDKs). That would be much more efficient. FSUIPC is a compatibilty layer for older programs -- why not move forward? Pete

What has this question got to t owith this thread? it's about FSUIPC stopping FSX working! I think you've dne this before! can you please STOP adding to other threads and, if you have your pwn, different, question, create a thread for it. Please? Pete

I've just lucked onto this. I saw you posted into other reference forums now -- FAQ (reference for main frequent questions) and User Contributions (useful hints and programs from users). Please USE THE SUPPORT FORUM, not any of the Sub forums if you have questions! I've deleted those wrong postings. I will delete this one tomorrow if i remember. i like to keep the place tidy. Reference forums full of specific support questions make them far less useful for reference. Pete

What does this have to do with FSUIPC Error 12? Why are you attaching such a question to someone else's thread on a completely unrelated subject? I think those offsets did operate to READ the viewpoint details successfully way back in FS9 and before (but never to set it -- that's why they were marked "read only"). Are you using such an old simulator? If not, as you'll see from the current documentation for FSX and P3D, there's no support now for that facility. Such a lack of support is indicated in the two right-hand columns in the offset list. Those offsets are being re-purposed. The offset status documentation will be amended appropriately for the next release. Pete

That sounds like your axis "going to sleep". Check that you don't have power management enabled on any of the USB devices listed in the Windows Device manager. The parameter is certainly LESS THAN, not less than or equal to, so the Rudder, only, is operational at less than 1 knot groundspeed -- i.e a speed surely only just perceptible, and certainly not a speed at which you could steer? HOWEVER, your question made me look at the code for this, and I see that the parameter it uses is wrongly calculated in any case! I'm re-checking this, as it must have surely have become apparent during testing, but it looks like it is using 1 meter/sec, not 1 knot, as the limit, which makes it nearly 2 knots (1.94). I'll fix that for the upcoming release 5.14 this weekend. If that is a problem, set the parameter to 0 and do without the new facility. But turning the tiller full left and right won't make any difference to this whatsoever, so that is certainly down to something else on your system. The < 1 knot check just takes only the rudder input to the sim's rudder control, ignoring the tiller altogether. Pete

64-bit Windows re-maps the registry entries for 32-bit programs to "Wow6432Node", so the actual path seen in the Registry Editor is: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0 This mapping is invisible to the programs accessing the registry, though they can be explicit if they want (I think! Never tried, as I like to keep it compatible with32-bit Windows versions). If the Installer doesn't find it there it will look in the Current User place. But I think the parameter is different there (InstallPath)? Pete

You can have 1, 2, 3, or 4 reversers, one for each engine. but you seem to have started with Engine 2 reverser. There's really no way one should affect the other. it sounds like you still have assignments in the Sim, instead of disabling controllers there as you should. Yes. there are instructions in the user guide. you simply have to give up part of the axis movement to reverse. Assign to Throttle 1 then calibrate the reverse zone as well as the main forward zone and the idel zone. Idle is simply the calibration point where the end result is zero! Zero throttle = idle. But note that the methods used by some of the controls use -16384 as idle. those controls don't have reverse thrust. Best to calibrate. If you use a reverse zone on an axis, the idel zone is the part denoted by the two centre values. Without a reverse zone, idle is denoted by any values less than the minimum point you calibrate. I think you need to read the User Guide, and follow the numbered steps to good calibration in the Calibration section. BTW you seem to be effectively asking me you give you a complete basic tutorial here. Sorry, that won't happen. That's what documentation is for. I can only deal with specific support questions here. Have you tried doing things in the sim first? Are you really sure you want to use FSUIPC? Unless you know how to use the simulator's facilities it seems a little bit of a stretch using a bag of tools like FSUIPC to do all sorts of other things. Pete

Why reverser2, ie for the second engine? How many reversers are you going to assign? And why are you setting things on the right-hand side? You don't want ANYTHING set on that side! You only need simple assignment, then calibration. also assigning controls to specific parts of the axis movement is not needed! Keep it simple -- don't mess around trying to make it complicated! You will certainly need to calibrate when assigning "direct to FSUIPC ...". It won't work otherwise. And be sure to have the throttles set to Idle before trying to engage reverse. Oh, and the two separate controllers are unrelated and seen separately. There's no such thing as "incompatibility" or otherwise. Such things don't apply to separate devices being seen and read separately. Pete

Sorry, to be clear: do you mean FSUIPC sees your physical switches? Why would it not? The input side is not related to the model of aircraft you use. Unfortunately, you are still not giving enough information! I can't help without more details. Do you assign to GEAR UP and GEAR DOWN respectively? Or to GEAR TOGGLE? For elevator trim, do you assign to ELEV TRIM UP and ELEV TRIM DOWN? Do please give the exact names, Those are all standard Sim controls. Are you saying that such standard controls, as assigned in the Sim to 'G' (Gear Toggle) and the Num Pad 7 (Elev trim down) and Num Pad 1 (Elev trim up), do not even work on thhe add-on aircraft you are using? Have you even tested them using those default sim assignments on the keyboard? Assigning in FSUIPC to those standard functions is exactly the same as assigning in the Sim to the same functions. So if your aircraft model is not responding to those, then you need to find out what it does respond to. Have you checked its documentation? Is there a support forum? Test your FSUIPC assignments with a default aircraft too, to ensure you are not making a simple mistake. Pete

The mouse macro facility wasn't added until version 5.13, in May this year!!! I do not support old versions. Please install the current version, 5.132. And Version 5.14 will be released this weekend. Pete

As I asked: which version of FSUIPC5? The macro facility was added relatively recently. It probably also needs P3D4.2 minimum, but I'm not sure. It relies on specific P3D facilities. Pete

Which version of FSUIPC5, and which version of P3D4? Pete