Pete Dowson

Did you follow the instructions and run FS9 "as Administrator" ? You need to do this else the program cannot update the Registry. Right click on FS9 and select "run as administrator". Additionally, you need to register when logged on as the user who is going to use FS9. Pete

There's no 4.58 as yet. The latest "Beta" (actually more like an Interim Version than a Beta -- I don't put Betas on general release) is 4.511. Robust? Against what, exactly? The install is good. If you don't update, you don't get support. it is as simple as that. I don't know why you mention "fsinsider". What is that? No relation to FSUIPC, for sure. That's totally irrelevant. You install 4.50 first, by running the Installer. Then you copy 4.511 (not 4.58, as it doesn't exist -- if you have something which says it is 4.58 be very very afraid!) into the FSX modules folder. That's all there is to it. There's no funny magic, no hidden strings. Why are you so paranoid? What on Earth has my software ever done to you to make you like this? And you don't need to register again if you already registered! I take that as an insult and ask you to retract it! I've never done this for the money, as you would know if you knew anything at all! The money enables me to spend full time on it, I would never have got much past the FS2002 version otherwise. I've been making free software for FS since FS4 days and only ever earned any real money at it till after FS2004, when my other sources of income dried up. Please just read the documentation. The user guide tells you everything. Stop being unjustifiably paranoid about software that never did you any harm. And don't come here telling me I owe you anything in that manner. It isn't nice! Pete

Found it. Seems there was a similar problem with Lua files numbered greater than 16, which I fixed a while back. I hadn't spotted the exact same error in the Macro code too! ;-( Please try version 3.911, now available in the Updates announcement above. The problem also applied to FSUIPC4, fixed now in version 4.516. Thanks! Pete

Sorry, I don't understand any of that. Landing gear isn't involved in NAV/GPS selection. And is this question not one more for the makers of the aircraft than for me? How does it actually relate to FSUIPC or WideFS? Regards Pete

Thanks for the files. the log shows that the macro is created okay as: Macro: mouse action="PMDG_MD11.GAU":X180540*X8b90 However, you are assigning the Button to a different macro, one for a different aircraft: Macro: mouse action="ACS.Logic-MD11.GAU":X1620*X8b90 ... not executed because required Module/Gauge is not loaded The problem seems to be related to the numbering of the Macro files. The log shows this on initial load: 65177 AIRCRAFT\PMDG_MD11\MD-11.air 66410 Aircraft="PMDG MD-11 Lufthansa" 66410 [buttons] now aircraft-specific: 66410 10=P4,0,K90,8 66410 18=P6,8,CM19:1,0 which refers, for button 6,8, to macro file number 19. Later your new, test, assignment, was: 268805 Button changed: bRef=0, Joy=5, Btn=17, Released 268805 [buttons.PMDG MD-11 Lufthansa] 21=U5,17,CM20:1,0 268805 Macro: mouse action="ACS.Logic-MD11.GAU":X1620*X8b90 268805 not executed because required Module/Gauge is not loaded i.e. to macro file 20, but it still got the wrong macro file. I don't think this is anything whatsoever to do with aircraft panel switches, but references to files. Please look in your FSUIPC INI file, at the [MacroFiles] sections. Are all of the macro files which don't work numbered greater than 16? If so, then I think this is a bug I thought i'd fixed long ago. I'll check here ... Regards Pete

In what ways might it be incompatible? Sorry, I don't really understand the question. If you mean "can you program all of the cockpit buttons and switches via FSUIPC", I really have no idea I'm afraid. You'd need to try first. You can do that before you build anything -- try via keypresses, for instance. Pete

Right. Let's see. The thing I don't understand is why there are any switches which you can create a macro for which responds to the "TAB" test, but then that macro does not work after creation. That's the only thing I need to know about -- because no one else has reported this and I've been able to resolve many cases even where the TAB test fails but using the numeric appendage to the macro lines. So. Please do this: before running FS, edit the FSUIPC.INI file as follows: Add these lines to the [General] section: Debug=Please LogExtras=4 LogButtonsKeys=Yes (or change those lines if already there) Then run FS, load the aircraft with a panel which behaves as you said. Choose just one such switch, and operate it via the Mouse, first, just so I get a "normal" log. Then go through the mouse macro creation process, to a fresh macro file (say "test"), using TAB just the once to test -- see that TAB works on that switch. Complete the macro creation process, assign a button or keypress to the "Test.xxxx", whatever macro you created, then operate it with that button or key -- just the once, please. See/confirm that it now doesn't work. Close FS. ZIP up the "test.mcro" file and the FSUIPC.LOG file and send it to me at petedowson@btconnect.com. The log should help. It should contain the details of the mouse actions initially and during button creation, and the attempted simulations by TAB and by button/key (which should really be identical). Hopefully this will show me what is happening. If not, it will suggest where I need more logging and I'll have to send you a special version of FSUIPC. Thanks, Pete

It sounds like WideFS is working okay then, else running programs on the Client would have zero affect on the FS PC. For WideFS? No folders need sharing, and the only file you need to place on the Client is WideClient.EXE, the actual client program. It will generate its own INI file, with default parameers, which you can change (as per the documentation) if needed, which isn't often. How much more of a guide do you need for one program -- just put it where you like and run it! It is that simple! Did you not even bother to read the first little bit of the wideFS documentation? Well, you actually seem to need help with Project Magenta, so you are in the wrong place entirely! fine, but direct your venom to the right place, please, not here, where it is completely unjustified and unwarranted! Pete

ErActive Sky Advanced can be used over a LAN but you have to install SimConnect on that PC and prepare some files -- and you must have FSX Deluxe or Gold, not the basic version. Traffic X is an add-on AI traffic package, surely, and runs INSIDE FSX, so cannot run across a LAN. Or are you referring to something completely different? For FSX ASA uses SimConnect, not WideFS. And Traffic X is not an FSUIPC client application, so doesn't use WideFS either. For ASA you need to refer to the documentation supplied. If you don't understand it please visit the Suport forum for ASA. I'm afraid I cannot undertake to support other folks programs. For Traffic X, I think you must be confused. What are you trying to run on a networked PC? AI traffic only ever runs INSIDE FS! Regards Pete

If there is no FSUIPC.LOG file then you have never ever run FSUIPC, so all these questions are moot. I suspect you are seeing the log file but have Explorer set to hide the filenames from you. Go into its folder options and uncheck the option to hide known file types from you! Anything like what? There is NOTHING in my question which requires ANY knowledge of computers whatsoever. You have a computer. YOU added Flight Simulator -- so FS is ONE of the things you added to it! You added FSUIPC, so that's another. Maybe you added Scenery, or Aircraft? Surely a list of WHAT you added is not such a tall task? If you really don't remember what you've done at all I can only suggest you start again from scratch: even to the extent of reformatting your disks, reinstalling Windows and FS and so on, making a careful note (yes, a list) of everything you added to your computer! At some time, if not now, you will really need to know what you have as against what you don't have! Pete

The FSUIPC4 log, and the Installer log, tells you. In the FSUIPC SDK of course. (Where else are you getting your offset data from?). What "ready to fly" flag? If you mean the bytes at FSUIPC offset 3364, they work fine. Many programs use them (including several of my own). Not here. Anyway, how come you have FSInterrogate if you don't have the SDK? Or maybe you have a very old copy of the SDK before the FSX information was added? for the first few months after FSX release, the FSX SDK additions were available separately, in the Updates and Goodies Announcement here in the Forum. There are still usually later versions of things here. Pete

As well as what Ian says, with a registered install of FSUIPC you could effectively assign the relevant key presses (+ and - was it?) to the lever using the right-hand side of the FSUIPC axis assignment Tab. You can have up to 10 zones in each direction, crossing which could produce a control (two, actually, one on entry, one on exit) -- and there are FSUIPC added controls which produce keystrokes. If 20 keystrokes in each direction is sufficient then that could work okay. Regards Pete

The numeric equivalents of the named controls are really what FS understands internally. For an external program or a Lua program wishing to send a control -- either via FSUIPC offsets or, in the case of Lua plug-ins, via the appropriate Lua library call -- these values are essential. They are also used in the FSUIPC INI file to record assignments you make, so you'd need to know them when editing the INI file or macros directly, as folks do for more ambitious button programming. Regards Pete

Yes, you need to not only simulate the cause but also the subsequent symptoms of such problems. Check out some of the Instructor Station programs for what can be done, and, for Project Magenta users, the TSR programs by Thomas Richter. I think the Lua plug-ins feature in FSUIPC has great potential for creating failures and consequences too, as they run inside the FS process and can use fairly tight loops to override quite a few Simulation things. Regards Pete

For buttons which execute an FS control, you can find out the name and number of that control by using FSUIPC's logging facilities. you don't need a paid-for version of FSUIPC to use its logging. On the logging Tab in FSUIPC options, just put a check against the Event logging option, on the left-hand side. not the Axis events, though, or the log will be filled with events from your joystick! Operate the buttons and check the FSUIPC Log file for the details -- you'll find it in the Modules folder. Note that many instrument panel buttons and switches are interpreted directly in the Panel or gauge code and do not emit any FS control at all. Regards Pete

There are no files you need to remove at all in the first place! And you don't actually have to purchase FSUIPC to run the PMDG 747. There should be 4 FSUIPC files in your Modules folder, if you've ever run it. You really ought to disable that stupid Windows Explorer folder option to hide the file types from you -- it makes using any computer much more difficult. i wish MS had never changed the default for that. In Explorer look in folder options. After enabling Explorer to actually read the real filenames you should find these files: FSUIPC.DLL FSUIPC.INI FSUIPC.LOG FSUIPC.KEY Assuming these are present, then at least FSUIPC has been run (at least once). Show me the FSUIPC.LOG file -- it is a simple text file and you can paste its contents into a message here. You also need to tell me what version of Windows you are using. If this is Vista and you have allowed FS to install into its default place (in Program Files) then there are other steps you may need to take to find and/or replace files, because Vista protects all Program Files folders from pryiong eyes and all those "malicious" users! :-( Regards Pete

What's the log for if it's working fine? The log is no use to me in any case as you didn't enable the event logging as I asked. But don't bother if it is working fine. Regards Pete

That works too, but it is more restrictive -- you can only abbreviate the name (i.e. chop parts off the end), not take part of the name from the middle. Yes -- that will work the same for both the "Yes" and "Substring" options, because it is an abbreviation. With "Substring" you could have "Kingair B200" or just "B200". Note that the list can be quite long with no real worries. It is easy enough to simply assign your named Profile (whatever it is named) when you first load an aircraft, without worrying about the names themselves, or editing the INI file. Regards Pete

The problem arises because of the combination of commands needed. You can compare what happens with that FSUIPC offset and the Gauge by using the event logging in FSUIPC's logging options and checking the log. I think it would work if you togglebits with parameter 0xC0. You only need one button teally, as you've found out! I'm not really sure why you are going to all the trouble of using offsets and parameters for these functions in any case. Why not use the FS controls provided for the purpose? After all, all FSUIPC does is convert your bit changes into those controls, so it is actually less efficient using the offset for writing. You want to read it to set the indicators, of course. In case you can't find the relevant controls they are: COM1_TRANSMIT_SELECT COM2_TRANSMIT_SELECT COM_RECEIVE_ALL_TOGGLE NAV1_SOUND_TOGGLE NAV2_SOUND_TOGGLE DME_SOUND_TOGGLE ADF_SOUND_TOGGLE MARKER_SOUND_TOGGLE I'm not sure now -- enable event logging, and (on the Right hand side) monitor 3122 as type U8, check the 2normal log" option below, run your tests on those buttons, and show me the log. Remind me which version of FSUIPC it is too, please. Pete

Does it connect if you remove the FSUIPC Key file from the modules folder? If so, then the key is being checked as invalid. Check your PC's system date. If that is wrong, set to some date BEFORE the key purchase date, then it will look invalid. If it still fails to connect, then most likely you are somehow running with different privilege levels between FS and the program trying to access FSUIPC. This doesn't seem likely with an add-in aircraft, but maybe it has an outside part? Vista actively prevents programs of different privilege levels from sharing data. If you run FS "as administrator" you have to do the same with add-ons, and vice versa. Finally, in none of this helps, please run FS, get the problem, close FS, find the FSUIPC.LOG file (you may need to run Explorer "as administrator" to get to the true Modules folder, if you've let FS9 install into Program Files, which is protected). Show me the log. Regards Pete

Which profiles list? The one in the INI file? If you mean the drop-down selection instead, you should have NO aircraft names in there. For the INI file list, just set "ShortAircraftNameOk=substring" (instead of "No") in the [General] section of the INI file, and use any reasonably unique part of the aircraft name, one which matches all of them somewhere. eg. "Boeing", or ~"MD11" or "747"etc. Pete

No, the bundle deal offered by SimMarket is for both purchased together as a bundle. No. No, none of that. WideFS is only to link FSUIPC-interfacing programs. WidevieW is what you want I think. Just close the scenery. Pete

Yes. See the SDK. Pete

In the LOG file, the file we were talking about. If you take bits completely out of context you are bound to confuse yourself! Please read the whole message not part of it! I don't understand. Which English words aren't you actually clear on? There's no mumbo-jumbo there. "List" means "make a list" -- i.e. itemise, like a shopping list (you ever been shopping?). "Add-ons" are thing (programs, aircraft, scenery, etc) you've ADDED ON to FS, ones you are running at the time you get the problem. After all, if your controls are okay and your settings are okay it must be something else you've added to the system which is doing it! Pete

Did you chack the FSX Offsets Status document first, to see if thery were valid? Okay. As you will see from the document, tor those this is the first feedback I've received since FSX was releases on any of them. So thanks. I should mark them down as non-working then? Note that 0B68, 0B73, 3BE1 and 3BE2 are already marked as non-writable in the document. The others are said to be writable according to SimConnect documentation. Maybe they only work in the later updates. Are you running FSX SP1 or SP2? There's no provision in FS for those, in that case. Most programs simulating failures of such things do so by actually implementing the failures in the operation of them. Oil and fuel leaks can probably be most easily implemented by reducing the quantity or pressure, control failures by intercepting the controls in FSUIPC, and so on. Regards Pete