Pete Dowson

Please ALWAYS post FSUIPC support questions to the FSUIPC Support Forum, i,e, here. You need to state the version number of FSUIPC and that of FSX (Original, SP1, SP2 or Acceleration?) And please don't use so many CAPITAL letters. It comes across as shouting! Pete

I shouldn't think so, but I'm not the right person to ask. You'd really need to apply to SimMarket. The problem there is that you can't reach them by email. You'd need to open an account then post a problem ticket". Pete

I've made a change already which may help, but I won't have time to test till tomorrow. If youcould test it for me, when you can, and let me know, downlaod it: http://fsuipc.simflight.com/beta/WideClient714a_TEST.zip Leave it running for a while if possible, please. Thanks, Pete

It looks like this is the same error reported in another thread near here Could you follow the replies there now please, save me updating both? I'll be working on this first thing in the morning and will advise there. Pete

I'll look into this in the morning. I have some ideas but I need to set things up to try something. I was about to release another Wideclient update with other improvements in any case (for the ext library in Lua plug-ins), so I'll try to attend to both together. Can you say how longit takes before you get the errors (the first error line in WideClient will tell you, e,g, 83585 New Client Application: "pmsystems" (Id=168) 116345 ###### ERROR: Data Requests Overflow! in the log fragment you showed me. So 116345 - 83585 = 32760, or a little under 33 seconds, are they all about the same? Pete Pete

Strange. I have a 7 PC system too, linked by WideFS. Are they the errors filling up your very large files? The WideServer.LOG you attached is no good -- all the connections are to wideClient 6.999. I need to see the one relating to the problem session. Pete

Must have been some sort of ocrruption in the 4.2 installations, somewhere. I'm glad it is now resolved! Pete

I tried your Lua program with FS-FlightControl, and I managed to make some improvements to the way FSUIPC gets hold of the Window handles. As far as I can find from all my testing here, your Lua now works -- except of course where you have mistakenly used "postmessage" instead of "postkeys". The message one needs full details of which message and its parameters. It is for programmers. Instead of starting FS_flightcontrol and having a fixed delay (which isn't long enough here unless it has been loaded before in this Windows sessio), you should use a loop, perhaps checking once per second, with an included sleep of just 1000 (1 sec), and have a fail exit after, say, 20 or 30 loops. I will release an interim update with the fix, probably tomorrow -- but possibly not till Wednesday, as I have folks here dealing with other things. Anyway, look out for an update in the Download Links subforum over the next few days. Pete

FSUIPC5 is needed for P3DV4 as the latter is a 64-bit program and 32-bit programs will not work inside it! No, there is no discount. The was one for the first three months, long gone. Please always post support questions to the Support Forum, not into Sub-Forums designed as reference places. Pete

Send as email attachment, to petedowson@btconnect.com. Don't forget to stsate this thread's title. And please try both full screen and Windowed mode. Also tell me what video driver you are using, and its version number. Pete

You'll need to use different SendKey numbers (the parameter in the assignment and the number on the left in the Wideclient.INI preceding the =). you do have 255 to choose from! Pete

Yes, mine has 8 PCs! * One for P3D4 and ProSim main and MCP, and ASP4, * one for ATC and ProsimUtils, * One for the EFB (FS-FlightControl now, used to be Aivlasoft's EFB), * two: one each for the two CDUs * one for the main PFD displays, * one for the EICAS display * one for PFPX and TopCat, and for monitoring the cockpit from downstairs in my office Apart from on the EFB (a touchscreen inside the cockpit) I have two other licensed installs of FS Flight-Control, as well as a "trial" one, unused, on the P3D PC just to generate the data it needs from the correct scenery files. Ah. I really MUST read documentation properly! I keep exhorting my own users to read the stuff I supply! (Do as I say, not as I do! ;-)) Ah, that's a different matter. Tell me, does the remote copy have focus when you use these "SendKeys" assignments? If you need it to have focus on the FS PC, then FS will lose that focus. That could result in a loss of FS sound and a slow down (less frames per second). Yes, you can. You need to change the ClassInstance parameter in the WideClient.INI file to something other than 0 (1 will do). Yes, another line. To overwrite an earlier line you use line > 0, and erase those below ready to rewrite. Okay. If I get time I will try your Lua script on my est PC, where I can run both P3D4 and FS-FlightControl at the same time. Pete

What is "FS-FlightControl remote"? I use FS-FlightControl and I don't think I've come across a different version. Actually I didn't even realise there were keyboard shortcuts for FS-FlightControl facilities. I'll have to check into the documentation more! SendKeys is only used by FSUIPC. It's an encoded message sent to the client like any other Sim information. Unless you write a program to link to WideClient in the same way FSUIPC does, using the same (undocumented) protocol and the apropriate Network code, you cannot instigate them without the link to FSUIPC. I don't understand why you'd want to in any case. What is "line negative"? You need to concatenate the text before sending. FSUIPC is simply calling on a SimConnect function to display the text. There's no way to amend something already sent. It's out of FSUIPC's control by then. You'd need to replace it. Do I need that for something? Pete

That's very strange. They are just simple bitmaps. Can you show me a picture? Pete

You need to press them together -- i.e Ctrl+Shft+F1. As you would for the Sim or anything else needing combinations. The message doesn't arrive otherwise --the F1 or a main (non-shift) key is required to get the proper message which FSUIPC can intercept. The Shift keys are just flags which arrive with the message. And only one 'normal' key can be part of the entry. One, so "a+k" is just "a". Which control are you calibrating? Do you mean there's no Slope button? Pete

Deleting the DLL and installing the same one again cannot make a difference. Maybe you mean you deleted everything including all your settings? Not a good idea really. Best to find out what is wrong and fix that. Apart from PMDG's own controls (assigned as <custom controls> in FSUIPC), as mentioned by Thomas, the usual way (for most jet aircraft -- not sure about PMDG ones) is to assign "Cut Off" to the "Mixture lean" control and "Idle" to the "Mixture rich" control. With P3D default keyboard assignments those are Ctl+Shft+F1 and Ctl+Shft+F4 respectively. Try those with the PMDG aircraft. If they don't work then you'll need to use PMDG controls or shortcuts. I don't really know what you mean by "When I press the selected keys after pressing Set, nothing happens." Are you saying no key names appear in the little box above? Otherwise I don't know how to interpret it. But, in any case, as I said above, you'd be better off using the controls which P3D assigns to those keypresses rather than the keypresses themselves. Pete

You don't say you can't steer the aircraft whilst taxiing, which would reflect problems with the controls, which is what Thomas is asking about. If you just mean what you see on screen, I think there's a general problem with nose wheels not reflecting the state of the steering tiller in P3D4 (maybe 4.2 only?). I seen it reported quite a lot elsewhere since 4.2 or maybe 4.1 was released. FSUIPC doesn't have anything to do with the on-screen graphics I'm afraid. Pete

I know. I wouldn't have been. That was actually the point -- if it was already there you'd not change anything by adding it! ;-) (I actually said "One thing you can try in FSUIPC is to set "UsePDK=No" into the [General] section of the FSUIPC5.INI file. Or change "Yes" to "No" if it is already there.") As Thomas said, those were only half the DLLs. As I said: "Please find both DLL.XML files and both EXE.XML files (there may only be one of each, or even none of EXE.XML) and show me. One set will be in your user Appdata\Roaming P3D4 folder and other in the ProgrmData P3D4 folder. The Joyscan file shows nothing untoward. Just the single device, your Logitech Extreme 3D. I don't expect that could cause a hang, though FSUIPC will of course be scanning it, but eliminating that might be something to try further down the road. Pete

The only change from 7.10 is that WideClient now works with 64-bit client applications. There's been no change in offset reading/writing. So, is there an actual connection? It sounds as if you are saying there isn't. If there isn't I need the WideClient.LOG and the WideServer.LOG files. If there is, I certainly need much more information. WideClient doesn't differentiate between offsets, they are all the same to it, and it is working fine here with my installations. If I knew the offsets being read I could make a test specifically with those offsets (via a Lua plg-in probably, or just using FSInterrogate). Put (or change the existing line) Log=All in the [User] section of the WideClient.INI file. Reproduce the problems then ZIP the WideClient.LOG file and attach it to a reply here. Pete

Wow! Congratulations! And I thought I was getting on, being 75 this year (not till August though). Pete

This problem seems to be unique to you, so it simply must be related to something in your specific system. According to that last file you attached, it's actually a hang, not a crash, which is why you get no crash report. A hang is rather different. I still need to see the DLL.XMLs and EXE.XMLs. When you updated to P3D4.2 did you do a full install? There are known problems if you don't also install at least the Content. It is also wise to delete previously generated P3D files -- you can do that by executing "Delete Generated Files" which you'll find in the main P3D folder. You'll need to run FTX Central again afterwards to get its changes re-installed, but otherwise P3D will make everything else afresh. [LATER] One thing you can try in FSUIPC is to set "UsePDK=No" into the [General] section of the FSUIPC5.INI file. Or change "Yes" to "No" if it is already there. Also, try renaming your FSUIPC5.INI file so a new default one is produced. And could you attach the FSUIPC5.Joyscan.csv file, please? (ZIP it if the Forum doesn't like that filetype). Pete

You need your original SimMarket email address and password to get into your account and retrieve the details. You must always register FSUIPC with the exact same name, email and key as frm the original purchase. Even I cannot retrieve the details using a different email address. You need to find or remember it yourself. I could retrieve it using the SimMarket order number instead. Certainly not with your new email or just your name. Surely you still have something in your archives or backups relating to your original email address? Why didn't you back things up in the first place? This is always important for all purchases involving a registration key of some sort. [LATER] Luckily I found it! There is a registration using herb@sympatico.ca for a Herbert Krosta dated 06/11/2010, so evidently the only change in your email was "herb" changing to "herb_k". Seems to be a pretty easy change to remember! ;-) Pete

You definitely have something seriously wrong with your P3D4 installation. There are very many users quite happily using it with 5.124. Earlier versions had problems with 4.2, for sure, but they are most certainly all fixxed in 5.124. If it isn't P3D4 itelf it must be some other add-on or add-in. Please find both DLL.XML file and both EXE.XML files (there may only be one of each, or even none of EXE.XML) and show me. One set will be in your user Appdata\Roaming P3D4 folder and other in the ProgrmData P3D4 folder. There may also be addons loaded by Addons.xml files. Do you have any in your Documents P3D4 add-ons folder? If so, try renaming the folder, temporarily, to see if it helped. BTW even if it "disappears without trace", Windows often records the reason. Please use Event Viewer and see it did. I'd need the details. Without those, even if it was FSUIPC, I've got no chance of locating it. Pete

When did you go there, because the link there points to exactly the same version and would have been updated simultaneously. The only versions are actually stored here on SimFlight and i update the files at the same time, though the text on the Schiratti site is often out of date waiting for Enrico to update it. You don't take backups? Anyway, you checked this yourself it seems, as you said this: Maybe the Profile you were checking wasn't the one currently in use. Did the name at the top of the Options tab display match the name of the Profile you checked? Note that for Buttons (but not axes) the Profile selection checkbox needs to be checked to see the Profile name and assignments, which override the default assignments in any case, which may be blank of course. Well, FSUIPC and the INI won't change themselves overnight. Especially if the PC was switched off! Certainly, I can check the INI file, but I'd also need the corresponding Log file of the incident to match the aircraft name to the Profiles lists. Not sure why -- but it doesn't matter as I really don't like screenshots in any case. They rarely tell me anything that a proper description and supporting files cannot do better. Mode3? FSUIPC knows nothing of "modes". Aren't you always in "mode3" whatever that is? What does it change? What was the displayed joystick number at the time you did the assignment? It's a different Joystick number, yes, for sure. That can happen, usually if you unplug them and plug them in again, or update windows. there's might be other reasons. This is why I always recommend using Joy Letters instead of numbers. FSUIPC then keeps track of the devices using the names and GUIDs and associates the same letters to them as before so that assignments, then all with letters, still work. There's a whole section in the User Guide about this. Pete

Did you RESET first so you could re-calibrate, as your calibration will be all wrong otherwise. Pete