Pete Dowson

As I said, and as clearly documented, the REV option is a checkbox evidently totally obscurely labelled "REV" in the joystick calibrations . Why would you expect it in the Assignments at all?? You could assign to FS control and reverse it there or calibrate it in FSUIPC and reverse it there. You don't seem to read what I write! :-( Please please please do refer to the supplied documentation. It would save a lot of time for both of us. Pete

Good. So will FSInterrogate then. It communicates even more reliably. Pete

Check the FSUIPC4.LOG file in the FSX Modules folder -- that sounds like a SimConnect problem. Was there an Add-Ons menu with FSUIPC listed? No. User registration is totally irrelevant, unless either the signature on the DLL is incorrect or an invalid (pirate) Key is being used. It sounds more like a SimConnect installation problem. Regards Pete

Sorry, I don't recall any problem arising with PMDGoptions, and I've certainly never made any change for it. I don't have a web site as such in any case, so I assume you mean this Forum? A search reveals nothing of what you say I'm afraid. Regards Pete

Well, if it works it's a bit of a sledgehammer, but why not try that offset change I mentioned? For a toggle action you might even try it with Offset Byte Togglebits with a parameter of 1, assuming it is normally 1 (for reset on crash) that would toggle it to 0 or back to 1. As I said, I don't actually know if it works. It needs trying. And there's no equivalent for FSX I'm afraid. Regards Pete

None of the VIEW specific directional controls use a parameter. They are the same controls FS assigns by default to the Shift+arrow/home/end/pgup/pgdn keys on the keyboard. They won't do any more than that, and the parameter will be discarded by FS. Without knowing how you had it assigned, I would say that this is because you were using Pan controls before, not the basic view contrtols -- try the VIEW controls on the keyboard for yourself. They are intended to work that way. I don't call that "jumpy but "responsive"! Anyway, if you reprogrammed your hat to work differently, you'd expect it to work differently, wouldn't you? If with your previous method you had it selecting all 8 views on the one hat, how did the same hat manage to select the height as well? It sounds as if you had a 10-way hat, which I've never heard of. Are you sure it wasn't just programmed to pan left and right on the left and right buttons and up or down on the forward and rear buttons? That would be the standard PAN axis control -- a completely idea from having different actions on each of the directions, which is what FSUIPC button programming offers. If you want panning instead you would need to assign the panning controls. There are examples in the FSUIPC4 user guide derived from one posted in this Forum -- see viewtopic.php?f=54&t=66828&p=414889 . That method should work okay in FS2004 too (you didn't say which you were using). This won't give you height control as well. For both direct and height you'd need to look at the other pan controls, and look at losing some precise direction selection in favour of maneuverability. The possibilities are almost endless, but you'd need to work out what you really wanted and see how the FS controls actually work. Alternatively if you just want what FS offers, why not leave it with FS? Regards Pete

Sorry, I appear to have pressed the "Edit" button and edited your last message instead of the "quote" button. So yours is lost now. However, the relevant parts are quoted here. Apologies for any confusion. Good grief! No wonder it doesn't work. Every single assignment is in a separate section -- only one of those will ever be readable!!! I think the problem is caused by the [ ] characters in the Aircraft name. The Windows INI file routines aren't handling that correctly -- it is probably reading "[Axes.[DXT3] Level D Simulations B767-300ER - First Choice Airways]" as just [Axes.[DXT3] -- which of course won't match the aircraft name. Why on Earth Windows writes each parameter into its own section, all with the same name, I don't know -- but it probably does the same sort of thing, reading and not finding a match, so it assumes it is new. Odd that in six or so years of this facility this has never come up before, and really annoying that it does come up just after I've made major releases for FSX and FS9 and am about to go on holiday! Grrr! Isn't that just typical? I'm afraid this isn't something I can fix now for three weeks or so. So you need to work around it for now. There are two ways of doing this: 1. Edit the Aircraft.CFG file to change the name of the aircraft -- it's the Title=... line you'd need to edit. Delete the [ ] characters. Then delete the entire section you showed me from the FSUIPC INI file, and start again. Alternatively, and maybe more productively: 2. Edit the INI file. Change the "ShortAircraftNameOk" setting (in the [General] section) to ShortAircraftNameOk=Substring. Then delete all of the stuff you showed me, and add this in its place: [Axes.B767] 0=1X,256,D,7,0,0,0 1=1Y,256,D,8,0,0,0 2=1R,256,D,3,0,0,0 3=2X,256,D,22,0,0,0 4=2Y,256,D,9,0,0,0 5=2Z,256,D,10,0,0,0 6=2R,256,D,23,0,0,0 [JoystickCalibration.B767] ExclThrottleSet=No SepRevsJetsOnly=No ApplyHeloTrim=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Rudder=-15620,377,377,15819/8 LeftBrake=-16383,16383/8 RightBrake=-16383,16383/8 Throttle1=-15602,-10791,-9361,15488/8 Throttle2=-16252,-11702,-10791,14976/8 Spoilers=-14720,15732/24 Flaps=-15732,13952/24 [Buttons] 1=P2,1,C65752,0 2=P2,11,C66080,0 3=P2,10,C66079,0 4=P2,2,K122,11 5=P2,3,K122,11 6=P2,5,K123,11 7=P2,4,K123,11 8=P2,9,K84,11 9=P2,8,K84,11 10=P0,0,K65,11 11=R0,2,C65607,0 12=R0,3,C65615,0 [Buttons.B767] 0=P2,3,K122,11 1=P2,5,K123,11 2=P2,2,K122,11 3=P2,4,K123,11 [Axes] 0=0X,256,F,65695,0,0,0 1=0Y,256,F,65694,0,0,0 2=1X,256,D,7,0,0,0 3=1Y,256,D,8,0,0,0 4=1R,256,D,3,0,0,0 5=2X,256,D,22,0,0,0 6=2Y,256,D,9,0,0,0 7=2Z,256,D,10,0,0,0 8=2V,256,D,23,0,0,0 Now this will make these assignments work for any aircraft in your collection with "B767" anywhere in its name. That may be more useful for you in the long term. Or if you want it specific to the LevelD, you could use "Level D Simulations B767" as the name in the lines above. Just don't use anything with [ ] in it. I'll fix FSUIPC to strip out such characters automatically in future, but as I say I can't do this for a few weeks. Interesting that it has never come up before. Regards Pete

Are you asking about FS in general, or when using assignments in FSUIPC? If you assign in FS there's a reverse checkbox there. It is in the column curiously marked "Reverse". If you calibrate in FSUIPC there's a reverse checkbox there, not really so obscurely marked "Rev". ;-) For FSUIPC reversal make sure you check the reverse option before calibrating, as the calibration points will not be symmetric. And if you assign in FS and calibrate in FSUIPC, don't reverse in both places or they will cancel each other out! Regards Pete

No, sorry. I've no way to get to such an option whilst FS is running. It's a menu setting only. There is an "action on crash" value (offset 0830) which can be 0 to ignore crashes, 1 to reset on crashes, 2 to abort the flight and show a graph. Maybe you can write to that. You'd need Offset Byte Set for offset x830 and parameter 0 for ignore, etc. I don't know if it works that way though -- it may be read-only. I've never had to turn collision detection off. If you cannot avoid other aircraft then maybe you need to reduce your taxi speed somewhat? It seems pointless having the realism of other traffic on the airport if you are allowed to drive straight through them! ;-) Regards Pete

Sorry, I've really no idea what you are talking about, nor what you are seeing. Let me pose some questions to try to understand: 1. What views can you "cycle" through in "spot view"? Isn't that just one view? How do you "cycle" through one view? Maybe you need to be explicit about what FS controls you are trying to use? 2. What does "jumpy" between each vbiew man? The scenery goes up and down? I can't imagine it. 3. What are these "parameters" you mention? Parameters for what controls? Very few controls take parameters. 4. What has "height" of a view got to do with it? How are you trying set height? So why are you changing things? What FS assignments are you talking about? Regards Pete

That DLL is specific to PMDG has has nothing whatsoever to do with FSUIPC. FS will load it if it is in the Modules folder, else it won't. There is nothing FSUIPC can do about it one way or the other, which explains why all your experiments with different versions of FSUIPC turned out to be so futile. What "same old problem?" Kindly explain yourself!! Pete

Of course. Just not at the same time. If you look at the WideFS components, there is only one "WideClient" program for the Client PC -- this is deliberate as the Client PC shouldn't care what version of FS is running on the Server. FS9 has a separate WideServer.DLL to install, but in FSX it is included in the FSUIPC4.DLL code. Both are separately registered, however, and FSUIPC handles that. You can't run WideFS to the laptop when it is running FS9, and you can't have a single client talking to both FSX and FS9 at the same time. But otherwise there's no problem. The client end is the same no matter what version of FS you use on the Server. Regards Pete

Sorry, please explain further. I need a blow-by-blow description. You program all your buttons THEN check the aircraft-specific box? Or vice versa? Have you a mixture of aircraft-specific buttons and other buttons? Maybe you should show me the [button ...] sections from your FSUIPC.INI file. Just cut the sections and paste them here. And is this name showing at the top of the FSUIPC options window when you are programming these aircraft-specific buttons? If not, you are not programming them for that aircraft. It sounds to me as if you are not following the simple rules -- select aircraft-specific WITH the specific aircraft loaded (and its name showing on the title bar of the options window), THEN program the specific buttons. These override any general programming for those buttons when that aircraft is loaded. It works fine here, 100%, so I am sure it is some misunderstanding you have about how this works. But at present I cannot fathom out what that is because you are not telling me what you are doing. Regards Pete

Just because the FS EXE process has started doesn't mean it has yet loaded FSUIPC and the latter has made itself ready to deal with your messages. It sounds as if this "error 12" (?) is the SendMessageTimeout to the FS window (class "FS98MAIN") simply timing out. Most programs using the IPC interface simply loop and retry until they get a successful connection. If you cannot deal with errors in that way then you can simply test for the FS window (class "FS98MAIN") or the FSUIPC window (class "UIPCMAIN"). The latter being present certainly means FSUIPC is up and running. The former is FS's own Window class and would be a better choice than the FS EXE process -- your program would work on a WideFS client too if you checked for FS98MAIN. Use the Windows API FindWindowEx with just the class name. Pete

If you mean User Keys, only from Intercraft (in Japanese), or direct from Project Magenta as part of a complete PM package. Regards Pete

It's optional. It simply allows FSUIPC to read FSX weather, modify it (to apply your choices, for example, like generate random gusts or turbulence), and write it back. It also enables FSUIPC to cut down the multiple spurious wind and temperature layers which FSX tends to generate over time. It has an effect no matter where the weather comes from, as it is modifying FSX's weather, as opposed to weather sent through FSUIPC -- the filters work on the latter in any case, no matter. That's why it has the word "own" in it -- strengthening the fact that it is the weather IN FSX that is being changed. It was supposed to be obvious! Evidentyle it isn't. :-( The same option was present in FSUIPC3 and was there for years without any misunderstanding as far as I'm aware. And it has been there in FSUIPC4 since it started too. Pete

OkayI've made a note and will add something like that when I get back from holiday, in about three weeks. Regards Pete

Well, all your settings go into the FSUIPC.INI file and are reloaded when FS is reloaded. Do you get the same if you ask it to "reload settings" in the relevant Option Tab? Axes, buttons and calibrations all have their own sections, and are all saved independently. Buttons and Keys have global assignments (for all aircraft) as well as aircraft-specific ones. All this has been working fine for many years, so I can only assume you are misunderstanding something fundamental. Maybe the "same aircraft" is actually a different one, a different paint-job or something, so not matching the stuff you saved? Or possibly you marked the FSUIPC.INI file as "read only", so preventing anything being changed there at all? There's no file "FSUIPC.CFG" used by FSUIPC. If you mean FSUIPC.INI, and you deleted it, you have lost all of your settings in any case. Please note that 3.75 is not supported as of today. The current release is 3.80. Get it from http://www.schiratti.com/dowson After upgrading, if you still cannot figure out what you are doing wrong, please go into specific examples, because there's no way I can really help with a general "I can't get it to work" complaint. Regards Pete

I didn't know that! Ah. You want a hot key. Why not the same hot key for both? Or is the space bar a fixed thing? I can see I'll have to try this stuff. ;-) Regards Pete

Ah, I don't know this "mouse look mode". Can you tell me more? It certainly is possible for me to make this change. Unfortunately, I've just finished finalising and releasing the biggest set of releases for a while -- 4.26 for FSX and 3.80 for everything else, along with fully updated documentation and SDK. A couple of days ago it would probably have been dead easy to "slip in". I am still developing FSUIPC4, but hopefully less so on FSUIPC3, so if I only do this change for FSX, is that okay? You failed to mention which it was you were using! I'm afraid it won't happen for at least three weeks either way though, as I am way from next Tuesday until the 24th and I am desperately trying to tidy up a load of stuff before I go! Regards Pete

Ahyou read the Advanced User's guide before the main User's guide? Oooh. That's brave! ;-) I hadn't realised it still said just "Settings" there. The FSUIPC options dialogue (which appears when you select FSUIPC from the Add-Ons menu) is actually entitled "FSUIPC Options and Settings", so really it should say that I suppose -- I'll change it for the next edition (shame, just missed this one). However, reading it it does go on to say "... obtained by selecting the FS Add-Ons menu, then FSUIPC (ALT, D, then F)", so it is a little difficult to construe that as going to a Settings window first, I would think. Anyway, mostly I'd hope that by the time folks got to referring to the Advanced guide they'd be pretty handy with the options setting in FSUIPC already. Well. if you insist, but I prefer not to really, in case it helps others. I'm sure no one will think less of you! ;-). Someone once set the only foolish question is the one that isn't asked (or something like that). Regards Pete

The Add-Ons menu, which is created by SimConnect for any add-on which requests it, is in the main FSX menu, not the "Settings" menu. In fact there is no "settings" menu, only a dialogue. The main FS menu is where it always has been, at the top of the screen when you press "ALT" in flight modes. The install log shows that it is installed correctly, and the FSUIPC4.log shows it is running correctly, as far as you've allowed it. Since it was only running for 48 seconds I doubt whether you ever even got to normal flight mode, where you first get a chance to see the FS menu bar. I think you must be getting confused with FS's start-up dialogue? There's no menu bar till you are ready to fly, never has been. Menu bars, as in all windows programs, are the little strips along the tops of Windows. The left-most entry in FS's Menu is labelled "flights", for instance. There's none labelled "settings" -- that's an item in the Options menu entry. And I've no idea where you got the idea FSX put its "Add-Ons" menu into a "Settings" dialogue. Please, please, please do read just a little of the User Guide, and always try looking at it when you run into trouble. If you had you would see that it says, right in the first line after the heading Okay I've installed, and optionally registered. Now what?, that it clearly says, and emphasises: :cry: Pete

I don't know why it is giving you an error. A not-present COM frequency should simply read zero, so giving you a result like "100.00". The flags at offsets 3364 and 3365 are used for this sort of thing -- only when both of these bytes are zero is FS actually fully "ready to fly". But if you are getting an error on the COM2 offset, I don't see why you won't get an error on every offset. What is the error in the first place and why is it occurring? Are you sure you aren't trying to connect before FS, and therefore FSUIPC, is even finished loading and running? If you get FSUIPC to load your program for you you will know you can connect to it as soon as your program is ready. If you are connecting via WideFS from a Client PC, use the "RunReady" method of loading your program, so that you know FS is "ready to fly" when your program is started. Regards Pete

You need Project Magenta offsets, documented by Project Magenta on the Project Magenta website. Look for the Documentation item on their Home page. Pete

Sorry, I have no idea about installing add-on aircraft. It sounds like it is one intended for FS2004 not FSX. Either way, best to ask at Simviation.com I would have thought. Sorry, what says what where? How is this related to the above? Obviously 4.26 is later than any previous version, as I only published it today! Pete