Jump to content
The simFlight Network Forums

WB_FlashOver

Members
  • Posts

    13
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    United States

Recent Profile Visitors

630 profile views

WB_FlashOver's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Pete, thanks so much for being on top of this. My morning flight was very frustrating trying to get my views to work properly. Finished flight, messed around for a while installing latest GPU driver, rebuilding Prepar3D.cfg, etc. Then remembered I had updated FSUIPC5 last week so went back to previous version with success. Came here and you're already on top of it. Thanks so much. I grabbed 5.121a from your updated modules page first then came here to read the threads. Again, thanks for the great program. Roger
  2. Just checked this Pete and it works great. It runs the external program perfect. Thanks for the tweak! FlashO
  3. Thanks Pete for the file. Have to test tonight. Soundman1, thanks for the suggestion on the quotes. I will double check those but think their correct. I'll look at those tonight as well. I've had trouble with Win10 and permissions with .exe files in the past. I will give it a try though if needed. Cheers FlashO
  4. I'm having a similar issue with P3D v4 and FSUIPC5 key command running an lua which in turn runs an external vbs file that has worked (and still works) under FSX-SE. I'm still working on it but no joy yet. My lua command: ext.shell("C:\\Program Files (x86)\\FSX Version Startup\\PostFlight.vbs") The key command is the same for both sims: 24=109,8,L18:R,0 -{Num-: Press=Lua DataBup }- Under "Logging" I've ticked Button and key operations, Log Lua plugins separately and Debug/Trace Lua plugins which returns the logging data below. DataBup.lua log file: ********* LUA: "DataBup" Log [from FSUIPC version 5.103] ********* 57437 System time = 16/07/2017 16:13:49, Simulator time = 16:13:01 (23:13Z) 57437 LUA: beginning "E:\Program Files\Lockheed Martin\Prepar3D v4\Modules\DataBup.lua" 57437 LUA: ...iles\Lockheed Martin\Prepar3D v4\Modules\DataBup.lua:1 57437 LUA: Global: ipcPARAM = 0 57484 >>> Thread forced exit (ipc.exit or os.exit) <<< 57484 System time = 16/07/2017 16:13:50, Simulator time = 16:13:01 (23:13Z) ********* LUA execution terminated: Log Closed ********* FSUIPC5.log. This is a segment of the log file: 41734 Advanced Weather Interface Enabled 42062 KEYDOWN: VK=109, Waiting=0, Repeat=N, Shifts=0 42062 .. This key is programmed in FSUIPC4 'Keys' options 42140 KEYUP: VK=109, Waiting=0 52953 Plug-in thread table check: Thanks for the great program and for getting version 5 out so quickly. Roger
  5. Ok, thanks Pete. It makes a little more sense to me now. I knew about the 1084 command but was unsure if killing "ALL" lua's was a good idea so I wrote one to test and that is where the incorrect line came from. I was still messing with it while writing my post and copied and pasted the lines prior to finishing with my testing. And yes, hand editing the ini file, scary huh? In reality, it sounds to me like there isn't a need for a killall command in the [Auto.xxx] as they are already terminated at profile change anyways and I don't actually have a generic [Auto] section. I love the program (wish I could get me head around it better) and thank you for your continued support. Roger
  6. Hello Pete, Yes, I'm familiar with the assignable controls within FSUIPC to run/kill/etc lua files. I actually have several already assigned to run/kill lua files to use a single rotary axis on my X52 Pro to control 'independently' the Heater, Windows, Turbo and Inter-coolers in my A2A B-17. My question was not clear now that I read it again. I've seen topics about assigning a KillAll under the [Auto.xxx] section in the FSUIPC4.ini file such as below. [Keys.B17] 18=38,8,L5:R,0 -{Up: Press=Lua A2AB17_Turbo }- 20=38,10,L5:K,0 -{ctl+Up: Press=LuaKill A2AB17_Turbo (Flag 0) }- 22=37,8,L6:R,0 -{Left: Press=Lua A2AB17_Windows }- 24=37,10,L6:K,0 -{ctl+Left: Press=LuaKill A2AB17_Windows (Flag 0) }- 26=40,8,L3:R,0 -{Down: Press=Lua A2AB17_Heater }- 28=40,10,L3:K,0 -{ctl+Down: Press=LuaKill A2AB17_Heater (Flag 0) }- 30=39,8,L4:R,0 -{Right: Press=Lua A2AB17_IntCool }- 32=39,10,L4:K,0 -{ctl+Right: Press=LuaKill A2AB17_IntCool (Flag 0) }- 33=75,8,L22:R,0 -{K: Press=LuaKillAll }- [Auto.B17] 1=Lua KillAll 2=Lua A2AB17_Turbo So, my question is about this command under the auto section. Thanks again, Roger
  7. Hello Pete. I am curious about the KillAll function. I have looked through the documents and forums in an attempt to learn more about it but it seems to escape my queries. Is it an actual lua file that I write up for the lua files I have in my modules folder or is it built into FSUIPC4? I apologize for my ignorance on this. Thanks Roger
  8. Hello, This is more of an 'info' post for any that might find the same issue I've had. I held off upgrading my Win 7 to Win 10 until just recently. I first upgraded my server pc last weekend that hosts FSX [boxed] and TeamSpeak servers as well as other items for me. It is my old gaming computer; an X58 build with i7 960 with a EVGA 680 FTW. Once I upgraded it and found troubles to be minimal I upgraded my game pc this weekend; an X99 build with a 5930K and GTX 980Ti. It went pretty well. [On both systems I did the upgrade and not a clean install]. My trouble came in Free Flight. I'd choose my stock FSX ac and spawn in (all is good), then change aircraft to test my A2A planes and FSX crashes to desktop. I can choose any plane at startup and it's fine. If I choose stock plane and switch to another stock plane (even different paint on same plane) game still crashes. 6+ hours of testing down to a couple sentences here... Installed ALL latest motherboard drivers, GPU drivers, DirectX, C++, made sure Windows was up to date, re-ran latest A2A update, re-installed latest FSUIPC, latest LINDA, etc etc. Finally started with fresh install and started adding my extras, i.e. A2A, FSUIPC, etc. I've narrowed it down to a couple of things. First I noticed that I had to remove some of my custom FSUIPC settings. I had to let FSUIPC build a new .ini file and then edit my settings again. I had to leave any weather settings alone in FSUIPC. I also found that on the Miscellaneous Tab checking "Non-scrolling FS msgs to be white" can at time cause it to be unstable. I left this checked however and went on a 2 hour flight today in the B17 and it went very smoothly. I found this in my Windows logs as well. It seems that the file ntdll.dll is to blame in almost all the crash reports. I could not find any error reports in the FSUIPC log file. Description Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: ntdll.dll, version: 10.0.10586.0, time stamp: 0x5632d9fc Exception code: 0xc0000005 Fault offset: 0x00053d87 Faulting process id: 0x15a4 Faulting application start time: 0x01d11eea207f1863 Faulting application path: E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: e12a8c9b-7883-4a2e-bc26-4adce8720c26 Faulting package full name: Faulting package-relative application ID: This is all a little above my pay-grade so it does not mean a whole lot to me but I have it working properly now. It is not just my gaming FSX that crashes but also FSX-SE and the FSX server on other pc. I know Microsoft just did it's first major update for Win 10 and thought possibly that has something to do with it. I'll be curious to see if others have the same issue. Maybe when Pete Dawson gets back in early December he can look into it and see if they have dorked something up that his wonderful program requires. Let me know if you have the same issue please. ;-) Roger
  9. Thanks Pete, For some reason I am struggling with some of this. I did more reading of manuals tonight and looking at the user contributions section. I'm "starting" to get my head around this. I'll keep at it... I'm determined and stubborn ;) Thanks again Roger
  10. Hello, I have 4 lua's for my A2A B17 all running on my Saitek X52 Pro axis Rx rotary. I'm running the multiaxis.lua plus P.D. Strogens turbo lua and then my modified of Strogens for heater, windows, and intercooler lua's. I have them assigned to run individually on left arrow, right arrow, up arrow and down arrow and then kill individually on Cntrl + xxxx arrow. What I would really rather have is for one key press to run choosen lua and kill the others. I hope this is not a repeat of a previous topic. If so I was unable to locate it. I've been through the manual(s) but have not located a way to do what I'm hoping to do. These are my current commands set is Key Presses. [Keys.B-17] 12=37,8,L7:R,0 14=39,8,L13:R,0 16=38,8,L5:R,0 18=40,8,L6:R,0 20=37,10,L7:K,0 22=39,10,L13:K,0 24=38,10,L5:K,0 25=40,10,L6:K,0 Thanks for the great progam Pete and for any help. B) Roger
×
×
  • 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.