Pete Dowson

You must either always run MakeRunways on the FS PC, or, if that isn't possible for any reason, first copy the real scenery CFG file to the FS folder. This is because MakeRunways has to use the Registry in order to locate the correct scenery file, and it can only read the Registry on the PC on which it runs. MakeRunways will also be very very slow running on any PC other than the one with FS because it has to read every single scenery file. Incidentally, the current supported version of MakeRunways is 4.65. I have a 4.661 ready to release but at present, due to a change in SimFlight servers, I cannot update any programs. Regards Pete

It is telling you that there is nothing called "Sound" (it has a 'nil' value -- 'nil' means nothing!) The sound library is called "sound" NOT "Sound", as documented. Lua is sensitive to case. Please be more careful. Pete

Of course. it's logging all you do. but only the parts leading to the problem are relevant. Er. I don't understand: Button 75 looks to be joystick 64, Button 18? Why do you call it 75? And offset 5428 is logged as being set to 75, how? What is doing that, and why BEFORE button 18 is shown pressed? Everything? 5428 goes to zero, and all the virtual buttons? 5428 became 75 again? How? You aren't showing me the logging of the button actions, so it is simply confusing showing things out of context. The 3340 offset now shows 6 buttons still pressed, including the one mentioned earlier! Are you really holding them pressed or doesn't your SIOC programmer clear the bits when you release the button? Still I have insugfficient information I'm afraid. Because it seems the bit showing it pressed remains set and your SIOC never clears it! You should be able to see if SIOC is clearing the bits correctly in 3340 etc when you release the button. Maybe it cannot do this, in which case you would probably need to try to set it to toggle the bit (ie invert it), and program both the "press" and "release" to do the same thing. . If you haven't "seen any option about that" you presumably are not using WideFS or have not looked at its documentation? Any program can be started from a KeySend assignment and similarly closed. Check "RunKey" and "CloseKey" parameters. Regards Pete

PMDG don't provide any details for access to their aircraft's systems -- except for the 737NGX, for which they provided an SDK which reveals both the special Control numbers for all ther switches etc, and a method of reading out (but not directly setting) all the values and switch positions. FSUIPC uses the information in the SDK to map the NGX data onto a set of offsets, which is what the document Paul referred to details. If you compare that mapping with the PMDG SDK "header" document which gives these details you will see that it is a direct copy, from their structure directly into FSUIPC offsets. Unfortunately PMDG never provided such information before, and most such previous data which can be gleaned has been through folks hacking. The FS9 versions of the 737 do use some FSUIPC offsets I think and folks have found some of those. On FSX, though, I think you have a problem with anything other than the 737NGX unless you pay PMDG to write a driver for you, or pay even more to give you secret information under an NDA. Regards Pete

There's not enough information here for me to help I'm afraid. I don't know SIOC and can't help that end, but I would need to see some logging to help with the FSUIPC end. Add 5428 (as type U16) and the three virtual button joystick offsets (as type U32 with hex option checked) to the Monitor on the right hand side of the FSUIPC logging tab and check "normal Log" below. Also enable Button Logging. Then when this happens check the log. For FSX you could also see what is happening in real time by putting FSX into windowed mode and displaying the FSUIPC console log next to it. You need to check if the offsets are changing and if so that the offset 5428 is reflecting your programming. If so, then you are going to need PM support because it will be at the CDU end of things. Regards Pete

As documented, in the FS Modules folder alongside FSUIPC, its INI file and any Macro files you use. Full details of the Lua system in FSUIPC (and WideClient) are provided with lots of examples in the Lua package installed in your FSUIPC Documents folder, which is also in the FS Modules folder. Pete

Why not simply unassign that keypress in FS, then? Keypresses in FS don't needto do anything you don't want them to. Everything they do is a result of assignment, either deliberate or default. VK means "Virtual Key" and the number is Windows' own code for the specific key. If you don't want to use Google to find these on-line, there are tables in the FSUIPC Advanced User's guide which list all the usual ones. If you don't want to unassign the keypress in FS you can assign it to something different, something innocuous, in FSUIPC, then it won't reach FS. But really it is easier to remove the original assignment. Regards Pete

I'm afraid there are no general "axis" type assignments available for the mouse, only the specific facilities of mouse look, mouse move and mouse trim already pre-programmed. Whilst a more generic assignment might be useful, the applications for such have, so far, been very very rarely requested. So much so yours is the first, really, in all these years. I would not want to add such a facility as a normal option. The most I would probably consider would be added Lua plug-in functions to allow mouse events such as left/right/up/down and wheel and button actions. Certainly with such you could program it as you wished. However, whilst this would cerainly be a possibility, it is not a trivial job and I can't consider it for a few weeks, with too many other things occupying me. However, i will add the idea to my list -- but for FSUIPC4 and Wideclient only. I'm not wanting to change FSUIPC3 (for FS9 and earlier) further. Regards Pete

Strange. Your ISP must be prohibiting you from doing searches, or something. I just Googled, just using the word "FSMetar" and it comes up with loads of references, viz: FSMetar - FlightSim.Com www.flightsim.com › ... › MSFS Multiplayer Adventures‎ Dec 15, 2008 - 4 posts - 2 authors I've been using FSMetar for some time now during on-line flying using FSHost, its a small freeware utility that updates weather METARS as you ... Installed FSMetar, but it has a problem - FlightSim.Com FSMetar and weather problems - FlightSim.Com - Home Something has happened to my FSMetar - FlightSim ... How do you get FSMetar to work - FlightSim.Com FSMETAR question - The FS2004 (FS9) Forum - The AVSIM Community ... forum.avsim.net/topic/274086-fsmetar-question/‎ Jan 27, 2010 – FSMETAR question - posted in The FS2004 (FS9) Forum: I know that a few here - thinking about Vololiberista mainly - use FsMETAR for ... FSMetar help? - MS FSX Forum - The AVSIM Community - Forums FSMetar problem - MS FSX Forum - The AVSIM Community Real World Weather - MS FSX Forum - The AVSIM Community ... FSMetar - The FS2004 (FS9) Forum - The AVSIM Community VATSIM.net • View topic - fsmetar and FSX and Windows 7 64-bit ... forums.vatsim.net › Members Helping Members › SquawkBox Help‎ Mar 9, 2011 - 19 posts - 3 authors Though, I am apparently the only person on Vatsim using SB4, FSmetar, FSX and Windows 7 64-bit, I will post the following, just in case there is ... CalClassic Forum - Considering installing FSMetar calclassic.proboards.com › General › CalClassic Discussion‎ Aug 21, 2010 - 3 posts - 2 authors I'm considering installing FSMetar in FS2004. I downloaded ... Which would you recommend using with FSMetar: IVAO, VATSIM, or NOAA? 2. Trouble with FSMetar? Question about FSMetar FSMetar 1.5.2 Update Released - Fly Away Simulation flyawaysimulation.com › News › Other flight sim related news‎ by Ian Stephens - in 309 Google+ circles Feb 4, 2004 – Now available from developer Ivan Alvarez is FSMetar, v1.5.2, a utility that allows flightsimmers to use live METAR weather downloaded from ..

Well, whilst that's certainly a good idea, you should really refer to the SDK installed for you when you updated the NGX. The PMDG_NGX_SDK.h file contain a list of all the controls it supported and I see these listed: // Gear panel #define EVT_GEAR_LEVER (THIRD_PARTY_EVENT_ID_MIN + 455) #define EVT_GEAR_LEVER_OFF (THIRD_PARTY_EVENT_ID_MIN + 4551) #define EVT_GEAR_LEVER_UNLOCK (THIRD_PARTY_EVENT_ID_MIN + 4552) You'll need to add the "... MIN" value to get the control number before assignment. I did add facilities into FSUIPC specifically to allow such custom controls to be easily assigned by number. I would assume the "EVT_GEAR_LEVER" control would take a parameter to tell tthe lever what to do. You'd need to experiment with that part -- it might be 1 and 0 or it might be more of a full range type of value, 0 and 4096 or 0 and 16383. I don't know, I've not got a working PMDG NGX installation. Regards Pete

Sounds suspiciously like bugs in 8.1 then. You did say it was a "Preview" (just a fancy name for a Beta, getting users to test it). I assume you are saying "yes" when it asks whether to send crash details to MS!? Pete

I doubt if it is specifically to do with Windows 8 or 8.1, just a result of a slightly different memory arrangement. It still means a problem either with overloaded memory or scenery conflicts which G3D.DLL cannot correctly resolve. FSUIPC cannot hook into every part of G3D.DLL which may or may not crash due to such memory corruption. There is only one very specific crash which it patches around. Every other one I've looked at is too complex, no way out of the routine which crashes. The simple one actually fixed is merely a TRUE or FALSE test and it was easy to patch in a FALSE exit when the conditions showed a crash would otherwise occur, resulting in a minor loss of perhaps one or a few scenery artefacts which go unnoriced. Regards Pete

I expect it is because PMDG do their own thing. You'll need to look in their SDK to find the correct controls to assign instead. Regards Pete

Sorry. I don't know of it. Have you tried Google? Pete

If there are less bits used to encode the state of something you can fit more states in. This is 2 bits instead of 3. Pete

Yes, that is how they look to FSUIPC. Of course BOTH is also "button 4 released" and IGN R is also "button 3 released". It would of course be far easier to do that if BOTH was buttons 3 and 4 released and the others both press actions instead. One way I can think of, which should work in both left and right cases, is this: Program Button 3 release to set offset x0892 to 1. That's the 'ground' (start) position on the jet left engine starter. It's an unsigned word so use "Offset Word Set". Program Button 3 press to set that offset back to 0 (the starter 'Off' position). Similarly, for equal effect Program Button 4 release to set offset x092A to 0. That's the 'off' position on the jet right engine starter. Also an unsigned word so use "Offset Word Set". Program Button 4 press to set that offset to 1 (the starter 'Ground' position). I think that should work okay, but I've not tried it here. Let me know. Regards Pete

Key presses are repeated by the keyboard system in Windows. No mechanism is needed is FSUIPC. In fact there is an option ("No repeats") which tells FSUIPC to actually discard the repeats if it recognises them, but by default it actions each one just as any other Windows program would do. Pete

Joystick button trapping involves calls to Direct Input. Virtual buttons are just bits in offsets. So, just use an event.offset to detect them and trigger your function. Each byte contains 8 virtual buttons, so use "logic.And" in the function to test the relevant bit. It's no harder, rea;;y/ Just an extra line (well, plus another 'end').. Pete

No. The profile is automatically selected according to the aircraft name. It doesn't need to "open" it once it is open. It only needs to change profiles if the aircraft changes. If you reload the same aircraft there's no need for it to change anything. You never need to go into any menu if the aircraft has previously been assigned to a Profile. Profiles are automatically selected based on the aircraft name -- once assigned of course. If you are loading different liveries or different aircraft which aren't yet assigned or covered by an abbreviated name in the profile's list then you'd get the generic assignments. Regards Pete

I've not even referred to any FSUIPC documentation!!! You referred me to a PDF which tells you how to set up iVap, and it seems to contain all you need. That's why I was asking why you were here? And surely if you have an iVap query you'd be best in an iVap forum in any case? Well I don't see it. what's wrong with the instructions you referred me to? Again, I think you'd be better off over in an iVap forum. I know nothing about it at all in any case. Sorry. Regards Pete

In an airliner like the 737, reverse isn't normally controlled by an "on/off" switch in any case, I notice the controls you are using are named as a "LEVER", and levers are really axes with values for the positions. As such I suspect it might need proper axis-type values, like 0 to 16383 or 0 to -4096 (the FSX range for reverse thrust). If so you can see why 0 or 1 won't do much. Otherwise, sorry, but I know very little about the PMDG 737NGX. I don't even have it. I think you would be best off asking in the PMDG forums -- the controls are part of the SDK supplied by PMDG after all. Regards Pete

I assume you are no longer using these assignments? 5=119,9,65966,0 6=119,9,65971,0 7=120,9,65976,0 8=120,9,65981,0 because the 119 is giving you 65971 and 120 is giving you 65966, consistently whether from the device or direct from the keyboard. Anyway: From the Hotas you appear to be pressing and holding pressed (for repeated action), BOTH shift+F8 and Shift+F9 at the same time. But only the second is repeating, as you can see from the KEYDOWN log entries for VK=120 with "Repeat=Y". This will be a function of the HOTAS driver. FSUIPC is only doing what it is told to do. Seem you cannot hold more than one button on the device at the same time if you want sensible results. Well it is only "alternating" because the keyboard messages are coming in on the queue one by one. There's no such thing as simultaneous messages in one processing thread. Each key press is repeating in its own right. That's what you'd want the device to do as well, but it doesn't. Well you'll need to apply reverse on one at a time or find some other way. Can't the device send actual button presses like nearly all other devices? Why is it sending keystrokes in any case? Pete

Please look at the logging tab. See the options to log IP reads and writes. That data IS logged in Hex. If you want to simply take a snapshot of the whole 65k range of offsets, enable the option to save it with flights (Miscellaneous tab, "Reload FSUIPC Data", any choice except 'Never') , and simply save a flight to create a binary dump. The file is named for the flight with "ipcbin" filetype. Otherwise check out FSInterrogate2, as supplied in the FSUIPC SDK. Another option, where you can select whatever you like to dump and when would be to use the Lua plug-in facilities and dump the data using your own Lua code. Sorry, you'll need to explain what you mean here. If by "ipc" you mean the same as the IPC in "FSUIPC", and your IPC data is going through FSUIPC, then you have all the tools you could possibly need. Pete

Well the only parts relevant to FSUIPC and WideFS are sections 9 and 11. Are they not clear for you? I don't know what you want from me! Seems mostly you need to follow the other instructions to get iVap working. Pete

There is no difference. Whether the initiation is by keypress or button, both end up sending the exact the same things to FS. There must be an error -- use FSUIPC's logging to see what is going on. Button and Key logging will show the initiation, and Event logging the results. As I said, use the logging to see what is going on. That's what it is for. Key presses? You are programming FS to send keypresses, not controls? It is not possibly to send simultaneous keypresses other than "shift keys" (Ctrl, Alt, Shift, Tab, Win, Menu) , denoted internally by flags, and a "normal key" (all the others) denoted by a key value. But all keypresses no matter how close, go into Windows normal message queuing system. They are not lost or discarded. However, I don't know where keypresses come into it since we were discussing controls. Axis assignment is completely separate and different to either of the other two subjects you've mentined here, so now this is even more thoroughly confused. Maybe you need to sort out the confusion, please. :-( Pete