September 30, 20178 yr This one has me stumped so far and is really strange. For some strange reason my prop pitch lever on my CH throttle quadrant will not work with the Milviz Beaver. It works in every other aircraft and the throttle and mixture work just fine in the Beaver. I checked fsuipc and there is a signal from the prop pitch lever when I look at the calibration tab but the animated lever in the Beaver does not respond at all. I'm reaching because it seems like this is a first as I can't find any answers in any search I do. LouP
September 30, 20178 yr Try changing your axis to engine 1 mixture instead of just mixture. CPU: Intel i9-11900K @5.2 / RAM: 64GB DDR4 3200 / GPU: 4080 16GB /
October 1, 20178 yr Moderator assign it to AXIS_PROPELLER1_SET in fsuipc. Vic RIG#1 - I9 14900K MSI Pro z790 RTX 5070Ti 40" 4K Monitor 3840x2160
October 1, 20178 yr Author 19 hours ago, vgbaron said: assign it to AXIS_PROPELLER1_SET in fsuipc. Vic Yep, this is how it is set up. LouP
October 1, 20178 yr It wont work like this. Its noted in the forums over at Milviz You need to set a profile in FSUIPC for the beaver and assign the prop lever to the main prop pitch command, not the separate 1,2,3,4 etc. Had the same issue myself. Glenn Ryzen 3700X, X570 Pro Wifi, 32GB 3600mhz RAM, Nvidia Titan Xp "Galactic Empire", RM750x PSU, H700 case, 2x NVMe M2 SSD, 1x SATA SSD
October 1, 20178 yr Moderator Double checked - I have mine set to PropPitch1 - works just fine. Vic RIG#1 - I9 14900K MSI Pro z790 RTX 5070Ti 40" 4K Monitor 3840x2160
October 2, 20178 yr Author Now confused. FSUIPC is not seeing this lever as a single prop pitch lever because I have is assigned in the sim as 1 of 2. I don't want to reassign this in the sim then it will be set that way for all aircraft. When I am in axis assignments tab in fsuipc, the lever does not even register there on that tab. What am I missing? Thank you all for your patience. LouP
October 2, 20178 yr 6 hours ago, vgbaron said: Double checked - I have mine set to PropPitch1 - works just fine. Vic Hmmmm.... that doesn't work for me. Mine has to be set to PropPitch. gb. YSSY. Win 10, [email protected], Corsair H115i Cooler, RTX 4070Ti, 32GB G.Skill Trident Z F4-3200, Samsung 960 EVO M.2 256GB, ASUS Maximus VIII Ranger, Corsair HX850i 850W, Thermaltake Core X31 Case, Samsung 4K 65" TV.
October 2, 20178 yr Author OK got fsuipc to recognize the tq. Not sure what step resolved that but I used fsuipc to set all assignments for the tq and made a profile specific setting for the beaver using just prop pitch. Still no joy. Man!
October 2, 20178 yr 1 hour ago, LouP said: When I am in axis assignments tab in fsuipc, the lever does not even register there on that tab. What am I missing? Thank you all for your patience. I thought said in first post that it was registering in fsuicp? Do you have the latest 5.121a version? http://forum.simflight.com/topic/80977-updated-modules/ gb. YSSY. Win 10, [email protected], Corsair H115i Cooler, RTX 4070Ti, 32GB G.Skill Trident Z F4-3200, Samsung 960 EVO M.2 256GB, ASUS Maximus VIII Ranger, Corsair HX850i 850W, Thermaltake Core X31 Case, Samsung 4K 65" TV.
October 2, 20178 yr Author Jus 29 minutes ago, gboz said: I thought said in first post that it was registering in fsuicp? Do you have the latest 5.121a version? http://forum.simflight.com/topic/80977-updated-modules/ gb. Just in the calibration tab. I have done a series of things to get it to register in the assignments tab also now and assigned the lever to prop pitch set under a profile I created for the beaver but it still isn't working.
October 2, 20178 yr Author YAHOO! got it. I had to send the profile specific prop pitch command to calibration NOT to the sim. Thank you all. :-) LouP
October 2, 20178 yr 6 hours ago, gboz said: Hmmmm.... that doesn't work for me. Mine has to be set to PropPitch. gb. Same here. Glenn Ryzen 3700X, X570 Pro Wifi, 32GB 3600mhz RAM, Nvidia Titan Xp "Galactic Empire", RM750x PSU, H700 case, 2x NVMe M2 SSD, 1x SATA SSD
January 3, 20188 yr I had the same Problem. Milviz solved the Problem with it`s latest Beaver update, so no workaround is needed anymore:-)
Archived
This topic is now archived and is closed to further replies.