Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.
Comments
ipc.runlua("gitlua");at the topAh, looking in that config file I see that number relates to FSUIPCPort. Does that need changing?
Ray (Cheshire, England)
Sorry, I completely forgot that with P3Dv4 you have to have WideFS setup too. See https://www.pollypotsoftware.org.uk/support/forum.html
Best wishes
Steve
I do have those files but despite that the FSUIPC5.log always shows a problem which I've never been able to fix. This is from the most recent log...
43781 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.13.32097 (SimConnect: 4.5.0.0)
43844 Initialising SimConnect data requests now
43844 FSUIPC Menu entry added
43844 LUA.0: beginning "D:\P3Dv4\Modules\ipcInit.lua"
43844 ... Using Prepar3D with Academic License
43859 \\CHILLBLAST\Prepar3D v4 Files\SIMstarter NG.fxml
43859 \\CHILLBLAST\P3Dv4\SimObjects\Airplanes\Carenado PC12\PC12.air
43937 *** LUA Error:
no field package.preload['socket']socket
no file 'D:\P3Dv4\modules\socket.lua'
no file 'D:\P3Dv4\modules\socket\init.lua'
no file 'D:\P3Dv4\modules\lua\socket.lua'
no file 'D:\P3Dv4\modules\lua\socket\init.lua'
no file 'C:\Program Files (x86)\Lua\5.1\lua\socket.luac'
no file 'D:\P3Dv4\modules\lua\socket.dll'
no file 'D:\P3Dv4\modules\lua\loadall.dll'
288125 ### The user object is 'CARENADO PC12 2'
Looking at gitlua.lua it local host entry with local host there. I’ve tried the IP address of the computer and it’s name - CHILLBLAST. But neither resolve the problem in the FSUIPC log. Any ideas why I can’t get a connection?
Ray (Cheshire, England)
I asked about the error in the FSUIPC log here and then it got very confusing when John Dowson pointed me to another topic with a set of files I may need. But it's way above my level of understanding. I've downloaded the package John pointed me to and stopped there. Can you advise precisely what I need to do to get gitlua.lua working properly please?
Ray (Cheshire, England)
I spoke to Pete Dowson and he confirmed FSUIPC receives its data from SimConnect. So when I monitor 3367 that has come from FSUIPC via SimConnect.
Pete reckons you should be able to retrieve the status of exits from SimConnect so I’m unclear why you can’t. Are you running P3D v4.x? If so and your FSUIPC5 logs don’t have that error then perhaps you could send me the files you have and that will correct the problem. Thanks.
Ray (Cheshire, England)
Regarding this "socket not found" error in my FSUIPC logs. As gitlua.lua is provided as part of the GIT software does it need a 64-bit lua driver in order for it to connect to FSUIPC? As you can see from my log it doesn't connect so any subsequent attempts via the GIT interface won't work.
45844 *** LUA Error:
no field package.preload['socket']socket
no file 'D:\P3Dv4\modules\socket.lua'
no file 'D:\P3Dv4\modules\socket\init.lua'
no file 'D:\P3Dv4\modules\lua\socket.lua'
no file 'D:\P3Dv4\modules\lua\socket\init.lua'
no file 'C:\Program Files (x86)\Lua\5.1\lua\socket.luac'
no file 'D:\P3Dv4\modules\lua\socket.dll'
no file 'D:\P3Dv4\modules\lua\loadall.dll'
Ray (Cheshire, England)
Those errors are because socket isn't available in FSUIPC5 because its 64bit. That's why you need WideFS which is 32bit and will provide socket. You'll have to talk to Pete about WideFS. Its been years since I worked with that, but a couple of customers got GIT working with it so it might help you to contact them (just search the forum for WideFS).
If Pete is certain his data is from Simconnect, I will take another look but those variables are dealt with in exactly the same way as all the others so any issue would show up on all indexed variables, so I'm not holding out much hope of a resolution.
Best wishes
Steve
I've had WideFS installed for years. What file in particular does GIT need to establish contact? From memory I have wideserver.dll installed on the P3D machine and wideclient.dll installed on the client
Presumably you run P3D v4 and have GoFlight modules so how do you overcome the problem of gitlua.lua not running? Or if it does run what files make it work?
Pete was certain of his advice. He's now away on holiday for a week.
Ray (Cheshire, England)
I searched the topics for WideFS and this discussion seemed the most relevant. https://www.pollypotsoftware.org.uk/vanillaforums/discussion/comment/4882#Comment_4882
But reading the linked topic on Pete's forum it's really about how to run lua files on a client PC using WideClient. I have a lua script on a client PC that runs using that process. But there's nothing about how to solve running gitlua.lua on the server PC.
The only thing I can think would fix it is to install WideClient on the server PC bizarre though it seems and place gitlua.lua into that folder.
Ray (Cheshire, England)
I'm afraid I'm like a dog with a bone when I have a problem. I need to understand why GIT cannot connect to 64-bit FSUIPC when it can to 32-bit FSUIPC. You said yesterday "...because socket isn't available in FSUIPC5 because its 64bit".
What is 'socket'? Is it a lua file or something else? If it's a lua file is it not possible for someone to create a version that will work with 64-bit software? After all, that is the way all flight sim software is moving. 32-bit is on its way out.
I have just installed 32-bit GIT into P3D v3.4 and the log shows a connection to FSUIPC. On the discussion on this in the FSUIPC forum John Dowson pointed me to a topic that included links to software that might solve the problem. Within that zip was a file named socket.lua. I'm attaching it for info.
It would be helpful if you could describe how GIT connects to P3D and FSUIPC so I can understand the process. As things stand it seems no GIT owner of a 64-bit P3D can connect to FSUIPC - not just me.
Ray (Cheshire, England)
Socket is lua functionality of the 32bit version of FSUIPC which was not included in the 64Bit version. I can't remember why, but I did see something from Pete about it ages ago. Unless that has changed the only work around that a customer found was to use WideFS because this has the lua socket functionality.
FSUIPC runs a lua file that I wrote that provides a socket for GIT to connect to (see gitlua.lua).
Your best bet is to PM that customer and ask how it configured it.
Best wishes
Steve
Further to my post, this was the situation from Pete at the time:
"I'm afraid I will have to remove the built-in LuaSocket facilities in FSUIPC5. I have been trying to compile 64-bit versions of socket.core, mimi.core and ltn12.core (I did find I was including them -- wrongly as they were the 32-bit versions), but there are vital bits missing in the LuaSocket sources I downloaded and the things just won't compile.
There is a work-around. Install WideClient on the same PC asFSUIPC5. Change the ClassInstance parameter in the INI to 1 so it can run at the same time as P3D4, and connect to FSUIPC in the normal way, and use socket plug-ins in WideClient. It's still a 32-bit program and has the requisite modules built in.
I'll publish this as a note in the next "changes" notice for an FSUIPC5 update.
Pete"
See this thread: https://forum.simflight.com/topic/83771-lua-socket-64-fsuipc-5/
Best wishes
Steve
Thanks for the reply and the info. When Pete says he doesn't understand how something works I reckon it must be horrendously complicated. Given the workaround is to run WideClient but with a value set in the ini so it can run a second instance that seems the best solution for my admittedly modest requirements.
I'll try that in the next few days and hopefully GIT can communicate with that offset and I can get my LEDs working for the doors.
Ray (Cheshire, England)
I would be happy to help you setting this up if you encounter any problems.
Regards
David
David
Thank you. But is it just a case of running WideClient on the P3D machine and setting the ClassInstance parameter in the INI to 1? If so I'm okay doing that. I'll try that tomorrow and come back if that isn't enough.
Ray (Cheshire, England)
Can I call on your offer of help please? I copied wideclient.exe and wideclient.ini from another PC and changed ClassInstance=1. With P3D running I started wideclient and it made an immediate connection.
I then started GIT 64-bit but the same message appeared in the log about the inability to connect to FSUIPC. What else do I need to do?
Ray (Cheshire, England)
I have looked into the EXIT_OPEN1 issue again and I'm bringing the value down as "Percent Over 100", so it may be that the value is the percentage it's open, so fully open would be 100 and not 1.
Best wishes
Steve
Ray (Cheshire, England)
Ray (Cheshire, England)
Can you configure one of your MCP PRO's display to show the variable to see what value it outputs?
Best wishes
Steve
I'm unsure how I could do that and I'd rather not start changing things I don't understand. Just to confirm. Which variable are you referring to? EXIT_OPEN1?
Ray (Cheshire, England)
Backup Documents\GoFlight Interface Tool and you can then easily restore.
Best wishes
Steve
Ray (Cheshire, England)
I bought this aircraft a long time ago, but because the way I have set up my cockpit, I was never able to use this aircraft (I need 2D instrument panels).
As such Ive never bothered to reinstall whenever Ive needed to to a clean install of P3D.
Ive just installed it now to see what I can observe re doors.
So despite P3D message to advise that exit 1 is either open or closed, I am not observing any change in the EXIT_OPEN1 LVAR at all.
The TEST1_MASTER_WARNING (or TEST2_MASTER_WARNING for door 2) does flip between 0 and 1 when the doors are open or closed, BUT, this appears to be related to the master warning button on the dash, and clicking that master warning, resets the value.
This is my biggest frustration with aircraft creators in P3D - so many no longer bother to set or expose LVARs making any hardware interface/cockpit installations impossible :-(
What is strange is that given P3D seems to know exit1 is either open or closed (via the sim message), that the standard SIM LVAR for exits (EXIT_OPEN1) value never changes.
Regards
David
David
Luckily most of the more simple gauges for this aircraft are written in XML which means that I can look at what drives some of the indicator lights.
It DOES appear that its reading an EXIT value for the doors, but for some reason, they are not translating/displaying in GIT as EXIT_OPEN1 or EXIT_OPEN2.
I wrote a quick bespoke routine, called START with the following:
LABEL:begin
ReadMemRef 3367 -> Bespoke Var 0
Sleep 200
Goto : begin
Offset 3367 in FSUIPC holds a byte, with each door status set as 1 bit
Assigning Bespoke Var 0 to an MCP PRO readout shows the following:
0 = all doors closed
1 = door 1 open
2 = door 2 open
3 = door 1 & 2 open
I'm assuming that EXIT_OPEN1 etc, are bitmask extracts from the offset 3367, but for some reason, those LVARs aren't being set.
David
Thank you for your analysis. On your second point I was able to read the relevant offset from FSUIPC to show the status of exit1 and exit 2 (pax and cargo doors) and they matched your values above.
Frustratingly, GIT cannot access those offsets so setting the light appears impossible. How frustrating for such a simple action when so much more has been achieved with far more complex stuff.
Ray (Cheshire, England)
I can write for you a bespoke event so that you can read the value directly and display via a GF LED.
Ill write it up in the next 24 hours and describe it here.
Regards
David
David
I'm not sure if you have written any existing bespoke events yet for your PC12. If you have, I would suggest making a backup of your GoFlight Interface Tool directory in your DOCUMENTS folder first, as I'm not sure if the import process to load my code will overwrite any existing bespoke events, or just add to them, as Ive never used the bespoke event import before.
Unzip the file (there are 2 XML files inside) to a temporary location.
To import my code, you need to click on the Detective button.
At the bottom right hand side of the Detective page are 3 icons, one with an upward arrow (export), one with a downward arrow (import) and the far right icon is a large red X.
You want to click on the IMPORT button on this screen.
Navigate to the temporary location where you have unzipped my 2 XML files, and select 'Carenado PC12.xml'
This will create a START event.
The START event is a special event. This will automatically execute as soon as you load in your PC12 aircraft.
The event reads in the FSUIPC offset, and stores it in Bespoke Var 0
It then uses a SWITCH command to determine what block of code will run next, dependant on the value stored in Bespoke Var 0.
Bespoke Var 1 will contain the status of door 1 (0 = closed, 1 = open)
Bespoke Var 2 will contain the status of door 1 (0 = closed, 1 = open)
Case 0 (all doors closed), will set Bespoke Var 1 to 0 and Bespoke Var 2 to 0.
Case 1 (Door 1 is open, door 2 is closed) will set Bespoke Var 1 = 1 and Bespoke Var 2 to 0
Case 2 (Door 1 is closed, door 2 is open) will set Bespoke Var 1 = 0 and Bespoke Var 2 to 1
Case 3 (Door 1 is closed, door 2 is closed) will set Bespoke Var 1 = 1 and Bespoke Var 2 to 1
The ENDSWITCH will stop any further checks against Bespoke Var 0
The sleep command tells GIT event to take a break (so it doesnt loop too fast and consume CPU time
It then goes to label :begin, which is at the top of the event, and the whole process repeats.
This will continuously read, check and set the Bespoke vars to the correct value.
For your GF LEDs, set a LED to read Bespoke Var 1 for door 1 status, and light it up when the value is 1
For door 2, set a LED to read Bespoke Var 2 for door 2 status and light it up when the value is 1.
Hope this explains the code, and solves your issue.
Regards
David
David
That's very mind of you, thanks. No, I've never written any code. Not my area of expertise I'm afraid. I'll test it in the next day or so and reply. I'm just setting up a flight in Concorde.
Ray (Cheshire, England)