Pete Dowson

On my fast PC (4 GHz) is takes several minutes. XML, ugh! Pete

I don't have time to be bored! I'd need to look af GFpower. I don't remember it. Okay. It will be setting lights off by using SetLights, but not by setting the colour to black. However, the GFDev.DLL probably sets lights off using colour black, and it is likely that the GF driver doesn't restore its own colour. I can't think of anything else which could be worng. With "on" as the mask? That can't work unless you pre-defined the variable "on" to some non-zero value. without seeing your code I can't really comment., but if it's like the SetLights example i'm not really surprised! ;-) Have you read the documentation? What is it you don't understand? Pete

Which PFC driver are you using (name, version number)? Why are you trying to assign in FSUIPC? What documentation? For the quadrant, for the PFC driver? You've given me no information I'm afraid. Why FSUIPC4? Why not the PFCFSX INI or, if it is a USB HID device, the PFCHID.INI? I don't understand what you are doing, nor what type of device it is. BTW you are using an old unsupported version of FSUIPC4. you should be using Version 4.70 or later if you want support. Regards Pete

Yes of course. Add as many as you like in the INI file. You just can't do it in the User Interface. Pete

I have a full 737NG cockpit, mainly PFC made, including the shell, but also including a full Cockpitsonic overhead. That uses 6 PCs and a 10 foot wide screen with outside scenery projected onto it. I use Project Magenta plus extra software from TSR. I also have an Aerosoft (Oz) GA28R cockpit for a Piper Arrow III. That's for VFR flights. I don't have any FS aircraft gauges showing at all. They are all deleted because the hardware is provided. I don''t have any real use for Goflight, VRInsight or Saitek equipment. That which I have is for developing software for others. In what way? It sounds like it's been explicitly programmed that way. What is GFpower for? What is it doing? I assume it's one of the examples I did years ago, or is it? Wasn't it only to load separate Luas for each unit? Are you trying to use Lua GF programming at the same time as GF's own driver? There's a good possibility they don't mix. Either. Er, what was the value of your variable "On"? And why omit the "off" value. If you want to control all the lights with one line, like that, you have to give the numerical mask for those to go off as well as those to go on. it looks like you've not referred to the documentation for the functions? Please read the documentation for the SetLights, SetLight and ClearLight functions. The SetLights one is the most complex as that allows any selection of lights to be turned on and off simultaneously. Mostly you'd use the single light controls. But unless you set the colour first, using the new SetColour function, they'll be whatever colour they were before you started. So if they were black, they'd probably look black whether on or off. Isn't that obvious? Black is a colour and will look the same as "off"! If you really don't understand any of this it looks like I'll have to wait until the unit arrives. Regards, Pete

Okay. I reloaded CFS1 and tested, and it's the same here. Which is odd because it is fine in CFS2 and that was the same as CFS1 before, and the code looks the same. I'll check into it tomorrow or monday. You can't have them assigned in FSUIPC and also in CFS1. They'll conflict. You realise you have several axes assigned twice -- aileron, elevator, throttle on the Pro Yoke and on the X52. This is okay if you want FSUIPC to arbitrate, but you'd need to leave the one not in use parked in a neutral (off) stable position. Did you try your FSUIPC INI file from FS9 at all? Pete

All of the documentation and examples areinstalled in your FSUIPC Documents folder, as clearly stated in the Installation and Registration Guide. Pete

1. You posted this exact same message twice. I deleted one of them rather than reply twice. 2. You didn't read what I told you? Look: It is a facility to BASE A NEW profile on an EXISTING one -- to save you having to copy things in the INI file. If you aren't creating a new profile, what do you think copying an existing one can possibly do? You aren't thinking or making sense. Pete

Sorry, you contradict yourself. If the key is "in the proper folder" how can it be lost? If you didn't keep a note or backup the KEY file, as advised in the documentation, you can only retrieve it from your account at SimMarket. That's not relevant because it is the original name and email address you used when purchasing the registration which matters. That stays for life associated with that key. Regards Pete

You are making it sound more complicated talking about loading different settings. What you want is simply conditional actions on buttons. You can have buttons or switches doing different things based on the state of other switches or buttons, or flags set or cleared by them, or on the state of FSUIPC offset values. There are examples in the Advanced User's manual for FSUIPC and probably a few around in the User Contributions subforum. You can't do this sort of stuff in the user interface. It means editing the FSUIPC INI file. The ultimate in flexibility is to use a Lua plug-in, which is executed by your button or switch, and which keeps track of everything. But that's a little like "programming" which seems to frighten most folks. ;-) But you may want to look at and try the Lua plug-in example provided called "tripleuse.lua" which shows how one button can be used for three different purposes by single quick press and release, a double click, and a press and hold. Regards Pete

There's no way a simple button programmed in FSUIPC can send keystrokes to any dialogues in FS, because the main parts of FSUIPC aren't actually running then, unless you enter its own dialogue -- though that is still in "dialogue mode". All those menus are "Modal", which means all else stops whilst they are active. This is normal Windows dialogue behaviour. Sometimes you can get a selection made by putting the keystrokes in the Windows keyboard buffer first, like for instance ALT O E D might get to the display Settings. But nothing thereafter. You can do it with Lua plug-ins because they run independently, in their own threads. I think there's an example in the Lua Plug-Ins package supplied with FSUIPC which does this to enter fuel quantities into the fuel menu. When you talked about "map" I was thinking "top down view", which is not the same of course. Sorry. Regards Pete

You've already assigned that aircraft to a Profile, then! There's no facility to UNDO profile assignments except by editing the INI file and removing the aircraft name from it's [Profile.<profilename>] section. Pete

GROUND = engine start -- bleed air turns the rotors, the ignition starts automatically when you enable fuel (start levers on throttle quadrant) OFF (fairly obvious -- engine OFF right?) No, starters off, used for all normal running. CONT = continuous ignition, to avoid flame outs on take off, final approach and in some weather conditions FLT = in-flight engine startThe center switch functions are pretty obvious -- starting either left, right, or both engines. = No, selects ignition coils. Both engines have a left and a right. Pilots use alternate ones each day so they know they workI didn't see any corresponding actions in the BUTTONS/SWITCHES pull down menu in FSUIPC. Could you please help me here too? = FS itself doesn't simulate much of it. There are starter controls which use a parameter to select position.When I move the center switch from BOTH (center position) to LEFT FSUIPC detects the action but when I move from BOTH to RIGHT it doesn't. However moving it back from RIGHT to BOTH FSUIPC does detect it. Is there a particular way that I should be doing this so that all positions are detected? = I answered this already in your similar post in "User Contributions".Pete

Sorry, no. I don't know either program at all. In fact I don't know XML at all. I hate such wasteful slow forms of database being more of a machine level programmer historically. The format of the RUNWAYS.XML file was exactly according to requests made. i think it conforms to some of the FS standards and BGL scenery building program needs. The provision of ID strings within the block delimiter seems to be a common thing in XML, looking at others. I would have thought standard MS ptrograms would be able to handle it. Maybe it's an option someplace, or maybe it's a function of that Windows XML DLL (something lie MSXML4.DLL? Can't recall offhand). I have Access 2007 and it can't load that XML file at all, just says it doesn't recognise it. But, although Excel 2007 takes an absolute age (SUCH an inefficient database format!), it does get the ICAO and make it the first column. It does say it doesn't come with a "schema" but will make one itself, and it seems to work fine apart from taking sooooo loooonnnnggg! I tried it on a Win7 and a WinXP machine, with identical results. So I've no idea what's wrong with your Excel. Regards Pete

It doesn't help me because i don't know what SimFlyer have done. Isn't there any documentation, any way of using keyboard instead of mouse? Don't SimFlyer have any support for the programs? There are only 4 possible ways to use buttons on panels or gauges through FSUIPC: 1. Direct assignment to an FS or FSUIPC control. It is unlikely they use FS controls, but to check just enable Event logging in FSUIPC's logging tab, click on the switches, and check the log to see if an FS control was registered. 2. Direct assignments to keystrokes which are assigned by the panel to operate those switches.. Documentation or support for the program is needed. 3. Mouse macro creation and assignment. This may work if the gauge is written using the Microsoft C/C++ SDK and incorporates into the aircraft as a gauge. Mouse macro creation is describe in the FSUIPC user guide. 4. Local gauge variable writing, via L:Var macros. These are more likely to be used if the gauge is written using XML. Most new ones for FSX are. L:Var macros are described in the manuals too. As a last resort, if mouse clicks are the only way, there is a program by Luciano Napolitano called "Key2mouse" which converts keystrokes to mouse clicks. But you must then always have the gauge in the same place on screen. I can't really help further. Sorry. Regards Pete

Yes, I know. Didn't I mention that? Same with CFS2. It wasn't like this back in Win95 days when CFS was released -- it's something to do with how they manage full screen mode which doesn't work so well with more modern versions of windows. You CAN run them in windowed mode instead, maximised if you like. Just ALT+ENTER as with FS. Hmm, that's odd. I actually didn't notice that! Not sure why it isn't present, because Axis Assignment is, for sure. -- AND it lists the axes you can assign to, including direct to FSUIPC calibration. I'll take a look at it over the weekend. Maybe it's something trivial. Meanwhile, have you tried using an INI file from FS9, already calibrated? You never know -- the mechanisms might work fine. No, that also doesn't have that Tab. Probably the same problem. I'll take a look. [LATER] I see what it is. It's not that you can't use calibrations in FSUIPC in CFS1, CFS2 -- it's that those sims (FS98 too) don't actually scan the axes whilst the sim is in a dialogue. In fact none of them do, but in FS2000 (or maybe later?) I found a routine I could call in FS which forced it to scan, so I call that regularly whilst in the dialogue. It looks like I couldn't find any equivalent in the Combat ones. But I'm pretty sure that pre-calibrated non-direct assignments will work too. you just can't calibrate them in the User Interface on CFS. However, now that FSUIPC does it's own scanning (because of the axis assignments, added much later), I can enable the dialogue just for "direct to FSUIPC calibration" assignments. Please try version 3.997g: FSUIPC 3.997g Regards Pete

I can host it on the Forum if the originator has problems, but I don't have a copy either I'm afraid. They are all recognised. Like all multi-position switches, one position is only "off". so you program that using the button "release" part of FSUIPC assignments. You are getting confused because the recognition system in the assignments needs an "off to on" transition. you don't get a different result going "on to off", it's just like taking your finger off a button. I don't remember exactly with the MESM, but I think what you actually get is: centre (both button numbers off) <--> Left (left button number on, right button number still off) and centre (both button numbers off) <--> Right (right button number on, left button number still off) which is quite logical when you think about it and allows you to do anything you like -- part of the benefits of being able to program "on" (press) and "off" (release) separately! ;-) Pete

No problem. I've got loads of other things to do. I've not heard back from GoFlight yet. [LATER] Magic! They just replied. I'll be getting one for a proper test here! Regards Pete

Seems to me that's the least likely area for compatibility, because many graphics experts in the field seem to point to the way the data is defined as one of the main things holding FS back, and that it was nigh time for a fresh start. The BGL style definition files have been around with things gradually bolted onto them for many years, even back before Windows. N-Gauge scale, mixed UK late steam era, mostly ex LMS + GWR areas. Not digital at all -- it predates that by a long way. Started building it in 1982. Cab control with track switching. The track power is controlled by banks of relays which it turn are controlled by a computer (an Amiga at present -- till i rewrite the software for a PC). The computer can operate the braking on the trains, with up to 6 trains running. It knows where they are by infra red detectors under the track and reflective foils under the locos and rolling stock -- so it knows how long they are too and which points they've cleared. Positions are drawn on screen as are signal states. It can be all hand operated or left to the computer. There are loco sheds, goods yards, carriage sidings and turntables only manually controlled. Can't find any pix at present. I'll take some next time I do some work on it. might be weeks, months or years, though. Flight simming's been taking priority since I failed to get a PPL due to my RP. Regards Pete

Sorry, it was still uploading. It's finished now. the 'net's a little slow for me today! Pete

Yes. That is exactly what button flags are for. You would have to edit the INI file though, because you need to have three actions programmed: one to toggle a flag and then the two ones you want each conditional on the flag -- one when set, the other when not set. Check the Advanced User's guide. Search for the paragraph which starts "The conditions can be made to apply not to the current state of a button, but to the state of a ‘flag’ that is set and cleared by a button (or even a keypress)." Regards Pete

Have you checked the section in the FSUIPC Advanced User's guide entitled "Gauge local variable access (L:vars), by macro!? It is listed in the contents. What don't you understand about it? I think you'll also find lots of examples of it being applied in the User Contributions subforum. Pete

Ah, good, 'cos that's the one I did first. Try FSUIPC 4.717 It should be intuitive to use the enhancement. As well as "New ..." you have a "New, based on ..." option. Selecting that will allow you to select the Profile the new one shjould be based on, then you get to provide the new name, as before. The FSUIPC log will show one of the "based on" Profile aircraft being selected, then your current one. This is due to the way I've had to implement the feature -- basically it finds an aircraft using the based-on Profile so it can load its settings calling all the (unchanged) loading functions, then changes back to your aircraft and saves them. Bingo, all new sections for the new profile, ready for your changes. Make a copy of your FSUIPC4.INI file before using this, just in case I've messed anything up! Regards Pete

How are you reading the XML? The whole XML section for each airport is enclosed in ICAO parentheses which give the ICAO, like this: <ICAO id="XXXX"> .... <<<< all airport data here </ICAO> Check it with a text editor and you'll see. Regards Pete

I had a look at this and it was relatively easy to do. I've tested it briefly here, but I'm not a heavy user of Profiles as I only fly one aircraft (my cockpit is a 737NG and won't suit anything else). If you or anyone else would like to test out the new facility, to base new Profiles on an existing one, please let me know which version you need -- FSUIPC3 or FSUIPC4 -- as the code change is similar to both but I only want to build one until I'm sure it's a good move. Best Regards Pete