Pete Dowson

For keyboard key presses, FSUIPC assignments will override FS assignments, so, yes, you can do what you want without de-assigning the FS assignments. Just assign the keypresses in FSUIPC which you want to be different But you cannot do this with buttons and axes (levers, yokes, rudders, joysticks). Either assign in FS and not have them different in profiles, or disable controllers in FS and assign all in FSUIPC. Then you can have different ones for different profiles. Pete

Thanks Dougal. :oops: :oops: :oops: Pete

What happens if you register WideFS first? Why not register both in the same install attempt? There has been no change in the registration system for years The last change was to allow separate email addresses from FSUIPC and WideFS. If you tell me both SimMarket order numbers I will try and see what your problem is. Pete

But earlier you implied (though your detail was very mised up) tht the IP address was 192.168.2.1. See here: Pinging 192.168.2.1 with 32 bytes of data: Reply from 192.168.2.1: bytes=32 time<1ms TTL=64 Reply from 192.168.2.1: bytes=32 time<1ms TTL=64 Reply from 192.168.2.1: bytes=32 time<1ms TTL=64 Reply from 192.168.2.1: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.2.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms However, I cannot ping my #1 PC by its name fresh1011-MSI The fact that "ping" also gets the wrong IP address shows something is wrong on your Network, or maybe the router set up. Pinging fresh1011-MSI.Belkin [198.105.254.228] Er, what's the difference? TCP operates with ports. The ports WideFs uses are defined in the INI files, and they only need to match. "Connect to FSX" surely just means "connect to WideServer which is part of FSUIPC which is running inside FSX". I really don't know what you are on about here. So earlier when youpnged it on 192.168.2.1 you were mistaken? When WideServer is enabled in FSUIPC options, it opens the port. It only does this when FS is ready to fly, not when in the preliminary setup screens. The title bar of FSX will sohw that it is waiting for clients. If it does not show this then it is not enabled. You've never showed me your WideServer.log file from the Server, so I can't tell whether you've got it enabled and licensed or not. Pete

Yes, I'm pretty sure Accelerator does both. I think it might be better to just try installing the two missing Simconnect's first. You'll find them in the SDK section of the disk, in the LegacyIUnterfaces subfolder of SimConnect. Pete

Well, I said it was okay, but you shouldn't get these if your FSX is up to date. If the SP2 and SP1 versions of SimConnect aren't installed you will find many add-on applications won't run. Pete

Looks okay, now. The error shouldn't return. Pete

Well that's the IP address returned by Windows for that ServerName when asked. Er, added it to ServerName? Why? As documented, you either give the name or the IP. They are separate parameters with different parameter names. Pete

Did you run Makerunways? The files it produces only get produced when it is run. It can't do anything just sitting there. Or maybe it is there and you have Windows hiding the real filenames from you? Pete

I really don't need screenshots for you to prove thngs. You only had to say so. It just wastes space and time. Similarly small text files like Logs and INI files are best pasted into the message. Else I have to download them, find them, look at them, delete them. Much more efficient just to paste them in, please. Anyway, event though they are in the same workgroup, the broadcasts from the Server evidently are not reraching the Client. Sorry, I don't know why. I wonder if it's to do with the new-fangled networking 'Homegroup'? I've never used that, mainly because it doesn't work on a large network with a mix of XP, Win7 and Vista PCs. BTW the log named "Wideclient0.log" is a backup of the previous one. The current one is always Widecient.log. It makes a backup because lots of folks have systems which automatically re-boot on error. One thing, from that log, strikes me as odd: IP Address = 198.105.254.228 Is that really the IP address of your Server PC? It looks very unusual for a home network. It just keeps trying, as in fact it is now. All my clients tend to be waiting, ready, because they are started by Windows startup, automatically. When I power up the cockpit all 6 computers in it switch on and load up ready. No keyboards or mice you see! (It's a 737NG, not an Airbus). Pete

Does FSX run if you tell it to continue? This is usually just a result of a SimConnect timing problem in the DLL loading. If not, I need to see the FSUIPC4.LOG from the Modules folder, if it actually generates a new one before the crash. If it does not make a log I need to see the Windows Event viewer details for the crash. Pete

Do you get this when BAV is not being used? Is BAV the only application using FSUIPC? Do you get it with other aircraft or only that one? There is nothing in FSUIPC which is on a 5 second cycle. But please do check the FSUIPC4 log file and see if any problems or failures are listed. If SimConnect is jamming up and being re-initialised regularly this could certainly cause a stutter. Pete

I think perhaps you miss the whole point entirely! FSUIPC profiles are collections of settings made in FSUIPC. If you aren't using FSUIPC for settings there's no point whatsoever in using profiles. FSUIPC cannot change over settings you make in FS for different aircraft -- that's one of the reasons folks use FSUIPC instead! If you make settings in FSX they are stuck and do not change unless you go back into its options and change them. FSUIPC instead loads settings according to aircraft assignment to profiles. Sorry you find FSUIPC harder than FSX. Perhaps that is because it offers a lot more ways to do a lot more things? Do NOT make assignments in both FS and FSUIPC or they will conflict. If you assign in FSUIPC you must disable controllers altogether in FSX. Pete

When you don't specify the Server name or IP address in the INI file, WideClient waits for a broadcast from the Server. If your Client is in a different workgroup to your Server, then broadcasts don't get through. They are limited to workgroup PCs only. So either specifically state the server and protocol details in the WideClient.INI, or make sure all your PCs are in the same workgroup. All this is actually explained in the WideFS user guide, in the section with a bold red request for you to read at least some of it, under the heading configure your network (or similar). Pete

That certainly wasn't how the 73NG sim I flew operated, which was a fixed-base, but training approved, one. Wonder if it's another one of the many "airline options"? I think the sim must have been wrong, or you are mis-remembering. Check any 737NG reference. I've been involved in 737NG cockpit simulation for over 10 years and have been in approved training ones. I strive for utmost realism in my own 737NG cockpit and have done the research and had expert advisors in doing so. What i said in my last message holds. Regards Pete

Yes, really! In C (and Windows API) an empty string ("") is a non-null (i.e. non-zero) pointer to a zero byte (or word for WideCharacter). NULL or a null pointer is actually zero, which isn't a valid pointer (in the sense that it can't be used as such without a vilation). Pete

I have no website. I supply all my stuff in the Download Links subforum here. Enrico Schiratti's so-called "Dowson" page isn't under my control. Mostly he publishes links to the same files as the subforum here. The whole point of FSUIPC was to provide on-going compatibility for its client applcations from FS98 through FS2000, FS2002, FS2004 and now FSX and P3D. I just don't have time or patience to update a few words in so many paces when the content stays correct. The changes from FS2004 to FSx are covered by the "FSUIPC Offsets Status" document. That's further updated with data in the "Changes from version xxxx" document accompanying each new release until I get around to updating the main user (not developer) documentation, at which time I also update the Offsets Status document and the Lua documents. Well, look like the sample code is still supposed to works with P3Dv2 and i'll assume future problems should be a PEBCAK :) PEBCAK? Never heard of it, sorry. Pete

There are alarm cutouts for the fire bell (press the FIRE button), and for GEAR horn (button below the flap selector section of the quadrant) and altitude alert (when the cabin altitude gets over 10,000 feet, a button on the overhead near the pressurisation gauges). But on a 737 there's no way to cut out overspeed warnings nor take-off configuration errors. And there are no alarm sounds associated with nor silenced by Master Caution. All the Master Caution button press does is extinguish the warnings currently shown on the 6-pack annunciators. It doesn't clear them, and if uncleared they'll reappear if recalled (again using Master Caution). Meanwhile the definitive reason for the annunciated warning will appear on the overhead. Overspeed is not one of them, nor is take-off configuration error. Pete

Why are you linking dynamically to FindWindowEx? Why not use it directly? After all it is a standard Windows library API. It is hardly likely to be missing. Does the top level window class "UIPCMAIN" exist at the time? Did you check? You can use something like Spyxx to check. Is your string in ASCII (you are explicitly selecting the "A" version of the Windows API)? If you've compiled for Wide Character use) as most modern compilers default to, I think, then the name you give will not match. If you'd used the direct call instead of dynamic linking things would have sorted themselves automatically. The source for the way to interface to FSUIPC is provided in the SDK. Did you look? I think it is provided in several languages. I'm only familiar with C, the others were provided by other users. Pete

No, not to write one. You only need an editor for that. Obviously, because the Lua program is just a plug-in for FS, enabled by FSUIPC, without FS it can do nothing. What could you expect it to be able to do, when the whole point is to interact with FS? But that's exactly what you'd do with Lua plug-ins, although you don't need two systems if you can run FS on the same system as your editor. There are lots of examples provided in the FSUIPC Documents Lua package, as listed in the documentation, and other folks have posted theirs in the User Contributions subforum. But I learned Lua from the Lua programming books published and easily available. Pete

That I think is a wrong diagnosis. If WideClient isn't sending data to the Server than it will also never receive data from the Server, as the Server only sends data which has been requested. Where do you see that? The session behaved normally without error until you terminated the Client at time 572836, which the server logged as a break of connection, of course. Where are you seeing any indication that anything is wrong? I do not know your software " sysboard" so I've no idea how to advise you. You can use more logging, but you'd need to know WHAT the software is trying to do before selecting the right logging options. Pete

By default, all settings, profiles, whatever, are in the FSUIPC4.INI file, in the modules folder. You can opt to have profiles stored separately, in a file for each profile, in a "Profiles" subfolder. There's a document supplied which explains this option and how to enable it. Pete

If you downloaded the package from here or on the Schiratti "Dowson" page, it is certainly okay, so it is what is known as a "False Positive" indication by the checker. You should notify the manufacturer and see if you can override it. Pete

That'll be a function of the PMDG model. You'll have to see if PMDG have supplied anything for it. The 737NG might have it listed in their assignable custom controls (listed at the end of the .h header file in the NGX SDK). I have no idea for the 777. In the real aircraft these are nothing to do with Master Caution at all. And there is no way to cut out either without correcting the situation. Pete

Yes, almost* the libraries listed in the FSUIPC Lua documentation are built in, as are the standard Lua libraries like string, math and so on. You do not need to "Require" them. I thought it was pretty clear in the documentation. * The exceptions are those which are marked "WideClient only". Wideclient also has most of the libraries, for use in Lua plug-ins on WideFS client PCs -- it doesn't have a couple but also has ones not included in FSUIPC. But it too has the standard Lua libraries as documented in Lua books and on their website. FSUIPC always stays in the FS Modules library, and is only active when FS is running as it is part of FS then. FS only sees Lua plug-ins which are placed in the Modules folder too. All this is surely very clear in the documentation? I don't know anything about a "clib" folder. This must be something you are doing by yourself. You CAN load Lua plug-ins from other folders, but you'd need to do this with the ipc.runlua function giving the fpath, in an already loaded plug-in. Unless you are trying to do something with other, specialist, Lua libraries downloaded from other sites, you need nothing but your plug-in and FSUIPC running. Pete