Jump to content
The simFlight Network Forums

MELKOR

Members
  • Posts

    55
  • Joined

  • Last visited

About MELKOR

  • Birthday 01/01/1970

Profile Information

  • Gender
    Male
  • Location
    Toronto, Ontario, Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

MELKOR's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare

Recent Badges

0

Reputation

  1. I see that the client-side API is open-source under the MIT license and hosted on GitHub. So, kudos for that! Prevents me from having to re-invent the wheel! 😀 Now, regarding the server-side WASM module: While I see this is freely downloadable from here, I haven't seen any documentation regarding license, nor is this on John's GitHub. Am I free to distribute this in my own products? (And, presumably, automatically install to MSFS if not already present). Thanks. - Bill
  2. Pete, allow me to be the first to ask the inevitable question... =) Is the most recent FSUIPC compatible with 4.3? (I withdraw the question if you've not been given the chance by LM to pre-test). - Bill
  3. Hi Pete, I can't seem to capture AXIS_THROTTLEn_SET events in my SimConnect client. I can capture every other axis, like AXIS_RUDDER_SET, AXIS_ELEVATOR_SET, etc. This only seems to occur when I run my throttle axes through FSUIPC... Any idea? Thanks, - Bill
  4. Argh, was my mistake, had a typo in my Keys section: no wonder it wasn't matching! =( Sorry for the false alarm: I confirm that all tabs are matching as expected. Many thanks, - Bill
  5. Thanks Pete, am just finding time now to test out the fix... The Buttons tab now works correctly. Unfortunately, the Keys tab still exhibits the same behavior: shows full name in title bar, and writes to the wrong Keys section. Thanks, - Bill
  6. I'm asbolutely sure the behavior did not exist at one point in time... would have driven me crazy. =) But with which prior version, I am not sure. Sorry I cannot be more specific, Pete. =( However, prior to these recent JS41 changes, the last time I made any changes to my FSUIPC4.INI file was around the time I bought the PMDG MD-11... which is definitely well before 4.50. So... the theory that it may be due to the Profile changes seems at least likely. Thanks, - Bill
  7. Pete, After some more experimentation, this appears to be changed behavior... 1) Tried a longer substring... same changed behavior (in every respect). 2) Tried with other aircraft, where I am absolutely sure this behavior did not exist before... same changed behavior (in every respect). However: I took a look at, and enabled, the "Profile" mechanism. Interestingly, everything works when this is enabled (i.e. FSUIPC is matching and displaying "41" in the title bars, and writing to the correct sections)! Please let me know if there is anything more you need from me. Thanks! - Bill
  8. Correct. Yeah, I would have definitely seen this before. So, either the behavior is new, or your suspicion about the short substring is correct. "41" is definitely the shortest substring I've ever used... (due to some inconsistent aircraft naming on PMDG's part!) I'll try a longer substring and see if that helps. Ack! I'm so sorry to hear that Pete, I hope that everything works out okay!! Thanks, - Bill
  9. I am quite familiar with the general vs "aircraft specific" concept (been a FSUIPC user for many years now). But, just to ensure I didn't do something stupid, I double checked everything for you. =) The behavior definitely occurs when I select "aircraft specific" prior to making any changes. In addition, when I click "aircraft specific", the full aircraft name is being displayed, not just "41". Some other observations: 1) The full aircraft name is also displayed in the "Axis Assignment" page... and yet any changes here get correctly saved to [Axes.41]. 2) The short aircraft name (i.e. "41") is displayed in the "Joystick Calibration" page. So... pretty inconsistent across the three pages! =) I have not had a look at the new "Profile" mechanism yet... do you intend on dropping support for the "old way"? If so, I had better learn more! Thanks, - Bill
  10. Hi Pete, Ran into a wee bug recently w.r.t. "ShortAircraftNameOk=Substring", and thought I'd pass it along. I have the following sections setup for my new Jetstream 41: [Axes.41] [JoystickCalibration.41] [Buttons.41] Now, if I go into FSUIPC settings and try to change a mapping for some button, the [buttons.41] section does not get updated. Instead, a new section is added. For example: [Buttons.PMDG Jetstream 41 US Airways Express] Notes: [*:2qhx2gkq]The Axes and JoystickCalibration sections are not affected by this: when I make changes there, the changes are written to the correct section.[*:2qhx2gkq]Not sure about the Keys section: I don't have any keys mapped. So it may or may not have the same bug.[*:2qhx2gkq]Running version 4.548 (the latest, I believe) Thanks! - Bill
  11. Oh wow, that is very cool!! 8) Thanks for pointing that out, Pete, going to play around with it... - Bill
  12. Dave, a couple of comments. 1) I too had the same behavior in the air. When I switched the axis to use "Direct to FSUIPC", it works properly now. 2) Where in the world did you get (or figure out) those macros for the PMDG DLL?? Thanks, - Bill
×
×
  • 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.