nantelp

Yes I forgot the NOT. I use FSUIPC for almost everything, this way I can configure the cirrus for plane with yoke and my joystick for plane with a stick. But I found that PFCcom64 does a great job for my different quadrants and for AP, electric trim up & down. If you need me to do any more testing do not hesitate to ask. Pierre

Hi Pete, Your wife will be happy ☺️, I manage to get it to work using the FSUIPC "Buttons & Switch" menu. I have it working with the <end> key configure to my yoke button. I still think there is a issue with the PFCcom64.dll, not sure if it does transmit the key. But I am more then happy to work with FSUIPC instead. Pierre

Yes it did work perfectly. I am sorry to cause all that trouble, I have assign the letter A and I get the same result in the log screen a (null). I also did another test, I assigned the bottom to the P keys for pause the sim. If I hit the yoke bottom, nothing happens both if I hit the P on the keyboard the sim goes to Pause. So it seem that the Dll is transmitting the key. I will try that tonight I will try to do that test, not sure if I understand what I need to do? Pierre

Hi Pete, I have been using this since about 5 years, I have stop using those software's since about a year now. I re-installed them a month ago. But it did work find for a long period of time. This is the only key I need to setup in PFCcom64. I do not assign any other keystrokes. I can also use the <end> key, I have tried to configure it in PFC and I get the same result in the log screen a <null>. Pierre

Once again thanks, Yes the assignment of a key seems to be working in the PFCcom64.dll. But when I hit the bottom in P3D to activate Push to talk in MCE (vr software) nothing happens, so I am wondering if the dll is sending or issuing a <del>. That's why I check the log of the dll. So I know that the hard coded bottom, such as AP, electric trim up & down works and I see them in the dll log and in action in P3D. There is no rush. Pierre

Hi, I have one more question, is it normal that in the log see picture, I can see the exact command when I use my trim bottom on my yoke or the left front bottom that is assign to AP & AT disconnect. But when I hit the bottom I have define to be the <del> key, I am not seeing the <del> transmit but rather the <null>? Pierre

Thank you so much Pete, It's now working I do not remember, but I guess it ok for the reset bottom to stay there? Wonder what happened.😁 Pierre

Just asking because I did received a update on 03-01-2021 I have a brand new install of Prepar3D and just FSUIPC6 6.0.12 and PFC 5.0.6.0 install as addons. I am still unable to assign keys in the Bottom menu. But now I can rule out all the other addons that I had. I will wait to see if you are able to find something before I start re-installing addons. Pierre

That's ok it will give me the time to re-install P3D. Before you go can you tell me if Visual c++ is in play with your software, I did get a updated version during Christmas Just a though Pierre

Correct see picture, the version that you see on the first page of PFC I did check the DLL version I am loading in P3D and it is the same as the one below, but when I open it in P3D I get the screen above. I was just thinking that what ever changed, affected both simulators. So by logic all the addons that I introduce was only configured for P3D and should not have affected MSFS. I was thinking that maybe it a change to window a patch for example. Does Microsoft Visual C++ play a role with PFC? I have decided to un-installed P3D 5 and start with a clean plate, so I will only install P3D and FSUIPC/PFC and see what happened. No addons. I will report back Pierre

Sorry it is a typo, should read PCF. I have download and installed the new version (just to be sure I have the right one, you did not change the update date on FSUIPC.com and neither the version number it is still 5.051.) This is funny, yesterday when I was testing I though that I had to select "list all FS Ctrls" and when I did P3D crash. I didn't report it, being a old IT guy, I didn't want to create an additional problem. I have tried the new version, I still cannot assign any key in the Bottom option menu. But now I can select the "list all FS Ctrls" without having P3D crash. since Christmas I have updated or installed MultiCrew (update) PF3 (update) UTlive2 (update from UTlive1) and received many MSFS2020 and windows updates. Beside that I do not see what else I have change. One question, the fact that it is not also working with PCF for MSFS2020 doesn't seem important for you. I am not using any of those addons with MSFS. Pierre

Long story short, in PF3 you need to send a <del> key, this is your PTT switch to initiate a pause when using VR software (multicrew). You have two ways of doing it in Multicrew. So I always used the top one. With my new joystick I decide to try using one or the other depending on the plane I was using. So for about a week, it worked, I was flipping from <del> when I was flying plane with Yoke and the Joystick bnt4 when using the airbus. I do not know why, but mid last week, the <del> key stop working, but the Joystick kept working find. So I started to do some testing and I deleted the keys assignment in PCF and tried to assign with FSUIPC. Since then I can no longer re-assign my right front bottom or anyone else, a key in PCF. I am very puzzled Pierre

Hi and thanks for the help I went back to the documentation and I am following the right way. select Yoke Buttons menu, then I select the Beech or Mooney yoke, then I press the bottom I want to assign, just to make sure it works. I press on the right black arrow aligned with the right: front bottom. I get a drop down menu and I pick option 1.use key press. At that point I get the same screen I posted at the top (first one). So I hit the <del> keys on my keyboard and nothing. I have been using this for at less 5 years, I am 100% sure it worked before in P3D. I never did it in MSFS2020 because I do not use it for now, it is too immature for me. So I only run the update. I have tried many other keys and none of them works. Unfortunately it is the only bottom on my Cirrus that I have to program. I do all the other programming using FSUIPC. For some reason the only way that PF3 and Multicrew recognized that key stroke, is when I configure it using PCF and not FSUIPC. Pierre

Ok I am all updated now FSUIPC6 6.0.12 FSUIPC7 7.0.4 PCFcom64 version 5.051 I have un-installed Multicrew ,Chase Plane and UTlive2, all new addons I added recently. I have un-installed window 10 20H2. I have upgraded all my FSUIPC and Download the PFCcom64, just incase. After all this, I still cannot assign a key in the Yoke Buttons menu in PCFcom64 and this in P3D and MSFS2020. I have look at the log in PCF and the DLL those see my front right bottom (see picture) I think it's strange that the problem exist in both simulator. In my opinion it is not related to addons for P3D 5 because they will not also affect MSFS2020. Pierre

Hi, Yes my Cirrus II is serial, it is about 15 year old but still working great. It's been a wild since I add to use this feature, so I do not know since when that problem started. I only need this feature to assign the <del> key to the right front yoke bottom. I need this when I use Multicrew and PF3, the <del> key is use to simulate push to talk. I know that PCFcom64 is a old DLL and it use to work find. For the version I am running fsuipc6 ver 6.0.8 and FSUIPC7 ver 7.0.0 so I will upgrade to 7.0.4. The only new thing I have been playing with is Multicrew and PF3. Those two addons are running outside P3D 5.1 so if I do not load those software and test PFC I can deduct that it is not them. I also upgrade window 10 to version 20H2 I will run more test and report back Pierre

The problem also occur with FSUIPC7 / PCFcom64 in MSFS2020 Pierre

Hi, not sure what is going on, but since a few days now, I can no longer assign key stroke to my cirrusII using PFCcom64. When I go to the Yoke Buttons menu and try to assign the DEL keys to my yoke right front button , like in the picture I pick the option 1.use key press, I get press key but it like the DLL doesn't see my keyboard. I am running version 5.051. I tried with the beech or Mooney yoke same thing. I tried different buttons and the same thing happened I cannot assign a key to my unit. If I press the button I want to use , I do get the grey square on the right side, showing me which one is active. So the DLL does see my CirrusII. This use to work perfectly before. Any help would be appreciated. Pierre

Yes thanks, With the last patch they did a lot of work on the C150, so I will see if I can now assign my axis, using the new SDK. If not, well to bad. Not a big problem Pierre

Hi, I been flying for about 7 hr in -25C and I cannot reproduce a carburetor icing event. The only thing I see is, when I put the Cab Heat at 100%, the RPM goes down about 10000. If I put the Cab Heat at 50% the reduction seem less. But I cannot guarantee that I have a icing issue. But on thing I learned, is that this software need to mature, so I am going back to P3D v5 until next year. None of the default aircraft are even close to reality. Pierre

Good point John, If it is well simulated I should see a impact on the power with 100%, according to the manual I should loss about 10% . I will test this on my next flight. Pierre

Thanks Pete, Something I do not understand is, I can use the mouse to pull and push the cab heat. The mouse doesn't use an axis? Pierre

This is too bad, for the Cessna 152 it is important to have the axis to work. I when back to my owner manual and they explain why they do not recommend to flying with 100% carb heat. Thomas for your info, this is from the owners manual: CESSNA SECTION 4 MODEL 152 NORMAL PROCEDURES The carburetor heat control knob should be pushed full in during all ground operations unless heat is absolutely necessary. When the knob is pulled out to the heat position, air entering the engine is not filtered. see document: Cessna 152 owners manual page 50.pdf Pete, I do have a icing push bottom on my Cirrus II and it does work as an on and off. I was just trying to get the blue arm of my quadrant to work. It is important for that plane to be able to increase or decrease the Carb Heat input. Thanks Pierre

That what I did, I assigned the set using the axis in FSUIPC. The axis doesn't show in the even log FSUIPC7.log From my understanding the Cessna 152 take is cab air from the front vent (filtered) and when you engage the cab heat it then takes the air from the manifold (not clean air, un-filtered) but hot. So at 50% you are getting 1/2 clean cold air and 1/2 dirty hot air. So if you need a little bit of hot air to manage ice building in the cab, you use a mix of air input, which is supposedly better for the motor. Pierre

I just check and it is the same in version 6, not a big deal . Pierre

Hi Pete, I did the test and when I assign to INTI ICE SET I can push the heat cab in from 100% to 0% but I cannot pull it back to 100%, with my middle blue arm on my quadrant . I need to use my mouse for that. I have include my profile, PFC and FSUIPC7 ini files for reference. Cessna 152.ini PFCcom64.ini FSUIPC7.ini Pierre