Jump to content

Joan Alonso

Members
  • Content Count

    154
  • Joined

  • Last visited

Community Reputation

64 Excellent

About Joan Alonso

  • Rank
    Flight Student - Solo

Recent Profile Visitors

1244 profile views
  1. I’m sorry if it doesn’t help you @Rosko In all the years I’ve been into flight simulation I always had to learn by myself a lot of things if I wanted to go further with the default settings of any piece of software. I think that there’s a lot of flight simmers that had to. There are a lot of people out there that can help you, but there are things that are not as easy as “do this and voila”, you’ll need to search, ask, do a lot of trial and error (I promise, a lot) and at least familiarize with the files and formats of that you want to modify or customize. FSUIPC forum would be a good start point, I always got feedback from Pete or his team, they can really assist you on this. Cheers!
  2. Hi Rosko, You don't really need to write any piece of code, of course if you take some time to figure out how it works it will be easier. You only need to copy and paste (replace) with the Lvars you want. So for a simple button or key in VC to toogle it from On to Off: function ExternalPower_conn () ----------------------------------> This is the name of the (A) function inside the toggle function (You can type the name you want for it) ipc.writeLvar("MCDU_EXTPOWER", 1) ----------------------------------> This is the actual Lvar name ("Lvar", Value) The value is usually 0=Off / 1=On end function ExternalPower_disc () ----------------------------------> This is the name of the (B) function inside the toggle function (You can type the name you want for it) ipc.writeLvar("MCDU_EXTPOWER", 0) ----------------------------------> This is the actual Lvar name ("Lvar", Value) The value is usually 0=Off / 1=On end function ExternalPower () ----------------------------------> This is the name of the whole toggle function, (C) (You can type the name you want for it) var = ipc.readLvar("MCDU_EXTPOWER") ----------------------------------> Read the Lvar State (0 or 1) if var == 1 then ExternalPower_conn()----------------------------------> If Lvar State is 1 then do function (A) else ExternalPower_disc()----------------------------------> If Lvar State is 0 then do function (B) end end event.flag(1, "ExternalPower") ----------------------------------> The name you gave to the toggle function (C) So you just need to replace the Lvar Name for the one you want to use, and replace the name of the functions to whatever you want to call them, and also rename the whole function to your liking. Two important reminders: 1) You must add your Lua to the [Auto] section inside FSUIPC.ini: https://forum.simflight.com/topic/86587-lua-file-not-loaded-but-why/?do=findComment&comment=524737 2) The event.flag tells FSUIPC what parameter assigns to that function. So when assigning the key inside FSUIPC select LuaToggle "Your file" and the parameter will be the flag inside the script. So for example: event.flag(1, "ExternalPower") event.flag(2, " Seatbelts ") event.flag(3, "APU) ... Hope this helps!
  3. This usually happens after opening some menu or for example changing time or date. The reallight (dynamic lights) go off. Moving the knob/switch to another setting set them back. I guess some kind of limitation inside the module.
  4. Hi, I think I read somewhere that the EFB for the upcoming A330 will be implemented on A320 series, is that correct? Will the EFB have airport maps based on scenery folders as PMDG done with the NGXu? Thanks!
  5. Hi @ahuimanu The code works ok with a gamepad which is the device I use. I can't comment on using other hardware. I did many many tests time ago with different code and nothing worked but this. Yes, this two variables are built-in simulation variable. (A:SIM ON GROUND, bool) 1 == (When the aircraft is on ground) Can be 0 or 1(A:BRAKE INDICATOR,position) 0.6 > (When the brake pedal position is greater than 60%.) Can be from 0 to 1 I don't know, you can try to adding this lines DETECT EXTERNAL BRAKING part of the code. It makes sense to start changing things there first, but as far as I remember nothing seemed to work there. I'm sorry I can't be of more help!
  6. Hi, As requested by private message I'll share the mod I did to ABRK.xml in case helps anyone interested. This solved the Autobrake disarm before touchdown for me. Replace the 7th line of the file: (L:ABrkactiv, number) 0 == by this two lines: (A:SIM ON GROUND, bool) 1 == (A:BRAKE INDICATOR,position) 0.6 > Cheers P.S. I'm not sure if I'm allowed to share the line of the original code. @DaveCT2003 Thanks.
  7. I realised some time ago that sometimes the .fms file does not save at all (a few times) or does not override the previously .fms file if saved with the same name (more often). So to be sure, I always delete the previously saved files and save the flight then. I always check if the .fms and .asc files have been saved correctly. The worst scenario is when the .fms file won't save at all, no matter what you try, you'll have to restart P3D losing the FMS data or finish the flight. Hope it helps!
  8. IAE Flex Temp with data from http://www.wabpro.cz/A320/ stopped working several updates ago. The last topic I opened was a month ago without further news on the topic.
  9. For what it is worth, the FD commands the momentary roll on approach also with AP off.
  10. Ok. I tried assigning buttons again and it works someway better with FSUIPC Throttle Incr and Decr than with P3D controls. But the overall feeling is worst than the other way around, the reverse range seems to be longer but the response on the manual range between IDLE and CLIMB is better with P3D controls. I was just curious if something could be done in the FADEC or ATHR code to make the reverse range longer or not to be so sensitive when button is applied as it does in manual range. Anyway, I will leave it as I had it before, barely pushing the button to get IDLE reverse. Thanks!
  11. Ok! Thank you. I'll try then to assign buttons again and see if I got it right. I'm glad to hear that there are up to seven steps to full reverse. So, it has to be something I'm doing wrong.
  12. Decrease. I tried with FSUIPC Throttle Dec Small with the same result. It feels that from Idle to full reverse it goes really easy to full with barely touching the button, I can sometimes put it on idle reverse as you say, but it does not feel like in manual range, where I can smoothly increase or decrease by small increments.
  13. Hi, I try to apply a single quick press, but most of the time it goes further than that. It’s way more sensitive than the manual range. Thanks
  14. Hi, Is there any way to make the reverse range less sensitive when applied trough a button or key? I mean, the steps in the manual range are fine, but when entering the reverse range the steps are much higher, it's difficult to apply idle reverse wihtout going to full reverse first. I know it's something related to the way of the thrust is coded, but can be something done? Thanks in advance
×
×
  • Create New...