Jump to content
The simFlight Network Forums

wahltho

Members
  • Posts

    37
  • Joined

  • Last visited

Everything posted by wahltho

  1. Hi Pete, thanks for your clarification. These discussion started this morning following the publication of version 3.53 within a German-speaking FS forum, which is hosted by Flightxpress (http://www.flightxpress.de), the largest FS-publication for the German language area. I think this was also linked to your announcement that people, which buy a license for FSUIPC now, must use version 3.53 or later to be able to register. Additionally one guy reported, that his registration was gone after installation of 3.53 (, which actually later turned out have been somehow a mistake). Some people obbviously got the impression that they would have to buy a new licence immediatly and their existing licences might be timely limited. You know how things like these tend to develop within forums, therefore I thought getting a quick clarification from the developer, would be the best way to get this sorted out immediately. I assume that your clarification will stop these rumours immediately. Thanks again :-)
  2. Hi Pete, first of all: Happy New Year to you and your family. According to my impression there seems to be quite some confusion within the FS-community regarding the planned handling of FSUIPC-licences and future versions of FSUIPC. My understanding is, that close to the introduction of the new version of FS also a new FSUIPC version 4.00, supporting the new FS version, will be available. In order to be able to use the full functionality of FSUIPC version >= 4.00 it will be required to buy a new licence (which I will happily do to support you and your work). It will not be possible to register FSUIPC with an old licence key. Existing licences will continue to work without time restriction with all FSUIPC versions >= 3.00 and < 4.00. Is my understanding correct? A clarification from your side would be highly appreciated.
  3. Pete thx for your comprehensive answer. Indeed I was refering to "View Reset". Will use the workaround you described.
  4. Hi Pete, I am just concerting some of my flight simming from FS2002 to FS9. I had "Reset View" assigned to the Right Front Button of my PFC Jetliner Yoke. In FS2002 this command did reset zoom level and view direction to the default. In FS9 with the same button assignment nothing happens. I have this command assigned to the Shift-Spacebar on the keyboard. Using the keystroke command it seems to work. Any ideas?
  5. Pete, I am currently thinking about completing my PFC equipment with a Jetliner Console. I know that there are problems with add-on aircrafts which are not using the standard FS controls, e.g. for the autopilot. My favorite aircrafts are the SSTSim/Koch Concorde and the RFP Version 1 (I am still using FS2K2). Are there any ways to make these work with the Jetliner Console using the features of FSUIPC/PFDLL :?: Best Regards Thomas Wahl DLH3210/EDDF
  6. Although not directly related to your products, you are probably the right expert to answer this question: Today in another FS forum it was suggested to always start-up the FS with a standard MS aircraft and then to switch to the desired addon aircraft, because otherweise some internal FS variables would not be properly initialized. Do you share this view and if so do you know about any impact?
  7. Thx a lot Pete, the reduction of the PollIntervall value solved the problem that the A/P disconnect button of my PFC Jetliner Yoke was not being recognized by the PIC767. Nevertheless I have another problem with 3rd party hardware and the PIC767. I own the Flighboard 2000 USB from ITRA. This is a device which has a lot of soft-buttons and emulates keystrokes once you press one of the buttons. I can assign all of the PIC767 A/P controls to these buttions (lik VS+/VS-), meaning the push of the buttons on the FB2000 is being recognized correctlya within the PIC767 control assignent menu. But afterwards, when flying the PIC these buttons do not work. I guess it is the same problem, the PIC767 flooding the Windows message queue. Would it be possible to have something like the PollIntervall for buttons also for keys or do you have any other ideas whow to solve this problem.
  8. I also took a look at the SDK of the Teamspeak client and found no appropriate message for the PTT-button. I message which I left in their "Suggestions" forum has been left unanswered since several days.
  9. Pete, thx for the very quick answer. Yes I am a registered user of FSUIPC (I even was one of the very early donators :D ) I will try to submit a corresponding post within the teamspeak support forum at http://www.teamspeak.org. Their client software contains a SDK, therefore it would be probably no big deal to get their permission for integration into your modules.
  10. Pete, I have a question regarding PFC.DLL (which you are also the author of): As you are probably aware, IVAO is planning to switch from Roger Wilco to Teamspeak. Currently I have the left rear button of my PFC Yetliner yoke configured as PTT-Local Roger Wilco Button. In Roger Wilco I have configured the L_CTRL key as PTT-button. Everthing works/ed fine so far. In Teamspeak I can only assign a general "CTRL" key for PTT; it is not possible to differentiate between "L_CTRL" and "R_CTRL". Using the PTT-button at my Yetliner Yoke does not work for Teamspeak. Any idea how to get this work. Best Regards Th. Wahl
×
×
  • 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.