Pete Dowson

Okay. I don't realy understand why the crash was occurring in "dinput.dll" if nothing else is involved in scanning joysticks. WideClient doesn't actually use DirectInput itself, but calls Windows simpler (and older) "joyGetPosEx" function to read buttons. But I guess that uses dinput.dll somewhere down the line. (In FSUIPC4 I use the DirectInput functions explicitly so I can read all 8 possible axes, but of course Wideclient doesn't provide axis input options). Regards Pete

Key presses? FSUIPC won't know whether key presses are coming from the keyboard or from a joystick driver. There's no way to distinguish them. If you mean buttons and switches, there is an "IgnoreThese" option -- see the Advanced Users guide, search for "ignorethese". Of course ideally you shouldn't have any buttons which are continuously signalling -- that's normally the sign of a fault. Pete

What's the problem? Either assign it in FS in the notmal way, or in FSUIPC Axes assignments to the appropriate FS axis control (eg "axis throttleN set" for throttle N), then calibrate in FSUIPC. Calibration has a chapter of its own in the User Guide. Follow the numbered steps. Pete

I seem to have seen this same post before, just recently? I replied there, too. It'll be there because you created a Profile for it. no one else can do it, unless you gave someone else access to your PC of course! The 737-800 profile only matches the "American 3" at present. If you change this: [Profile.Ifly 737-800] 1=ifly 737-800 American 3 To this [Profile.Ifly 737-800] 1=ifly 737-800 it should match all the iFly 800's. You omitted to include the [JoyNames] section, which is a shame as it shows which devices you've assigned for what, but: [Axes.Ifly 737-800] 0=0X,256,D,7,0,0,0 1=0Y,256,D,8,0,0,0 2=0Z,256,D,3,0,0,0 3=1X,256,D,22,0,0,0 4=1Y,256,D,4,0,0,0 5=2X,256,D,1,0,0,0 6=2Y,256,D,2,0,0,0 shows device 0 assigned to toe brakes and rudder, device 1 assigned to spoilers and throttle, and device 2 assigned to ailerons and elevator. So it appears there's a problem with that one device. Is it connected to an unpowered hub? The calibrations look reasonable (except you have no centre zone for elevator and rudder -- a small dead centre zone is usually pretty important for rudders when you have toe brakes as otherwise it is easy to move the rudder when braking. And also you need a better feet-off dead zone for the toe brakes to make sure you don't accidentally brake when using the rudder. Other than that it looks fine -- ypur problem must be with that device (aileron/elevator) or its connection. Pete

I have no idea what that tutorial advises, but it sounds like you either did not assign them correctly or have not calibrated them. There are simple numbered steps for correct calibration given in the FSUIPC User Guide. Follow those. If still no success, please find the FSUIPC4.INI file ("config settings") in the FSX Modules folder, and paste it into a message here. Regards Pete

It's a crash in DirectInput. Some sort of a problem with one of the devices you have attached, or its driver. Maybe something addressed by your LINDA configuration, or your levelD767 macro file? Perhaps you can do a process of elimination, unplugging one device at a time? I see you have 6 of them: 0=BU0836X Interface 1=G-Throttles 2=Saitek Pro Flight Rudder Pedals 3=BU0836X Interface 4=BU0836X Interface 5=Plasma-MM2 If you cannot locate it I'll see if I can add some more diagnostic logging into FSUIPC to narrow it down somewhat. [LATER] Meanwhile, I've realised you can probably get a little more datas by adding this to the [General] section of the FSUIPC4.INI file: Debug=Please LogExtras=x200000 Then reproduce the error. Show me the log. Regards Pete

Seems then that it must be a faulty Bodnar board. Try swapping the connections over to one of the others. Pete

Should do I suppose. I don't really know what those "cat" numbers mean. Providing it's a crossover. Pete

Okay, that's a good start: You have a generic throttle AND separate throttle 1 and 2 axes calibrated: If there are axes attached to all then those will obviously conflict. Worse, these are your axis assignments in FSUIPC: 65763 is the FS Axis ailerons set control, and 65762 is the FS Axis elevator set control. They are from your "CH 3-Axis 10-Button+POV USB Yoke". You've assigned those via FS, not direct, so they don't get arbitrated with your dual assignments which are for the same controls, yet direct, on one of your Bodnar boards: Then your throttles: The generic throttle on 1Z (the CH yoke, again), and throttles 1 and 2 on a Bodnar board. These will also conflict. But, to the main problem. Looking at the log: 5328136 *** AXIS: Cntrl= 66534 (0x000103e6), Param= -4230 (0xffffef7a) AXIS_FLAPS_SET 5328136 *** AXIS: Cntrl= 66382 (0x0001034e), Param= -2546 (0xfffff60e) AXIS_SPOILER_SET 5328136 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 6060 (0x000017ac) THROTTLE1_SET 5328136 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 7564 (0x00001d8c) THROTTLE2_SET 5328136 *** AXIS: Cntrl= 66534 (0x000103e6), Param= -16383 (0xffffc001) AXIS_FLAPS_SET 5328136 *** AXIS: Cntrl= 66382 (0x0001034e), Param= -16384 (0xffffc000) AXIS_SPOILER_SET 5328136 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 0 (0x00000000) THROTTLE1_SET 5328136 *** AXIS: Cntrl= 65821 (0x0001011d), Param= 0 (0x00000000) THROTTLE2_SET[/CODE] This sequence repeats throughout. Whatever one of your controllers sets, another is setting the minimum (-16383 or -16384) for the AXIS controls and 0 for both throttles. Since there are NO such duplicate axis assignments in FSUIPC, I think you must be mistaken about the FS settings. Are you sure joystick controls are DISABLED in FS -- not simply not assigned -- FS makes automatic assignments, and in any case you have to select every one of your attached controls in turn to see what is assigned. You cannot see them in one glance, you select one controller at a time. Have you done that? Pete

Nevertheless, all the axes are "springing" back to a fixed value, by the look of it. And all at the same time. something is clearly doing it. It doesn't look like spiking or jitter at all. I can do, by all means post it. But also, before that, go into FSUIPC's Logging tab, enable both event logging choices on the left hand side., Then reproduce the error (don't spend too long in FS -- the log will get too big!), and show me the FSUIPC log file too. If you temporarily clear one of the assignments you've made in FSUIPC and move the contorlsd, if the cleared one still moves, then there's another assignment, or try moving it with the mouse and see if it leaps back to the "spike" position. Regards Pete

Really? You aren't trying to use a wireless connection, are you? I've never found those very reliable for continuous use. If WideClient OR WideServer detect a disconnection they are continually trying to re-connect in any case, so it would make no difference. I've heard of occasional re-connections (on a wireless or faulty network), but never one whch didn't recover. If it is showing that it most certainly thinks the connection is broken. How are you determining that the communication is ongoing? Don't forget the WideClient maintains a copy of the FS data locally, so unless the applications are checking for a change in something they won't notice. I can't really help further without information. I'd need to know the version of FS, the version of FSUIPC and the version of your WideClient. If FSUIPC or WideClient are out of date please update first -- see the Download Links subforum. Then, if you get a disconnection which doesn't reconnect (or even if it does) I need to see the WideServer.log from the FS Modules folder and the WideClient log from the folder in which you placed WideClient. Regards Pete

Not with Navigraph -- though I presume you scanned through their list of supported programs? Might be a good idea to email them that question -- might be an avenue they've not thought of, though of course they probably aren't allowed to let the data be used for real-world navigation. Pete

That's what is called a CTD, "crash to desktop", and, yes, it is certainly a crash. The Windows log will show details. I await more details. Regards Pete

Why is it spiking? Are they cheap pots, or just dirty? I use those same Leo Bodnar boards for analogue controls and they are as smooth as a baby's bottom! Video They are all changing together! That looks more like a conflict with a dual assignment to me. Have you disabled controllers in FS? If not, that's your reason. Pete

I have an GF45 and that most certainly had only one alphanumeric-capable display, so I assume the GF46 is similar. You should be able to tell by looking at the number of elements -- 7-segments in an 8 pattern = numeric, 11 elements (I think), like an 8 with a X as well, is alphanumeric. Pete

Try a number. Also, please tell me what version of FSUIPC or WideClient you are using. The way the displays are handled was changed in one version not so long ago in order to get around a problem with '9's on one of the GF units. Maybe the change doesn't suit the GF46. Regards Pete

Well, there is a feature operated by FSUIPC offsets which allows FSUIPC / WideFS to lie to the client programs about the values in an offset. This has to be programmed in a Lua plug-in. Ah, then there is no chance. WideFS is 100% dependent upon FSUIPC which is 100% dependent on FS. It is a module of FS, not a free-standing program. It would be far less work to get FSC to read your GPS direct. To build a freestanding WideServer interface would be a huge undertaking in itself, as it would need to emulate all of the things WideClient relies on -- much more than a few numbers representing aircraft position. I should think FSC would require rather more too. Odd that I went to a lot of trouble to provide GPS-emulating output from FSUIPC/WideFS so that real world moving map applications, used with real GPS's, could be used with FS. It seems very strange to want to use a simulstor world moving map when the real world ones are so good! I use Jeppesen FliteMap, but even google maps can be used, of course, and there are many other map programs which follow GPS coordinates. Regards Pete

Well, of those the ones which would presumably be involved are: linda linda_config ipcReady.lua levelD767.MCRO Linda.exe linda.lua NGX_AUTO.lua sb3guagebridge.dll But that isn't the point. FSUIPC should never crash FS, so I need to find out why and fix it. So, please: 1. Change to version 4.811 (from Download Links subforum), so you are on the same version as me, 2. Reproduce the crash. 3. find the error details in the Windows error log. On this you asked: Go to "My computer" or "Computer", right-click, select Manage -- or go to the Start menu and enter "Manage" and press Enter. Select "Event Viewer" then "Windows Logs" then "Applications". Scroll down the list till you find an Error (red icon with exclamation mark), see if it was for FSX. Find the FSX one, Double-clcik on it, select "Copy" then paste the details in a message here. Regards Pete

Strange. Does it work using the GoFlight software? What are you trying to display? Isn't the GF46 the one which has one alphanumeric display and the other numeric only? Regards Pete

By "terminates prematurely" I presume you mean "crashes"? What does the Windows error log show? I need the details, please. Better still, please update to 4.811 (Download Links subforum) so you are on the same version as me, then I can make use of any module address you find in the log. I run from an SSD. That won't make any difference. Maybe there's a difference in the FSUIPC4.INI file? Compare them and see. But first check with 4.811. Are you using two different PCs or two installs of FSX on the same PC? If the latter, could there have been a problem with the SmConnect part of the install? The logs don't show anything.useful except that SmConnect never responded to the Open request to it, presuymably because of the crash beforehand. Maybe a SimConnect log will show something -- see the FAQ thread on that. Regards Pete

The Clients are the same for both. Only the Server is different because one runs in FS9 and before and the other (built into FSUIPC4) runs only on FSX and later. Otherwise they are totally 100% compatible. On a client PC? Not sure why. It runs perfectly here, and the Client copy of SimConnect is dead simple. ASE works better with Simconnect because it is designed to do so. It will work via WideFS too I believe, but it will need to think the server is running FS9. Regards Pete

You don't need to purchase it to read any or all of the documentation, whch is installed automatically for you when you install it. Or browse the subforums above where you will find a lot more information. The one for FSX, of course (FSUIPC4), because the one which says it is for "FS9 and before" won't work with FSX! Regards Pete

Aren't they just two different displays on the same device? One will be display 0 and the other other display 1, I should think. What is the problem? Regards Pete

I don't know those Lua plug-ins. But a brief look at them shows that they are documented. Just open the files with a text editor and read the stuff near the top. They list the parameters you set for each of the commands. So you just assign to the Lua xxxxx control and put the appropriate parameter in the parameter field, the space where it says 'parameter'! Regards Pete

They are part of the Lua language. My documentation is just for the functions added by the built-in libraries.I can't better the official documents and tutorials. For information about Lua please follow the link to the main Lua website. There's a reference manual and lots of guidance on Lua programming there. There are also several good books on it. Regards Pete