Pete Dowson

No, they are provided by library code within FSUIPC and WideClient. You'd need a library DLL written that you could call upon. I don't think Lua provides the sort of Windows access you'd need to make an FSUIPC client application, but you could look at the source of the supplied application LIB in the FSUIPC SDK to see if you'd like to build one. Pete

The main Scenery.CFG file looks okay. Except for this at the end: [ ] Active=FALSE Those two lines need deleting. They look like an aborted attempt by an installer to install sceneries -- probably one of those ones you added. I wouldn't have thought this would upset the Lorby program, but try after fixing it. What's "LorbyScenery.CFG"? I don't know that one, though it looks identical to the MakeRwys_Scenery.CFG file which contains only this: [General] Title=Prepar3D Scenery Description=Prepar3D Scenery Areas Data Clean_on_Exit=TRUE [Area.001] Title= Did you try this: "try temporarily removing the Lorby program and run MakeRunways again (as administator). See if that at least finds the default sceneries." If not please do so and let me know. At present I've no idea what is going on. MakeRunways merely passes on the job of listing the scenery in the correct order to the Lorby program. i've no idea why it is failing. I'll probably need to ask Lorby-Si to take a look. But first, do you have the Lorby-Si AddOnOrganizer program? if not please get it (https://www.lorby-si.com/downloads.html) Run that and see if you get a proper scenery list.

No, not for the same event type, only for different ones. Otherwise you get problems with backlogs catching up when you don't really want it. On the first question: The latter case is more efficient as the plug-in remains compiled and resident (you'd have to preload it, probably by [Auto] or a call in ipcReady.lua). But that's only really significant for frequently used actions. For plug-ins being loaded each time you are really better off with smaller separate ones rather than very large ones proceeing one parameter then unloading. Of course there's a crossover point somewhere between the extremes. Horses for courses. Pete

It knows where to look, and provided you are running MakeRunways "as administrator", does have access. It has access if you run "as administator", but it doesn't need access if the Lorby program is provided. The results of the Lorby program are in this file: E:\Lockheed Martin\Prepar3D v4\MakeRwys_Scenery.cfg Does that contain anything at all? Even if it couldn't find any AddOn scenery it should find the SCENERY.CFG file in your ProgramData folder for P3D4v4. Maybe that's got corrupted? Check the file just mentioned. Then try temporarily removing the Lorby program and run MakeRunways again (as administator). See if that at least finds the default sceneries. Pete

So you can use that with Win XP? If so I'd stick with it. Pete

I don't know the DC3. What does the "fuel contents gauge selector" do? Is there just one fuel level gauge with three tanks? If you use FSUIPC event logging, does it show a control action occurring when you operate the switch on screen? If not then I fear that the switch ad its action are local specifically to that Gauge file. You'd need to consider either sing a Mouse Macro for it, or see if there's an L:Var (local panel variable) you can use. There's a Log LVars plug-in you can use to display a log of the L:Vars and their values when they change. Try that to see. Pete

What version of WideClient? I don't think recent versions will run on Win XP. We haven't supported that for a long time. Assuming you've not changed the version recently, what have you changed? And when and how does this error appear? Pete

Sorry, I don't quite understand. Are you looking to control the selector, as you ask, or to read its status? You found the selector controls, so I assume you just mean you want to read their current position? Check out offset 0AF8 for engine 1 selection, or 3880 Engine 1 and 37C0 Engine 2 (with 3700 Engine 3, 3640 Engine 4). Pete

No. Don't you see the " " and the , (comma)? And where does your = come from? Please just follow the documentation: ipc.writeLvar(“name”, n) name is obviously (?) the L:Var name., L:klid. The comma is a comma (,) not an equals (=), and n is your number. So ipc.writeLvar(“L:lid", 1703010) What is the "sleep(100)" for? 😞 Please please read the documentation supplied! When you save the file you give it a short filename, right? In FSUIPC you assign to Lua filename -- it'll appear in the list. Pete

I see John helped with that. ZIPping files is best for any and all uploads, but it is especially good for text files where you'll get excellent compression. Can you tell me what this section is about: 61250 Write: Offset=8624, Size=0001 83 61250 Write: Offset=861C, Size=0002 14 00 61250 Write: Offset=8620, Size=0002 14 00 61250 Write: Offset=861E, Size=0002 00 00 61250 Write: Offset=8622, Size=0002 FB FF Are those offsets being written by one of your programs? What for? Or is that internal to SimAvionics? I doubt if that question is related to the crash, though, as the same values and others are being written to those offsets regularly -- about 4 times per second, in fact. I think I'm going to need a much fuller log. Could you reproduce again, but with "Log=DebugAll" instead of "Log=Yes". This time the log will become massive, so even with ZIP you might struggle. if so just include the last few Mb. Pete

As James (AND the documentation in fact -- see below) says, you must run MakeRwys "as administrator". You don't need to tell the Lorby program, though, as MakeRwys runs that and if it is running "as administrator" then so will it. The reason for this is that the Lorby program needs access to both your AppData and ProgramData folders, and MakeRwys needs access to Appdata. I append the relevant paragraph exactly as it appears in the included READ ME document, bottom of page 1. If you still get 0 runways the log file will be very short, so please paste it here (the file is "runways.txt"). Pete NOTE that you should run MakeRunways“as administrator”.This is especially true on Win10. The best wayisto mark it needing adminprivilegesinits (or its shortcut) “Properties – Compatibility” settings (right click on the EXE or the shortcut).

Ah, so you are not assigning to a keyboard command as you originally sent. Therefore my previous reply was rather irrelevant. Have you set the button to Repeat? If you can't make it work at all with this assignment then as well as Spokes2112's suggestion there are two other alternative approaches I can think of: 1. Make a mouse macro to press the screen button and assign to that macro. 2. Try writing to the starter offset: 0892 2 Engine 1 Starter switch position (Magnetos), Jet/turbojet: 0=Off, 1=Start, 2=Gen/Alt Prop: 0=Off, 1=right, 2=Left, 3=Both, 4=Start This can be done by assigning to Offset Word Set with 0892 in the offset field and 1 or 4 as the parameter (according to aircraft type). Assign the same to button release but with a different parameter as needed -- 0 or 3 probably. Pete

Unfortunately they are relating to a crash in the Windows NTDLL library, which is a collection of many small utility functions. The log with more data should allow me to narrow it down, but after that i may need to put extra logging in the area this suggests may be responsible. It sounds like a Windows update has changed something in one of the NTDLL functions WideClient uses making one of the parameters being supplied or returned need a different size reserved (the errors being the usual "access violation"). Pete

In what way "didn't work"? The program isn't going to suddenly change itself just because you install some new sceneries. No, none at all. Sorry, but you give no useful information whatsoever i'm afraid. "didn't work" doesn't help at all. 😞 Pete

Using the keyboard is different in two ways: 1 it relies on the keycode to be converted into a command by referring to your assignments 2 holding a key down generates repeats. #2 matters if you are relying on holding it down to get the engine started. Unless it is programmed to press the aircraft's button when pressed, and release it when released (with repeats disabled), what will be happening is loads of separate commands being sent. Perhaps you should actually describe what the aircraft "on screen starter" needs and what you are actually assigning your keypress to. Pete

Excellent, and thanks for letting us know the cause / solution. Pete

It is probably recognizing it but cannot do anything because of the GUIDs being the same. I think you should read through the last parts of this thread, because i fear the answer will be the same: The only way possible for duplicate GUIDs is a registry mess. Pete

That's a bit odd. How does a client crash cause the sim on the other PC to crash? The logs don't show anything useful I'm afraid. Apart from Windows updates, are you aware of any other changes made to your long-working setup? Can you take a look in the 'Event Viewer' (a standard Microsoft utility, should be installed)). Look under Windows Logs -> Applications, and see if there is an error report there for WideClient. If so, please post the details. In case it is related to some specific exchange between the client and server could you also change the Wideclient INI to have Log=Yes instead of Log=Errors+. Pete

Good. Yes, that seems to be a common problem. You wouldn't have thought that in developing a faster interface they'd lose some compatibility with the previous incarnation. Pete

I'm pretty sure that the USB yoke they make is a standard joystick device and doesn't need FSUIPC. It should be recognised by Windows Game Controllers as a normal joystick and by P3D. If Windows doesn't see it then FSUIPC cannot either. But you're saying that Windows complains that it needs a driver? In Windows Device manager is it listed as a COM device or only a USB device? And how listed in Windows Settings? By name? Pete

Excellent! Thanks for letting me know. Pete

Save the following in a text file named "FixMyJoys.reg". Windows Registry Editor Version 5.00 [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_294B&PID_1900] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_294B&PID_1900] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16D0&PID_0A38] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_16D0&PID_0A38] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_10C4&PID_82C0] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_10C4&PID_82C0] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_8807&PID_8807] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_8807&PID_8807] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_294B&PID_1900] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_294B&PID_1900] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16D0&PID_0A38] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_16D0&PID_0A38] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_10C4&PID_82C0] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_10C4&PID_82C0] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_8807&PID_8807] [-HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_8807&PID_8807] Now this should in no way do harm to your system -- it is just deleting your joystick device entries from the Registry. however, before editing the registry at all i always play safe and do a Windows backup (the Window backup and restore facility in Windows Settings or Control Panel). Unplug your devices. Then run the .reg file you just created by right-click and selecting "run as administrator". Now power off. Plug your devices back in, and start the PC again. This should give you a clean registry with your devices properly registered. Pete

It looks like it crashed whilst reading the complete ground and air traffic data in one go. Does one of your programs do that? It's a long time since I delved into the nitty-gritty of WideFS, so it might take me a while to work out what is happening. But there are two more steps you could do, please, to narrow it down more conclusively (after all this is only one crash and it might just be coincidental that it is doing this particular thing). First do the same sort of test but with Log=Yes instead of DebugAll. Second, see if the crash still happens if you don't run the program which is reading traffic. Pete

Okay, yes. I see the registry details. I'll work out what you need to do ... Pete

You tried "(L:klid) = 1703010" where, exactly? and what do you mean by "the fsuipc list"? I really don't know what you are talking about there. To set an L:var from a Lua plug in you need to use the ipc.writeLvar function. Please do refer to the Lua library documentation. Pete