Jump to content
The simFlight Network Forums

ark1320

Members
  • Posts

    591
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by ark1320

  1. What I am finding is sometimes when I start the sim, although FSUIPC7 is also started (I see the FSUIPC7 Splash screen) by the time the aircraft has loaded, something has terminated FSUIPC7 and I have to restart it to get things working. The other thing is I have different Pilot's Deck profiles for different MSFS aircraft. Currently the way I am handling this is I have a standard Stream Deck "default" profile that does nothing but let me select the Pilot's Deck profile I want to use at that time (Switch Profile buttons). How would you handle multiple Pilot's Deck profiles? I know I could have one profile with multiple pages for the different aircraft, but I prefer not to do that because I want each profile to fit on one page and don't want to devote buttons to navigating between pages. Another approach is to use the Stream Deck Settings window to switch profiles. Thanks for any ideas, Al
  2. No Problem! Different issue: Does Pilot's Deck start FSUIPC7 or assume MSFS does that? Currently when I start the Sim FSUIPC7 is also started and sometimes there seems to be a FSUIPC7 conflict of some kind so that FSUIPC7 does not start or the sim locks up. Does Pilot's Deck/Stream Deck assume the sim is running. Should I start Pilot's Deck before starting the sim, or maybe vice versa. What do you suggest? Thanks, Al
  3. The Calculator mode using the Lvar STEP syntax now works with or without the leading L: before the Name. Al
  4. Yes, the above now works with the L: in front of the Lvar name, still can't have any spaces after the colon, which is fine -- just need to make that clear to users I think. Thanks, Al
  5. Good call, that worked! You also cannot have any spaces after the colon(:) preceding the step size although the syntax checker does not object to it. Suggest you update the below on Github (or make allowances for the L:). For simple Tasks like increasing/decreasing a L-Var you can use the $Name:Step(:Limit) Template (the Plugin will build the right RPN-Code for that): Name: The Name of the L-Var with or without preceding L:. Thanks for the help, Al
  6. I had tried it both ways as far as the signs are concerned, still did not work for some reason. The RPN approach was my second try. Al
  7. I also could not get the following increment and decrement by 100 to work: But the below using XML code did work. So again what am I doing wrong? Thanks, Al.
  8. I am using this version and am having some trouble using the LVAR command mode. For example I could not get the toggle LVAR mode below to work, but when I used Calculator code it did work. I also noticed in LVAR mode the syntax checker did not like having a space in the LVAR name. Am I doing something wrong as far as the LVAR mode goes? Thanks, Al
  9. ark1320

    Keysend

    Very strange. Some ideas: Did you make any changes -- new app, new hardware, or new addon in the Community folder that may be in conflict with FSUIPC7? Kind of sounds like your system suddenly thinks FSUIPC7 is NOT registered for some reason. Does your FSUIPC7.ini file show your registered version #? If you haven't tried it, maybe worth trying a FSUIPC7 reinstall? Al
  10. Seems to be a Windows file handling error of some kind (e.g., maybe couldn't find or open the sound file): https://learn.microsoft.com/en-us/windows/win32/api/mmiscapi/nf-mmiscapi-mmioopen Is the install of FSUIPC7 and the sound file both on the F drive? Al
  11. Any chance sound.path("F:\\FSUIPC") should be sound.path("F:\\FSUIPC7") ?
  12. I always put the sound.path instruction at the top of my scripts as part of the general script setup rather than just before the soundlplay call. Wonder if in this script a small delay is needed between the sound.path and sound.play instructions? Al
  13. Suggest you create a test Lua script with just the call to the wav file and see if that works, e.g.: sound.path("F:\\FSUIPC") sound.play("bong",2) ipc.sleep(2000) Al
  14. While waiting for John's help, here's a few things you could try if you haven't: - In the Lua script, add in some additional sound.play("bong.wav",x) lines (separated with delays) but all with different sound device #s ( none, 1, 3, 4 etc) "just in case" to see if one of them works. - Put a copy of the sound file in the same location as your Lua script, adjust the sound path accordingly, and see if that works (I'm assuming that won't be the F drive). - If you double click the wave file, an app should open and play it -- does that work? In other words, are you sure the wav file is good? - If your Lua script calls different functions, etc, make sure the sound code part of the script is actually being executed. You could make a separate Lua script just with a sound path, sound play and delay instructions and see if that works. - try a different wav file. Al
  15. No, rephrase it for what purpose at this point? It was just a beginner's mistake and maybe seeing that will help someone else. I'm brand new to both Stream Deck and Pilot's Deck, and as a start for a couple of days had been assigning "hot keys" to buttons using the standard Stream Deck capability. So that was my first thought with Pilot's Deck. As I learn more both about Stream Deck and Pilot's Deck I get a little "smarter" in how to use them. 😉
  16. OK, I understand. I'm familiar with sim XML coding, so I used calculator code with a simple button to either toggle autopilot Approach (short press) or BC (long press) on and off. Thanks, Al
  17. Seems if you just keep typing and ignore the location of the Ckeck-Symbols it works, so all good. I'd like to assign a key (or key combination) to a Stream Deck + button, but don't see how to do that. This would allow executing a default MSFS key control binding with a Stream Deck + button. I could certainly do this using the standard Stream Deck "Hotkey" assignment, but wanted to take advantage of Pilot's Deck capability to send a second keystroke using the long press option. If I can't send a keystroke directly using Pilot's Deck, I could use tiny Lua scripts to send the keycodes and then use Pilot's Deck to call the scripts, but that's seems like a cumbersome solution. Thanks, Al
  18. Finally just got it to work. I learned you have to ignore the little white round edit symbol in the variable field -- just keep typing. Trying to move the edit symbol out of the way to "make space" for typing the rest of the variable I think was a problem. And I think the slash was also an issue. I ended up using "feet per minute". Thanks again for an excellent plugin! Al
  19. Great program -- many thanks! While setting up a Stream Deck + dial stack in MSFS with a Display Value with Switch I ran into a problem because the variables (A:AUTOPILOT VERTICAL HOLD VAR, feet/minute) [ also tried (A:AUTOPILOT VERTICAL HOLD VAR, feet per minute)] and (A:AUTOPILOT AIRSPEED HOLD VAR, Knots) where not recognized in the variable address field. The tool tip said "Please match the requested format". I have not been able to figure out what is wrong. These variables are from the MSFS SDK. I had no problem setting up two other similar encoders. Here is the entries for the Vertical Speed part: This is the rest of the variable entry I also was unable to set up a button Display Value because again the variable was not recognized by Pilot's Deck. I am using FSUIPC7 ver 7.3.20 and Pilot's Deck ver 0.7.10. Thanks for any suggestions. Al
  20. You are very welcome -- glad to help out a bit where I can. Thanks for letting me know changing the gear_and_flap_chk_alt value did what you wanted. Now if you want to use the script with a different plane and do want the gear and flaps check, just copy the script, give it a slightly different name, and put back a reasonable value for the gear_and_flap_chk_alt setting. So you then have two Approach Callout scripts, one with and one without a flap and gear check. Al
  21. I think as John suggest above it is best to just comment out some lines of code rather than actually delete code. If you don't want to try that here is something easy you can try. At the top of the script in the User Settable Parameters area is this line of code which sets the Radar Altimeter altitude (in feet) at which the gear and flap call out happens: gear_and_flap_chk_alt = 800 -- RA for callout gear/flap check Try changing the 800 to a value that will never happen, such as 60000 or 0 (unless maybe you land gear up!!) Now that won't remove any code to make the script smaller if that is what you want to also do, but it should stop the call out of the gear and flap positions. It will also be easy to go back and put in a reasonable value should you want to do that for another plane sometime in the future. Let me know how that works. Al
  22. Below is a version of my Approach Callouts script for MSFS. It uses a main LUA scirpt, called ApprCallOutMSFS.lua, and a Sound folder called ApproachCallouts that contains wav files for calling out altitudes, flap settings, gear position and Minimums (Decision Height). This ApprCallOutsMSFS script works for most aircraft with flap settings F1, F2, F5, F8, F10, F13, F14, F15, F17, F20, F25, F26, F28, F35, F38, F40, F45, F48, F50. Altitude callout windows are at 2000ft, 1000ft, 500, 400, 300, 200, 100, 50, 40, 30, 20, and 10 ft. At 800ft(a user settable altitude) there is a callout of gear position and flaps position. The Decision Height callout is based on an aircraft DH Radio Altimeter setting. You will see the path to my sound folder at the top of the main Lua script -- modify the path as needed. There are a few displays as well that appear in a small window (based on the FSUJIPC Window library) which is located in the upper right corner of the screen on my particular setup -- modify the window location as needed. The uploaded zip file below contains the main Lua script and the sound folder with the wav files. There are comments at the top of the script that are worth reading if you plan to try an use or modify it. I'll be glad to try an answer any questions. Although I use this script all the time, it has been years since I originally wrote it for FSX and P3D, and also a while since I updated it for MSFS, so some of the design details are a bit hazy right now . Al ApproachCallouts4MSFS.zip
  23. Below is a version of my Approach Callouts script for MSFS. It uses a main LUA scirpt, called ApprCallOutMSFS.lua, and a Sound folder called ApproachCallouts that contains wav files for calling out altitudes, Decision Height, flap settings and gear position. You will see the path to my sound folder at the top of the main Lua script. There are a few displays as well that appear in a small window (based on the FSUJIPC Window library) which is located in the upper right corner of the screen on my particular setup. The uploaded zip file below contains the main Lua script and the sound folder with the wav files. There are comments at the top of the script that are worth reading if you plan to try an use or modify it. I'll be glad to try an answer any questions. Although I use this script all the time, it has been years since I originally wrote it for FSX and P3D, and also a while since I updated it for MSFS, so some of the design details are a bit hazy right now (age problem!). I've also put this script in the User Contributions subforum and there is a little more info there. Al ApproachCallouts4MSFS.zip
  24. You are right, I had NO idea the term "calculator code" referred to an actual MS/Asobo defined construct. Though it was just a FSUIPC name for a new capability. A search of the MSFS SDK turned up this relevant warning: Always good to lean something new! Thanks, Al
  25. Hi John, It seems the ipc.execCalcCode function does not recognize the use of > for the greater than symbol > in XML code. For example, if I execute the little test code below as shown it works in that the displayed value for Test Var1 is correct, a 3. But, if I then go back and change the 3 to a 4 and change the > symbol to > in the first line so it becomes ipc.execCalcCode(" 4 (>L:TestVar1) "), a 3 is still displayed when the code runs. Unfortunately, for some reason the > syntax (which I don't like) is frequently used for the > symbol in XML coding. I copied some code to use in a Lua script that used the ipc.execCalcCode() function in a number of lines, and it took me a loooong time to figure out it wasn't working because the code I copied used the > syntax. If getting the > syntax to work with the ipc.execCalcCode function is not a viable option, then I think a warning note of some kind in the Lua Library and Advanced Users guide would be a good idea. I looked but did not find anything on this. Thanks, Al ipc.execCalcCode("3 (>L:TestVar1) ") ipc.sleep(500) Test_Var1 = ipc.readLvar("L:TestVar1") wnd.clear(w) wnd.text(w, " Test Var1 = "..Test_Var1) ipc.sleep(5000)
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.