Having trouble with FSUPIC6

[raptor84]

hello,

I'm currently having trouble with FSUIPC6 for P3Dv4.5

About a week before Christmas, I updated FSUIPC6 to the current version (6.0.11), assigned a few more functions from my LUA file to use the keyboard and did a few flights. All was working well. On 08Jan21 when I decided to do some flights again, I noticed that when I was pressing the buttons on the joystick or key pressing on the keyboard for the functions I had assigned, none of the functions assigned in FSUIPC was working. P3Dv4.5 does pick up the FSUIPC add-on file. Not sure what's going on but I was wondering if someone can help me figure this out.

FSUIPC6.log

[John Dowson]

First, if its FSUIPC assignments, could you disable Linda for the time being. Otherwise, if you are using Linda, you should use their support forums.

Activate event logging and button & keys (already activated), then produce a short log where you press one of you assigned buttons. Then attach the new log, together with your FSUIPC6.ini file and I'll take a look.

John

[raptor84]

I'm not using LINDA even though the program may be installed on my PC. Basically I never use LINDS GUI when I fly, I understand FSUIPC picks up LINDA.LUA and starts communication with it. Why I installed LINDA, I don't know nor do I know how to disable it. Everything is assigned via FSUIPC. The link below are the FSUIPC files

https://www.dropbox.com/s/4ctvvs1f8s3w852/FSUPIC logs.rar?dl=0

[John Dowson]

15 hours ago, raptor84 said:

Why I installed LINDA, I don't know nor do I know how to disable it.

Just rename your linda.lua script, or, better, remove the call to that script from your ipcReady.lua script.

15 hours ago, raptor84 said:

The link below are the FSUIPC files

There is no FSUIPC7 log file included, only you installation log which is not relevant. Please disable Linda, activate the logging requested (event and button & keys) then produce a short log where you press one of you assigned buttons (i.e. not keys - we'll check your issue for buttons first)

Could you update to FSUIPC6 v6.0.12 first though please - this was released yesterday.

Your ini file also shows that you are not using the JoyLetters facility. This means that you joystick IDs could have changed, which would invalidate your assignments. You should activate the JoyLetters facility by setting the AutoAssignLetters ini parameter (in the [JoyNames] section) to Yes.
You also have one assignment to a non-existent device (with id=0) that you can delete:
     0=0X,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-

Maybe also check your FSUIPC6.ini to see if you can determine if your assignments (buttons and axes) are assigned to the correct devices (with 1=T.16000M, 2=TWCS Throttle, 3=Yoke).

[raptor84]

7 hours ago, John Dowson said:

Just rename your linda.lua script, or, better, remove the call to that script from your ipcReady.lua script.

So, do I just delete it the ipcReady.lua file or do I have to open it using Notepad and delete a line or something within the file??

7 hours ago, John Dowson said:

There is no FSUIPC7 log file included,

I thought I did provide the FSUIPC6 log file in my first post. Anyway, after I did the update, to FSUIPC6.0.12, I created a log which is now attached.

https://www.dropbox.com/s/57o2txjq3r0m89t/FSUIPC6.log?dl=0

7 hours ago, John Dowson said:

Your ini file also shows that you are not using the JoyLetters facility. This means that you joystick IDs could have changed, which would invalidate your assignments. You should activate the JoyLetters facility by setting the AutoAssignLetters ini parameter (in the [JoyNames] section) to Yes.

 

You also have one assignment to a non-existent device (with id=0) that you can delete:
     0=0X,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-

Maybe also check your FSUIPC6.ini to see if you can determine if your assignments (buttons and axes) are assigned to the correct devices (with 1=T.16000M, 2=TWCS Throttle, 3=Yoke).

Never seemed to be a problem for me not having done that in the past using the JoyLetters facility.

The      0=0X,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-   I have the CH Products Flight yoke which I use it as a steeringTiller as I don't have any rudder pedals. Not sure if this assignment is in reference to that. I also have my joystick as assigned as SteeringTiller as well. Perhaps I need to play around and figure out, during takeoff roll, if I need the joystick to be assigned as SteeringTiller as well.

[John Dowson]

1 hour ago, raptor84 said:

So, do I just delete it the ipcReady.lua file or do I have to open it using Notepad and delete a line or something within the file??

The latter. But if you can always do the other option - rename your linda.lua to linda.lua.unused (or whatever new name you want to give it).
I just want to know that Linda isn't doing anything behind the scenes. Its probably not related to your issue, but always better to eliminate (at least temporarily) when investigating an issue.

I'll look at your new log tomorrow.

[John Dowson]

First, when you provide files, can you always give me both the latest FSUIPC4.ini and your FSUIPC4.log. I always need to see them together (and sometimes the Joyscan.csv file).

On 1/13/2021 at 12:35 PM, John Dowson said:

Maybe also check your FSUIPC6.ini to see if you can determine if your assignments (buttons and axes) are assigned to the correct devices (with 1=T.16000M, 2=TWCS Throttle, 3=Yoke).

You didn't respond to this. This is important as I need to know what assignment is assigned to what device. For example, your P3D A320 axis profile has your aileron, elevator and rudder assigned to device 1, your T.16000M - is this correct?

There is also an error in your My320functions.lua that needs correcting:
   241771 *** LUA Error: ...Users\Rich Dogg\Documents\Prepar3D v4 Add-ons\FSUIPC6\My320functions.lua:188: 'end' expected (to close 'function' at line 121) near '<eof>'
 

And your latest log shows that you have event logging activated, but not Buttons & Keys, as requested - but I cannot confirm as you didn't attach your FSUIPC6.ini file.

So, to be clear, please do the following:
    - correct the error in your lua script
    - let me know if your axes assignments are assigned to the correct device or not
    - change AutoAssignLetters=No to AutoAssignLetters=Yes in your FSUIPC6.ini
    - disable Linda (temporarily) by renaming your linda.lua file
    - start P3D/FSUIPC6 and load the Aerosoft A320 professional UNITED AIRLINES N449UA
    - activate logging for events and buttons and keys in FSUIPC6
    - press one of your assigned buttons
    - Stop P3d, and show me your latest FSUIPC6.log and FSUIPC6.ini files

John

 

[raptor84]

5 hours ago, John Dowson said:

First, when you provide files, can you always give me both the latest FSUIPC4.ini and your FSUIPC4.log. I always need to see them together (and sometimes the Joyscan.csv file).

Please see attached file. I also included a screenshot of FSUIPC that show I do and always had the event, along with Button & Keys, logging activated. Not sure if there is something else I need to do there. If none of my log files are providing the info you need after the 4th attempt, it probably safe to say there is something wrong with either FSUIPC or on the user end. Again, not sure.

5 hours ago, John Dowson said:

There is also an error in your My320functions.lua that needs correcting:

   241771 *** LUA Error: ...Users\Rich Dogg\Documents\Prepar3D v4 Add-ons\FSUIPC6\My320functions.lua:188: 'end' expected (to close 'function' at line 121) near '<eof>'

 

There should be no error occurring with my lua file. As I said in my first post, when I started to assign additional functions a few days before Christmas using the functions outlined in my lua file, I tested it out a few times to ensure if the function was working, which it was, and when I did do a few flights, all was well. It wasn't until after New Years that when I did a flight again, most of the functions were not working anymore. Now, at first when I was assigning the new functions to use on keyboard (i.e Ctrl+F1) it wasn't working. After I assigned the newly functions and did an FSUIPC update (from 6.0.10 to 6.0.11) the functions worked. So I figured it was just me needing to update FSUIPC in order for me use the newly assigned functions. So I doubt there is anything wrong with my LUA file although I am providing a copy it and you can take a look and see if there is something I left out.

6 hours ago, John Dowson said:

You didn't respond to this. This is important as I need to know what assignment is assigned to what device. For example, your P3D A320 axis profile has your aileron, elevator and rudder assigned to device 1, your T.16000M - is this correct?

Yes, its assigned correctly. Never had a problem controlling the elevator, aileron and rudder that is assigned to my joystick.

6 hours ago, John Dowson said:

So, to be clear, please do the following:

    - correct the error in your lua script
    - let me know if your axes assignments are assigned to the correct device or not
    - change AutoAssignLetters=No to AutoAssignLetters=Yes in your FSUIPC6.ini
    - disable Linda (temporarily) by renaming your linda.lua file
    - start P3D/FSUIPC6 and load the Aerosoft A320 professional UNITED AIRLINES N449UA
    - activate logging for events and buttons and keys in FSUIPC6
    - press one of your assigned buttons
    - Stop P3d, and show me your latest FSUIPC6.log and FSUIPC6.ini files

Did all of the above except for the first one as I believe there is nothing wrong with my LUA file although I did provide a copy of it for a second pair of eye can take a look and see what and where I'm missing any additional info.

As for the 4th one, I changed the Linda.lua file to Linda.lua.unused as suggested in earlier post.

https://www.dropbox.com/s/oxao6yxhcvwcmkm/My FSUIPC logs.rar?dl=0

[Pete Dowson]

4 hours ago, raptor84 said:

There should be no error occurring with my lua file.

But this error:

4 hours ago, raptor84 said:

241771 *** LUA Error: ...Users\Rich Dogg\Documents\Prepar3D v4 Add-ons\FSUIPC6\My320functions.lua:188: 'end' expected (to close 'function' at line 121) near '<eof>'

is a syntax error in Lua, not an error from any function supported by FSUIPC.  This is the function:

function AB_OVH_Ext_LANDING_toggle ()
    if A330 then
        if _tl("AB_VC_OVH_ExtLight_Landing_Sw", 0) then
            AB_OVH_Ext_LANDING_on ()
        else
            AB_OVH_Ext_LANDING_off ()
        end

    else
        if _tl("AB_VC_OVH_ExtLight_Landing_Sw", 0) then
            AB_OVH_Ext_LANDING_on ()
        else
            AB_OVH_Ext_LANDING_retract ()
        end
    end

Note the number of "end" statements. They complement only the "if ... then ... else" statements. There's no 'end' to finish the function.

Unfortunately it only takes one error in a Lua file to stop the Lua interpreter compiling the plug-in. This is why it is always a good idea to look in the Log to see if the Lua is loaded without error when you find something not working.

Note also that the interpreter fails on the first error it finds, so you need to check again after correcting this one, just in case.

Pete

 

[raptor84]

5 hours ago, Pete Dowson said:

function AB_OVH_Ext_LANDING_toggle ()
    if A330 then
        if _tl("AB_VC_OVH_ExtLight_Landing_Sw", 0) then
            AB_OVH_Ext_LANDING_on ()
        else
            AB_OVH_Ext_LANDING_off ()
        end

    else
        if _tl("AB_VC_OVH_ExtLight_Landing_Sw", 0) then
            AB_OVH_Ext_LANDING_on ()
        else
            AB_OVH_Ext_LANDING_retract ()
        end
    end

Note the number of "end" statements. They complement only the "if ... then ... else" statements. There's no 'end' to finish the function.

So are you saying that I needed 1 more "end" to fix the problem in my LUA file??? Therefore, it should look like this below:

function AB_OVH_Ext_LANDING_toggle ()
    if A330 then
        if _tl("AB_VC_OVH_ExtLight_Landing_Sw", 0) then
            AB_OVH_Ext_LANDING_on ()
        else
            AB_OVH_Ext_LANDING_off ()
        end

    else
        if _tl("AB_VC_OVH_ExtLight_Landing_Sw", 0) then
            AB_OVH_Ext_LANDING_on ()
        else
            AB_OVH_Ext_LANDING_retract ()
        end
    end

end

[Pete Dowson]

4 hours ago, raptor84 said:

So are you saying that I needed 1 more "end" to fix the problem in my LUA file??? Therefore, it should look like this below:

Yes. As well as following the clear unambiguous error report given in the Log, it's easy to check. Just make sure there#s an 'end' to go with and end every function and an 'end' to finish every "if ... else".

For more information and tutorials on the Lua language please see lua.org.

To correct things given error notifications you need to use the line numbers it gives you, so use an editor with line numbers enabled.

Pete

 

[John Dowson]

I see Pete has responded. The button presses in your log are assigned to toggle a lua flag for that script, which is why they aren't working.
Correct that script and try again.

John

[raptor84]

Thank you guys for taking the time to help me solve the issue I was having. I made the correction and things seems to be working now as they should. Always good to have a second pair of eyes to help point out what the problem is.