Pete Dowson

You make the 4th person unable to paste. I assume you are using Internet Explorer? Somehow some recent update from MS has really clobbered things. Please see this thread where I believe the answer was found: http://forum.simflight.com/topic/76255-wide-fs-connection-fsx/?hl=%2Bcut+%2Band+%2Bpaste#entry464896 Pete

If you want a private exchange use petedowson@btconnect.com. Pete

If you want to make a habit of stopping them then, if they are looping have them test a flag and use LuaSet to set the flag, upon which they exit tidily, or, for all Lua's with one notification, have them test an offset or button instead. You can use the user offsets 66C0-66FF. If they are event driven (which is a better design in any case), then, again, you can have an event based on an offset change, which leads them to exit. Ah, well 16-30 isn't as many as I thought you meant! ;-) Not so bad. It might be a good idea to start them all from within an [Auto] Lua in any case. I actually use ipcReady.lua, to save even having an [Auto] section. (ipcReady.lua is automatically started in any case and is actually intended for just this purpose, starting a batch of Luas). Pete

Why do you have so many in the first place? You realise each one takes a thread and is running in your FS PC? You can kill all Lua plug-ins using the LuaKillAll control. To start them all again you'd have to write another plug-in which uses RunLua to start them all, or program a button with them all assigned to it -- an INI file editing job. Of course if any of them are aircraft or profile specific (i.e. [Auto.<name>] loaded), all you need to do is change aircraft back and forth. Note that killing Lua plug-ins can be hazardous. Regards Pete

Well, you have no Keys assigned in FSUIPC, so I don't understand your earlier reference to assignment of Ctrl+. in FSUIPC. Your button assignments are pretty simple: [buttons] ButtonRepeat=20,10 1=P0,8,C66241,0 master battery 2=U0,8,C66241,0 master battery 3=P1,5,C65752,0 parking brakes 5=P1,4,C65752,0 parking brakes 6=P1,6,C65759,0 flaps decr 7=P1,7,C65758,0 flaps incr 8=R1,11,C65607,0 elev trim down 9=R1,10,C65615,0 elev trim up In this sequence:from the log: 307510 *** EVENT: Cntrl= 65758 (0x000100de), Param= 0 (0x00000000) FLAPS_INCR 307556 Button changed: bRef=0, Joy=1, Btn=5, Pressed 307556 [buttons] 3=P1,5,C65752,0 307556 FS Control Sent: Ctrl=65752, Param=0 307556 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES 308149 Button changed: bRef=0, Joy=1, Btn=5, Released that first FLAPS INCR command has occurred with no button pressed at all -- at least in the 4 seconds since you enabled the button and event logging, so I don't know where that comes from. But when you pressed button 4, here: 311519 Button changed: bRef=0, Joy=1, Btn=4, Pressed 311519 [buttons] 5=P1,4,C65752,0 311519 FS Control Sent: Ctrl=65752, Param=0 311519 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES 311519 *** EVENT: Cntrl= 65759 (0x000100df), Param= 0 (0x00000000) FLAPS_DECR 311940 Button changed: bRef=0, Joy=1, Btn=4, Released although FSUIPC only sent the one control, the FLAPS DECR control is sent as well. Not by FSUIPC -- so I believe that button is also assigned in FSX. I notice you have no axes assigned in FSUIPC, even though you are using a yoke, pedals and a throttle quadrant. So either those are assigned in FS or being sent by some other control program. That is where you will find your duplicate assignments. Pete

Most likely poorly calibrated controls. But check that your aileron trim is centred too. If that's off-centre you might get such a result because you are trying to find an off-centre centre on the aileron to compensate. Also check rudder and rudder trim. In that case, if it isn't due a very bad aircraft model, or the trim being off centre, you either have a faulty potentiometer, or it is a logarithmic one not a linear one. A log pot will have rapidly changing values towards one end. Apart from the above, test with a default aircraft. After all it may be just that model. Pete

I do wish I could actually reproduce this sort of problem, because it has never occurred here on any of 4 systems. And I run all sorts of add-ons, a different selection on each PC. I can only think that there's some bad interaction between two or more of the add-ons you have loading via DLL.XML or EXE.XML. The only things I can think of trying are: 1) re-ordering the loading of things in DLL.XML 2) more drastically, removing everything else except FSUIPC4 from the DLL.XML, and loading any EXEs separately, later, instead of via EXE.XML. 3) trying the FSUIPC4_Loader to change the timings 4) Using the Initdelay parameter in FSUIPC's INI file. to delay its Simconnect interaction. When you get the loading failure is the a part of an FSUIPC log file produced at all? If so it would be a good idea to show it to me so I can see where it got to. If not, then the problem certainly lies in SimConnect's loading sequences. Pete

You are out of date. I only support the current version - 4.929 or later. There's absolutely no way FSUIPC will do anything you don't ask it to do. It simply sends whatever you tell it to do. Very simple. You must have some additional assignments, in FSUIPC or in FS which you've forgotten about. If it is all too confusing for you, show me your FSUIPC4.INI file, and also try enabling Button logging and Event logging in FSUIPC's logging tab, and show me the Log file too. You can paste the text into a message here. Pete

Okay. Download FSUIPC 4.929c. It is also shown in the Download Links subforum. Pete

FSUIPC is only an interface into FS for applications. It doesn't do anything by itself, and certainly it doesn't provide any Flight Management System! That is certainly a job for a gauge or an application! Pete

Ooops! Sorry. It's been that way since 4.921g, last October. If you look at the Changes document, number 4 details new "TimeForSelect" options. They affect all controls which are designed to work with a succeeding "Select 1, 2, 3, or 4" control, and of course that includes the Pushback. The parameter options are for registered users only, but the way I coded it meant that the controls themselves were not registered with SimConnect as events in an unregistered install! What a silly mistake! I'm surprised t has taken so long to be discovered! That is a big bug! I am fixing it now -- in 4.929c. I will advise when it is ready ... Pete

Is there nothing in the FSC9 instructions? If not, that is very bad and you should go to the FSC 9 support forum and register a complaint. If you download FSUIPC yourself you get an Installation and Registration guide which explains things. I suggest you do that in any case as it is likely that the version you have is out of date and therefore unsupported. You only need to purchase and register FSUIPC if you want to make use of the user facilities int contains. Unregistered installs support applications in any case. I would certainly assume so or it wouldn't be installed by the FSC 9 installer, would it? I'm amazed that there's no documentation supplied to tell you such things though. Really all your questions should be directed to their support forum. I really cannot support other folks' software. How did you find this support forum, by the way, if you have no information about FSUIPC? Pete

Same folder as your FSX.cfg, something like C:\<user>\AppData\Roaming\Microsoft\FSX. Whilst you are there check also the DLL.XML and EXE.XML files, tell me what other FSX applications are being loaded. The logs merely show wat we know, that the FSX access is being blocked. If it isn't some sort of firewall I can only think it is some other application. The server just isn't receiving anything at all from the client. Since the code in FSUIPC4 is identical in both P3D and FSX -- they are the same modules and the Server part is 100% the same -- it must be something else installed. Yes, I note that the Client log shows many attempts to connect to "ERAZERSIM", IP Address = 192.168.0.140 but only the last one the successful one (to P3D I assume). The closing summary confirms this: 291219 ********* Interim performance summary ********* 291219 Total time connected so far = 35 seconds 291219 Reception maximum so far: 29 frames/sec, 4178 bytes/sec 35 seconds before 291.219 seconds would approximate to timestamp 256.xxx, which relates okay to that last connection attempt: 254422 Server = ERAZERSIM 254422 Trying TCP/IP host "ERAZERSIM" port 8002 ... 254422 ... Okay, IP Address = 192.168.0.140 254422 Connection made okay! Pete

I've no idea how multiple attempts at running the installer can be any different from one attempt. It just does straightforward things like checking versions and copying files. Your backup should have included the KEY file and your settings (the INI file) from the Modules folder, which would then have given you registered status and settings back. You should in any case download the current version as old versions cannot be supported. If you log into your account at SimMarket you will be able to retrieve your key(s). Pete

What do you mean "program on top of FS2004"? You mean display something? Full screen mode means what it says -- the screen belongs to the program which is using the mode. There's no way anything not in that program can display on top of it. You would need to have it displayed as a gauge or other component. FSUIPC can do it with its display windows only because it is within FS and is calling functions inside FS to do the displays. This is only for text, in the status window or similar. For instance you can use the Lua plug-in ipc.display function for text -- see for example the Log Lvars and Display Vals plug-ins in the pack of Examples installed in your FSUIPC Documents folder. Pete

Reinstalling FSX wouldn't lose it, you must have deleted it explicitly, or reformatted the hard disk. Best to keep backups of all add-ons you purchase! How did you find the Forum? Go to SimMarket for purchase, which also provide the link to the program download on Schiratti.com, or download here in the Download Links subforum. Pete

Odd. you're the third person to say they can't paste into messages. It is very odd. Please see this thread which I think includes an answer. http://forum.simflight.com/topic/76255-wide-fs-connection-fsx/?hl=%2Bcut+%2Band+%2Bpaste#entry464896 Only in the SimConnect.XML file -- you need to avoid ports 8002 and 9002. OR you can change the ports used by WideFS instead (both WideServer and Wideclient). BUT I think really it is more likely that you have installed something else on FSX and not on P3D which is doing it.? Of course, you may have the firewall in Windows set to stop FSX.EXE but not Prepar3D.exe? I would have thought it more likely that such a tool would mess up P3D, not FSX. Why should it do anything to FSX? Pete

No updates to FSUIPC have changed anything relating to WideFS in many years. Evidently you have something set incorrectly for FSX. Perhaps your SimConnect.xml is set to use the same port? No you haven't. I don't think you can attach such files here. Best to simply paste their contents into your message. After connecting? Error 10060 is the Windows error "connection timed out". That will be from the WideClient end. It is being blocked. I am not surprised, because none of those things have anything at all to do with WideFs connections. And because merely upgrading FSUIPC also has nothnig at all to do with WideFS connections, I think somethnig else has changed in your system since it worked. Additionally, WdeFS is EXACTLY the same whether on FSX or on P3D. Which is why I'm suspecting that the ports needed are being taken by something else on your FSx installation, possibly SimConnect or another add-on you've installed. Pete

I don't know where you are looking. There's certainly no "install" button in the FSUIPC4 installer. I think you must be mixing up some other program entirely. When the FSUIPC installer is run it will tell you, one by one, all off the versions of FS it is installing into. You simply OK each prompt after reading it and it goes on to the next. If you were really running the FSUIPC Installer, and not some other program, and it did not find a copy of P3D2.1 to install into, it will because your P3D2.1 installation is bad -- the registry entry for it's install path does not exist. It is that plain and simple. Pete

You have all of the bits in the resulting 1 byte Value. A byte contains all 8 bits. The rest is simple programming! Test them as you wish -- if you don't know how to use logical functions in a program (And, Or, etc) I suggest you get a book on Delphi. I don't know it so cannot give you examples. But to learn about numbers, bits and bytes please see the FAQ subforum -- there's a thread on this subject. Pete

No. and there is no such message. Where are reading this? The installer will automatically install in FSX, ESP, P3D1 and P3D2, any or all. If your current version in any of those is later then it won't replace it. What may be the problem is that you should use the current supported version, 4.929, not an old version. As very clearly stated at the very top of this forum, version 4.929 is the earliest which will work with P3D 2.1 -- version 4.928 was issued before P3D 2.1 was released and cannot possibly work. Pete

You need to be able to run P3D. If it starts then an FSUIPC4.LOG will normally be generated, and will show the point of the crash. Look in the Modules sub-folder. If you have the latest version of FSUIPC4 (4.929) then you can use this unpublished "hack" (in the [General] section of the INI file) to make FSUIPC think the P3D version number is different. I don't like this method, though, as it is highly likely to cause more problems further down the line. I think you need to get FSInn sorted out instead. AssumeP3Dversion=n.n.n.n where the n.n.n.n part is the exact 4 part version number of the true EXE, before your Resource Hacked faking. Pete

The only things which might stop an application interfacing correctly with FSUIPC, on the same PC, are: 1. An invalid FSUIPC registration key. To test this try removing the FSUIPC.KEY file from the FS Modules folder. This will make it unregistered -- the applications interface works with unregistered installs. 2. The computer date being set to one BEFORE the registration, making it look invalid. Check the date. 3. Running FS in "as administrator" mode but the applicationat normal provilege level, or vice versa. Programs at different privilege levels can't talk to each other. Some one else found they couldn't paste into messages here. I don't recall the solution -- some setting in your browser I believe. I have used Firefox for some time, never with any problems, and am now using Chrome, which I'm not so keen on but which is definitely faster. I suspect the problems are with Internet Explorer which has a lot of over-protective features on by default these days. [LATER] I did a search for "cut and paste" on this Forum and found the previous reference to the paste problem, and the answer: http://forum.simflight.com/topic/76255-wide-fs-connection-fsx/?hl=%2Bcut+%2Band+%2Bpaste#entry464896 Pete

Not I, I'm afraid. I don't know VB6 at all. However, if you enable ipc write logging, as I suggested, then run your program, I can look at the log for you. Pete

Okay. Good. Hopefully, then, the OP can sort it out. Pete