Pete Dowson

The Lua ext library will position and size undocked FS windows consistently as you wish. All you need to know is the title of each Window, as shown in the undocked title bar. The file downloadable from the Schiratti site is actually 4.745 -- the text hasn't been updated there. It isn't my site and I have no control. I'll get that sorted when I manage to get all the documentation fully updated and release a version 4.80. Meanwhile this forum and its subforums are under my control (within reason), and you'll find updated versions like 4.747 and the updated Lua package in the Download Links subforum, along with lots of other useful stuff. Please do browse the subforums, seems a lot of folks miss out on them altogether, which is a shame. Regards Pete

Not without programming. You'd need to assign both the spoiler and throttle axes to two separate Lua plug-ins, with the throttle one setting the time of throttle change in a Lua global, then simply passing on the throttle value using the normal control, while the other discards spoiler changes within so many milliseconds of a throttle change (reading the Lua global for the time), but otherwise passing the value on via the spoiler control. Regards Pete

Strange. Two things appear to be wrong. First is your registry does not correctly contain the installation details for FSX. How did that happen? The registry says your FSX is in "H:\AI Mil" whilst you told the installer, correctly, that it is in "E:\FSX" You need to fix that. You didn't move FSX yourself without re-installing it, did you? If you want to move FSX best way is to rename the original folder, the install FSX to your other location, and then simply delete the original. That way all the registry links get corrected. Best not to uninstall then install as this can make a really nasty mess of SimConnect. Which brings us to the second problem, your SimConnect installation is corrupted. That could be fatal. I don't understand how 4.70 could have recovered from such a problem, so perhaps something has gone wrong on your system in between times? Please can you show me the Installer Log from 4.703 so I can compare them. Can you re-run the 4.70 installer? It won't replace a later version of FSUIPC, but it will confirm the problems you have or or not. You can get it with this link: FSUIPC470.zip BTW, if you already have 4.703 and are using it successfully, you don't actually need to re-run a later 4.7xx installer. The separate FSUIPC update (now up to 4.747) can be installed manually. However, I'd still be interested to see the 4.70 install log AND an FSUIPC4.LOG please. Regards Pete

Thanks. I'll have the Installer fixed with the next new main release. You shouldn't have to. It's all to do with the video driver and how full screen mode is used. CFS2 seems rather primitive in this regards compared to FS9 and FSX, but even the latter can have similar problems with some video drivers. Regards Pete

Hmm. Interesting. Are you sure there's a space? CFS1 has both "path" and "InstalledTo". All the other FS variations have one of "EXE Path" or "InstallDir". Also, can you tell me if the last part of the Key is 2.0 or 2.00 please? CFS1 had 1.00, which again is unusual because FS9 and FSX are 9.0, 9.1 and 10.0. Hold on. If you've done that then no change to the Installer will make anything different. That's all I've done. I do have CFS2 but it was copied from an older PC, which was defunct, and not installed. It works fine with FSUIPC simply copied in. You mean it switches to Windowed mode to display the dialogue, I assume? Here, if i run CFS2 in full screen mode, the FSUIPC dialogue does indeed come up behind the CFS2 window and you have to ALT TAB to get to it, but after having exited from that, the CFS2 screen is obtained again by clicking it's icon in the task bar. Best anyway to run CFS2 in maximised windowed mode, or at least switch to Windowed mode before using the options. I don't think it gains anything at all in full screen mode. Use ALT + ENTER to switch, as with FS. You've got problems with your video driver in that case. The same sort of thing can happen with FS9 and FSX with video drivers which don't handle FS's style of full screen use. Either find a better video driver or stick to Windowed mode. The LOG is fine. There's nothing wrong with FSUIPC. Your CFS2 is hanging in the video driver. Sorry, but FSUIPC can't do anything about that. Regards Pete

The offset interface (designed originally for my obsolete Esound module in about 1998) has a fixed volume setting of 100% -- i.e. the maximum value DirectSound accepts. The same internal code is used by the Lua plug-in sound library but that is provided with a volume control facility. But of course still 100% is the highest it can go. If the sound at max isn't loud enough then you'd need to either adjust the sliders for the playback device, or edit the WAV files you are using to increase their volume. Maybe it the other sound channels you are comparing it with which are recorded louder? Regards Pete

Close FS9 and show me the log. Are you running both FS9 and Topcat at the same privilege levels? If not they can't talk to each other. Please always quote version numbers. Pete

Nor I. But I don't have any proper installations except for FS9 and FSX, so I can't tell. If you'd like to look in the Registry and tell me how its path is defined I can fix the installer in a future update. The problem is that Microsoft sometimes use a key "EXE Path" sometimes "InstalledTo", and sometimes just "Path". I may have guessed wrong -- no one's provided any feedback on this so far, you are the first, so run RegEdit, search for "Microsoft Games", find "Combat Flight simulator\2.0" under that and then tell me within which keys in that you see the correct path. Same way every other user must have done it. Copy the FSUIPC.DLL from your FS9 modules folder into your CFS2 Modules folder. Make sure you run Explorer by right-clcking its EXE and selecting "run as administrator" in case you have it installed in Programs and Windows stops you writing to the real Modules folder. It this doesn't work (because of Vista or Win7 protection), let me know the registry result and I'll fix the installer right away. Regards Pete

No. There are no true button presses from axes! If you mean virtual buttons the one universal repeat rate applies. Pete

Hi Nico. I thought he was interested in using FSUIPC for this, as else he needs to go to the Goflight forum. FSUIPC doesn't use any GoFlight config software for basic button or switch assignments. The RP48 rotaries are detected by FSUIPC as 4 buttons -- fast clockwise, slow clockwise, and the same counter clockwise. All he needs to do is assign those to appropriate FSUIPC Offset controls -- there are increment, decrement and cyclic inc/dec controls available for bytes, words and dwords. The cyclic controls have a limit parameter, which would be 360 for a heading. And the increment is also specifiable so he can have larger and small increments for fast and slow.. All he needs to know is what the offsets are and whether they are byte, word or dword. Regards Pete

Correct, as mentioned in the offsets list. It has to be either yes or No, not indeterminate. What do you think deleting it will mean? Please look the parameter up in the Advanced User's guide so you have some idea of what you are doing. Not sure how reading posts here in the forum is relevant or helpful. documentation is the best first resort. Correct. Also as documented. What do you think is wrong? The readouts from FS provide the control surface deflection achieved by the input you provide. I believe the deflection value is proportional to the actual angle achieved, which is not linearly related to the input control. Regards Pete

Please never say "similar problems". They rarely are. No, there is no "demo" mode for WideFS. you need to purchase it. There's no demo mode for any of my FS programs -- only either free use or purchase. You will not read anything about any demo modes in any of my documentation. What's an "upper menu"? If the normal in-flight menu bar is not being made visible in FSX when you press ALT, then your FSX installation is severely broken. The menu is the place where you can do all sorts of things in FS, such as select and change options, view the Map, select views and so on. It isn't specific to FSUIPC, is it an essential part of FS as it has been in every version since the original Bruce Artwick one. Regards Pete

You simply assign the button numbers produced by the rotaries (there will be 4 for each -- fast and slow in each direction, exactly as documented in the FSUIPC documentation). Assign to the appropriate Offset controls -- there are offset increment and decrement controls for different types of values, and cyclic ones for things like the heading. I cannot advise more specifically because I do not know the details of the offsets you mention. They are private to LekSeeCon, so not part of my documentation. Have you tried LekSeeCon support, or documentation? Regards Pete

Before your addition this thread was last contributed to in June 2006, over 5 years ago! You've been following it all that time? I think it best if you started a new thread and explained what your problem is. If it is anything to do with any of my programs, please state version numbers -- and make sure you are up to date first. A *lot* has changed in 5 years! Current versions of FSUIPC, for instance, are 3.998j and 4.747, though the last installer releases were for 3.998g and 4.745. Pete

Please then see the FSUIPC Advanced User's guide -- look up "ButtonRepeat", the INI parameter which controls all button repeat rates and the initial delay. But when you adjust that you adjust it for all buttons. The button repeats act like the FS repeats. If you actually prefer the FS repeat rate why not use its assignments? The operation of such brake buttons is similar to using the key presses (. fopr both brakes, F11/F12 for left/right). If you want less braking you have to "feather" them -- i.e press and release, press and release, faster or slower depending on how much braking. If you want real proportional gradual braking you need to use braking axes and replace your brake buttons with potentiometers and analogue inputs. You could also program your own braking quantity, increasing it or decreasing it according to how long the buttons are pressed, by devising Lua plug-ins to detect the button and send appropriate AXIS_LEFT_BRAKE_SET or AXIS_RIGHT_BRAKE_SET controls with proportional parameter values. Regards Pete

I've no idea at all what you mean by "the button. Is like a bar and you have 3 position to set", but you only need to assign one button to BRAKES LEFT and the other to BRAKES RIGHT, and in each case enable the "repeat whilst held". I'm sure if you'd look you'd easily find these controls. They are the same as the FS keyboard ones! Pete

Maybe there's a User Forum for it under Logitech auspices? Regards Pete

Unlikely. The only chance there'll be for FSUIPC on Flight is if it supports SimConnect in a reasonably compatible way (though hopefully with a far better bug-free weather interface). I think this is unlikely, though, and I am simply not going to embark on a complete new development. I want time to enjoy my old age a bit whilst I've still got some! Sorry, I don't know what that means. I don't know anyone who knows anything about Flight other than the rumours and what's been publicised. Regards Pete

If the switch is local in effect to the device then no software in the PC will be able to deal with it. If, however, it is seen by the Logitech driver than maybe it can be handled by other programs too. But if, without the Logitech driver, it doesn't look like a normal joystick switch (i.e. is not seen in FSX), then it would need special programming if you wanted to dispense with the driver. The HID programming facilities in the Lua package part of FSUIPC (and WideClient) could no doubt handle it, but it is a programming job then, albeit not that complex, not a simple assignment. Pete

ActiveSky does not need an FSUIPC registration, it is a licensed FSUIPC product in any case. I don't remember ActiveSky 6.5 well enough to know if it retries connection. I use ASE. Why not try starting it after FSX is up and running to see if it simply needs it running first? If that doesn't work I'd need to see the FSUIPC4.LOG file. First, make sure you are using a supported version of FSUIPC4 -- no older than 4.70, but better the current release, 4.745 or later. Close FSX afterr attempting to connect please. You can paste the log here. Regards Pete

Unfortunately the main problem here is simply that I just don't understand. I just haven't got my head around what it is you think is wrong or need to do which can't be done as it is. It is all very well pointing out how easy it is and that it doesn't affect any compatibility, but I really do need to understand first, and i don't. If you'd like to make it really really simple, perhaps with diagrams to illustrate what you are talking about, then I might get it? Best probably to use Email for this -- petedowson@btconnect.com. Regards Pete

You want a gap, with zero or random or unpredictable winds? Why not simply place a dummy zero/zero layer on top of the surface layer? I want to avoid making any changes whatsoever to the weather code. It is complex and I've not really touched it for five years. I'd need a really good reason to mess, and so far either you haven't given one, or you have and I haven't understood it. Sorry, Regards Pete

Odd that I've never suffered from it. Perhaps it's the different starting technique I use, supported by FSUIPC. The engine starter controls in FSx have always been a bit iffy. The PM reference you quote doesn't really describe the same problem, only the way to make sure the actual FS cutoff switches don't operate until all the right conditions for starting prevail -- because FS doesn't care about duct pressure and so on. It really does sound like ProSim is doing something odd over time. Can't you monitor the relevant conditions, see what is changing? Regards Pete

Why are they operating automatically? You should have to move the switches. Sounds like there's something wrong in ProSim's logic. Are you losing duct pressure? After you start the APU you need to switch on the APU bleed to build up the air pressure needed to turn the jet rotors. Surely the instrumentation should show you what is wrong? No, sorry. I've really no idea. Only the ProSim author can really analyse this -- he knows what he's doing. I thought he simulated the systems flow quite accurately? I use PMsystems (or used to -- I've recently changed to Thomas Richter's 737NG system). Regards Pete

Just assign a button in FSUIPC to the PTT controls in the drop down list. Press on, release off. Nothing else to do. How many steps do you need for that? Pete