Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


spokes2112 last won the day on January 23

spokes2112 had the most liked content!

Community Reputation

36 Excellent


About spokes2112

  • Rank
    Advanced Member
  • Birthday 04/03/1967

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
  • Interests
    FS Programming, Electronics, Vintage Radios

Recent Profile Visitors

3,318 profile views
  1. Hi guys, The script I wrote for FSUIPC v3.x/4.x was done so some prerequisites could be used to turn on/off the auto save. Because the auto save in these versions of is basically a fixed function in FSUIPC I had to write a full save routine - requisites, save files, file name format, increment files etc.. The stock FSUIPC (v3/4) autosave works brilliantly already, it is just the problem that it is either on or off, switched within the UI of FSUIPC. FSUIPC v5+ now has a control (C1151) to toggle on or off the built in excellent, extensive autosave. All that is needed is a little lua to
  2. A calculated guess here, but I do believe FSUIPC can automatically do that for you as long as the following is true in your FSUIPC7.ini ( default) : [JoyNames] AutoAssignLetters=Yes As stated in the v7 Lua Library for event.button : “joynum” is a joystick number, the same as shown in FSUIPC’s Button assignments tab. If you use joystick lettering, you can put the letter here instead but it must be "" quotes, as a string. Note, however, that the function is called with the translated number as its first parameter. With that you could change just 1 line in TripleUse
  3. John, Was working on a reply the same time as you were. Wouldn't the value of v be 4 if on? OFC "true" boolean is 0 or not zero, so it would work if checking for 0. v=logic.And(n, 0x4) if v == 4 then -- landing lights are on end - or - v=logic.And(n, 0x4) if v ~= 0 then -- landing lights are on end _____________________________________________________________________________________________________________ Here's another way to look at it.. Refer to this chart: Here is an example if you were to use a loop to check, not recommended at
  4. @Eliagh, as mentioned here you can use only 1 L:Var in a .MCRO file. Using buttons, in this case, 1 button, you can cycle through the ranges and repeat : 1 = L:B747_8_MFD_Range = Cyclic,11 This will give 0,1,2,3,4,5,6,7,8,9,10,11,0,1,2 .... On each button press. See FSUIPC# for Advanced Users.pdf, "Macros to change Lvars" section. For an increment/decrement you would have to use lua. Something like this, NOT TESTED : Use [AUTO] in .ini to start the lua then assign buttons or encoder as such - Decrease = LuaToggle <lua_name> with a parameter of 1 Increase = Lua Toggle
  5. No worries Roger, what I was asking for is a stock cameras.cfg file.. I have 1 highly modified one, and 5 backups. None of my backups were of the bone stock one. 😒 Alas, after reading thru the SDK it was found that FSX keeps a stock, unmodified one in the FSX root folder.. Now I have 2 stock ones just in case. With that, I can be 100% certain of the hot keys used by the master cameras.cfg file. 1 thru 4.. That leaves 0 & 5 thru 9 available for your own use. No, already done & tested - thanks. I like it as it gives a full view of all the avionics close up ( GPS specially ) s
  6. Good news Roger ! I believe you could do it.. Although, just to make sure, go to C:\Users\<USER>\AppData\Roaming\Microsoft\FSX\Cameras.cfg and check that file for all the HotKeySelect= entries. If 7 is not used in any of them then it is free to use with no side effects. May I ask a favor? I noticed my backup Cameras.cfg files are not good backups.. I don't have a stock backup. In lieu of attaching yours here (path above) I did a little work & setup a view that shows the garmin, nav/com 2 & the adf, all without seeing the quadrant levers.. ( kind of tough ) This
  7. Roger, An edit after another test.. When the button is released, using VIEW CAMERA SELECT 1 "should" return you to the original direction, position, zoom etc.. in the VC "Should" = I cannot be 100% positive with this view select number, my master camera.cfg file is highly modified, checked my backup and it was 1 also. If it doesn't work try VIEW CAMERA SELECT 0, VIEW CAMERA SELECT 2, VIEW CAMERA SELECT 3 etc.. One of the numbers will get you back. Roman
  8. Hello Roger, Noticed you posted this on Avsim too, hopefully this will help. Alabeo provided camera definitions for the fuel selector panel in the aircraft.cfg :) This will make it easy. 1) First you need to provide a "hot key" entry & number to your aircraft.cfg camera definition for the view "Fuel Selector". I have modified mine as such. Make a backup of the cfg if wanted. Warning! Do not go "willy nilly" on the hot key numbers. Numbers 0-4 (i believe) are reserved in the master camera.cfg file. I used 9, the max, as the value just in case you use some other kind of camera s
  9. Completely agree with you John, in fact I can almost bet 100% that the Logitech installer is using text string based logic rather than using the XML DOM & imports to their program such as system.xml to do the work. ( the tab spacing seems to give it away ) An idea for "gracefulness" when improper <Launch.Addon> additions are made by a program that is not doing it properly IE using text strings to figure it out. Use line breaks in key locations.. This should help when a text string based program is trying to add to what you already have. XML doesn't care about whitespaces
  10. One of the the 2 installers/dameon is providing its own closing </SimBase.Document> closing tag which is part of the "root" document - not good. The file will not parse, therefore not load due to the error. Mistake shown shaded below. This should work by either removing the highlighted selection above from your own file or, Copy the complete code below and replace all the code in your file with this, save it. <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>EXE.xml&l
  11. Gustavo, Most, if not all the switches/buttons you are referring to have logic built in to the VC click spots, mainly timers. Much like interfacing the AP, there is no real way to do this via L:Var macros & lua is out of the question too. Just returned home after some time away and continuing on your AP interface ( some FMC too 😉 ). If you take some screenshots highlighted with all the buttons & switches you need , I can add those too. (send via our PM thread) Roman P.S. Here's an example of the APU code needed just to make it work - (M:Event) 'LeftSingle' scmi 0 ==
  12. Definitely a non-standard way of using the sim. When this happens, did you try going to the FSUIPC dialog --> Axis Assignment Tab --> Click the "Reload all assignments" button? That should fix it for you without restarting the sim. 1 extra step for your non-standard SOP. Roman
  13. I like doing these things. Still workin on it, hope to get all the AP done today. May even include the DCP(?) and the CCP(?), while not as complicated AP there are some slightly funky things going in the code. Roman
  14. Have it going & it works, just to give an idea of the background logic here's just the press of the VS button. There's also the release. The AP master and VNAV are even more complicated! <!-- VS Press, Param = 5 --> (L:XP850_HW_IF, number) 5 == if{ 1 (>L:BUFFER_BTN_FMC,number) 0 (>C:carenado:AutoPilotAltitudeEnabled) (A:AUTOPILOT MASTER,BOOL) 0 != (C:carenado:AutoPilotAltitudeEnabled) 0 == and if{ 1 (>L:ASD_BTN_850XP_VS,number) (A:Autopilot Nav1 Lock,bool) (>L:NAV,bool) (A:Autopilot Heading Lock,bool) (>L:HDG,bool)
  15. Whoah!! This may be much tougher than thought. The actual AP panel gauge is in XML but is compiled in SimPropBinary. (*.spb) Inside this .spb are XML style calls to a macro eg. @MacroName, which are slightly exposed, and in some cases, very, very important! Also, there are XML style "C" calls to an external Carenado module eg. (C:<module name>:<variable>) Attempting to use L:Var macros or direct FS Controls, in most of the cases, will be overridden by the autopilot gauge itself. About the only thing I can think of doing for a hardware interface is to transpose the exposed
  • 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.