Jump to content
The simFlight Network Forums

spokes2112

Members
  • Content count

    133
  • Joined

  • Last visited

  • Days Won

    3

spokes2112 last won the day on April 8 2016

spokes2112 had the most liked content!

Community Reputation

9 Neutral

About spokes2112

  • Rank
    Advanced Member
  • Birthday 04/03/1967

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male
  • Location
    KGRB
  • Interests
    FS Programming, Electronics, Vintage Radios
  1. If my memory serves correct - no.. The commands left/right/up/down overwrite the axis values.. (?) I'd take that with a grain of salt without testing.. (lol) It was so long ago and have no reference (or sim) in front of me..
  2. This is either a bug or designed as is..(internal sim, not FSUIPC) When using a pure "set", not "axis set", if the value is unchanged from the last time "set" was used it does nothing.. Dealt with this on throttle set gauge. Try these instead. AXIS ELEV TRIM SET 65766 For aileron & rudder keep using your compounds but on press set them to a value of 1 then on release set to zero. An alternative... A lua may be a little better for these 2. Should work for you.
  3. spokes2112

    Fuel Pump LO setting BB 58

    Answered over at AVSIM --> https://www.avsim.com/forums/topic/532223-beechcraft-baron/?do=findComment&comment=3818424
  4. spokes2112

    Saitek Elevator Trim with FSUIPC

    Search for "ButtonRepeat" or pg 19 in the FSUIPC4 for Advanced Users.pdf. That should do it for you.
  5. spokes2112

    Start and stop sounds

    Dave, You need to use "listening" code or a loop to keep the lua alive. The best way is a listener, it's all part of the Event Library in the Lua Library.pdf. The one drawback is that it should be started via the [Auto] section in the .ini . Although it could be started in some other fashion. There should be no need for a query since the flag can only be 1 (sound playing) or 0 (sound off). Maybe this will help - taken from a previous code project (it works) and not tested in this example. Roman -- Use (LuaSet "lua name") to start the sound and (LuaClear "lua name") to stop it. -- The parameter for the FSUIPC UI in this code example is zero -- The lua should be started via the [Auto] section in the FSUIPC#.ini -- OPTION, adjust path as needed, if wanted -- sound.path("G:/FSX/Modules") local flagged = 0 function Sound_Control(flag) flagged = ipc.testflag(0) if flagged == true then -- OPTION, play sound once -- MySound = sound.play("ElectricPump.wav") -- OPTION, loop the sound continuously until turned off MySound = sound.playloop("ElectricPump.wav") else sound.stop(MySound) end end event.flag(0,"Sound_Control")
  6. spokes2112

    Elevator pitch/trim error.

    Pete is away until the 15th.. Looked at the .ini, doesn't seem like anything is awry. Best thing is start FS for a very short period, up to showing the bad pitch trim, correct the trim, then shut down. Attach the FSUIPC#.log Roman
  7. spokes2112

    ?-SimC Offsets Status Feedback

    Hi Pete, Went through the tests again. It seems that the write within the original while-do wasn't fast enough, too many other things going on. Tried a while-do in it's own thread and the result is that the write occurs - sorry 'bout that.. But, the updates are factors slower than XMLTools. while 1 do ipc.writeDBL(0x2020, 123) end Yes that is exactly what's happening. XMLTools seems to have a fast enough update to make it usable. Tom Taguilo's .dlls are here - http://www.fsdeveloper.com/forum/search/13164829/?q=XMLTools&t=resource_update&o=date The P3Dv4 package does not include documentation, refer to the P3Dv3 package for the docs. The XML interface to his .dll is there, also included are some other things that are way over my pay grade ;-), specifically "XMLTools.h" & "XMLTools Class for C++ projects.pdf". Maybe that will help. Roman
  8. Hi Pete, Been putzing around with a little trick found on FSDeveloper regarding corrected fuel flow & keeping turboprops running away during start and other conditions. It uses (>C:SIMVARS:TURB ENG CORRECTED FF:1, pounds per hour) through the XMLTools.dll interface. It works well but needs gauge coding per aircraft. I was trying to get this to work using lua by writing to 0x2020 (& the 3 others) so it could work globally on all turboprops. The feedback is --- doesn't work. The following code was inside of a while - do loop which does work perfectly but there was no return as wanted via logging. ipc.writeDBL(0x2020, 200) Tested some others too w/ ?-SimC in the write column - no go. I guess "it is what it is", just feedback is all. I know you're busy with all the P3Dv4 stuff, but if you ever get around to looking into it, getting the "Turbine Engine # corrected fuel flow" & "Reciprocating engine # starter torque" (another trick) working, both ?-SimC for writes, would be "the cat's meow" ;-) FSX Acceleration / FSUIPC v4.971b Regards, Roman
  9. IIRC if it's not a "green line" type message you can, once it's open, drag, resize & undock the window and move it over to where you want. It should work if GSX does not supply the location/size when opening the window. All my development LUA's which use the non-green line message displays are put in certain locations using the drag/size fashion and they are remembered by FSUIPC between sessions. ex. FSUIPC4.ini snippet - [Window.LUA display] Docked=7354, 2810, 3545, 1704 Undocked=2446, 208, 312, 134 They are also entered within a saved flight (FSX) although it looks like there is some "cleanup" problems ex. Test.flt snippet - [WAR EMERGENCY POWER] Undocked=False ScreenUniCoords=0, 122, 819, 0 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 0 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 0 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 0 UndocCoords=0, 0, 0, 0 [AUTO COORDINATION] Undocked=False ScreenUniCoords=0, 122, 819, 0 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 0 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 0 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 0 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 0 UndocCoords=0, 0, 0, 0 [WATER RUDDER] Undocked=False ScreenUniCoords=0, 122, 819, 404 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 404 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 404 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 404 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 404 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 404 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 404 UndocCoords=0, 0, 0, 0 Undocked=False ScreenUniCoords=0, 122, 819, 343 UndocCoords=0, 0, 0, 0 [LUA display] Undocked=False ScreenUniCoords=5627, 616, 1782, 707 UndocCoords=0, 0, 0, 0 Since this P3D and you use GSX I could be all wrong... No harm in trying. Roman
  10. Try updating to version 4.959 (you have 4.958). Just about every time P3D is updated FSUIPC requires the newest version.
  11. spokes2112

    Configuring the ND BK-117

    Dave, Sent you a PM. Roman
  12. spokes2112

    Configuring the ND BK-117

    I can bet that they are using L:Vars with logic to control the audio panel. ex. ( the L:Var "(L:ADF_IDENT, bool)" is just made up as an example ) (L:ADF_IDENT, bool) (A:ADF IDENT, bool) != if{ (>K:RADIO_ADF_IDENT_TOGGLE) } Or even worse, code similar to this which would cause "command flooding" (L:ADF_IDENT, bool) if{ (>K:RADIO_ADF_IDENT_ENABLE) } els{ (>K:RADIO_ADF_IDENT_DISABLE) } You're going to want to "see" what's going on by using ( at the same time) the facilities in FSUIPC to monitor L:Vars and the commands sent to the sim to figure this out. For commands use - FSUIPC | Logging Tab | "Events (non-axis controls)" | "Send to console window" For L:Vars use (for ease) - Using these will sort out what is going on. If my suspicions are correct you will need to use LUA to interface in the long run. Wish I could help more but I do not own the BK-117. EDIT - If the gauges are the XML/.CAB style, you could also go through the code to see what they're doing. If it's a .GAU/.DLL you may be out of luck dealing with possibly poor programming. (Seen it before, the ABC F-8F Bearcat has this problem, of all things -- ADF Ident too!) The last resort may be to use the original artwork and then recode properly.
  13. Maybe ?? - f:write("\r\ <DienstBeginn>" .. DienstBeginn .. "</DienstBeginn>" ) As a full string you would write the xml tag followed by the contents (as already a formatted string) of the variable "DienstBeginn" followed by the string of the ending xml tag. Concatenate command for strings = ..
  14. spokes2112

    No Aileron Control

    If calibrating through FSUIPC make sure there is no assignment in FSX-SE for the aileron (and any others) axis. Clear them if so.
  15. spokes2112

    No Tabs for controller config

    Is it registered for full use? Did you check previous registrations on install? Without a valid registration that's all you'll get. http://secure.simmarket.com/pete-dowson-fsuipc4.phtml
×

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.