Pete Dowson

That's what you said, but then you didn't show the logging which might tell me why!!! The point of logging things was to show what actually happened. There's no point otherwise, don't you see? In any case there's obviously a discrepancy between your stated assignments and the actual ones in use. You'll need to make sure that confusion doesn't still exist when you try changing to the other suggestion. Regards Pete

As far as I am aware, for all purchases on SimMarket you just open your Account to retrieve your registration keys. I don't receive tham by email when I purchase things. Did you look? Regards Pete

That's the title of a Downloadable file, it isn't a thing you purchase. Anyone can download that and install if for free. You can purchase the Registration for FSUIPC plus WideFS, or just FSUIPC, or just WideFS. The choice is yours. If you want both the bundle is cheaper. You'd have both WideServer and FSUIPC4, because they are both part of the DLL you'd install. Whether they are registered or not depends on whether you purchased keys for them and Registered them correctly when installing. For WideFS you also need to download the WideFS7 package in order to get the documentation and the Client to run on your other PCs. Pete

You posted this three times within a few minutes of each other. Please don't do that. I've deleted the other two copies. FSUIPC3 for FS9 and FSUIPC4 for FSX. There are not cross-compatible. You'll need to buy both WideFS6 and WideFS7 and register both. WideFS is in two parts - Server and Client. The Server is speciific to the version, FSUIPC3 + WideServer.DLL , or FSUIPC4 with server built in. The thing that runs on the remote PC is the WideClient, and that is common to all versions. In the WideFS ZIP of course! Pete

In that case you must have had conflicting assignments somewhere in the earlier INI file. Regards Pete

If it couldn't find your FS installation, it would not have been able to save it. You have to save it manually via the File menu on the displayed log, when if prompts you as installed or to find FS9.EXE. BTW when it did prompt you to find FS9.EXE, did you do so, and what did it then do or show? Pete

The Installer ONLY replaces FSUIPC4.DLL with the updated version, and replaces the documents in the Modules \ FSUIPC Documents folders with updated ones. It checks that the DLL.XML is set correctly to load FSUIPC4. It writes a new FSUIPC4.KEY file if you re-registered. And that's it. NOTHING else whatsoever is touched, and FSUIPC4 itself does not touch any files outside of its own Modules area. Therefore I'm sure you have a corrupted FSX install. It won't be FSUIPC related -- that it happened at about the same time as you updated is merely a coincidence. I think you've proven this conclusively by the fact that you get the identical problem with or without FSUIPC being loaded. I can only suggest repairing your FSX installation. Regards Pete

FSUIPC4 recognises POVs as both Axes and as a set of (usually) 4 or 8 buttons. You program is in one or the other tabs. It really depends on what you want to use them for. Hmm. Not so sure about that. It depends whether OPUS is written to access devices using DirectInput or the easier to program but more limited "joyGetPosEx" API. FS itself changed over about FS2002 time. FSUIPC3 uses the older interface, but FSUIPC4 doews use DirectInput. The difference in your case is that whilst DirectInput recognises 4 POVs per device, the older joystick API only recognises 2. Regards Pete

I'd use "strlen(Metar)+1" instead of 42. The length must include the zero terminator. For the METAR format needed, please refer to the SImConnect SDK -- function SimConnect_WeatherSetObservation. FSUIPC simply passes your string to that function. I think you might get away with: KSEA METAR 030405Z 270007KT 15SM SKC 17/13 A2992 Don't forget, if you are writing a lot, do the Writes first with one Process at the end. Regards Pete

All you needed to do was rename the DLL to, sa,y DLX, so it doesn't load. What do you want to do? If you want to use FSUIPC you'll need to install it. Without Regstration FSUIPC doesn't touch any devices whatsoever. Regards Pete

All files which have anything to do with FSUIPC are in the FS Modules folder. The ones you should copy over are: FSUIPC.KEY (your registration) FSUIPC.INI (all your FSUIPC settings) plus any .MCRO or .LUA files you may have installed or created. Those are Macro and plug-in files. Regards Pete

I only need to see the WideServer and WideClient log files. You've shown me the WideServer log, which shows it is working fine, but not the WideClient log, which is undoubtedly where the information needed lies. Did you try putting in the client ServerIPAddr and Protocol parameters, as suggested in the little "must read" part of the User Guide? Regards Pete

There's no difference, it is still there. Pete

What, don't you know what you want to use it for? Rotary encoders vary. The easy-to-program ones send one button number for one direction and a different one in the other. The more complicated ones send both in both directions, but in a different phase. You need to determine what yours does first. Pete

It sounds like your FS9 installation is more damaged than merely the registry. But I'd need to see the Install log to help. Regards Pete

In FSUIPC you can't directly assign keypresses to keypresses -- for what should be reasonably obvious reasons. Generally there is never a need in any case. There are ways round it (using FSUIPC "krypress/release" controls), but they are fraught with difficulty and unreliability, because the real key down/ keyup messages get intertwined with the mapped ones, and the end result is not easily predictable. It sounds like you only have one throttle lever, right? The best bet is to use the FSUIPC Offset controls to access directly the value in FS which those E+ keystrokes affect. That is 0888. Assign your choice of key for engines 2+3 to Offset Byte Set with x888 in the offset field and 6 in the parameter field (4=eng 3, 2=eng 3, 4+2=6). Assign your choice of key for engines 1+2+3+4 to Offset Byte Set with x888 in the offset field and 15 in the parameter field (8=eng 4, 4=eng 3, 2=eng 3, 1=enf 1, 8+4+2+1=15). Regards Pete

I think error 740 means that the program cannot be executed because of a difference in privileges. If you are running FS "as administrator" and Linda.exe is not set to run in that mode, or vice versa, I suspect you'd get such an error. You shouldn't need to run anything in administrator mode, but if you run one thing you have to run all related things in that mode. Sounds like you've not calibrated them properly. Please follow the numbered staps in the Calibration part of the User Guide. Any range of inputs will map to the full needs of FS once proper calibration is performed. In fact that's really the whole point of the exercise. Regards Pete

But unfortunately the log extract you showed me only shows button 2 being pressed and released once, and button 3 pressed and released once, so naturally you'd get one increment and one decrement. There's also another strange thing. Look at this and then compare it wityh the setting you said you had in your message for button 2: (75=P72,2,Cx42000BC0,xC00101F4) Evidently the lines you are showing me from your INI file are NOT the lines being used, so either you are looking at the wrong INI file, or the wrong [buttons] section in it! Perhaps next time you'd better show the whole INI and the whole LOG if you can't find the right places? Also, please, on the right-hand side of the Logging tab, enter 01F4 as an offset of type S16 and check the "norml Log" option below. That will give use the value off the offset for each change your assignments are making. Regards Pete

How is this input occurring? Do you have a driver for this card? If so does it emulate a joystick, in which case it should show up as an axis in any case, or does it have an FSUIPC interface and send the data to an offset? If there's no driver, and you have to resort to reading the USB data directly, as a HID device ("Human Interface Device"), then it can be done but you'd have to resort to some plug-in programming in Lua, using the Lua com library hid functions. Regards Pete

Why did you uninstall? If you deleted your settings and your KEY file then either restore them from your backup, or you'll need to re-register and re-establish all your settings. There's really never any need to uninstall. If you've tried to re-register and your key isn't accepted you are making a mistake. As suggested above, find your full registration details and enter them exactly. Pete

Sounds like a bug in this "RwyAdv" module. Have you reported it to the author or supplier? Maybe he's hooking into FS and unhooks without taking into account other possibly programs also hooking in. I looked up R6025 and found this (my red highlighting): ------------------------------ The C++ program fails and reports the following run-time error: runtime error R6025 - pure virtual function call Cause: This error occurs when your application indirectly calls a pure virtual member function in a context where a call to the function is not valid. In most cases, the compiler detects this and reports the error when building the application. But depending on how your code is written, sometimes the problem is detected only at run-time. The error occurs when you indirectly call a pure virtual function within the context of a call to the constructor or destructor of an abstract base class. Resolution: Calling a pure virtual function is a programming error, so you need to find the call to the pure virtual function and rewrite the code so it is not called. ----------------------------- So I suspect the fix will be easy for the author. [LATER] I have RwyAdv installed also. Seems to be part of the freeware RAAS package. I never noticed any problem when I was using that. Currently it is disabled because I upgraded to the payware RAASPro. Regards Pete

Nothing in either Loader or the FSUIPC proper can affect whether FSX freezes later -- once FSUIPC is actually loaded and running the problems of FSX crashing when it is started are long past -- the initial crash is not even in any Loader or FSUIPC code, it is in SimConnect when it is trying to load it. The odd thing is that this problem is rare -- out of all the thousands of users it only affects a few -- so it is a very complicated timing glitch (which explains why Microsoft never managed to fix it -- though they did lessen its likelihood in SP2/Acceleration. In the original and SP1 releases it was much worse). I would be delighted to try to fix it once and for all, but I have to actually be able to reproduce it. It has never once been a problem on any of the 6 systems I've installed it on, whether XP, Vista, Win7 or Win8. Since the exact cause is indeterminate and it isn't within the code I have control over, the solution is only that already proposed in that FAQ thread -- persistence. In all the cases I'm aware of, persistence has paid off. Once it is loaded ands registed in FSX.CFG as Trusted, it doesn't recur. Regards Pete

No, providing it stays there. FS9 will only load DLLs in the Modules or main FS folders. Just make sure there isn't another one in the main FS folder. Did you make sure Windows USB power management was turned off on all listedhubs in the Device manager? Purely user preference. I don't like any of the Saitek stuff myself, so wouldn't use it in the first place.. Regards Pete

No problem. Glad you pinned it down. The Norton false alarm has been reported elsewhere too. Seems to be the only AV doing it. See thread http://forum.simflight.com/topic/74359-norton-anti-virus-and-3999z2/ Pete

That does sound like either software interference, or more likely an disconnected and possibly ancient (game port even) type joystic kdriver sending signals. Disconnection looks exactly like a full on or off spike. There is a spike suppression facility in FSUIPC which you could try, but it would be best to find the source. Nothing's changed to do anything like that in my software. I've no idea what "a EngineXThrottlePosition = blah" is. Sorry. It isn't one of my messages. Is this maybe a question for Linda support, if that's where it's from? The fact that it all "went away" for a significant period, then came back, points to something more hardware, temperature or condition related. Software really doesn't do that sort of thing, at least not voluntarily. I'm afraid I'm now off for a long weekend (steam train tour in Ireland). I'll be back on Wednesday next week. Regards, Pete