Pete Dowson

I assume so too. CAB8? You've jumped from FS98 weather offsets to something in the Advanced or New weather interface? Please tell me what you are looking at. No idea without more information. Where are you reading? In that case it might be a good idea to be a little more specific, please. Pete

Sorry, I really do not understand. The WideClient screen occupies whatever size window you size it to. If you maximise it, of course it occupies the whole screen, just like any other program! so why are you doing that? You can make the WideClient button screen occupy any part of your screen you like. What else can you expect? WideClient cannot magic screen space out of nothing. I do not understand what you are expecting of it! If you have no space for it you cannot use it --- is that not blindingly obvious? Pete

The WideClient button screen only ever occupies the WideClient window. you can size it and position it as you like, to share the screen as you like too. It sounds like you have maximised the WideClient window. simple restore it and size it to suit! Pete

What does it use FSUIPC for? Sounds like a grphics problem in the particular aircraft. FSUIPC knows nothing about the aircraft or its visual parts. If your joystick axes are operating the controls correctly in VC mode, they must be sending the correct values. If the changes aren't visible in the outside model then you need to speak to VRS support. Sorry, I don't understand this part. What are you trying to do with full power and brakes at the same time? I think you need to explain a little more. Is your problem purely graphics, or something else? Sorry, what is "STRG"? Do you mean simply terminating FSX? If you have an error on FSX termination it is usually because something is calling something else still (probably from a different thread) after that part has obeyed the closure request. This seems to confirm it. It looks like part of the VRS add-on is calling FSUIPC4 after it has terminasted (unloaded). Error C0000005 is "access violation", which is what you would expect. Regards Pete

The most usual cause of this is multiple assignment, and there they all are, clearly shown in your INI: You see (the red parts) that you have no less than FOUR separate axes actually assigned to the FSUIPC Flaps facility (internal 23) -- 0 U, 2 Y, 3 S and 3 T! The ones you don't want will provide your "ghost" inputs even if the devices are not connected -- not connected looks like zero which will be the same as full flaps (as the lever movement is reversed for flaps, the lever nearer to you for full). Additionally, see the Green highlighted lines? You have axis 3U sending specific Flaps Up/1/2/3/down commands using the range system in axis assignments too, and 2X sending the FS axis control "FLAPS SET"! No wonder you have odd things going on! In fact, of the 7 axes you are assigning in FSUIPC, 6 (SIX!) are assigned for flaps operations of one sort or another, and the other, oddly, is assigned by range to do "Spoilers On" and "Off"! Why? Why not assign to the spoilers axis and calibrate as usual to give you a full range of spoiler/speed brake movement? I don't understand how you are getting yourself into such a weird mess. It is a first for me. You seem to be making things really complicated for yourself. If you were really set on "starting over" as you said you should think about deleting the whole lot from the INI file and doing it all properly. Okay? Regards Pete

I need more information in order to help you. Please paste your FSUIPC Install log, and, if there is one, your FSUIPC4 log files. You'll find them in the FSX Modules folder. Regards Pete

I only refused to make the dialogues any more complicated than they are. There are enough folks who get confused as it is. The numbers who want to do complex conditional methods simply doesn't justify making it more difficult for others. Maybe if I were an expert in designing good user interfaces it would be a different story. But i am most certainly not. It can all be done with lines in the INI file, and I think that is sufficient. I've always been of the opinion that it should always be easy to do easy things, and it doesn't then matter so much if it is a bit harder to do harder things. After all the user has to understand more of what he is setting out to do in any case. Regards Pete

You'd need to do one of two things: either edit the FSUIPC INI file and make the button actions conditional on FSUIPC offset values (such as, in this case. the "on the ground" flag), or write a Lua plug in to do a similar job. FSUIPC INI file formats for Button assignments, including examples of conditionals and FSUIPC offset references, are given in the Advanced User's document, and you'll also need to download the FSUIPC SDK to get the list of offsets. The Lua facilities are described in documents you should have already, but the Lua language is descrbed on the Lua website, unless you buy the book. Sorry, I don't know. I am still waiting for the Saitek yoke and quadrant they promised me many months ago! Regards Pete

Good! Carry on flying! ;-) Pete

If you refer to the FSUIPC Lua Library documentation you will see that the very first function listed in the whole document is just for this very purpose! How did you miss it? ;-) Pete

More information please: 1. What is the symptom of "FSUIPC not loading"? The fact that an add-on "can't find it" doesn't automatically mean it isn't loaded -- more likely just that the application cannot connect, and that is an entirely different matter. When you run FSX and get to the normal flight mode, ready to fly, is there an "Add-Ons" menu entry, and if so, does it contain FSUIPC? 2. If not, look in the FSX Modules folder. Is there an FSUIPC4.Log file? If so, it is being loaded but you have some FSX installation error. Show me the FSUIPC4.Log. 3. Please also show me the Install log from the FSX Modules folder. Re-installing FSX is usually a very very bad idea. It seems to be the major cause of SimConnect corruptions. Folks getting into these problems sometimes then have to resort to reinstalling Windows completely. Does that use FSUIPC? Not sure how to interpret that. If AI Carriers uses FSUIPC, then obviously FSUIPC is installed okay. Please answer the questions above and we'll go from there. Regards Pete

Thanks .. but isn't the best thing you could do now to purchase it and become a proud and legitimate user? ;-) Pete

There's a facility in the Flaps calibration page to calibrate the range for each detente. It is specifically designed to do what you have done, but much more easily and reliably. There's a complete section about it in the User guide, entitled "Calibrating flaps with specific détentes", and it is listed in the contents at the front, so I don't know how you missed it! :-( You have assigned the axis to flaps, so the axis is trying to control the flaps directly, and you have also assigned specific FS controls to specific ranges! Those two things will certainly conflict! I'm surprised it works at all! :-( Either do one thing or the other, NOT both! You either treat it as an axis and calibrate it properly, with detentes if you like, OR you treat it as a set of switches, as in the right-hand side of the axis assignments! By doing both it is conflicting, and this certainly explains your problems! The axis assignment will send axis controls to move the flaps and the control assignments will send different ones. There's something wrong in any case if you are only getting a range from -16143 to -12356. Have you checked the Windows' game controllers? A more normal range would be -16000 ot more to +16000 or more. Most USB axes give at least -8000 to +8000. You seem to have very little measurement on your axis. Regards Pete

No, sorry. The WideFS data rate should approximate the FS frame rate, at least up to values like 30 fps. I use Project Magenta with FSX on a 7-PC network, and they all keep up with FSX frames rates locked at 30. If you aren't limiting FS frame rates, try doing so. If FS is running away with the processor WideServer may not get enough time. This is less of a problem on multi-core PCs of course, since WideServer uses different threads. If you check the WideFS logs (WideServer.log in the FS Modules folder, and WideClient.log in your WideClient folder) you might find that there are multiple errors or reconnections, which would certainly cause a severe degradation. If you want to show me, please make sure the logs are complete -- close down FS and WideClient first so that the performance summaries appear at the ends. An FSUIPC log might help too. Regards Pete

Using the range assignments on the right-hand side? That is a rather complex and inflexible way of doing it. For flaps you can simply assign to the flaps axis, then calibrate in the Joysticks tab. You can optionally assign detentes and calibrate those too, but this is only really needed if you actually do have detentes on your lever. Otherwise you can fairly easily determine the position by visual feedback. That way you have the same facility on all aircraft no matter how many flap positions they have. Without seeing exactly what you've done (the [Axes] and [JoystickCalibrations] sections of the INI file) I couldn't really guess what is going on. Normally such things are down to jitter on the axis or possibly a bad connection. Logging the axes would tell you. Jitter without lever movement is more likely due to voltage variations or bad (dry) joints or cabling. You could try using the Filtering option in the calibration tab, but of course if you are not using the flaps axis control, but assigning to ranges, you cannot use that. Regards Pete

If it is regarding use of FSUIPC for a commercial or freeware project, please write to petedowson@btconnect.com . If it is merely technical clarifications you need, please stay in the Forum. Regards Pete

I've no German either. Google translation makes this: I am sorry, but I do not know what the problem is from this. If there's a problem with the time displayed in your add-on I think you need to contact the support for that add-on program. FSUIPC does not include any clocks or time component. Any time read through FSUIPC is supplied by FS. Regards Pete

No, none. Yes. It is an FS module and the only files involved live in the relevant FS modules folder. Of course you cannot run FSX and FS2004 at the same time on the same machine, but that is an FS restriction too. No. You can also have FS98, FS2000, FS2002, ESP, CFS1 and CFS2 installed, all with FSUIPC (3 except for ESP which uses 4) with no trouble -- just as long as you only run one at a time. Pete

FSUIPC only scans joysticks which it needs to scan because there are assignments made to them. The word "function" here is not a programming term, it is an FS function, something you are using the joystick for in FS. If FSUIPC is not scanning the joystick it cannot supply you with button states. And in any case the same wording is used in both the descriptions of "testbutton" and "buttons" functions, so I don't understand why you'd think one was different to the other in this regard. The encoder is using a pulse -- each 'click" either makes or breaks the contact, alternately. You will therefore see the button turning on and off alternately. If you want to act on every 'click' you need to remember the previous state and act only on a change. If you act every time you see it "pressed" (set) then if you leave the dial in an "on" position it will repetitively tell you it is set forever. You cannot treat a rotary as a momentary button like most joystick buttons. You can of course do such things via a Lua plug-in, and it makes a good educational exercise, but I'm pretty sure it would in fact be easier and quicker to do it via normal FSUIPC assignments, even if it also meant a little bit of INI file editing for conditionals. Regards Pete

Have you tried selecting more or different NMEA Sentences? Different applications get the assorted data parts from different ones. Regards Pete

It sounds like you need to select another or different NMEA sentence. You'll need to check the specification for the device to see what it needs. Sorry, this is totally confusing. WideFS is to connect to programs running on a Networked PC. How will that help? How is it in any way related to your first paragraph? FSUIPC has no idea about Bluetooth or any other types of dental equipment. The GPSout facility operates with serial devices. Your Bluetooth driver emulates one of those, and you seem to have it partially working according to your first paragraph. The rest of your message makes no sense in relation to that. All you need to do is find out what data your device needs and select it in the GPSout options. Regards Pete

No, sorry. Those are only directly assignable in FSUIPC. However, there is a way around this which was implemented in FSUIPC(long ago, in fact), and which is documented in the section of the Advanced User's guide called "Assignment of additional controls". What you need to do is assign, in FS, those two axes to two axis control you aren't using. maybe if you never use a 4-engined aircraft, mixture/prop or throttle control for engines 3 and/or 4, or some other axes maybe. It doesn't matter provided you don't use them. Then you have to find their control numbers in the list of FS controls document I provide in the FSUIPC documentation set. As use those to make the special parameters in FSUIPC.INI file, "AileronTrimcontrol" and "RudderTrimControl". Have a look in the documentation. I hope it will become clear. Regards Pete

Because that is all that are supported by the Windows "joy" interface, which is used by FSUIPC, just as it was in FS98, FS2000 and, I think, FS2002. The axis complement was extended to 8 axes by DirectInput, used by FS9 and FSX, and that is supported by FSUIPC4, in which, because it was a full re-write (of necessity), I had the opportunity to rewrite that area. You can assign in FS. FSUIPC can still be used for calibration. Regards Pete

I don't think Lua supports Binary notation (like 0B00100...), you could check in the Lua reference manual available on the Lua website, as referenced in my Lua packaages. Even if it did it wouldn't need leading zeroes. It certainly supports decimal (no prefix) and hexadecimal (prefix 0x). The initial 0 is needed in languages to distinguish a number from a name -- names start with an alpha. Sorry, I don't understand the question. What do you mean " it must have assigned any macro or lua function in order for fsuipc to watch it"? Sorry, I've no idea where you are coming from with that. The only difference between testbutton() and buttons() is that testbutton reads the 32 bit button state, makes the 32 bit mask with the bit you specify, and does the AND for you. It is MORE efficient for testing a single button, not less, because all of that is done in high-speed compact compiled C whereas you doing it separately in Lua is a series of interpretations. The buttons() function is provided for those dealing with multiple button states, such as those encountered with multiway switches. Regards Pete

Yes, a grave omission by Microsoft when designing the SimConnect weather interface. The internal structures for weather do allow the upper altitudes to be set, but getting at them is very complex. I managed in in FS9, and that was convoluted. It is much worse in FSX. I gave up. They did promise a thorough overhaul of the interface in a later SimConnect release, but of course, like FSXI, it wasn't to be. Regards Pete