Pete Dowson

Write to me at petedowson@btconnect.com Pete

You would need to purchase it, but not "again". The FSX version is FSUIPC4 which is a complete re-write owing to the substantial changes in FSX. So it is a new product, not just an update. Pete

What does "mapped and working" mean? You assigned it in FSUIPC, direct or via FS controls? OR do you mean you assigned it in FS and just calibrated in FSUIPC? And this was "mapped" how? Pete

FSUIPC doesn't even touch the keyboard input unless you program them in FSUIPC. You must have something else going on there. I'm using TrackIR with FSUIPC 4.30 and it works fine. I was merely a bit peeved that something in the way TrackIR reads its keys stops me programming them on a Button instead, as my keyboard is usually rather out of reach, and the "re-centre" key seems to be needed quite frequently when it appears to lose its orientation. Not nice on approach! ;-) Regards Pete

Yes, just change the upper limit (the 8 in x00080001). In one byte you can cycler through as many as 256 values (8 bits gives a 0-255 capacity, or 00 to FF in hexadecimal). If you need more than 256 you'd need to use the Word increment, giving you up to 65535 (hex FFFF). No, all you've changed there is using 2 bytes (16-bits) instead of one. Since the value "8" easily fits in one byte of 8 bits (capacity 256 values), the original command is fine. I'm afraid I don't recall whether the limit provided is INCLUDED or EXCLUDED. I don't use this stuff and the code dates back many years. Have you tried it? That's what I would do -- it is quicker than trying to work out what old code does! If it cycles back to 0 after 7, just make the limit 9 instead of 8. Pete

Yes. You should ALWAYS use the Installer to update FSUIPC4. The interim increments here are only meant to amend the installation created by the Installer. If you downloaded it and unzipped it why not simply run the installer? What are you afraid of? That said I don't think the list of FSX controls has changed much. Maybe it is time I generated a new one (it isn't automatic). Let me know if you find something is missing. Pete

Again, that depends how you use it. Each addressable byte contains 8 bits, by definition, but the same addresses (offsets) can be accessed as Words (2-byte or 16-bits), Dwords (4-byte or 32 bits) or even 64-bit values where supported by the programming language used. Then there's 32-bit floating point and 64-bit double floating point numbers. Any of these can be addresses at any offset value. You choose the method suited to the data being contained and manipulated. Not by single bit, no, and not with 9 bits. There are two errors here. 1. The command is "byte cyclic increment", and a Byte contains only 8 bits, so the 9th bit doesn't exist for it and cannot be reached. To deal with a word (16 bits) you'd need the x52....... command for "Word cyclic increment". Please see my previous explanations of what bytes and words are. 2. "Increment" here implies ADDITION. so each button press will add the increment you specified - i.e. 1 - until reaching your limit, i.e. 8, then cycle back to 0. So you will get values 0, 1, 2, 3, 4, 5, 6, 7, 8, 0, 1, 2 .... etc. These are NOT "bits". For separate bit settings you'd need 1, 2, 4, 8, 16, 32, .... 512 (for 9 separate bits). This is not "incrementing" but "doubling" or "multiplying by 2". You need to understand a bit more about numbers. If you don't understand binary, consider decimals. your need, if it were in decimal, would be for numbers 1, 10, 100, 1000, 10000,100000000. To get from one to the next you have to multiply by 10, right? Not add 1! It's the same with binary numbers except the multiplier is 2. What you appear to want to do cannot be done with any control offered by FSUIPC at present I'm afraid. I'm looking at adding LUA programming facilities in the next version, though, and then you could do almost anything (but you'd need to lean LUA first). However, looking at your original message, you don't appear to want "bits" at all, but "numbers", numbers 0 through to 8. Why are you talking about and worrying about bits in the first place? Regards Pete

Whatever you like. Each of the bytes from 66C0 to 66FF contain 8 bits, which is what "byte" means -- an addressable set of 8 bits. The units named "U8", "U16", "U32", for 8, 16 and 32 bits, and so on, only determine how you USE them, not what they are! If you address 66C0 as a U16 you are referring to the two bytes at 66C0 and 66C1. With a U32 you are referring to the 4 bytes at 66C0 through to and including 66C3. In other words, you can refer to the data in groups of 8 bits or 16 or 32. it doesn't matter. You use whatever is more suitable to your purpose. Pete

Evidently. I used "spoiler" as my search word and soon found offset 3412. Pete

Oh. right! Good! Thanks for letting me know! Pete

Really? I thought i was being pretty helpful back there when I explained exactly the quickest and easiest way of making several "aircraft specific" settings in the INI file, something I've not done before because I've tended to assume folks would know all that and do it anyway. Then you reject all my help and say you want to do it a way completely unrelated to all the work I've done in this area. That's fine, but why on Earth come and ask the question in the first place? Don't you see how irritating that can be? And you accuse me of being irritating in trying to help more than I usually do? :roll: I did not tell you, I merely expressed amazement that you implied you hadn't a clue! Or was "a little bit complicated" meant to mean "oh, I know all that but I don't want to bother"? Please, go ahead and do it your own way. You don't need anything from me at all! I don't know why you asked if you take such a fixed attitude. My "normal" answer would be basically to RTFM. I went a lot further than that, trying to help, and I'm sorry if it came over so irritating for you. I don't intend to irritate, I try hard to help. I have no way of judging how clever or stupid people are other than by what they say here. Pete

You've never edited a text file? There's really nothing to it. You've not done "cut and paste" editing at all, in any documents, emails, etc? That's all that is involved. It's much easier than flying a plane! Why? Are the multiple INI file facilities provided also too complicated? :-( You can do what you like, sorry. I thought you were asking for help in doing something with the facilities I provide. Obviously you can swap your own INI files. That isn't really anything to do with FSUIPC's facilities. you work out your own system, then. Regards Pete

Apology accepted. Thank you. I think to raise a problem ticket you just go to SimMarket, open your account, select the "Customer Service" menu, then "Write a trouble ticket". You enter your order number/ID and category of problem, and write your message. Note that, in order for me to write the above instructions I've had to open another Window in Firefox and follow it through. I've not done it before, but it seems pretty easy. If there's a technical problem, rather than a mistake in your order, I will try to help. But first you need to tell me what program it is you are trying to Register. I have 4 different ones which accept different keys -- FSUIPC3 (for FS9 and before), FSUIPC4 (for FSX), WideFS6 (for FS9 and before) and WideFS7 (for FSX). I cannot guess. You also need to state Version numbers of your FS, and of my programs, so I know whether you need to update. Regards Pete

Yes, I have -- and I described how to do this specifically in the FSUIPC documentation, as it is one of the most common needs. Did you try looking in there? Check the section in the User Guide on calibration. Following the 12-step guide to calibrating there's a few notes on special needs. Read the one starting • If you have a single throttle control and you’d like to have an idle and reverse zone on this Regards Pete

Okay, if you prefer. Before doing anything, before loading FS, edit the current INI file. set "ShortAircraftNameOK=Substring" (change its current value), then make a complete copy of your [Axes], [JpystickCalibration] and [buttons] sections, changing the names in the copies to [Axes.], [JoystickCalibration.] and [buttons. is part of the title from your currently configured aircraft which will distinguish it from your new one. Then when you load your new aircraft and change things, it won't affect your current one. You can again make those copies, with the new name identifying the settings. There is one exception, however -- the default [buttons] section is always active as well as the aircraft-specific buttons. For obvious reasons this doesn't apply to Axes and calibrations, but usually there are a lot of common buttons for every aircraft so it is more flexible to have all the common ones in [buttons]. So, if you don't have aircraft-specific buttons, don't copy and rename that section. On the other hand, if you do, it would then be best to delete the general ones from the renamed section and delete the aircraft-specific ones from the original. By the way, you can do all this sort of stuff whilst FS is running, then simply use the "reload" buttons in the relevant tabs -- once each for Axes, Joysticks and Buttons. Regards Pete

And how does that happen? You evidently have not got them set correctly! But that means restarting FS each time you want to change aircraft. It isn't something I would like, but it is entirely up to you. I would have thought that your first question was "why have I got the settings for the two aircraft mixed up?", and sort that out instead. Regards Pete

Sorry, that is all gibbering nonsense. I don't publish any phone numbers and I answer all sensible email, but I don't openly publish my email address either. You seem very confused, even demented, to say the least. Stop, think, write separate sentences. Read what you write before pressing send. If it makes no sense to you it makes no sense to anyone else. And if you come here making stupid wild accusations you will get nowhere, I will simply delete your messages without comment. If you have a problem with some purchase at SimMarket then they do have a proper procedure, which works, and it does not involve Emails or Phones. You need to raise something called a "Problem Ticket". Take a look. I'm afraid I have nothing to do with the SimMarket side of things, I can only help you with technical problems, but for that you do need to actually explain them. Okay? Pete

Sorry, I can't do anything about that. All I can do is scan the POV and send the values on to FS. I have no idea why it doesn't accept them in replay mode. Have you tried using the far superior FSRecorder software (it is freeware -- or rather donation-ware)? Check it out on http://www.fs-recorder.net/ Regards Pete

I repeat, the entry for the result you want must start with K for a Keypress, C for a Control, or M for a Macro. You have none of these at all!!! What is the "M" at the beginning for? For a Compound condition that should be "C"! Why ignore all the examples? No where will you see "M" being allowed to define a compound conditional! Please do refer to the definition of the format. This is directly from the Documentation: See the letters denoting the action needed now? The format of a Macro reference is M: as I already said. You have things like "1:26" with no letter to say what it is. Pete

The only difference between using a Keypress, Control or Macro in any [buttons] parameter line is the letter at the start: K, C or M. So, any examples of conditionals to do what you want can use macros simply by substituting one form for another. Keypresses are K, Controls are C, Macros are M: (remembering Macro files have numbers assigned in the FSUIPC INI file [MacroFiles] section). Regards Pete

It sounds like part of their proposed Electronic Flight Bag, which sounded interesting. I was suppose to see that (courtesy of an arrangement with PFC and Jeppesen), but it never materialised. Regards Pete

Okay. Meanwhile, I found and fixed the problem. The difference between the Windows action in the two orders is as follows: A downA repeats till T downT repeats till A upT still repeats .... T up. This works. A downA repeats till T downT repeats till T upNo repeats, so no more KEYDOWNs .... A up. Doesn't work. I found code in FSUIPC which ignores any KEYUP without a preceding KEYDOWN. In the first case the Repeats stop that code operating. In fact if you release the keys in the working order fast enough not to incur repeats between them, it fails there too. Version 3.825 fixes this, and the "no repeats" un-setting problem too. It is now available in the Other Downloads announcement. The same things affect FSUIPC4 too and will be fixed in 4.305, later today (I have other changes in that to be tested first). Thanks & Regards Pete

Ah, right. So you are connecting real buttons and switches to the PC as if they are keyboard items rather than the more usual USb/joystick switch adapters or Hagstrom key encoders? I'm not sure. I thought perhaps the keyboard matrix you were using was based on AZERTY so A and T would be in the same matrix row, but I checked using Microsoft Spyxx with my Q and T keys (the same positions as A and T on an Azerty) and all KEYDOWN and KEYUP messages were seen. Only one of the two pressed actually repeats -- the last one pressed. But both KEYUPs seem to occur in either order, at least here with this Keyboard and this version of Windows. So, I will do some tests in FSUIPC and get back to you. Quite honestly I don't know how FSUIPC could operate KEYUPs in one order and not the other if they are both arriving. I keeps no lists of keys pressed or anything. I'll get back to you. Meanwhile, please test your Keys (A T down, A T up) with the attached DIVIEW program. It will show the exact keyboard actions and you can see if you are getting the needed KEYUP messages. Let me know please. Regards Pete DIView.zip

Interesting. I don't know "fliteDeck" (never actually heard of it), but i use Jeppesen FliteMap to both plan my flights and as a moving map from GPSout --the plan actually has to be loaded into FS after being generated in FliteMap via my FStarRC utility. So, the plan is already in the moving map program. [Actually I don't use FS's plan loader in any case, as I use Radar Contact for ATC and Project Magenta's system for the FMS]. So, if you have what is a superset of FliteMap, why aren't you using its far superior (compared to FS's) planning capabilities? Not really, because from inside FS I don't know any way of reading the flight plan, other than by loading the PLN file itself (assuming it has been saved, and not modified since loading). Its pathname is available from SimConnect for FSX. Not sure about FS9 or earlier. This really sounds like the perfect application for a small utility run before GPSout is connected, i.e before running FS. It isn't something I'd want to get involved in unless I had a lot less to do at present. Regards Pete

If you can find out why it is happening, or better, how to reproduce it, let me know and I'll see what is wrong. As I say, I've not seen it crop up before. It would be instructive to learn what line was missing, if any. Regards Pete