Jump to content
The simFlight Network Forums

spokes2112

Members
  • Content Count

    294
  • Joined

  • Last visited

  • Days Won

    13

spokes2112 last won the day on January 21

spokes2112 had the most liked content!

Community Reputation

33 Excellent

3 Followers

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

Recent Profile Visitors

3,099 profile views
  1. Been looking at this one, off & on with the morning coffee 😉 This one may take a little more than just a L:Var Macro, either a support XML gauge w/ L:Var Macro -or- Lua should do it. The thing about VS hold in flight sim ( since FS2002 ) is that the supplied VS Hold commands never worked. Designers have been using altitude hold and background logic to make their own & separate the actual ALT hold from VS hold in this logic. BTW - It seems all those L:Vars have nothing to do with the actual control of the VS hold in this aircraft, more so that they are there as an interface betwee
  2. In the 850xp this L:Var has 3 values : 0 = Batt 2, 1 = Normal, 2 = Batt 1 Using 2 buttons, the left click can be : #=L:ASD_SWITCH_ISOLATE_850XP=Inc,2 then the right click can be : #=L:ASD_SWITCH_ISOLATE_850XP=Dec,0 Save a button! 👍 😃 Just make 1 button cyclic : #=L:ASD_SWITCH_ISOLATE_850XP=Cyc,2 Ref - Pg. 43 FSUIPC for Advanced Users.pdf Hope this helps, Roman
  3. 0x0D0C is a 16 bit word if you want to get all the lights. 2 function examples below, "getTaxiLights1" is run by the timer, "getTaxiLights2" is run on first load & anytime there is a change at offset 0x0D0C. The last is the preferable method. function getTaxiLights1(time) tL = ipc.readUW(0x0D0C) tL = logic.And(tL, 8) -- Taxi lights are on bit 3, therefore the mask is 8 if tL == 8 then -- Taxi Lights are on else -- Taxi Lights are off end end function getTaxiLights2(offset, value) value = logic.And(value, 8) -- Taxi lights are on bit 3, therefore the mask is 8 if value ==
  4. Perhaps the "log tape" means logging to title bar or to a "green line" display. In any case the VAS number is in kilobytes - 024C Available FS memory in kilobytes (updated every 10 seconds) That is.. If 024C is used. Other memory outputs ( from FSUIPC# Offsets Status.pdf ) 0258 Memory currently assigned to FSUIPC4 (including WideServer) This is in Bytes. 0290 Maximum available FS contiguous memory block in kilobytes (updated every 10 seconds). Roman
  5. No clue on this one. Perhaps the errors below fail the whole lua. IIRC the ipc.ask() returns a string so you could do this 1 of 2 ways - 1) Put this line under ipc.ask() and change your comparison signs in the then following line from = to == & you should be good the rest of the way : doors = tonumber(doors) -or- 2) Change the following 2 lines to first, test against a string & correct the comparison signs, and second, to convert to number for ipc.setbits if doors == "1" or doors == "2" or doors == "3" then -- check input is valid ipc.setbitsUB(0x3367, tonumber(door
  6. Was thinking of this too, perhaps easier than lua? While not using throttle position exactly, it relies on the "effect" of throttle position --> speed. Assign the axis to both Rudder & Nose Wheel Steering and then use the .ini parameters MaxSteerSpeed=<speed> and optionally RudderBlendLowest=<speed>. ( In advanced users .pdf ) Roman
  7. Just an idea I've read about, I have no experience. Have you tried reflashing the Bodnar boards using alternatively named .bin files? On this page at the Bodnar site, it states : " The serial number is unaffected by any firmware change however each renamed device is given a new ProductID (PID). " With 2 of the same boards with 2 unique ProductIDs and 2 unique serial numbers maybe Windows wont get so confused. The link above is also referenced in each of the BUO836X product pages in the "Product Downloads" tab. Again, just an idea. Roman
  8. Pete, Just some early morning theory with the coffee )) I think it's because FSUIPC picks up the first 32 buttons, correct? In this line * all * the buttons are picked up but we only need the ones * not * picked up by FSUIPC to be placed into the VJ offsets. buttons[1], buttons[2], buttons[3], buttons[4], buttons[5], buttons[6], buttons[7], buttons[8] = com.GetHidButtons(dev, CurrentData) So with that, if true, "i" should equal 2 starting the loop. Again just a theory, you 2 are the masters! 😉
  9. Pete, In the demo, i = 2 to begin with, skipping the first 32 buttons picked up by FSUIPC, therefore ipc.writeUD(0x3340 + ((i-1) * 4), buttons["eye"]) -- "eye" = i, the forum picks it up as italic formatting will yield 0x3344 as the first address used. No biggy, excellent demo lua! Never looked at it before.. Now what can I do with it here? lol Roman
  10. Morrispe, Using the HIDDemo as is for both devices will never work. It is a demo to prove that 256 buttons can be programmed to ONE joystick. By using the same lua for both the ALPHA & the BRAVO, they will write to the same address space reserved for virtual joysticks. (0x3344 thru 0x3363. The first joystick slot 0x3340, Joy #64, was not used in this lua ) Attached are 2 luas : 1 for the ALPHA, 1 for the BRAVO. ALPHA buttons greater than 32 will be on joystick #64 with 32 additional buttons provided. (0x3340) BRAVO buttons greater than 32 will be on joystick #65 with 32 additi
  11. Thanks for the help! That was it. Roman function b(flag) ipc.display("TEST", 1) end function c(flag) event.cancel("b") -- if the only one active, worked up to flag 1 event.cancel("b") -- if added then it worked thru flag 2 event.cancel("b") -- added the 3rd, worked on all end event.flag(1, "b") -- test event.flag(2, "b") -- test event.flag(3, "b") -- test event.flag(4, "c") -- turn off
  12. Pete, Thanks so much for taking a peek at it. I guess what I will do is make 2 versions, the one above & another using the "switch" style, of which I have already started but it is just a huge mess! The one above is so much more elegant. If that one has inherent bugs I will have a fallback. On last question if I may - I have 2 listeners with different offsets, pointing to the same function : event.offset(0x0001, "UB", "GoHere") event.offset(0x0002, "UB", "GoHere") Will the following cancel both? event.cancel("GoHere") I am assuming it does, hope so. Thanks again and.. To
  13. Hi Pete, Wondering if you could take a quick look at this lua test script. It works but I am little worried because I cannot test a final version, for another sim in which i dont have and... In the final version there will be only 5 or 6 "x" arrays, but there will be around 15 - 20 filled indexes in each. ( haven't got that far yet ) What I am trying to do is monitor the same offset (a few of them) but direct the function call to somewhere else, cancel the other function calls, all based on a selector knob. Am I treading on thin ice here? Thanks in advance, Roman function
  14. IIRC, AP_VS_HOLD has never worked, dating back to FS2002. ( using XML ) Even looked at the advanced users PDF looking for a special (controls 1930 - 1945) FSUIPC VS_HOLD control provided by Pete, no luck there. Roman
×
×
  • 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.