foxfan911

Hey Pete. I made some really good progress today and got alot of my switches and buttons and axis done so that's good. I am still having a couple issues... Yes, the specific examples would be MCP and autopilot functions such as AP functions when you click on certain buttons with the mouse, either 2D or virtual cockpit. I have found some that do have a corresponding controls which is obviously MUCH better than the FSX options. Another example would be LNAV and VNAV, which in my QW 757 is activated by pressing VNAV or LNAV on the MCP. I wanted to program that to a switch. Another example would be Vertical Speed Hold, but I don't seem to see one that works for that. I have tried almost all the FSUIPC controls that refer to Veritcal speed, but I don't seem to have one that will activate/deactivate it. Or maybe even a toggle between VS hold and Altitude hold would be cool. So, if there isn't a FSUIPC control for that, wouldn't I need the event id??? Also, I attempted to use the Mouse Macro and followed the instructions properly. It allowed me to name the file name and when I went to the simulator to click on a control, it did not give me the option to name it, thus it was not in the FSUIPC control drop down box. I tried the controls on the 2D panel and VC. I'm pretty sure I followed the instructions right as I read them and watched a few youtube videos on the subject. Also, since Quality wings does not provide a list of the controls, I will check their support and their forums to see what I can find. It would be nice if they would have done it like PDMG and just put it out for those of us that want to make cockpit building easier. I am not familiar at all with L:Vars, so what does that entail and how do I use that to accomplish what I'm trying? Sorry if some of these are dumb questions, but I am a beginner getting to know this program. I have learned a lot in only 1 day which was filled with youtube videos and reading the manual. This program is simply a masterpiece and I look forward to learning more. Now I know why people said they don't know how they lived without it. Outstanding job! Let me know what you think and thank you!!! Chris

Hey guys, I am trying to map some functions on my QW 757 to the buttons and switches on my Thrustmaster Warthog HOTAS. I have already figured out how to do this with key presses and FS controls, but from what I understand, I need to obtain the event ID to get developer-specific functions (like MCP functions, engine functions etc. and others that do not have a corresponding FSX function in the FSX settings/controls menus. I can't seem to find anything online. I did see a post that one guy used the logging tool in FSUIPC and was able to figure out the event IDs. I also saw a youtube video of a PMDG aircraft where they released a list all the functions with their associated Event IDs so they could be easily programmed. Apparently Quality Wings does not make such a thing. Let me know and thank you!

I thought I had the latest. I will update. I am running FSX steam edition

Well, I know for sure that FSUICP is used with the payware plane because it stated it in the manual and said that for some things to work, it was required. It also was installed along with the a/c and exists under the add-ons drop down menu. So I think he means to be saying that they are using some or all of it to to interface their a/c with FSX. When he said throttle locking, I think he was saying that the autothrottle would not reduce thru FSUIPC. Is autothrottle controlled by FSUIPC? I'm using the unregistered FSUIPC, whatever came with their aircraft. I installed it because Quality Wings said it was mandatory to make the 757 function properly. It says in their documentation that FSUIPC is required, and that the unregistered version is provided. The only thing I have been flying for some time now is the QW757, which they said FSUIPC was required. What I have says FSUIPC Version 4.948, 2nd November 2015. This copy is unregistered. It will not provide full functionality. Chris

Hey Pete, I have a QW757 (Quality Wings) and we can't get the VNAV to work properly. I do not have the registered pay version of FSUIPC, but I reinstalled the latest version. Basically, when in climb mode, the VNAV will overspeed past the speed constraints in the FMC. Like way past the assigned speed. This consistently occurs as it's leveling off at an assigned altitude. It's strange what happens. As the plane levels off, the throttle levers initially starts to reduce for just a second, but then snaps back up. Then it does it again and again, down lightly and then the throttle snaps back up. With the throttle levers remaining up like this, the plane accelerates way past the assigned speed. The throttle levers will only stop this snapping back up when the plane gets to withing about 100 feet of the assigned altitude, but by then it's already severely overspeeding. Let me note that this problem exists both on my desktop and laptop, using two totally different joysticks. The reason I'm asking you is that one of the developers at Quality Wings seems to think it's an FSUIPC issue. He says that he thinks it may have to do with throttle locking and that FSUIPC is required for throttle locking. Today he said that "I'm thinking the throttles are not unlocking for some reason (ie via FSUIPC). But if that is the case, it does not explain why they unlock for most users. Or why they then unlock upon reaching the target altitude." So he thinks it's an FSUIPC issue. Here is a video I made showing and explaining what is happening. https://www.youtube.com/watch?v=z5fYFR4DM1Q Note in the video the throttle levers appearing to try slow, yet they snap back up to about full range. They repeat and repeat and repeat this until about within 90-100 ft from the assigned altitude. Here is a link to the Quality Wings support forum if you want to see more videos and what the support guys are saying. Any information would be great....I really want to get this fixed. Everything else works quite well on the A/C, just the VNAV overpseeds like a maniac cause the throttle levers don't want to seem to retard.