raptor84
-
Posts
23 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by raptor84
-
-
11 hours ago, John Dowson said:
I can't help if you don't show me/attach your updated script.
I've attached the files. I also have the event log checked within the FSUIPC but no log file was created.
My789functions.txt FSUIPC6.1.log FSUIPC6.ini My789functions.log
-
8 hours ago, John Dowson said:
Note that you arer starting two lua dunctions in your [Auto] section, one for each profile. Better to use profile Auto sections (e.g. [Auto.B789]) to only start the luas needed for that profile
I'm a bit confuse with this one. Are you saying that in the AUTO section, it should look like this:
[AUTO.A320]
1=Lua My320functions[AUTO.B789]
1=Lua My789functions9 hours ago, John Dowson said:The functions QW_OH_LT_L_RWYTF_toggle and QW_OH_LT_R_RWYTF_toggle do not exist (and neither QW_OH_LT_L_RWYTF_on, QW_OH_LT_R_RWYTF_on, QW_OH_LT_L_RWYTF_off, QW_OH_LT_R_RWYTF_off and QW_OH_LT_R_RWYTF_offQW_OH_LT_R_RWYTF_off).
So, I need to include the above functions as well in order to use the QW_OH_LT_Both_RWYTF_toggle function??? I thought the above function was to be use individually, that's why I left it out because I wasn't trying to turn them on individually, which is the case that is happening. Meaning, when I went back and included the missing functions and assigned Ctrl+F2 to the function you saw in my lua file, what ended up happening, it turned on/off the only Left Runway Turnoff light instead of turning on/off Both Runway Turnoff light as how I want it. The function name is copied correctly from the action file, so I don't know why the QW_OH_LT_Both_RWYTF_toggle function isn't working as its intended to do?
-
Hello everyone,
I'm having some trouble with the current version of FSUIPC for P3Dv5 when assigning key assignment for the QW 787. For example, when I assign the key Ctrl+F2 to toggle on/off the Runway turnoff lights and press it, nothing happens. Meaning, as I look up at the overhead to see if the function works, nothing happens. However, when I press Ctrl+F1 to toggle on/off strobes, that works. The issues continues when I try with the Taxi light as well when pressing Ctrl+F3. Any thoughts?
-
On 1/19/2024 at 12:49 AM, John Dowson said:On 1/18/2024 at 11:11 AM, raptor84 said:
Also, I wanted to know if there was an Lvar entry for the predictive windshear (PWS)??
I don't know...try listing the lvars to see what is available.
I did try using the Lvar function AB_WX_GCS_off replacing "GCS" with "PWS" and it works. Tried it a few times. I assume the function AB_WX_PWS_on and function AB_WX_PWS_toggle will work as well.
function AB_WX_PWS_off ()
ipc.writeLvar("AB_WX_PWS", 0)
AB_MPL_LightSwitch ()
DspShow ("PWS", "off")
end -
9 hours ago, John Dowson said:Quote
[LuaFiles]
1=ipcReady
2=LINDA
3=actions
4=autopilot
5=approach
6=My320functionsSo they should be present. However, if you are not using any of these (note that ipcReady.lua will always be started automatically) then you can remove the entries. However, do NOT change the index number of the scripts you are using (My320functions.lua) otherwise the assignments to this script will no longer work.
Are you also using LINDA? If so, make sure that is installed and up-to-date.
I don't have LINDA installed on new PC, so is it ok if I remove it?? How about the actions one? Should I remove that as well?? And if I understood correctly about the index number, if I did remove LINDA and actions, it should look like this below, right?
[LuaFiles]
1=ipcReady
4=autopilot
5=approach
6=My320functionsGoing over my lua file last night, I made some updates has I had some key assignment missing (i.e. Ctl+F8) and after making the updates in my lua and ini files, everything now works as they should. Buttons on the joystick I haven't tried yet however I assume everything there is working as they should as well.
Also, I wanted to know if there was an Lvar entry for the predictive windshear (PWS)?? For example, if I were to copy and replace the "GCS" with "PWS", will work FSUIPC recognize it that way if I were to add an assignment key (i.e. if I pressed CTL+F9 ), it could have the PWS switch go from AUTO to OFF??
function AB_WX_GCS_off ()
ipc.writeLvar("AB_WX_GCS", 0)
AB_MPL_LightSwitch ()
DspShow ("GCS", "off")
end -
8 hours ago, John Dowson said:
This was because you had a VRInsight section in your ini
Well, that's interesting. Does that section automatically in the .ini file?? If that part is in my ini file for P3Dv4.5, never experience any issues with it.
8 hours ago, John Dowson said:Looks like the name of your T.16000M Joystick has changed - it was just 'T.16000M' but is now 'T.16000M Joystick'. This is why your assignments to this device were not recognised. I have corrected for this in the ini attached below.
Hmmm.... I'm surprised the name of the Joystick got changed. I think the new PC read it differently than what my old PC had read it.
8 hours ago, John Dowson said:if you are having problems with your lua, try debugging them. If they have errors on your new PC then they would have had errors on your old PC, or they are different scripts...
Remind me again, how do you debug them?? Its been a couple of years and I forgot how. Again, in my old PC, never had any issues so I like to think that it may be a different script?? I mean, new PC is Windows 11 and old PC is Windows 7, so I don't know if that has anything to do with it.
8 hours ago, John Dowson said:The lua errors should be obvious - you are using functions AB_MPL_LightSwitch, AB_OVH_Pushbutton and AB_MPL_LightSwitch which are not defined anywhere. This must also have occurred on your old PC, or it is a different script.
And you only have assignments to keys F1, F2, F3, F4, F6 and F7. No assignments to F6 (116) or ctrl (17).
Wow, then something bad really happened when I made copy of my lua file from old PC into new PC because in my old PC, again, everything worked, no issues, no errors. All buttons on joystick, key assignments I pressed did what they were suppose to do in P3Dv4.5 (old PC). So naturally, I would assume that if I copied the same lua file into new PC (P3Dv5), everything should work as assigned.
Thank you for correcting the ini file. Do I need to have any other file/program installed with FSUIPC6???
-
11 hours ago, John Dowson said:
Lua files, by default, should be placed in your FSUIPC6 installation folder.
Thanks for the reminder. In new PC, I did exactly that, putting my lua file in the installation folder ( C:\FSUIPC6 )
11 hours ago, John Dowson said:1110 VRI port 1 "com0" failed to open
As for the other error below, I don't know what that is. Never had that error or encountered any issues when using P3Dv4.5 (perhaps the reason why it doesn't fully launch anymore, you know, showing my the menu where you select airplane, create flight plan, etc.) If you go back to the beginning of the thread, I provided both my .ini files for P3Dv4 and P3Dv5 and then you replied back in the next post with an updated .ini file to use in P3Dv5 in which I downloaded it and put in the FSUIPC folder. So I don't know where that VRI port error is coming from.
11 hours ago, John Dowson said:Line 191 is:
event.flag(12,"AB_OVH_Ext_LANDING_retract")There is no such function called AB_OVH_Ext_LANDING_retract in the lua file, hence the error.
I don't have that function in my lua file then again, I may have taken it out, forgetting the reason why. I've attached both lua files with the dates in the title name. I think what I did was I updated the lua and may have copied the wrong lua and placed it in the FSUIPC folder. The lua file that is working in P3Dv4 (error free when last check on 16May23) is the file name titiled My320functions (04062022).
I'ma go back myself and take a look myself. In fact, the My320functions (04062022) lua, seems to work but I think I got some of my key assignments wrong, for example, Strobe lights not turning on, hmmm... Either way, I've attached the files below and a link to the FSIUPC6 log as well since the file was too big to upload here.
My320functions (03272022).txt My320functions (04062022).txt FSUIPC6.ini
-
15 hours ago, John Dowson said:
You can do this but you need to manually update the [JoyNames] section as your devices GUIDs will have changed. I have done this for you in the attached ini file if you could try it. Any issues, please re-attach your .log and .ini from the same session please.
Note you also need to copy across your lua scripts to the new PC - mainly My320functions.lua as you have quite a few assignments to that one...
John
Ok. I tried using the updated FSUIPC6.ini file you gave me. Again, opening up FSUIPC6, Buttons&Switches tab and putting check mark in the Profile specific? box, FSUIPC6 seems to recognize the profile I have "P3D A320" However, in the cockpit, pressing any of the assigned keys I have based off my "My320functions.lua" file (i.e. Ctrl + F7 to turn off Nose Light), nothing happens. I uninstalled FSUIPC6, deleted any folders/files left behind, restarted PC, re-installed FSUIPC6 and placed the updated .ini and My320functions.lua files in the "C:\FSUIPC6" folder, fired up P3Dv5 and opened up FSUIPC from the add-on menu within P3Dv5 and selecting my profile, again FSUIPC6 seems to recognize the profile and yet nothing happens.
Going over the FSUIPC6 log, I see that there may be an error ( *** LUA Error: C:\FSUIPC6\My320functions.lua:191: Event proc not found ). I'm not sure if that's what causing the issue? That LUA file is actually in the C:\FSUIPC6 folder and I don't think the LUA file itself should not be an issue because that's the same LUA file is use in P3Dv4.5. I've attached it for your reference. Perhaps you'll find the error that I can't see.
-
12 hours ago, John Dowson said:
You can do this but you need to manually update the [JoyNames] section as your devices GUIDs will have changed. I have done this for you in the attached ini file if you could try it. Any issues, please re-attach your .log and .ini from the same session please.
Note you also need to copy across your lua scripts to the new PC - mainly My320functions.lua as you have quite a few assignments to that one...
John
Thanks for the help. I will give it a try. My lua scripts "My320functions.lau" is already in the new PC. I have it in 3 different places (as seen below) because I mirrored it on how I have it on the other PC, that way FSUIPC is sure to read it. It may be a bit much, but at less I feel safe about it 😁
C:\Users\...\Documents\Prepar3D v5 Add-ons\FSUIPC6
C:\Users\....\Documents\FSUIPC6
C:\FSUIPC6
-
Hello everyone,
I'm having some trouble with the current version of FSUIPC for P3Dv5.
Context: I have a new PC with P3Dv5.4 installed while I have another PC that has P3Dv4.5 on it. With the current FSUIPC installed on new PC, along with all the hardward (yoke, throttle, etc.) I copied the content in the FSUIPC.ini file that I had for P3Dv4.5 for the Aerosoft A320 professional and pasted it into the FSUIPC.ini for P3Dv.5. When I start up P3Dv5 and go to FSUIPC, go to the Buttons & Switches tab and select Profile specific? check box, FSUIPC seems to acknowledge the profile. However, the issue I'm currently having is, when I press a function key, for example, if I want to turn off the RWY Turn off lights, by pressing Ctrl + F6, it should turn off the light like it did in P3Dv4.5 yet nothing happens when I do it in P3Dv5. None of the inputs I do such as moving the yoke, throttle, joystick, I'm not seeing the movements made on the aircraft. Any thoughts?
I know that the .ini for P3Dv4.5, the FSUIPC is out of date and perhaps the detection of my hardward (i.e. yoke, throttle, etc.) is missing, but that's intentional. The hardware is now connected to the new PC and I never bothered to update FSUIPC for P3Dv4.5 because earlier 2023, I was having trouble getting P3Dv4.5 work where it worked one day and all of sudden, it decided not to work. Presumably it a corrupt file somewhere and I wasn't going to figure it out even though I tried some of the troubleshoots to get P3Dv4.5 running.
FSUIPC6 (for P3Dv5).ini FSUIPC6 (for P3Dv5).log FSUIPC6 (for P3Dv4).ini
-
On 3/1/2022 at 2:22 AM, John Dowson said:
Please show me your FSUIPC6.log and FSUIPC6.ini files - they will be located in your FSUIPC6 installation folder.
John
Hi John,
I am having the same problem with the current version of FSUIPC6. For some reason, it is not reading my LUA file anymore after I made an update in it to allow me to turn off the Autobrake using one of the buttons on the joystick. Before I updated FSUPIC and added a function in the lua file, it was working fine. I've attached my .ini, lua and .log file (via the link below).
https://drive.google.com/file/d/1fEMhKrRpbhw-dReg0_JURfMN8TaMk9xB/view?usp=sharing
-
2 hours ago, nixdevelopment said:
I have a quick hot-fix:
- download and install Sublime Text Editor (it's free)
- open the PSSRWY.dat
- Go to Find -> Replace
-
in the Find textbox add
-999.000000
-
in the Replace textbox add
99.000000note: there are two empty spaces before the minus sign (up) and the first nine (down), something like __-999.00000 and __99.000000
-
hit Replace All
-
Save changes
Update utility should be working fine now.
Made the following correction above as suggested and now the utility works. Thanks for the help.
-
Hello,
Having trouble with the utility after installing AIRAC 2102. When I run the program, I get error message as per attach photo. I installed the updated PSS and PMDG AIRAC and still have this problem. Any idea what is causing this issue??
-
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.
-
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 endNote 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 ()
endelse
if _tl("AB_VC_OVH_ExtLight_Landing_Sw", 0) then
AB_OVH_Ext_LANDING_on ()
else
AB_OVH_Ext_LANDING_retract ()
end
endend
-
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 filesDid 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
-
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.
-
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
-
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.
-
got it, thanks for the clarification.
-
So that I understood correctly:
1). The existing key I have for WideFS for FSX and can be used for WideFS7 for P3D4??
2). The existing key I have for FSUIPC4 for FSX WILL NOT work for FSUIPC6 for P3D4 which results me having to purchase a key for FSUIPC6??
-
I already have FSUIPC4 with WideClient for FSX that I purchased last year. Now that I have P3dv4.5 installed, do I need to purchase FSUIPC6?? Because I'm a bit confused as on the website, it says,
Note: if you have purchased WideFS to work with FSUIPC4 or FSUIPC5, there is no need to re-purchase. Your existing registration details will still be applicable.
Am I to presume that the FSUIPC4 was for those who had it installed for earlier versions of P3D??
QW 787 Key assignment not working
in FSUIPC Support Pete Dowson Modules
Posted
Pretty interesting you say that because I'm not writing or changing anything. Using the files from the link below, in fact, all I'm doing is after I convert the file extension from lua to txt extension, I 'm copying the functions that I only want to use. So its not me causing the error. It appears the error is already there to begin without me knowing.
https://www.avsim.com/forums/topic/538165-qw787-dreamliner-v11-9-mar-2020/
I don't have or use LINDA. I don't know if the coded functions in the files from the link above is missing anything or if it contains errors like you mentioned about the numeric lvars? How was I suppose to know what was wrong? I assume the functions in the lua files from the link above are correct. So for example, if I'm copying the QW_OH_LT_Both_RWYTF_toggle function (those 2 or 3 lines) as outlined from auctions.lua file, I assume its going to work however, it appears something is missing because whom ever created that function must've left something out for that function to work, wouldn't you agree? Perhaps what I got to do is go back and modify the QW_OH_LT_Both_RWYTF_toggle function to look something similar to how QW_OH_LT_TAXI_toggle and QW_OH_LT_STROBE_toggle look like because those 2 functions work perfectly fine when I assigned the press key I wanted to use. Unless you have a different solution on how its suppose to look like.
I'm not trying to rant here but if I didn't need to come to this forum and seek help, I wouldn't have done so, even if the errors were obvious. In fact, I try searching the forum to help me solve the issue I'm having before posting my issue because I'm not trying to waste anyone's time here. I don't know what I'm looking for or even know what the error means. I don't think there is a manual to help translate the error, is there?? I'm not someone who knows code or software programming. That's why I post my issue even if they are obvious errors. I do appreciate you helping out.