Pete Dowson

Why not just show me here? It's only a simplw text file. If you keep the FS session short it will be a short log in any case! Haven't you looked at it yourself? It might be obvious what the problem is. Pete

If the standard command doesn't work, then the A310 code is continuously sending commands to disable it. I can't do anything about that. Why not simply also assign your yoke aileron axis to the rudder in FSUIPC's Axis Assignments, and calibrate it in FSUIPC joystick calibrations. Then it will act as aileron via FS and rudder via FSUIPC. You'd need to experiment with the calibration to get the coordination correct (for flying), but it will be fine for steering on the ground. Regards, Pete

Sorry, that was an error in an earlier version. Please just download the current supported version (3.65) from http://www.schiratti.com/dowson and you'll be okay. Pete

Sorry, I am not involved in that process. Please see the sticky thread near the top somehow obscurely entitled "READ THIS IF YOU LOSE YOUR FSUIPC or WIDEFS keys" Regards, Pete

Not negative. It's just that you are asking for something I don't know how to provide without spending many many hours trying to look for something I don't really understand, in parts of FS I've never been before. And, on top of this, it is after three years of FS2004 when I really have to look forward to FSX instead. I've been "tidying up" all my modules over a period, ready, and hope to issue to another FSUIPC and WideFS update by the end of this week, hopefully the last before FSX. No, I'm not upset at all. I don't know how you read that. I am only saying if you or someone you know can tell me how to do it, I'll do it, but otherwise I'm afraid is isn't going to happen. Possibly someone has, but if so they've presumably kept it to themselves. There are a lot of commercial add-ons which do some very clever things (Aerosoft being one, RealityXP another), but they keep the things they've discovered secret for obvious commercial reasons. Sorry. If any reader here knows about these things and is willing to divulge details, please come forward. Regards, Pete

So you have the correct Token Variable name for it? If it is as you say then it should be easy enough for someone to write a Gauge to control it. By "area" I mean "graphics" as opposed to, say, aircraft position or engine data or weather and so on. See, you know much more about that stuff than I do. If you can locate the information you need to read (and write?) I'll be glad to map it to an FSUIPC offset for you, but it will need someone who understands that subject (I used area before and you misunderstood me) to go find it and know how to use it. This is how many things have been built in FSUIPC. I have spent many thousands of hours hacking and tracing through disassembled parts of FS to find things, but always things I would be able to recognise if I saw them. Other folks have contributed for other areas, and so the edifice has been built, over time. If it is so easy, please go ahead and let me know. Thanks! Regards, Pete

It means your FSUIPC is not user registered and you are trying to run one or more programs, gauges or modules which are trying to use FSUIPC but which have no access permission. If you look in the FSUIPC LOG file, which you will find in the FS Modules folder, it will contain more details of the problem. If you want any further help identifying the culprit(s) just show me that. Regards, Pete

No, not with FSUIPC which is intricately tied into FS. Please apply to Project Magenta support, who I think will have the answer (but it may not come cheaply!). You'd need to do some programming in any case. Regards, Pete

Well, what was it? We are all curious! ;-) Pete

Nice, but have you any idea at all howe to get at such things "programmatically"? I haven't. I've no idea about ANY of the graphics stuff in FS. You might want to suggest this to the guys at places like Aerosoft. It is more their area of expertise I think. Regards Pete

And is the same thing appearing to happen when outside of FSUIPC, i.e. when you are flying, if you hold an aileron position? If sounds very much like something else is giving you aileron control input. Whilst the joystick values are changing, they are "winning2, but unchanged values are discarded. if something else is providing an input, that would then take precedence. You don't lose anything is you make a copy of FS9.CFG first -- you can always put it back. At least that should prove whether its a funny assignment someplace. But other than that you should check all the assignments in FS, just to see if you have something else doing it. Also, if you have been using FSUIPC's axis assignments page, check the FSUIPC.INI files [Axes] sections. Regards, Pete

Okay. Let me know when you get FSX, then I'll give you something to do, don't worry! ;-) Pete

Check the sensitivities and null zone in FS. The sensitivity slider should be at or near max (full right) and the null zone slider \ero, full left. Really, unless you've gone into FSUIPC options and tried calibrating it there it isn't anything to do with any of my software nor Squawkbox. I'm not sure why you are asking here? Regards, Pete

I don't know VB at all. sorry. Is the correct hexadecimal format "&0AEC" or "$0AEC", or even "&H0AEC"? Seems different in different reports. You need to check the VB reference manuals I think. Pete

I may be able to do so, but as of this moment I have no information. What FSUIPC read and write errors? Have you any FSUIPC logging to show me? I cannot help without information. Regards, Pete

AhI know about that problem. Apparently, in VB, for some reason best known to Microsoft only I think, if you write: $F084 it assumes you meant $FFFFF084 in the whole 32 bits. I'm told it even does this if you say $0000F084, which is quite bizarre. Now FSUIPC reserves some of those bits for special uses (the Advanced Weather Interface for one), and the best it can come up with is the 8FF084 you saw. I believe that you can stop VB from doing this silly thing by adding another $ at the end, thus: $F084$ I would have thought that it would be documented someplace in the VB guides/manuals. Regards, Pete

Sorry, this is so out of context I do not know what you are talking about. Please don't start new threads assuming I can pick things up from elsewhere -- just add new comments onto whatever thread you posted your original problems in. Thank you. If you are having problems with FSXpand why not ask their support? I really know nothing whatsoever about the product and would be very unlikely to be able to help in any case. Sorry. Regards, Pete

In what way does FS2004 "not work", and why do you think it is anything to do with FSUIPC? Pete

It really does sound like it cannot be 3.65. Please show me the log, or check the version again yourself using any one of the many methods. The previous one was certainly not 3.65 then. Always check versions -- in Poperties, on screen, or in the Log. Regards, Pete

Sorry, I cannot help with VB. But have you tried to help yourself at all? First of all, look in the FSUIPC options screen and find the Tab "Logging". On the left-hand side check "IPC Read" logging. Then run your program and look in the FSUIPC.LOG to see exactly what you are actually asking for. That's exactly what these facilities are provided for, to help you develop and debug your program. Another tool which you should find some place in your VB compiler installation is a debugger, Try that too. It is a great help when developing programs as you can see exactly what is happening. Pete

Did you not even look at the User Guide? It isn't hard, only one step, as the documentation says: Installation Copy the FSUIPC.DLL file into your flight simulator Modules folder. There. Not too difficult, surely? ;-) There's no difference whether it's a "Beta" or not, for ten years now the installation method has been exactly the same as that! The current version is 3.65 by the way. Pete

It won't be anything to do with Squawkbox. Sounds like you need to calibrate your throttle. Pete

Sorry, the code is no good to me. It doesn't tell me what you are writing to FSUIPC. Please use the FSUIPC Logging (see the options, Logging page). Log IPC Writes, then repeat your test, and look at the log. Show me it if you like. You should easily be able to see what you end up writing to 32FA. Yu are probably writing a value that tells FSUIPC to let the message to stay there till replaced (eg zero), or maybe for a very long time (eg thousands of seconds). Pete

Use a toggle switch so you can see? I'm not sure where to put such an indicator at present. It can't go in 310A, that's a programmable control which times out in any case. I'll add it to my list of requests for now and see what I can do before the next release. Regards, Pete

I just received the Log and the Key file, thanks. Now, see this clearly shown in the log? ********* FSUIPC, Version 3.50 by Pete Dowson ********* The Key is good, but it was purchased in 2006 and you are still using a very old FSUIPC 3.50. It was made perfectly clear in the notification you received with the Key, AND in the top announcement in this Forum, that you need AT LEAST 3.53. The current version is 3.65. Please just update your copy. Old versions are not supported in any case. You can always EASILY find the version number of your FSUIPC, by any of these methods: 1) Right click on the FSUIPC.DLL itself, select proprties then Version. 2) Run FS and look at the FSUIPC options. The first page which appears shows the version number. 3) Look in the last FSUIPC LOG file generated by FSUIPC. The version number is on the first line, as above. Regards, Pete