Jump to content
The simFlight Network Forums

All Activity

This stream auto-updates     

  1. Past hour
  2. sisoffi

    ipc Lvars read slowly

    Hi spoke2112, I've tried to use your script but not work. Can you please modify the script directly in the previous? many thanks
  3. sisoffi

    ipc Lvars read slowly

    Thank you Pete and thankyou Spokes2112. this is in attach the complete Lua script. I see the example and will try it. I have also a reply from maddog team that : "I think it's all backed up by the refresh of the "exposed" variables, he kept it deliberately low for a performance talk" ill try to investigate. MADDOG.lua
  4. Today
  5. Driver170

    New windows 10 and prosim

    Sorry pete all a bit daunting at first. If I didn’t have that windows 7 ini file how would i know what ID number goes with what device and GUID? Also you said Unfortunately you have two "Flybycockpits£ devices. You'll need to test your assignments for those. If they are the wrong way around just renumber the 0 to 1 and 1 to 0. Don’t you mean 0 to 2 or 2 to 0 per my windows 7 ini file for FBC ID number?
  6. pete_agreatguy

    Voice recognition

    Well others haven't reported this. Their issues have always been solved by referring them to the main thread as I did in my original post found here:
  7. Braf123456

    Voice recognition

    I’m not worried about it I wanted to see if others had a similar problem
  8. christianbt31

    FSUIPC and HOTAS

    thank you very much, I will try.
  9. Braf123456

    Voice recognition

    It’s pro
  10. Pete Dowson

    ipc Lvars read slowly

    The offsets you are using are listed in the FSUIPC Offsets list as "reserved". Why did you choose them? They are listed in the FSUIPC as "reserved". I don't recall what for, but they may be is use for other things. As listed, and as I stated, the offsets free for users to use as they please are 66C0 to 66FF. I have no idea. What is actually reading these offsets to display them? It is that to which you need to refer, surely? I told you earlier and just above (please do read things): 66C0 to 66FF. I see spokes2112 has contributed -- his suggestion looks very good indeed. However, the big question for me is: what is reading these offsets and writing to your displays? The Log file is useless. For some strange reason you are pressing "NEW LOG" -- you did it trice, as indicated here: [Continuation log requested by user] and here: [Log closed by user request, and continued in new file] Please do NOT press NEW LOG. That starts a new blank log and you may lose the important details! Pete
  11. John Dowson

    FSUIPC and HOTAS

    Sorry, those images are specific to CH throttle calibration software. If you want a reverse zone back from idle on the same axis, then you can set that up in the throttle calibration page - just make sure that 'No reverse Zone' is not checked, and set your idle value (as well as Max (full) throttle and reverse (min) values). Check the calibration section starting on page 40 of the User Guide. John
  12. Pete Dowson

    New windows 10 and prosim

    I told you this: just make sure the ID's (the 0, 1, 2 before the = or .GUID= in those 6 lines) match your assignments! There in the [JoyNames] section in the INI -- the one I showed you in my first reply!!! Didn't you see them? Well that makes it easy then, doesn't it! In the Win10 INI the 0= and 0.GUID= should be 1= and 1.GUID=, and the 1- and 1.GUID= need to be 0= and 0.GUID=, respectively. That will sort your JetMax assignments. Unfortunately you have two "Flybycockpits£ devices. You'll need to test your assignments for those. If they are the wrong way around just renumber the 0 to 1 and 1 to 0. Pete
  13. pete_agreatguy

    Expected level of traffic at KPHL with default install

    Real Traffic would certainly be required but Real Colour isn't. You would however, see white liveries everywhere. I would recommend Real Traffic to anyone.
  14. blacklabelbraai

    Expected level of traffic at KPHL with default install

    Thanks! I thought though that to install one of the customized schedules I need to purchase Real Traffic and Real Color as well? You really are a great guy 🙂 Of course we share the same first name so I might be biased.
  15. spokes2112

    ipc Lvars read slowly

    Is this the full lua script? Probably not as there is an "end". Might be better to show the whole script. Are you using "event" listeners? If not you should. "Event" listeners will trigger only when the value has changed. It seems like you are loading script this each time any l:var is changed or it is on a constant loop, either will cause delays. The free to use offsets are 0x66CO - 0x66FF. (Modules\FSUIPC Documents\FSUIPCx Offsets Status.pdf) Another thing noticed is your offset types, maybe(?) use the following to save available user space - - UB for the cautions - UW for speed and heading - UD for altitude - SW for VS Just an example of using listeners and proper offsets. Load this lua using [auto], leaving it running while flying the maddog. --GLARESHIELD ---------------------------------------------------- --WING function md_warn (varname, value) ipc.writeUB(0x66C0, value) end function md_warn (varname, value) ipc.writeUB(0x66C1, value) end --GUIDANCE IPC function md_speed (varname, value) ipc.writeUW(0x66C2, value) end function md_hdg (varname, value) ipc.writeUW(0x66C4, value) end function md_alt (varname, value) ipc.writeUD(0x66C6, value) end function md_vs (varname, value) ipc.writeSW(0x66CA, value) end event.Lvar("L:masterwarn_adv1", 100, "md_warn") event.Lvar("L:mastercaut_adv1", 100, "md_warn") event.Lvar("L:md_ipc_ap_spd", 100, "md_speed") event.Lvar("L:md_ipc_ap_hdg", 100, "md_hdg") event.Lvar("L:md_ipc_ap_alt", 100, "md_alt") event.Lvar("L:md_ipc_ap_vs", 100, "md_vs")
  16. christianbt31

    FSUIPC and HOTAS

    Thank you John, I am using FSUIPC v 5.1.5.1 and I do not see the same image? And I only use jets type AIRBUS or BOEING ON P3D v4.5 and I do not understand how to pass in reverse when I'm idling
  17. John Dowson

    FSUIPC and HOTAS

    All axis can be reversed by selecting the 'reverse' check-box in the axis calibration screens. For throttles, there is an option to calibrate with or without reverse zones ('No reverse Zone' tick-box, top-left on throttle calibration page). Please check the user manuals. Also, this FAQ entry on setting reverse thrust: John
  18. sisoffi

    ipc Lvars read slowly

    Dear Pete, I think I understood the logic of Lvars. If the maddog reads for exxample the variable md_ipc_ap_alt = ipc.readLvar("L:md_ipc_ap_alt") and writes it in a free offset (of my choice?) ipc.writeUD(0x68F0,md_ipc_ap_alt) why this offset is 0x68F0 is in use? ( i found this old script from my old maddog) Then, instead 0x68F0 can you say me which free offset can use? there is a list of free offset can find somewhere? thanks Simone
  19. christianbt31

    FSUIPC and HOTAS

    Is it possible to program the transition in reverse with the joysticks on a HOTAS WARTHOG and if so how to proceed. Thank you for your help. *** Moved from FAQ to Support Forum: please post support requests in the Support Forum ***
  20. pete_agreatguy

    Expected level of traffic at KPHL with default install

    @blacklabelbraai, The default Real Traffic schedule traffic volumes can be found here: Tower3D Default Schedules (Real Traffic) - Album on Imgur I would HIGHLY recommend installing one of the many Custom Schedule's found here: Computer Help Blog: Tower 3D (inc. Pro) Custom Schedule's list :)
  21. sisoffi

    ipc Lvars read slowly

    log file in attach. my script for lua is : --GLARESHIELD ---------------------------------------------------- --WING master_warn = ipc.readLvar("L:masterwarn_adv1") ipc.writeUD(0x6748,master_warn) master_caut = ipc.readLvar("L:mastercaut_adv1") ipc.writeUD(0x674C,master_caut) --GUIDANCE IPC md_ipc_ap_alt = ipc.readLvar("L:md_ipc_ap_alt") ipc.writeUD(0x68F0,md_ipc_ap_alt) md_ipc_ap_spd = ipc.readLvar("L:md_ipc_ap_spd") ipc.writeUD(0x68E8,md_ipc_ap_spd) md_ipc_ap_hdg = ipc.readLvar("L:md_ipc_ap_hdg") ipc.writeUD(0x68EC,md_ipc_ap_hdg) md_ipc_ap_vs = ipc.readLvar("L:md_ipc_ap_vs") ipc.writeUD(0x68F4,md_ipc_ap_vs) ipc.sleep(50) end are not correct the offsets? thanks. Simone FSUIPC5.4.log
  22. pete_agreatguy

    Voice recognition

    Do you own Tower 3D or the Tower 3D Pro version? If you do not own the PRO version, you will not be able to use voice.
  23. Driver170

    New windows 10 and prosim

    Here is my windows 7 FSUIPC entrys [JoyNames] AutoAssignLetters=No 0=Flybycockpits 0.GUID={E1A43F20-297C-11E6-8001-444553540000} 2=Flybycockpits 2.GUID={1C3177B0-AF83-11E7-8001-444553540000} 1=JetMAX 737 Throttle 1.GUID={A9095060-D445-11E5-8011-444553540000}
  24. Driver170

    New windows 10 and prosim

    Pete thanks for the explanation but I don’t quite follow sir. What am I exactly changing and what to? Where do i find the IDs for my FBC and TQ and also the GUIDS Regarding the Autothrottle arm i just assigned that before sending the INI file to test my AT disengage button, but that didn’t even work! Do you think I should start a new Profile for PS
  25. Pete Dowson

    New windows 10 and prosim

    You are not using Joy Letters, and your Windows change will have changed the IDs as well as GUIDs associated with each device. You [JoyNames] section contains: AutoAssignLetters=No 0=JetMAX 737 Throttle 0.GUID={9C0DB280-638E-11E9-800A-444553540000} 2=Flybycockpits 2.GUID={2A48FB90-638F-11E9-8001-444553540000} 1=Flybycockpits 1.GUID={9C0DB280-638E-11E9-800B-444553540000} Your buttons are almost all assigned to devices with IDs 1 and 2 (the only exceptions being Pause Toggle and Auto Throttle Arm). So only the two are assigned to the JetMax! Change the IDs above to match what they ought to be for your assignments. The IDs are the 0, 1 and 2 before the = in each case, including the GUID lines. Also set AutAssignLetters=Yes so that letters are used for assignments and avoid these complications in the future. There's a chapter about Joy Letters in the user guide. Pete
  26. Pete Dowson

    ipc Lvars read slowly

    Check the log file! I don't understand why you are using L:Vars for standard values available direct from P3D in existing offsets. I have no idea what you "intend", I'm just amazed that you resort to L:Vars when there's no need! Look at the main FSUIPC Offset list! BTW why are you using offset 68EC? The user offsets are 66C0 to 66FF. Your zero displays might simply be something else using that reserved offset! Pete
  27. Just updated windows 10 and started prosim. I copy paste my previous FSUIPC.INI but when starting P3D none of my buttons are working that i assigned to my jetmax TQ. Surely having my Backed up ini file will restore my settings? FSUIPC5.ini
  1. Load more activity
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×

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.