Pete Dowson

No it isn't. Where on Earth do you get that from? The WideFS package contains WideServer.DLL for FS9 and before and WideClient for any FS. There simply is no WideServer for FSX as its functions are built into FSUIPC4, but this was never the case before FSX. Have you not even looked at the main download site, http://www.schiratti.com/dowson? Have a more thorough look if so, then please just download the package and see what's inside. The main thing to read, before you pay for it, is the documentation. Don't buy anything you don't need! ;-) Pete

Well, this is not the FSMeteo support place, but it sounds simply as if you forgot to turn on your pitot heat and/or enable anti-ice, so when you fly through any layer (usually clouds) with icing conditions your pitot tube freezes up, stopping the ASI, and/or your engines fail, or maybe even your wings lose lift due to icing. Maybe you never experienced this before because you never had realistic weather? Regards Pete

Okay. Thanks for letting me know. Pete

Quickest way, first, really, is to simply monitor the Avionics switch offset in FSUIPC's Logging page (set offset = 2E80, type=U32, and check the Adv or FS display option below). You will see the value change on screen as you operate the switch. If it doesn't, you have a switch problem, if it does but the avionics still don't light up, it is another problem -- maybe battery. Check offset 281C as type U32 for the main battery switch and 2834 as FLT64 for the voltage. There's room for up to 4 variables to be shown all at once in any case. Pete

I really don't know of any relationship inside FS which would affect the avionics switching on or off -- provided the battery is on and sufficiently charged -- the generators won't be doing much till the engines are started. Why not just monitor the values inside FS -- use either the monitoring facilities (see Logging page), or FSInterrogate. Either can show you real-time changes in any FSUIPC offset. Ctrl-E is a "cheat" in FS which bypasses any and all subsystems in any case. You can't really go by that. Regards Pete

Sorry, I've no idea what these Gauge variables are. FSUIPC only supported CFS1 and CFS2 "by accident", because they were derived from FS and had sufficient similarities. I never extended FSUIPC to cover combat-specific parts of it at all. FSLook uses an unpublished and unsupported interface into FSUIPC. It was part of an experiment to see if it was worthwhile providing a method for external programs to read Gauge variable values just as Gauges do. But it turned out too inefficient, slowing FS down too much when used for realistic gauge operations. If you really want to use it badly enough I can supply you with the source of FSLook (it is all in C) but you will have to analyse it yourself to figure out what to do in Delphi. If you want to try this write to me at petedowson@btconnect.com. I'm afraid I couldn't offer much in the way of support. Regards Pete

Correct. That is why FSUIPC4 is supplied as an Installer! Why not simply try looking inside the Zip? You will see an Install program, which you can run from anywhere, and, even more importantly, a document which explains everything including installation! :roll: :roll: :roll: Pete

That is surely something already handled fine by FS itself. Panel part states, sizes and positions are saved in the Flight file in sections like this: [Panel.6] ScreenUniCoords=0, 0, 0, 0 UndocCoords=0, 0, 0, 0 Visible=False Undocked=False HiddenOn=False ID=20000 ViewsOn=1 When the coordinates/sizes are all zero as above they are defaulted. But all you need to do is set up everything exactly the way you like it, then save a Flight. When you re-load that flight all will be as you wanted. Pete

No idea -- though it must have come about through some manual editing. Maybe you caused FSUIPC to save some changes whilst also having the file open in an Editor? Not sure what happens when Windows is accessing the same file being manually edited. All of FSUIPC's access (both reading and writing) to INI files uses Windows Profile interface facilities. It never ever actually creates the [sections] or the lines in the form "key=value" -- all that is done by Windows, given section, key and value names, rather as it handles Registry access. The same applies to FS's own CFG files. Only one of those sections with the same name will ever by used -- probably the first one, though I couldn't be sure about that. Best delete one completely. Regards Pete

What's a G15 keyboard and what are its G-keys? So this is some sort of programmable keyboard which doesn't look like one to the standard Windows keyboard drivers? How did Logitech propose it be used? Changes are saved when you OK out, but cancelled completely if you Cancel or Escape out, or just close the dialogue. For the keypress tab you need to Confirm each assignment as you make it too, using that button -- this transfers all the details to the internal table. But the whole set of changes you are making since entering the Options is cancelled unless you OK out. Possibly you are visiting more than one Tab and then changing your mind about something else -- if the exit other than by OK then, any other changes you made will be lost too. This is a safety precaution, so that you can cancel everything and retain the settings you went in with. Otherwise it would get quite confusing what was saved and what wasn't. This is ALL are saved or NONE. A lot clearer (or so I hoped!). Yes, you can edit the INI any time, in fact, even whilst in the menus -- but only the Buttons, Keys and Axis Assignments sections can be changed to any effect -- the main parameters (in [General]) are only read during initialisation. There are "Reload ..." buttons for Buttons, Keys and Axis Assignments so on which you can use to force FSUIPC to load your changes. Haven't you noticed these? Must be a coincidence. The aircraft-specific assignments are always loaded on an aircraft change, so that may be the reload you saw. Either way it is easier to use the facilities provided to explicitly reload stuff. That's what those buttons are there for! ;-) Regards Pete

What's this "Interface IT drop down"? Sorry, I don't know what you are doing, sorry. Surely you are using my documentation to get information about offsets. If not, what are you using? Document searches are straight-forward. Pete

If you'd searched the offsets list for "Generator", as I just did, you'd soon find the four separate Generator switches, one for each possible engine supported in FS, at offsets 3B78, 3AB8, 39F8 and 3938. Please always try a search! Regards Pete

Do you know what the option actually does in LevelD? Does it use anything in FSUIPC in the first place? When you say "latest version", could you be more specific, please? I need numbers. It has happened when the "latest version" folks mean turns out to be the "latest version they downloaded a year ago"! Really, without knowing what Level D are doing or trying to do, and whether it has anything at all to do with FSUIPC, I can't help. Are you actually using FSUIPC for your throttle, or only FSX? If FSUIPC for calibration, are you assigning things there or in FSX? What happens if FSUIPC isn't even installed? Regards Pete

I cannot support such old versions. Please install FSUIPC 3.75 and WideFS 6.75 (both Server and Client) and then tell me what is happening. If you still have problems I need to see these files to start with: FSUIPC.LOG and WideServer.Log, from the FS Modules folder Wideclient.log from the Folder where you run Wideclient from, on the client PC(s). Pete

Actually the installation of the SDK should not in any way affect an installed FSX or SimConnect version, as it does not change any of that -- the SDK only supplies additional components. There are, of course, additional MS add-in DLLs like the TrafficToolBox which come as part of the SDK -- these need the DLL.XML file editing to point to wherever you installed the SDK components. Regards Pete

I don't think there has ever been one. Well, it isn't realisitc, but then niether is having the trim way off when you disconnect A/P ;-) You can program a button or key to use the Elevator Trim Set control, with a parameter of 0. Regards Pete

Good. Thanks for letting us know! Regards Pete

Ground speed is at offset 02B4 as a 32-bit value in 65536 x metres/sec. You could assign your button as normal and then edit the INI to prefic it with the condition "D02B4=0", or for almost zero (as the value goes down to as low as 1/65536th of a metre/sec), something like "D02B4<1000" (less than half an inch per sec). Etc. Pete

Ah. In that case, since my software is not driving your motors at all, I can't really help. You need to talk to whoever did the driver for your throttle unit. If it is inputting a trim axis value, don't forget that you would need to make sure it is disconnected when the FS autopilot is enabled in any vertical modes -- see the FSUIPC4 Miscellaneous options page, to quote from the User Guide: However, this would only concern autopilot use, and you didn't actually mention any A/P. Regards Pete

Either one or both of your FSUIPC / WideFS keys is faulty, or your FS system date is set earlier than your purchase date for one or other of the keys. If you believe you have legitimate keys Zip up the FSUIPC.KEY file and send it to me for checking. petedowson@btconnect.com. Pete

There were still some problems with 4.151, please go get 4.152. PFC 2.30 doesn't work with FSUIPC4 as it is the FS9 version. I assume you mean PFCFSX 4.30? How does the PFC driver relate to a non-PFC throttle system? Or is the CockpitSonic device sourced from PFC and meant to be driven by the PFC driver? I've not heard of any motorised throttle at all from PFC. My 737NG cockpit has motorised trim, that's all. I'd love to have a motorised throttle system. Sorry, none at all, since I don't know the equipment nor how it is controlled. Have you asked Cockpitsonic? I assume they know how it is supposed to work? Regards Pete

Not really. Sorry. This is all outside my "sphere of knowledge". I would have to experiment -- trial and error. Compare a simple (!) aircraft.cfg with a sim.cfg to start with. I assume it isn't just the presence of an aircraft.cfg file? Or an air file? Regards Pete

Phew! Great, such a relief! What did you re-install -- just FSUIPC4? Maybe the one which gave the problems was 4.150 after all? That would explain it if so. Thanks for letting me know so quickly! Regards Pete

4.150 was the one with problems. You had none? Sorry, I'd need a lot more information than that. No. the intermittent hanging problem was in 4.150, possibly a little in 4.151 too, but I thought fixed in 4.152. That was the reason for the quick updates. It was caused by looping controls (non-intercepted controls being re-transmitted and received again, etc). Possibly you've found another way it can do this, but I need more information to track it as I am reasonably sure I covered all the routes for these through SimConnect. In case this is what it is, I need: 1. FSUIPC4.INI file. 2. Set up for a SimConnect log file, as described in the "FSX Help" Announcement above. 3. Enable Axis logging in FSUIPC4 Logging options. 4. Reproduce the problems, in as short an FSX session as you can (else the Logs get too big). 5. Zip up the INI and two Logs and send to me at petedowson@btconnect.com. Thanks, Pete

Sorry, I've no idea about that. I didn't even know you could. That's a rather weird idea. How would you expect these to appear in a views menu? You could have thousands of objects all over the virtual world!? Regards Pete