ScotFlieger

One of the fixes for the repeat runaway problem in LINDA 2.8.3 cuts the repeating buttons after about 20s. If the button is pressed again it will continue for another 20s.  
You can increase the auto repeat cutoff time by increasing the value 99 in the following lines at Line 377 in handlers-hid.lua (in \linda\system\):
 
if JREPc[jid] > 99 then
JREP[jid] = nil
JREPc[jid] = 0
_loggg('[hHID] Repeat Reset’)

Hi KPBG
 
Thank you for promoting LINDA at FlightSimCon and for the offer of support. Please check that you installed the new config-vri.lua file when you installed 2.8.0. This file now contains a new display reset delay value VRI["DELAY"]=xx. You should be able to reset the fault by disabling and enabling the MCP setup. This will write the correct file to disk. Then Reload LUA Engine.
 
Please see your PMs.

No don't do anything. Can you just do a screenshot of the Range Check Error for me? I will send you a link to a new build but it won't be until tomorrow (by 1200 GMT).

Welcome to LINDA. For LINDA to work you need a registered copy of FSUIPC4. With FSX-SE you need to have all the FSUIPC and LINDA files in the correct Modules folder which is buried in /steam/steamapp/.... ( I can't remember the full path at the moment).

I can't explain why the data displayed on the MCP is no resetting. Does it matter? Surely the next time you start P3D and LINDA is clear and initialises correctly. I will do some more investigation when time permits.

Hi inancatil
 
LINDA only handles buttons and switches on joystick type devices. You need to use FSUIPC4 to assign the potentiometer as an axis.

Hi Calibra
 
Following similar reports, I have found an error in the operation of the GLOBAL SHIFT and issue a patch to fix it on the Download subforum here.
 
Please read the notes as both shift functions now latch on with a single OnPress.  If you require a the shift only while the button is held pressed then an explicit OnRelease assignment is required to cancel it.
 
This fix should allow you to solve the question you raised.

Hi Nibbo
 
Sorry to hear you are having problems setting up LINDA.
 
A couple of questions for you.  Are you using a VRInsight Combo type and, if so, what type?  Unless you are using the original MCP panel, I suggest you download LINDA 2.5.
 
To setup LINDA to work with FSUIPC:
 
1.  Make sure you have the latest full (paid) version of FSUIPC, currently 4.937.
 
2.  After copying and pasting LINDA into the FSX\Modules folder, you should see 2 folders (linda and linda-cg) alongside your FSUIPC files.  Importantly, you should have files: linda.exe, linda.lua and ipcReady.lua.
 
3.  You then need to select the Setup MCP MCP Combo page (even if you do not have one) and check the FSUIPC config. If it is not showing connected then click the 'Make change for you?' button.
 
4.  Then locate and open the file FSUIPC4.ini.  Look for the following entries:
 
[LuaFiles]
1=ipcReady 2=linda   [VRInsight] 1=COM3  
The second entry is for users of the Combo panels.
 
5.  After ensuring the above is correct, close FSX and LINDA, open LINDA and then FSX.
 
6.  Finally, make sure you have the aircraft module installed that matches your aircraft.
 
That should get you going.  Let me know how you get on.

Hi swadeep
 
Simply fsuipc.ini contains all the settings and configuration for FSUIPC including all your Warthog joystick axis data. Open it up in Notepad and have a look BUT DON'T CHANGE IT.
 
Andrew

HI Twinsim
 
Welcome to LINDA. It looks like you have the Battery Toggle function assigned to the OFF position of your Saitek switch.  Normally, you will find in each LINDA module an ON, OFF and Toggle function.
 
To check, go to the Saitek Switch Panel page and move the switch to each position. You will see the appropriate switch and function highlight. I think you need to change the functions to Battery ON (for the on position) and Battery OFF (for the off position). To do this simply click on the On Press action for each position, click on the A2A Cherokee list and find and select the correct Battery Switch function. Then click Save.

Hi Patrick
 
You are in the right area. You should be able to insert a call to your function in VRI_TIMER (at the bottom).  Then put your function (as you listed in your first posting) in lib_user.lua.  Use some test code to see that it is working first.  I can not guarantee that it will work if you do not have a VRInsight Combo MCP but give it a try.
 
A little more explanation might help. The idea behind all real time systems that must interface with the real world is that all operations need to be completed at a regular iteration rate.  This is normally 50Hz with reacting to real world events, such as handling a navigation sensor, to as slow as 1Hz for display updates. In LINDA, the core code triggers the timer code (i.e. VRI_Timer) at fixed intervals, VRI_Timer then calls all the required functions to handle button pushes and switch selections and other functions.  All these functions must be short with no long loops that would prevent them exiting before the next timer event.  Otherwise, control is not handed over to LINDA to do its own functions (such as handling joysticks) and the system will appear to freeze.
 
In more sophisticated systems, there would be a heart beat timer that would force any overrunning code to be interrupted and hand control back to a scheduler. This allows longer code to be stopped, the data saved and restarted again until it reaches completion over multiple cycles.  This was especially the case in older, much slower systems of the past.
 
Andrew