Pete Dowson

Aha. There's the problem: DirectInput8Create failed, return = 80040154 There's another thread featuring a Saitek device with the exact same problem. See here: http://forum.simflight.com/topic/76089-directinput8create-failed-return-80040154/ FSUIPC is reporting an error occurring in Windows when it tries to access the device as a DirecInput device. I am now suspecting an incompatibility between Win8.1 and certain Saitek devices. You could try uninstalling the device (frm the Windows Control Panel-System-Device Manager list), ensuring you also remove its driver if possible, then re-booting the PC and letting it be found again. Pete

Installing FSUIPC never changes any of your files or settings, it only replaces the FSUIPC program (DLL) itself and updates documents and examples in your FSUIPC Documents folder. You should back up your settings for sure. Copy all .KEY, .INI, .MCRO and .LUA files from the Modules folder to a safe place. Pete

Hmm. Sounds like there's a Saitek driver blocking it. Are its buttons recognised in the Buttons & Switches tab? Try this: add these two lines to the [General] saection of the FSUIPC4.INI file: Debug=Please LogExtras=x200008 Then run FSX and try again in the Axes tab. Then close FSX, and paste both your FSUIPC4.INI and FSUIPC4.LOG files back into a message here. Regards Pete

Okay. That's good. Now in the FSUIPC Axes tab, when you move the levers sufficiently (from one extreme to the other), they should be recognised and you can assign them. Regards Pete

Oh, sorry, I didn't realise that was not already being done -- either by the Phidgets code or by iFly's own A/T code. Othercockpit builder software like Project Magenta, ProSim and SimAvionics normally do that for A/T, just monitoring the axis values for override by the pilot. Yes, if that is not done you will certainly get the affect you describe, because the FS throttle is being controlled by both the A/T and the axis values. You can't do it in FSUIPC alone because, although you could set the appropriate offset by an assignment (perhaps a dual assignment along with the A/T switch), in order to keep the axes disconnected the bits being set need renewing every few seconds -- there's a safeguard against a disappearing application so that throttles aren't lost forever in a session. Si you'd need a Lua plug-in which checks for AT being enabled and if so sets the disconnection bits in offset 310A at 5-8 second intervals. You'd need to detect A/T being enabled -- if iFly uses the FS A/T that is easy. If it does its own thing you might need to link to it using that iFly2FSUIPC program or the Phidgets programming. Regards Pete

Very odd, because the change I made is nothing at all to do with G3D nor PANELS.DLLs. These crashes are on shutdown, I take it? There's been no change except for the hook removal at shutdown. FSUIPC does have a hook in G3D.DLL -- its the patch to cure some of the well-known G3D crashes. There's also one in PANELS.DLL in order to implement "mouse macros". I can only think that your aircraft add-on is somehow managing to continue on, using FS facilities to execute itself, long after FSUIPC has been told to close down. I've never encoutered anything quite as strange. I might take a look at those two hooks, to see if they can be easily undone before FSUIPC disappears, but I won't promise anything. It looks best if you retain that Terminate time fiddle. Okay. The removal of the hooks I've already done will still be occurring, before this delay, in any case -- so this at least proves that change is working. It is just insufficient. Okay. I might do, but not as a top priority. I'll add to this thread if I do. Regards Pete

Sorry, no idea. I've never used either FSINN or Squawkbox. Don't they have a support forum? Pete

It sounds like the motor control is from an offset in FSUIPC which is in conflict with whatever iFly is doing. I'm afraid I know nothing about either the iFly implementation nor Phidgets. I don't think iFly use FSUIPC at all, but you can use a program called iFly2FSUIPC to map stuff between them. Maybe you need to use that to get the actual iFly throttle values for Phidgets to read? If the Phidgets programming doesn't allow you to change to iFly2FSUIPC mapped offsets, maybe you can use a Lua plug-in to fake the offsets it is using with the values fromiFly. There's an example Lua plug-in in the package of Examples installed in your FSUIPC Documents folder which shows how such "spoofing" is done via offset 0024 (see "Liar.lua"). Does iFly support Phidgets directly? Sorry, I've no idea about that. Regards Pete

FSUIPC uses the same DirectInput system to read the joysticks as FSX, so I would have thought the results would be the same. Does FSUIPC list your joystick, with its allocated number (0-15) and its "GUID", in the FSUIPC4.INI file? It'll be in a section like this: [JoyNames] AutoAssignLetters=No 0=Saitek Pro Flight Throttle Quadrant 0.GUID={B0ABDEC0-6DA5-11E0-8001-444553540000} Pete

FSUIPC4928a.zip To test, just put this version into the Modules folder, replacing 4.928, and remove the ForceTerminateTime parameter. Hopefully the undoing of the Hooks will solve the problem in a tidier way than using a delay. If not, well, it was worth a try! ;-) Thanks, Pete

If FSUIPC detects the joystic it will show the axes. Sorry, I may be misunderstanding you. Perhaps you can give more information? Pete

It will look exactly like that until you move an axis which it can recognise. If it doesn't see any axes then you have some driver which is preventing it, or your device doesn't actually have any real DirectInput axes. Does FS recognise any axes? FSUIPC is only using the same DirectInput facilities as FS. Pete

Okay. The other way around that is to provide the ServerName and Protocol parameters in the WideClient.INI file. Then it isn't dependent on the Broadcast messages which don't operate over different workgroups. Hmm. Another one. I'll take a look at that. Regards Pete

You merely need to delete the sections which you want to re-do -- for example. all sections [xxxxxx] with Cylinder Props in their titles. Use a normal text editor, like Notepad. Pete

Good. However, I've also worked out some code to "unhook" the weather DLL before FSUIPC is unloaded. If you'd like to test that for me (without the ForceTerminateTime parameter) I'd be grateful. Let me know, and if okay I'll upload the amended version. Regards Pete

Well, it certainly works on FSX. I've not tested every SimConnect function on P3DV2. ... but, I've just tried it and it works on P3Dv2 too. I think the problem you are seeing using it with WideFS is that WideClient starts any Lua programs it finds as soon as it gets a connection to FS. I think SimConnect or FSUIPC isn't geared up to do the "Init Pos" action through SimConnect right at that time. Try inserting a delay before the last line, something like ipc.sleep(20000) for a 20 second delay certainly works. Maybe something less will too. Regards Pete

I don't know FSIP200X. I take it that it is an FSUIPC application? There are logs -- WideServer.log on the Server and Wideclient.log on the client. You need t show me those. Paste them into a reply here. Those services needed for Windows to support Networking and networked compute recognition, whatever they are. I expect it depends how you've configured WideFS. Have you read the section in the user guide about configuring your network, the part which starts with a strong red suggestion that you read at least part of it? Regards Pete

As the error shows and the log confirms, FSUIPC is not actually running at the time you got the crash. The log shows it terminated quite normally. I can't really fix crashes outside my own code as I have no control over them. I don't know what is using FSUIPC which might be crashing when it closes -- I assume the AN-2 isn't using it for anything? It looks like the "fault offset" is actually the place where a hook from the Weather module is linked to, for use in Wind Smoothing, so it seems for some reason, after installing the AN-2, some weather actions continue after FS is closing? Not seen that before, it is most odd. All I might be able to do is work out a way to unhook this before terminating. Not easy, and may cause more crashes elsewhere because the modules being hooked might be unloaded first. [LATER] After looking at that I don't think it is possible without making things worse. I think the best I could do would be to keep FSUIPC runnng, somehow, for some seconds more. You could try that yourself. Add ForceTerminateTime=N to the [General] section of the INI file, where N is a number of seconds. Regards Pete

Well, the only thing I see odd there is that you have no generic [Axes] section, so you won't have any axes assigned to an aircraft which isn't yet assigned to a Profile. However, you do have a generic [buttons] section, so you will see buttons assigned in the Buttons & Switches tab. You have no [Keys] assigned so you won't see anything assigned in the Keys tab. Pete

Just renaming FSUIPC4.DLL as FSUIPC4.DLS will not change any settings whatsoever. The settings are all in the FSUIPC4.INI file, and if you haven't deleted or renamed that then they are all intact, and will certainly be reloaded when you next reenable FSUIPC by renaming it. It sounds to me like you deleted or renamed the settings file. If you've made no changes to the INI file then of course reloading it will do nothing, as it will simply load the same settings which are already loaded. You don't need to "send" the information to FSUIPC. Your INI file will be read by FSUIPC when it starts running. If it finds no INI file it will make a new one with only default settings. If you have an INI file which contains all of your settings then you do not need to make a new one, FSUIPC will load them automatically. I think you must either have deleted the settings, in which case (unless you have a backup) you will need to make them all again, or you have renamed the settings file and so FSUIPC has made a new default one. Why don't you paste in the contents of your FSUIPC4.INI file into a message here for me to see? Pete

Okay. Not sure what the difference is between "innocent" questions and "guilty" ones, but still ... ;-) It sounds like you deleted your settings (FSUIPC4.INI). Why did you do that? You say you just renamed FSUIPC4 -- do you mean the DLL? If so then it simply wouldn't be loaded, it wouldn't cause any other files to change. I'm not sure what you mean. If you have all your settings still in the FSUIPC4.INI file then those are what FSUIPC4 will read. It doesn't store settings anywhere else at all, it simply reads those saved in the INI file. There won't be anything in the manual to help folks who throw away and delete all their settings. What did you expect to find it saying, some magical spiriting back of your settings from nowhere? ;-) What is the second question? You've only asked one! ;-) Regards Pete

WideFS is a system for extending the FSUIPC application interface to other PCs, ones not running FS. It won't work with extra PCs actually running FS and it doesn't help in any case with programs which don't even use FSUIPC for anything, like FSINN (as far as I know). FSUIPC does not have any facilities for creating traffic in any case, so neither Squawkbox nor FSInn can be using it for such things -- at most they would be reading the user aircraft data through FSUIPC/WideFS and maybe setting the weather. Regards Pete

If it uses SimConnect, as I thought it did, you need SimConnect configured for it. Or else it does its own Networking and needs two components, one on the FSX PC and one on the other. But I really do not know. I don't use Squawkbox at all so can't help directly. The documentation should really tell you what to do. Isn't there a Squawkbox forum where you can get more specific help? Most visitors here are more concerned with FSUIPC and WideFS. Perhaps your virtual flying website, or VATSIM or IVAO forums? Pete

It really isn't hard to identify yhings in the INI file. To start with you need the Joystick number. you can see that from this section: So, you know it is Joystick 1. Then the only place Buttons are assigned is in sections called [buttons ...]. I've isolated them here and highlighted the lines assigning Joystic 1, Button 3: As you can see, there is only one assignment in operation in FSUIPC, from wither the general section or the specific sections, so it cannot be button 3 which is the problem. Note also that the assignments in the specific sections are identical to those in the general section, so really there's no point -- you only need specific assignments when you want them to do something different. I suspect you are really referring to button 2. You should really identify the button by going to FSUIPC's Buttons assignment tab, pressing it and seeing what number it displays. Some drivers count button numbers from 1, but FSUIPC and Windows internally count from 0, so your button 3 may be the 3rd button which is number 2. Isolating the references to button 1,2 instead we see: Again the assignments in your specific sections are identical to the one in your main general section, so I think you can safely delete the whole of those last two sections - Cessna Aerosoft 172 and Real Air Turbo. But look at the general [buttons] section. The two assignments there are for different actions: 13=R1,2,C65607,0 says send control 65607 repeatedly whilst the button is pressed (65607 = "Elev trim dn", as you can see from the List of FSX controls in your FSUIPC documents folder), whilst 16=U1,2,K0,8 says send the NULL key press when the button is released. Now that latter one really won't do anything unless some add-on you have processes the NULL key value, which seems very very unlikely. I think you should delete that line. But it won't solve your problem, which I therefore think MUST be due to an assignment in FS itself which you've made. Since you appear to be assigning axes as well as buttons in FSUIPC I think you should disable controllers altogether in FS, otherwise you will run into conflicts. Regards Pete

The version of Squawkbox which works with FSUIPC, and just maybe WideFS, is Squawkbox 3, which is for FS9. The FSX version, Squawkbox 4 does not use FSUIPC and therefore does not use WideFS -- it uses SimConnect. Pete