Jump to content
The simFlight Network Forums

Hans Billiet

  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Hans Billiet

  • Rank
  • Birthday 06/02/1965

Profile Information

  • Gender
  • Location
  1. @Ross McDonagh A bit rude of me not to thank you as well Ross. I have read your post with much interest, and it was indeed very helpful. Thanks!
  2. @John Dowson Ok, maybe I am too "hungry for knowledge"🤓 But can you then just advice me. If I want to use an input (example: button), is it adviced to always use events rather than offsets? I know that in some cases you can use offset as well, but is that info (choice) derivable from your table? Because that is info that I do need to successfuly control the sim.
  3. I'm again having some "beginners question". Although I succeeded with my first attempt to control the Parking Brake in FSX via FSUIPC, MobiFlight and an Arduino Mega. So making progress!😎 I now start realizing the difference between Offsets and Events (yes, this is step by step...). I was also guided to the document "FSUIPC4 Offsets Status.pdf", which lists all the available offsets. There I found the Parking Brake (offset 0BC8). So start linking MobiFlight info with FSUIPC info. In my first attempt, I used the FSUIPC offset to connect with both output (LED) and input (button). It worked, but via the MobiFlight forum I learned that I should use an EVENT instead of an Offset to connect to my input (button). I did, and it also worked. Perfect! If I look at the above mentioned document, I see for the Parking Brake: FSRead: Ok-SimC FSWrite: Ok-SimE The explanation of "Ok-SimE" reads "for write only, works okay, but resorting to Sim Events via SimC, not SimVar reads or writes". Hmmmm... being a beginner, I have searched the forum, checked the user manuals and Googled... but didn't find a real good explanation of what that phrase really means. I always like to make a guess first. Please correct me if I'm wrong. "Ok-SimE" means that you can write at this offset, but FSUIPC intercepts this and uses an Event instead of controlling that value? Meaning that it "resorts to Sim Events". But still... the complete phrase doesn't make much sense to me.
  4. @John Dowson Thanks for your quick reply. Can you just tell me what you mean with "simulator variables" vs "controls"? Are these variables the so called "LVars", which are kind of "Local" (although, they seem Global) variables that contain values like "speed", "altitude", etc...? But how about controls? I would also assume that these are variables like "Up = 1", "Down = 2", but as you mention them separately, I assume this is a different method? (Sorry, I'm still a newbie... but learning fast 🤓)
  5. I am experimenting with FSUIPC4 (just downloaded, and bought a license). I find the logging extremely useful, as it allows to identify which commands are triggered. I have searched both the normal user manual, and the one for advanced users, but none of these documents seems to give a description of what the different columns in the log file mean. Example: "108797 *** EVENT: Cntrl= 66529 (0x000103e1), Param= 0 (0x00000000) EYEPOINT_BACK" What is the first number 108797 - I assume some kind of "timing"? Where does the description "EYEPOINT_BACK" comes from? Is this defined by the simulator (FSX), or is this mapped somewhere in one of the FSUIPC files (a "human readable" format of the Cntrl?) Are these the same labels used in "Key Presses"/"Control sent when keys pressed"? For the above example, I find the same text "Eyepoint Back" (although, not in CAPS and without underscores). Bottomline - if I press a button in a plane, not knowing exactly what the command is, can I use the logging to identify it's description (EYEPOINT_BACK), and by this know which control to use when defining keys? Would be handy, because some controls have not always "obvious" names.
  6. Thanks @Thomas Richter, I just did. https://www.mobiflight.com/forum/topic/5904.html
  7. Thanks a lot @John Dowson. Pretty clear. Summary: FSUIPC -> SimConnect -> Simulator Does SimConnect exists for both FSX, P3D, FS2020, ...? Is this the same API, or are they all have their own version? And final question (so far...). What about MobiFlight? If I understand it correct, it makes use of FSUIPC? MobiFlight -> FSUIPC -> SimConnect -> Simulator Although, I do understand that MobiFlight's focus is to provide an interface to the frontend, to make it easier to configure HW via Arduino, but I don't see the benefit of working through FSUIPC, and not directly through SimConnect. But I's sure there is a good reason? (I probably should ask this in their forum, I know, but would be nice to have the whole thread in one).
  8. I tried to find the answer in this forum, but didn't find one. Can somebody explain me: what is the difference between FSUIPC and SimConnect? is there a reason to use one or the other? will both be supported in the future, or will only 1 "survive"? some advice/links to some interesting reading stuff about these 2 interfaces? (I'm in "study and buying phase" for a good A320 add-on and building my own DIY cockpit - currently using FSX)
  9. @John Dowson and @Pete Dowson, really appreciate both your answers. For me it was a bit "the chicken or the egg", whether I would ask it in this forum, or on the FSLabs forum. thanks!
  10. Hello, I'm reviving my flightsim hobby based on FSX (and later probably FS2020). My focus is on A320, and my goal is to build my own cockpit (multi-year project). I'm still in the study phase. Luckily, a huge amount of info can be found on Google. But for some "basic" questions, I seem not to find any answer. I'm tempted to buy the FSLabs A320-X add-on (looks like the best affordeable realistic A320 simulation). Although, it seems hard to integrate with a DIY cockpit, as they seem to be married with Skalarki, and not much "official" info seems to be found on offsets, LVars, etc... On their forum, they talk about "Rotor Brake codes"? What are "Rotor Brake codes"? As far as I can read, these are "custom codes". But where does the name "Rotor Brake" comes from? Is this a "historical" name that has now been re-used in a complete different context? Thanks!
  • 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.