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.
Problems with START functionality in 64 bit GIT
HI Steve,
Ive set up a series of START functions for a particular aircraft in 32bit GIT and P3Dv3.
START contains a CALL to an INIT BESEvent (which sets inital values for BESVars), then after a label, makes multiple CALLs to other BESEvents which interact with the sim's events and lvars, sleeps, and then loops back to the label to repeat over and over.
This worked really well, and I was able to make the Boeing style GoFlight MCP PRO act like an Airbus FCU.
Now that my airbus is available in 64 bit P3D, the same functions dont seem to work the same in 64bit GIT.
The lvars and events in the aircraft have not changed between 32 and 64 bit, but the functionality of how START seems to work looks like it has.
I havent been able to track down exactly what the difference is, but its almost as if either only one CALL in the sequence is ever executed, or, its not looping back after the Sleep.
Any ideas why I am seeing a difference between the 64 bit and 32 bit GIT?
It goes something like like
START
sleep 50
Call START-INIT
:LOOP
Call START-FCU-SPEED
CALL START-FCU-HDG
CALL START-FCU-VS
CALL START-COMMS
Sleep 1
Goto LOOP
None of the other START named functions contain loops
Regards
David
Ive set up a series of START functions for a particular aircraft in 32bit GIT and P3Dv3.
START contains a CALL to an INIT BESEvent (which sets inital values for BESVars), then after a label, makes multiple CALLs to other BESEvents which interact with the sim's events and lvars, sleeps, and then loops back to the label to repeat over and over.
This worked really well, and I was able to make the Boeing style GoFlight MCP PRO act like an Airbus FCU.
Now that my airbus is available in 64 bit P3D, the same functions dont seem to work the same in 64bit GIT.
The lvars and events in the aircraft have not changed between 32 and 64 bit, but the functionality of how START seems to work looks like it has.
I havent been able to track down exactly what the difference is, but its almost as if either only one CALL in the sequence is ever executed, or, its not looping back after the Sleep.
Any ideas why I am seeing a difference between the 64 bit and 32 bit GIT?
It goes something like like
START
sleep 50
Call START-INIT
:LOOP
Call START-FCU-SPEED
CALL START-FCU-HDG
CALL START-FCU-VS
CALL START-COMMS
Sleep 1
Goto LOOP
None of the other START named functions contain loops
Regards
David
Regards
David
David
Comments
I have just checked the change log and nothing has been done on bespoke event processing and calling. If the same code works in GIT with P3Dv3 and the GIT versions are the same, I think it may be suggesting an issue with the 64bit version of the aircraft.
Have you ran the Bespoke Events in Detective via the Test button and see if they work as you expect in P3Dv4?
Could it be that one of the commands Im using in one of the START-* functions is failing, and therefore stops the START routine from being able to loop?
In one of the START- functions, Im using a ReadMemSB call
BES-TXPDR-MODE-C = ReadMemSB(7b91)
Does ReadMemSB work the same in Git64, and is the offset value still valid and correct between 32 & 64 bit P3D?
(That offset value is not aircraft specific, but a value used by VATSIM's vPilot app)
Regards
David
David
I don't think Pete Dowson has changed the memory values in FSUIPC 64bit, but it may be worth double checking.
I'll do some testing at my end and see if I can spot anything.
Best wishes
Steve
Some further debugging has shown that if I remove the ReadMemSB call, then START loop works without breaking/stopping.
The GIT log shows this entry on start of GIT, which I'm not sure if this is relevant or not:
FSUIPC: Connection Failed: No connection could be made because the target machine actively refused it 127.0.0.1:8385
Registered FSUIPC5 is running successfully. I dont have any firewalls running, and both GIT and P3Dv4 are started as Administrator.
This code worked without issue on P3Dv3/ GIT32 with or without vPilot running.
Regards
David
David
Thx
Steve
ipc.runlua("gitlua"); (only quotes around gitlua)
The modules directory does also contain the file gitlua.lua
fsuipc5.ini also contains a section called
[LuaFiles]
with 4 lines underneath, numbered1-4, with gitlua being listed against 1
fsuipc5.log file contains this, which may be of interest....
14991 LUA.0: beginning "D:\P3Dv4\Prepar3D v4\Modules\ipcInit.lua"
...
15085 *** LUA Error:
no field package.preload['socket']socket
no file 'D:\P3Dv4\Prepar3D v4\modules\socket.lua'
no file 'D:\P3Dv4\Prepar3D v4\modules\socket\init.lua'
no file 'D:\P3Dv4\Prepar3D v4\modules\lua\socket.lua'
no file 'D:\P3Dv4\Prepar3D v4\modules\lua\socket\init.lua'
no file 'D:\P3Dv4\Prepar3D v4\modules\lua\socket.dll'
no file 'D:\P3Dv4\Prepar3D v4\modules\lua\loadall.dll'
...
67174 LUA.0: beginning "D:\P3Dv4\Prepar3D v4\Modules\ipcReady.lua"
67267 *** LUA Error:
Version of FSUIPC5 is 5.121b (2nd October 2017)
David
The work around mentioned may work.
Best wishes
Steve
I am licensed for WideFS, which I see mentioned might work, although I'm not sure what I would have to install where, and configure how, to get WideFS Client to support your GITLUA script.
I can assist and try it out, if you can make some sense of what's being discussed in that link.
Regards
David
David
Best wishes
Steve
I was able to get this working via the link above.
Thanks
David