Pete Dowson

I tried but got this response: Regards Pete

Why are you "starting as administrator"? There should be no reason to do that. If you want to Register FSUIPC you do that in the Installer -- just run the installer again. That's almost always a symptom of a video driver problem. When you select FSUIPC all that happens is Windows opens a dialogue box, a standard Windows feature, but some driver versions don't seem to handle that well when FS is in full screen mode. Try setting FS9 into Windowed mode first (ALT + ENTER), or else see about updating your video drivers. If you are using the default Win7 video drivers you will certainly have problems. You need to go to the nVidia or ATI sites (depending on your video card) and get updated versions. Or try www.guru3d.com -- they have a range of recent drivers for most cards. Regards Pete

Did you mean to say anything in those last two identical posts? They only contained a complete quote of my previous reply to you, nothing added! (I've deleted the duplicate now). Pete

There's no recognisable code in the ZIP -- all of my programs are supplied encrypted and compressed, and then codesigned to guarantee they cannot be infected without invalidating the signature. Your Virus checker is giving a false positive. You should report it to them so they can fix it. When you do manage to get to the EXE itself, right click on it, select Properties then signature, select the signature and check that it says it is good. That is the guarantee. Regards Pete

Are you talking about FSUIPC's options? If so, are you talking about FS9 or FSX, or one of the other sims? And what is the version number of FSUIPC? What are you "right" or "left" clicking? You said you were pressing ALT, not clicking anything! Some information might be useful if I am to help you. Regards Pete

What was "showing a list of AI aircraft"? WideServer doesn't show anything at all, it runs in the background. At most, if you are running FS in Windowed mode, it would amend the FS Title bar to show "with WideServer: waiting for clients" or ""with WideServer: n connected". But if something else also amends the title bar, then it may not be able to. However, that doesn't stop it working, it is cosmetic. TrafficX is in no way related to WideFS. How exactly are you detecting whether WideFS is "working" or not? Why not paste here the WideServer and WideClient log files, which would be the first place to look to determine if there's a problem? I can't do anything for you with no information. Pete

3.90 is way out of date and not supportable. the oldest supported version is 3.98. Test in the air, not on the ground. FS automatically deploys them on the ground. Pete

In the place where i provide all my updates, ancillary programs, extra goodies and so on -- the Download Links subforum. Pete

No, not a mistake. 4.60a is the current main user release. it's where the documentation is at, and comes with an installer to set things up. It's a lot of work making a full new user release, and I update FSUIPC frequently to answer folks wishes and problems. And I can't update Mr Schiratti's site so often even if it wasn't a lot of extra work -- the updates go through him. so all of the little interim changes are posted here, in the Forum -- or actually in the sub-forum I mentioned. The only reason I suggested you change to the same later version I'm using is so we're on the same page. I can help you better if I know we are doing the same things. If you have version 4.60a installed then you most certainly already have the full documentation installed -- in the FSUIPC Documents folder inside your FS Modules folder, exactly as pointed out in the Installation document. That installation document lists all the other things which were installed for you, AND tells you where to find them. Please do have a read! There's nothing of mine on any PM site. The main releases are put up on a "Dowson" page by Enrico Schiratti, but that is on a Schiratti.com site, not a PM one. In any case everything you need for 4.60a was installed for you already, except you forgot to read the installation instructions, and updates and other goodies are here, in the Forum, in the Download Links subforum, exactly as I pointed out in my last message and which you seem to have missed. :-( Ah, that control. That's one added by FSUIPC, in fact, and documented in the list of added controls in the Advanced User's guide (one of the documents you already have, as explained). Here is what it says: Efis ND scale set (parameter 0–7 for 738, 0–5 for A321) (default B738 and A321) I'm not sure what you mean there ... as you turn the knob you get different button numbers, so everything will change. The different parameters would appear only if there's an assignment for those other button numbers. Otherwise the field go blank and gray awaiting your assignment. The button numbers go from 20 for Range 10 up to 26 for range 40. The GoFlight EFIS is missing the 5 nm range position, so you would need to assign parameters 1 to 7 to buttons 20 to 26. You are getting very confused, for some reason. Both the Scale and the Mode switches represent several buttions each. You program each position separately. There's no "inc" and "dec" needed -- and if you did want to use INC or DEC yuou'd be using the "EFIS ND scale inc" and "EFIS ND scale dec" controls, NOT the "Set" controls!!! That's why they are named with INC and DEC in the name, rather than "SET". The mode switch is also several buttons, four in this case, 16 to 19. Assign each individually, with parameters 0, 1, 2 and 3, as documented. for the EFIS ND Mode Set control. Exactly what I said in my first message of course. You have all the documentation already. Please, please PLEASE do refer to the installation document which tells you this! Regards Pete

Your nice table seems to have been scrambled by the formatting in the post so I'm trying to show it better by enclosing it in the code brackets (the <> button) (Even then I can't get columns lined up. I don't know how you get columns in this Forum! :-( ). joy btn control rep control sent parameter DH 170 31 DH dec 0 30 inc 0 VOR L 9 VORAD 1 dec 257 8 # inc -514 11 VORAD 2 dec 257 10 # inc -514 Range 21 ND scale inc 257 22 inc 514 etc. However, I'm not sure I understand what you are doing. Where are you getting those controls from? And what's with those odd parameter values -- where do 257 and -514 come from? What's "Range-file"? Where are you getting this? In FSUIPC the Mode knob gives Joystick 170, Buttons 16, 17, 18 and 19, clockwise. Not sure what you mean by mode buttons, but if you mean the 7 along the bottom these give button numbers 6,5,4,3,2,1,0 left to right. If you are not seeing these then one of these things is wrong: 1. Your FSUIPC is out of date for this device. I'm using the current interim update, 4.633, or 2. Your GFDev.dll is out of date. I'm using 1.93.0.20 from May of this year, or 3. Your EFIS unit is faulty. Check the Download links subforum threads for interim updates to FSUIPC4 and for the GFDev.DLL. Regards Pete

If it only happens with that one particular aircraft then you need really to deal with Ariane support. They should know what their autopilot is doing. Otherwise, if it occurs with default aircraft too it sounds a combination of poor hardware and bad or duplicate assignments to me. FSUIPC never does anything unless asked to do so. Remove the FSUIPC INI file from the modules folder, so that it resorts to defaults (i.e. doing nothing) and try again. Incidentally, I cannot / will not support Saitek gear. Probably best if you don't try using their stuff with FSUIPC. Pete

Yes. No. All your settings are contained in the INI file and maybe some macros. All the FSUIPC installer does is update the program itself (FSUIPC4.DLL), and the documentation and example plug-ins. Everything else is untouched and will work with the updated version. Correct. You only buy FSUIPC3 or FSUIPC4, just the once. The purchase covers all version 3's or, in your case, all version 4's. Regards Pete

You do realise that you added your post to a nine-month old (and well dead) thread about some "FSUIPC Hardware Button", I suppose? If you want folks to spot your questions and answer helpfully i suggest you re-post in a new thread with a title which corresponds to your question. I cannot help directly because I do not know that laguage you are using, nor even whether it is VB or C#. However, I can see that you are reading and writing both the old FS98-compatible combined lights offset 0280 as well as the much more useful individual light switches at 0D0C. You should use one or the other -- 0D0C is normally better as it gives you individual control over each of the 10 possible lights in FS. Additionally, here: You should NOT perform two successive "process" calls. The second has nothing at all to do. All Reads and Writes are accumulated in your program's own memory (obtained when you did the FSUIPC_Open), and the Process call fires them off, all together, to FSUIPC. Also, there's no point in accumulating error results separately (dwResult and dwReault2) unless you are going to examine them. Regards Pete

Further to the other reply: You can change things in the WideClient.INI file to display some extra stuff in the title bar -- like the current data frame rate between the FS Server and Wideclient. but there is normally nothing in the window area -- just narrow the window to just show your title bar, or even change the options (in the INI) to hid Wideclient altogether. It is really only a background program, supporting the interface to FS on your Networked PC. The reason for the screen is that there are (or at least used to be) applications which actually docked themselves to the FS window. The Wideclient window just provides one to dock to if needed. You can have Wideclient load a bitmap into the window for display if you wished, but really the only useful information WideClient can give is Connected or not, and optionally the performance, or frame rate. Regards Pete

Strange, because what the aircraft coding sees then is EXACTLY the same as when the axes are assigned in FSX. Assignment in FSX sends the exact same controls to the same places. Sounds like those aircraft have something wrong with them. Maybe you're missing some updates? Which would be the same with normal everyday FS assignments. Follow the numbered steps in the section on calibration in the user guide. You set 4 values for all centred axes -- minimum, centre low, centre high and maximum. The 'dead' zone is the range between the two centre values, so you control exactly how wide it is during calibration. If you've never noticed this then you probably have never actually calibrated, but merely accepted the default values which are always wrong -- they may be close, but they are still not YOUR hardware's values. Similarly the minimum and maximum values should normally be set slightly away from the end stops on the lever, to make sure you can always reach the end values despite any small variations (temperature, humidity, dirt, voltage, etc, all affect joystick readings). If you follow the documented steps, these things will fall out. Regards Pete

if you assign axes in FSUIPC in the "direct to FSUIPC calibration" mode, then naturally they have to be calibrated or nothing will happen. If you assign them instead to the FS controls then calibration in FSUIPC is optional. It is possible that assigning direct to FSUIPC calibration is bypassing the way in which those particular aircraft handle the autopilot. It sounds like they intercept the FS controls, and of course you are bypassing those. That doesn't normally matter with the built-in FS autopilot as it cuts off the external influence itself. However, it does also indicate that your axis controls are continuing to send enough changes to override the aircraft A/P inputs. That sort of jitter is unwanted. If your axes are so unstable, the one way round is to use a larger dead centre zone when calibrating, and take care not to move them out of that zone when on autopilot. FSUIPC doesn't do anything with axes which aren't moving, and that would effectively silence their inputs. The other altenative, for those aircraft only, is to assign, in FSUIPC still, to the FS controls instead of direct to calibration. You should still be able to calibrate in the same way. It's just a little more inefficient, that's all. Without knowing what you did I can't say. The INI is updated the moment you press OK to confirm changes and exit the options. Maybe you made the calibrations, but then thought of something else, went to a different options tab, and ultimately pressed Cancel or escape, so not saving any changes made during that complete visit. Yes, as described above. I've no idea, I don't know everyone, and they've not all written to me one way or the other (thank goodness!) ;-) Regards Pete

FSInterrogate merely reads and writes offsets. The control numbers are DATA values, not offsets! They are the numerical equivalent of the named controls in the drop-down assignment lists. Please check the documents placed in your FS MOdules/FSUIPC Documents folder. In there you will find a list of FS control numbers, related to their names (the names as in the FSUIPC drop-downs). There's also a long list of controls added by FSUIPC. These are listed in the FSUIPC Advanced users document. Additionally you should most certainly NOT be using FSInterrogate as your reference. It is a tool for experimantring with offset values and debugging programs. The reference for Offset usage for FS9 in the FSUIPC Programmer's document, in the SDK In your subsequent message: The control number is the number listed in the documents I mentioned. Yes, all FS controls are 65536 or above. Most FSUIPC added controls are less than 65536, but there are some large hexadecimally-encoded ones for offset controls, macros and Lua calls. Pete

It doesn't read the CFG file, it gets the data from FS directly. I would guess FS gets it from the CFG file directly. No, not at present. I don't tend to waste offset space unless there's a need. Is there? Flight numbers aren't provided whilst the aircraft is "sleeping", awaiting the off. Regards Pete

Yes, it should be easy enough, providing I can find the space to avoid having another query protocol. I've put it on my list and will look at it early December. Yes, it is possible. Just a lot more work, that's all. And really it shouldn't be necessary. I would have thought that you'd want to filter out all those commands which might vary between aircraft in any case. If you still want SerialFP2 to handle some of those (or the device to handle SerialFP2's) you can still pass them on. All the filtering does is stop the straight-through copying back and forth. Yes. And if you filter it, you get to decide in your Lua program. Pete

OIC. I assume that's an instruction to the built-in ATC. Hmm. Sorry, but I don't know how FSUIPC could get hold of that choice. Regards Pete

Probably that FS control doesn't work in VC mode. I think, in FSX, everything changed over to the use of "Cameras". SimConnect seems to provide several ways of setting cameras, but no ways to read their settings. Very annoying. You didn't need to use FSInterrogate. It is documented in the FSUIPC4 Offsets Status PDF that they do not work. Things are different in VC and 2D cockpit modes, but the normal way to control view direction from an axis, as with a Hat, is by using the PAN VIEW control, with the number of degrees as parameter (or it might be the degrees x 100, I can't remember offhand). You can send any control and parameter via offset 3110. Regards Pete

No, sorry. And it is far from a trivial job to implement. Best to filter off all the commands you want to handle and then simply treat them differently according to the aircraft loaded. You can read all sorts of things about the aircraft currently loaded by reading the appropriate offsets. The aircraft title, for instance, is read by title = ipc.readSTR(0x3D00,256) Unfortunately, at present the name of the Profile in use, if you are using Profiles, isn't available through the Offsets. Shame you didn't ask me for this a few days ago -- it would have been easy enough to fit it before the updates I've just released. As it is now my time is rather committed for at least the next two weeks. But I'll put it on my list if you think you'd find it useful. Regards Pete

TrafficLook just gets the information available through FSUIPC. The TCAS tables in FSUIPC can contain different things according to the setting in its INI file, also controlled by a drop-down list on the Miscellaneous Tab in its options. This is fully described in the paragraph about "TCAS Id" in the FSUIPC User Guide (about page 22 I think). If it is reading the data from the TCAS tables it will get the same as TrafficLook. If it becomes confused you need to contact the author to find out why. There's not enough room in the tables for more than one short ID, and the default is what most folks and programmes want. There is an interface in FSUIPC for programmes to obtain any of the main identifying strings, in full, for any AI plane, but these have to be individually requested not read in bulk from a large table. I'm afraid much of the technical information in your message is pretty meaningless to me, especially the part concerning "using the letter R instead of F" ... so maybe you are trying to point out something else that I've missed? Regards Pete

Oh, b****r! It's this new Forum software. It is much more complicated putting the links in and each time I miss some crucial step or other out!! Sorry ... fixed now. Pete

Hmm. Angry? Sorry, but I'm not sure how you read anger into it. But certainly your first post that started all this was rather angry. Read the part ending in Seemed unjustly accusatory to me, especially illustrated by the devil. I think, in the circumstances, my reply was quite controlled. Maybe showing my impatience with your unfair implications. Anyway. enough. I'm locking this thread as it cannot go anywhere from here, and i do really need to get on and do some work. Regards Pete