Jump to content
The simFlight Network Forums

Stevan

Members
  • Posts

    30
  • Joined

  • Last visited

  • Days Won

    1

Stevan last won the day on December 15 2018

Stevan had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    ATL

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Stevan's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare

Recent Badges

1

Reputation

  1. Thanks John, I will look at the separate document entitled "FSUIPC Lua Plugins" to better understand the lua plugin process. Thank you for help!
  2. You're right this is the first time dealing with LUA scripts. I did look at your plugin document in your Adv guide. It clearly states that the script should reside where the FSUIPC.ini file is and don't add anything to the [LuaFiles] section. But I missed or did not see anything as to what the new command selection should look like "Lua SetPauseMSFS&P3D", so I was looking for the "SetPauseMSFS&P3D" and I did the example like "1=Lua SetPauseMSFS&P3D" that went under Auto section. Thats why I added it, but I did not know that I did not need it. I only see one page dealing with Lua plugins (pg-39). Is there somewhere else it's list under? Sorry for taking up your time on matter like this. Steve
  3. Thanks I see it now, I was looking for it under the S commands.
  4. Removed [Auto] section Added 1=Lua SetPauseMSFS&P3D to General section .Restarted FSUIPC7 it adds it to the LUAFiles section Try to assign button to SetPauseMSFS&P3D but it does not show up in the drop down list
  5. Thanks John, Sorry and thanks , when I was on the site I clicked on the file, it would not download. This may be because I was not logged in at the time. I read the docs on LUA implementation, but I can't seem to see it in the button selection drop down box for commands. I have it listed in the FSUIPC7.ini [Auto] 1=SetPauseMSFS&P3D I want to assign it to my ~ button. I'm in the middle of a 50-hour flight, do I need to stop FSUIPC7 and restart it to see the LUA? What I'm I missing? Steve
  6. I can't find it anywhere. I'm hoping that someone has it. The script name is SetPauseMSFS&P3D.lua or PauseMSFS_TOD.lua The SetPauseMSFS&P3D.lua script attached below makes use of the FSUIPC Lua event and wnd libraries (as suggested by John Dowson) and can be used to pause MSFS or P3Dv4.5/v5.1 from 1 minute to days after the script is run. When run, the script asks for a pause time and if none if provided within two minutes the script closes with a brief message. If a pause time is entered, for example 260 minutes until a Top of Descent, the user would see Then after hitting the Enter key the display would change to This display will change once per minute as the time to pause counts down towards zero. If the user decides to cancel the pending (future) pause with the Enter key, the display briefly changes to When the pause time is reached, the sim pauses and looks just like a pause had been initiated with the ESC key. To cancel a paused sim you just need to click on Resume. This script uses the wnd (Window ) library for display, so you can move the display window with the arrow keys and use the ctrl + arrow keys to resize the window. The window must have the focus to do this. The new window display position will be stored in your FSUIPC .ini file. As an alternative to using the arrow keys you can directly edit the window position and size coordinates in the FSUIPC7.ini file. Look for the entry under [ExtWindow]. It seems best to do this when FSUIPC7 is not running. You may also have to edit the window size and position in the lua file.
  7. Thanks John for your work on the beta version. I will try it. I was using 7.08.
  8. Hello John, Try to configure the switch using button press in FSUIPC, but its not detected. Is this a known issue?
  9. I must be tried, I don't see anything using D device. Sorry that the .ini file was not appended. This 6=DR,256,D,36,0,0,0 -{ DIRECT: SteeringTiller }- was deleted but it was added again (5=CR,256,D,36,0,0,0 -{ DIRECT: SteeringTiller }-). Steve FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log
  10. Ok I found the issue was the reg entries that were to be delete were not being deleted. So I removed them out that fix the duplicate message. In my .ini file under joystick I'm getting "missing joystick" message but everything else is ok. I image its one of my reg entries for joystick but I can't tell which one it is. [JoyNames] AutoAssignLetters=Yes 0=X56 H.O.T.A.S. Throttle 0.GUID={0F856C10-889C-11EB-8001-444553540000} 1=T-Rudder 1.GUID={7CCBF530-0A68-11EB-800E-444553540000} 2=X56 H.O.T.A.S. Stick 2.GUID={0F856C10-889C-11EB-8003-444553540000} A=X56 H.O.T.A.S. Throttle A.GUID={0F856C10-889C-11EB-8001-444553540000} B=T-Rudder B.GUID={7CCBF530-0A68-11EB-800E-444553540000} C=X56 H.O.T.A.S. Stick C.GUID={0F856C10-889C-11EB-8003-444553540000} D=<< MISSING JOYSTICK >> << MISSING JOYSTICK >> ********* FSUIPC7, Version 7.0.6 (10th March 2021) by John Dowson ********* Checking for FS path in 'C:\Users\steva\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt' FS path found = E:\Games\Microsoft Flight Simulator 2020\ WebSocket server found: E:\Games\Microsoft Flight Simulator 2020\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe Windows 10 Pro 64 Bit reported as Build 19042, Release ID: 2009 (OS 10.0) Reading options from "E:\Games\Microsoft Flight Simulator 2020\FSUIPC7\FSUIPC7.ini" Checking the Registrations now ... FSUIPC7 Key is provided WIDEFS7 not user registered, or expired 79 System time = 19/03/2021 10:15:43 79 FLT path = "C:\Users\steva\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\" 110 ------------------------------------------------------------------- 125 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 157 FS path = "E:\Games\Microsoft Flight Simulator 2020\" 157 ---------------------- Joystick Device Scan ----------------------- 157 Product= T-Rudder 157 Manufacturer= Thrustmaster 157 Vendor=044F, Product=B679 (Version 1.16) 204 GUIDs returned for product: VID_044F&PID_B679: 204 GUID= {7CCBF530-0A68-11EB-800E-444553540000} 204 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1023,Y1023,Z1023 219 Product= Saitek Pro Flight X-56 Rhino Throttle 219 Manufacturer= Mad Catz 219 Serial Number= k0003507 219 Vendor=0738, Product=A221 (Version 1.0) 219 GUIDs returned for product: VID_0738&PID_A221: 219 GUID= {0F856C10-889C-11EB-8001-444553540000} 219 Details: Btns=36, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X1023,Y1023,Z255 219 Product= Saitek Pro Flight X-56 Rhino Stick 219 Manufacturer= Mad Catz 219 Serial Number= k0023297 219 Vendor=0738, Product=2221 (Version 1.0) 219 GUIDs returned for product: VID_0738&PID_2221: 219 GUID= {0F856C10-889C-11EB-8003-444553540000} 219 Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U255,V255,X65535,Y65535,Z0 219 ------------------------------------------------------------------- 219 Device acquired for use: 219 Joystick ID = 1 (Registry okay) 219 1=T-Rudder 219 1.GUID={7CCBF530-0A68-11EB-800E-444553540000} 219 Device acquired for use: 219 Joystick ID = 0 (Registry okay) 219 0=X56 H.O.T.A.S. Throttle 219 0.GUID={0F856C10-889C-11EB-8001-444553540000} 219 Device acquired for use: 219 Joystick ID = 2 (Registry okay) 219 2=X56 H.O.T.A.S. Stick 219 2.GUID={0F856C10-889C-11EB-8003-444553540000} 219 ------------------------------------------------------------------- 282 LogOptions=00000000 00000001
  11. I reinstalled the device drivers after running removeDevs.reg and rebooting the system. The x56 will not be recognized with installing the software and drivers. I will play around with this until I get it right. Thanks far getting me this far.
  12. FSUIPC7.ini Sorry the .INI file was not attached
  13. Follow your steps, but it looks like that (duplicated in Registry) areFSUIPC7.ini still there. FSUIPC7.log
  14. Thank you, John! Here's my JoyScan.csv file. FSUIPC7.JoyScan.csv
×
×
  • 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.