Pete Dowson

The problem is that your T-Rudder clashes: 922 Device acquired for use: 922 Joystick ID = 1 (Registry okay) 922 1=Flight Throttle Quadrant 922 1.GUID={38F6A6D0-BB3C-11E7-800A-444553540000} 922 Device acquired for use: 922 Joystick ID = 1 (Registry fixed) 922 1=T-Rudder 922 1.GUID={FE144CF0-B4D0-11E7-8001-444553540000} You defined the T-Rudder as Joystick 1 whilst that was actually assigned, in the Registry, to the Quadrant. Your INI file contains several other oddities, as if it's an old one which has gone through a lot of problems and weird changes. You haven't got much assigned or calibrated yet, so you might be much better off just deleting it and starting again. but if you want to persist then some further changes will be needed. In this section for instance: [JoyNames] AutoAssignLetters=Yes 1=T-Rudder 1.GUID={FE144CF0-B4D0-11E7-8001-444553540000} 0=Flight Yoke System 0.GUID={38F6A6D0-BB3C-11E7-8008-444553540000} A=Flight Yoke System A.GUID={38F6A6D0-BB3C-11E7-8008-444553540000} B=T-Rudder B.GUID={FE144CF0-B4D0-11E7-8001-444553540000} C=USB Multimedia Keyboard C.GUID={2FFA85B0-0242-11E1-8001-444553540000} I'm not sure where you got the USB keyboard listed from -- maybe an old INI file? it isn't recognised as a Joystick type device in the CSV file or the LOG. Delete both C= lines. Then add lines for your other quadrant: 1=Flight Throttle Quadrant 1.GUID={38F6A6D0-BB3C-11E7-800A-444553540000} C=Flight Throttle Quadrant C.GUID={38F6A6D0-BB3C-11E7-800A-444553540000} You also need to delete these lines which refer to a rudder which isn't connected 9=2X,256,D,7,0,0,0 -{ DIRECT: LeftBrake }- 10=2Y,256,D,8,0,0,0 -{ DIRECT: RightBrake }- 11=2Z,256,D,3,0,0,0 -{ DIRECT: Rudder }- You have some very strange assignmentrs to the T-Rudder: 4=BX,256,D,8,0,0,0 -{ DIRECT: RightBrake }- 5=BY,256,F,66387,0,0,0 -{ TO SIM: AXIS_LEFT_BRAKE_SET }- 6=BZ,256,D,3,0,0,0 -{ DIRECT: Rudder }- 7=BR,256,D,10,0,0,0 -{ DIRECT: Throttle2 }- 8=BU,256,D,23,0,0,0 -{ DIRECT: Flaps }- Two different ways for Left and Right brakes? Strange? And 2nd Throttle and Flaps assigned to the rudder? Surely not? Maybe that dates to some time when B was a quadrant? Best delete those two and re-assign. Pete Pete

With what? Can you use a translator. There's really no information I can see in the earlier messages. Pete

No, not for FSX or P3D. wideServer is built into FSUIPC, as the dcumentation tells you. What data? Any parameters you want to change will be in the [WideServer] section of the FSUIPC4.INI file, where all FSUIPC settings are kept. but you have no need to change anything. If you do, be sure to read the WideFs documentation first! The Technical manual describes the parameters. I can't help with PM, but for WideFS the documentation is provided as your "helping hand", though you shouldn't need much of one. Pete

Read the WideFS documentation, not the very outdated PM stuff. WideServer.DLL was used with FS9, never in FSX or P3D. The WideFS files, including the documentation and the WideServer.DLL for FS9, are all in the WideFS download. Where on Earth did you get WideClient.EXE from, which is the part you presumably think you "installed" when you say: The fact that you keep calling it "FSWide", which is never a product of mine, is worrying. Perhaps you are talking about something completely different? Pete

Aha! Excellent! Thank you very much, Luis! So, then, what would the "require" declarations need to be in your Lua code as I'd like to document this in the installed Lua PD). You'd need to provide for the missing 64-bit socket.core, mime.core DLLs which were buillt into 32-bit FSUIPC, and presumably also the ltn12.lua, socket.lua and mime.lua which I also included? Sorry if I appear ignorant about this stuff, but, in fact, I am! :-( Thanks, Pete

This certainly appears to be a P3D bug with certainly add-on aircraft. I have no quick references, but check the L-M support forums. It may well be fixed in the 4.2 update due soon (I hope). Just having some add-on aircraft installed often enables DLLs they install, so you might need to test with those disabled. I should add that I cannot reproduce andthing like this here, or any of my 3 systems running P3D4 (one on Win7, two on Win10). But then I don't have any 3rd party aircraft with their own DLLs installed. Pete

You definitely have something wrong in your program, then, or you are asking FSUIPC to do something which takes a long time and hence pausing FS9, like loading a new flight or aircraft every 250-500 mSecs. But you'd certainly notice that! Pete

There's never been any changes in any varsions of FSUIPC4 which will do that. The assignments and profile settings are the same. And if you just "upgraded to 4.971", why wasn't the INI file there still from the previous install? Installing FSUIPC updates touches neither your settings nor your registration. Surely you didn't delete everything? In that case the corrent INI is not in the correct place. Please show me the FSUIPC4.LOG file in the place whereyou think you placed the correct INI. Maybe also show me this "correct INI" in case it is not actually quite correct. Pete

Possibly a mismatch. I don't know Arduino, but it looks like the "Serial.print" function sends exactly the numerical value of what you give it, not the character it represents. 255 is hex "FF" which realy has no normal printable character reprsentation, but 48 is the code for the character '0'. Maybe the Arduino Serial.read function doesn't wait for characters and returns 255, or more likely -1 (which would look the same as 255 is only an 8-bit part was used) if no data was (yet) available. Either way, I think you need to investigate the Arduino side of things. Pete

Sorry, I don't know why either. May be worth asking on the Lua website. Not sure of the actual link to a support forum, but start as lua.org. What actually was the "didn't work"? Gave an error, or obtained incorrect values? BTW, you are using an expanding array but only seem to use two elemants at a time: indexed and [i-1]. why not make it more efficient using just a "current" and "previous" value and moving one to the other? Even a small structure with your v, t and e in it, to make it a one line copy over. And elapsed doesn't need to be an array as you only use the first and the current. Pete

Does the JS41 come with an SDK folder? If so, check the file with filetype .h, to see if they have custom controls like they do in the 737, 747 and 777 products. Otherwise your recourse will be one of the following: 1. Use FSUIPC logging to see if any relevant Events are produced by that key (log events via Logging tab) 2. Log Lvars and see if an L:var can be used to control it There's an added FSUIPC control to list L:Vars and their values, and there's also a Lua plug-in in the Examples ZIP which will show them on screen in real time, as they change. 3. See if a mouse macro can be created for the button (not available in P3D4). BTW there are a couple of threads about the JS41 in the User Contributions subforum above. Might be worth looking through those too. Pete

Okay. Will do, ready for next release. Thank you! Pete

Yes, I have 2 x GF-RP48s, 2 x GF-P8s and 2 x GF-T8s, with all switches and knobs working perfectly through FSUIPC using GFDev64.DLL. I have no other Goflight software installed, however. Does your FSUIPC5.LOG file show that GFDev64 has been located and loaded? My log shows: 344747 Using "E:\Prepar3D v4\Modules\GFDEV64.DLL", version 2.2.8.0 344747 GoFlight GFP8 detected: 2 devices 344747 GoFlight GFT8 detected: 2 devices 344747 GoFlight GFRP48 detected: 2 devices The number on the left is just how many milliseconds since FSUIPC loaded. Pete

There's no trial version of FSUIPC, never has been. I'm closing this thread now. If you can't even supply a log showing the problem then I cannot help you. There's no point in tis futile discussion continuing. I support and fix problems IF there's information from those who encounter them, but you simply do not cooperate. Pete

Why? What is it you need to do which can't be done in the PFC options? Pete

I know the ADI or PFD (as it is also known in the 737 -- my cockpit is a 737. But the function of the INS in that is not needed on a simulated cockpit which does not feature an INS instrument. Is that the Airbus you are using, or something else? Oh, so it's an F-104. Is that an add-on freaturing an INS? If so you need to find out what is needed to operate that, then assign your switch to its controls as appropriate. Becasuee as I said there are no controls in the default sim because the function is not simluated. Pete

There would be for a particular add-on aircraft, but currently none of the FS-based simulators simulate the IRS by default. You'll get an IRS capability in the FSX A320 and presumably the Aerosoft one too. "Attitude direction"? Er, what's that, and how is it related to IRS? Sorry, you'll need to explain what you thonk mean by an "attitude" indicator. Do you mean the horizon level on the PFD attitude indicator display? How do you think that's related to the IRS, which is a system which keeps track of the aircraft's movements across the globe in order to determine position (Latitude and Longitude) based on a known start position. So how are you expecting to control something you haven't got? Pete

I don't think you have, unless you are running with an unregistered FSUIPC. I need to fix whatever it is in case it affects others, whether you are interested in a fix or not. But if what 2actually worked" is not registering FSUIPC and so not using any of its facilities, then it is not the solution! Well, thanks,, but how am I supposed to even start to do that with no useful information, simply becaue you refuse to supply it? There are no other reports at all, and it certainly doesn't make sense to me with the information you have so far supplied. The logging FSUIPC produces is precisely for such an eventuality, and all I need you to do is show me that logging! And "finally" is an odd word to use when this was an unreported problem until your post of just 9 hours ago! If you are not interested in assisting in this way, then it will be ignored as a non-bug, just a problem in your system. Pete

Ah, so the FLT file isn't relevant. That was only needed it it loaded the flight plan for you, as happens if, for example, you save a flight when the plan is loaded. In that case i'm rather puzzled. i'm away now till Weds 15th Nov, but I've made a note of this and will do some further hecks when i get back. It isn't a big deal at all unless an FSUIPC application uses the plan path for something. Pete

I don't know of a way I can do it programmatically. But then those Windows (FSX? P23D3?) are created by a hack into WINDOWS.DLL, and it may be that it would be possible if I could identify the right things to tweak. But I'm really not doing any more hacking into code. I've not done anyin P3D4, and those Windows just use standard SimConnect calls. And oyu can only have one, and you can't set your own titles. I think there may be a way in to control it for all SimConnect windows, but whether it applies to the ones Lua creates I don't know. You can undock the windows which would give a solid colour background. What I usually do is move the display to a part of the screen with a contrasting colour, like the sky. but i suppose if that's complex cloud graphics it doesn't help. Pete

Of course. It is a licenced user benefit. Without being registered FSUIPC acts ONLY as an interface for other programs. That's its free function and has been since 1998. The licencing simply enables all the USER facilities. You also didn't read my last message properly. The Previous flight file is ONLY created at the end of the session, for the reasons I stated. If you are getting it created more often then there is something else wrong which i would like to solve. And merely not writing that FLT file will not solve problems of "Simconnect failing to send data". After a close down notification to FSUIPC, FSUIPC disconnects from Simconnect, of course. THAT is why I asked to see a Log file with this occurrence happening. Why do you refise? I KNOW the feature, and it is harmless and operates on session shut down only. If FSUIPC senses a shutdown then other things will also go wrong. I need to identify the cause, not give you a new switch which should be completely unnecessary. Please PLEASE actually read what i write! I would like to solve the problem, not just add yet more options, but since this only appears to affect you, I need more data, which is what i asked for! If you have had this weird problem for "years" as you say, why have you never come forward and stated so, AND supplied data about it? I HATE bus in my software and do all I can to fix them as fast as I can. FSUIPC is continuously updated both with improvements and new facilities and as part of that I fix any other problems people have. Unless you can find the time to at least generate a log of this occurring and supplying it,I cannot do a thing. Pete

Yes, of course. It is only executing existing macro files, ones you can assign. It uses the offsets you can program to. Macros are any macro file containing one or more commands. The term "mouse macro" refers specifically to a macro file created using the mouse macro facility, where FSUIPC records actual code positions in the add-on Gauge DLLs to which it will jump when the macro is instigated. Mouse macros are but a small and increasingly insignificant type of macro file which work in less and less aircraft because of the lack of use of the old C/C++ FS2002 SDK libraries and code examples for building gauges. I doubt if anything like that will ever be available for P3D4, though I've asked L-M if there's any way they can do something to the same effect without having to make direct calls into their code. Pete

For which options tab? The Profile name is only applies automatically to Axes and Calibrations. With Buttons & Switches, and Keys you have the general non-profile assignmetns presented first, and the Profile ones (which may override the others) when you check the "use profile" option. And of course the profiles don't apply to the other option tabs. Which version of FSUIPC are you using? Pete

Is this a rotary giving digital pulse outputs, configured as such on the Leo Bodnar connections? Are you assigning buttons or analogue (axis) data? And to which controls? A digital rotary encoder properly decoded will give pulses on one button number going on and off when turned one way, and a different button number when turned the other. But some rotaries just pulse the same lines, but in a different phase depending which way they are turned. It is much harder to properly decode those as you just see the same buttons pulsing. I don't know if the Bodnar boards handle that or just pass on the pulses for you to deal with. If you have to do it please see the examples described in the FSUIPC advanced manual, towards the end of the section entitled "COMPOUND BUTTON CONDITIONS". Pete

This is not in any way realted to autosave. Previous flight files are ONLY created when FSUIPC receives a closing down notice from SimConnect. It is to provide a facility which was provided in FS2004 but seemed to get lost in FSX. Previous flight files are useful when folks always want to start up their next session from where they left the aircraft last time -- all that is then needed is to set the Previous Flight file as the default. If you are getting Previous Flight files saved during a session when something, somehow, is telling FSUIPc things are closing down. Maybe you should show me a pertinent log? Pete