Jump to content
The simFlight Network Forums

All Activity

This stream auto-updates     

  1. Today
  2. Yesterday
  3. sisoffi

    ipc Lvars read slowly

    all other Lvars (apart guidance) are only output Leds
  4. sisoffi

    ipc Lvars read slowly

    Pete, I don't use Linda. I installed it to understand if through its logging I can better understand the lua variables. I can unnistall it. The hardware I still use relies on Skalarki (hardware manufacturer for 320) but no longer supports the md80 anymore since the old version. I reused the same file even on the new version as many Lvars are still in use and I added the new Lvars for guidance/glareshield. Could you help me better solve the script? I tried to insert the one above but it doesn't work.
  5. Pete Dowson

    New windows 10 and prosim

    Test them first. You need to determine which is which of the two identical units. Pete
  6. Pete Dowson

    ipc Lvars read slowly

    I see you are using LINDA. I think you may need to ask their support. You are constantly writing zero to those offsets, the ones you will or cannot say why you chose. You still haven't said what it is driving your displays. How can you expect help? The other thing I note is that your Lua plug-in is headed: -- MD80 Interface BY sKALARKI -- LUA Script V 1.0 -- 20.10.2011 2011? That must surely pre-date the MD80 aircraft you are using? What makes you think it is in any way still relevant? Maybe this "sKALARKI" can offer something for your P3D4 version? BTW, the Lua is a bit of a mess. All the part till "--GLARESHIELD" only gets run once, when the plug-in is first loaded. Is that what you really intended? Then, at the end of your Lua plug-in you have "ipc.sleep(50)" which is really unnecessary and is only excuted the once too. and the "end" right at the end is invalide -- there's nothing for it to complete. Pete
  7. Driver170

    New windows 10 and prosim

    Thanks pete, i will change them about tonight. Hopefully it goes smoothly 😂
  8. sisoffi

    ipc Lvars read slowly

    i attach the new log file. The lua script post to spoke2112 doesn't work FSUIPC5.log MADDOG.lua
  9. Pete Dowson

    ipc Lvars read slowly

    I've no idea what that means1 This is probably because the offsets are being read by something else, which oyu haven't identified, and changing them won't work without changing that too1 WHAT is reading the offsets? Is it the MadDog directly? does it use FSUIPC? Does it say it needs FSUIPC? Pete
  10. Pete Dowson

    New windows 10 and prosim

    The GUID and name of the device go hand in hand. They are read from your system as it is now. it is only the IDs which need sorting out. To do this just look as your assignments. Button assignments will bt P, R or U (for Press, repeat or Up) followed by the axis name (X, Y, Z etc). You can see the joystick IDs on screen in the assignments tabs, at the top. Yes, sorry. So, you get the hang of it now? Pete
  11. Driver170

    New windows 10 and prosim

    Only buttons i need to assign are these. The rest are through PS [Buttons.PS] 6=P2,4,C65561,0 -{PAUSE_TOGGLE}- 7=R1,3,C65602,0 -{THROTTLE_DECR}- 8=U1,3,C0,0 -{Custom control: <0>}- 9=P1,0,C65752,0 -{PARKING_BRAKES}- 10=U1,0,C65752,0 -{PARKING_BRAKES}- 11=P0,4,C65561,0 -{PAUSE_TOGGLE}- 12=R1,1,C66635,0 -{THROTTLE1_DECR_SMALL}- 13=U1,1,C65967,0 -{THROTTLE1_CUT}- 14=R1,4,C66636,0 -{THROTTLE2_DECR_SMALL}- 15=U1,4,C65972,0 -{THROTTLE2_CUT}- 16=R2,5,K190,8 -{Key press: .>key}- 17=R65,0,K190,8 -{Key press: .>key}- 18=R65,1,K190,8 -{Key press: .>key}-
  12. 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
  13. 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
  14. 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?
  15. 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:
  16. Braf123456

    Voice recognition

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

    FSUIPC and HOTAS

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

    Voice recognition

    It’s pro
  19. 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
  20. 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
  21. 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
  22. 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.
  23. 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.
  24. 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")
  25. 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
  26. 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
  27. 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
  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.