airernie

Thanks, will give it a go..

Flying the Majestic Q400, Windows 11, FSX:Steam. Profile Specific setting is recognized when Axis Assignment is selected, but not Buttons + Switches. I check the box, set my button, select FS Control, and choose the action and it works immediately after I exit the FSUIPC interface. However, when I reopen FSUIPC4 or the next time I load the aircraft the profile specific check is empty and it doesn't recognize my aircraft. BTW,, Axis Assignment does see it.. Thanks, Ernie FSUIPC4.ini

Thanks. This was actually one time I was hoping that it something that I was doing incorrectly. 🙂

I am attempting to assign a joystick button to one of the Zoom functions. I've tried all of the functions and multiple buttons, yet nothing seems to happen. If I assign something like the parking brake to a button then it works fine. Not sure if this is a MSFS issue or that I need to do something different. I'm testing it with the stock CJ4. Thanks..

Will do.. Thanks..

Okay, so this is strange, but if I use my Saitek Trim Wheel to set trim, the plane errors out as I described above. If instead I use the buttons on my Extreme 3D Pro to set trim, then all appears well. Not sure and I guess only time will tell if this was the cause and solution, but for now blue skies..

Thanks for the response. I don't have failures turned on. Sometime in the next couple of days I'm going to try some 'flaps off only', 'trim off only', or 'FD off only' flights to try and narrow down which is actually the cause of the error. It may be that something on my system is conflicting with one of those settings. Either way, the workaround works, so I'll add it to my checklist.

Following the instructions in the Introductory Flight for the 100. Every thing goes great until I advance the throttle to taxi. Then all sorts of errors pop up; Flaps Error, YD off, Fuel, etc. I then have to shut off and restart the engines, then it proceeds okay. Last night I decided to not engage the flaps and trim until I was actively taxing and the only error that popped was 'A-I E1 Fail', which isn't listed in the manual. Doing an Internet search it appears to be a 'Anti-Ice failure in Engine 1'. I know it's an old aircraft, but wondering if anyone else has experienced such errors on the initial taxi. Thanks, Ernie

Thanks John, I would have, but it's long gone. I uninstalled FSX and add-ons when I made a move almost four years ago, for some reason. I kept all of the add-on and utilities, so they could be reinstalled, but stuff was lost along the way when I thought "I'll never use this again". Ernie

Just saw the message. My VAC script is probably simpler than yours, but I found that I had to run VAC as an administrator to get it to react to FSX in Windows 10. Otherwise it failed whether FSUIPC was installed or not. Ernie

I'm cross posting from AVSIM, hoping that it finds a more targeted audience. During the re-installation of FSX I pulled one of my FSUIPC.INI files from backup. There is a lua file referenced titled 'FSMFS9Payload'. It's not critical that I locate a copy, but it is that itch I want to scratch. I've looked in the scripts that come with FSUIPC as well as the support forum without luck. Also, I've installed just about everything aircraft or utility related that I thought might have contained it with the same results. Thanks, Ernie

There are also the Logitech Plugin and Panel Drivers. Of course what works best depends upon what flight simulator you have.

Thanks Pete.. Not sure why I didn't catch that, but thank you for your patience and guidance.

Hi Pete. Thanks for the reply. I admit that I am now more confused, because at the top of the Feelthere_ejet.ini file are the following definitions: [Profile] Created=12/02/2016 16:51:28 [Buttons] 1=RE,21,K113,8 -{Key press: F2}- 2=PB,5,C66852,0 -{VIEW_CAMERA_SELECT_2}- 3=UB,5,C66654,0 -{VIEW_VIRTUAL_COCKPIT_FORWARD}- 4=PB,4,C66853,0 -{VIEW_CAMERA_SELECT_3}- 5=UB,4,C66654,0 -{VIEW_VIRTUAL_COCKPIT_FORWARD}- 6=PB,3,C66854,0 -{VIEW_CAMERA_SELECT_4}- 7=UB,3,C66654,0 -{VIEW_VIRTUAL_COCKPIT_FORWARD}- 8=PB,0,C65752,0 -{PARKING_BRAKES}- 9=UB,0,C65752,0 -{PARKING_BRAKES}- 10=RE,20,K113,8 -{Key press: F2}- 11=UE,20,K113,8 -{Key press: F2}- Perhaps I misunderstand and it requires specifically opening FSUPC and ticking the profile specific checkbox to access them, unlike the Axes which are automatically selected based on the aircraft. Ernie

I apologize for the delay in responding, but I wanted to make sure the issue was repeating. I have tried starting with both the default C172SP and the FeelThere e-Jets 175 and the issue occurs in both cases. When I start the aircraft, FSUIPC recognizes the profile for the Axis, but not the buttons. If I then check the profile specific checkbox, then the buttons work fine. I have uploaded several files which may help or only serve to confuse. The two jpgs show the state of the title bar when I initially open FSUIPC. Thank you.. FeelThere_eJet.ini FSUIPC4.ini FSUIPC4.log

There is a DynamicFriction LUA script that you can use to reduce some of the surface friction during the taxi process. It should have been included in the 'Example LUA plugins.zip' file that was added to Modules\Documents when you installed FSUIPC. I think there is also a 'Patchsimfriction' variable that you can add to the FSUIPC.ini file, but I don't really know how it functions, so haven't tried it. The LUA script is easily installed and can be removed without effect if it doesn't solve your problem. The instructions for LUA script usage are in docs.

Not an insurmountable issue, but frustrating. I am using separate profiles for each class of aircraft (ASEL, AMEL, ASEL Complex), etc. I have noticed that recently FSUIPC is not recognizing some of the aircraft when I load them. If I open FSUIPC and check the box for the appropriate tab then the correct profile displays at the top of the dialog. I'm not sure what has changed. I have tried reinstalling 4.974 by itself and also4.974b. As I said, it's not insurmountable, but I didn't experience this in the past. Thanks, Ernie

Sorry, replied, but re-read you message and determined it didn't apply, so deleted content..

I'm sure the issue is made all the more difficult because I've only seen one mention and he had written it off to Windows 10. In any case, it's nothing more than a minor annoyance that is easily dealt with through Thomas' Lua script if need be. Thanks for the help, Ernie

Hi Pete, FSX SP2, Windows 7 Pro 64-bit, FSUIPC4 4.966c. I replaced the Lua plugins with "P3DV2fiddles=Yes", but it didn't resolve the issue. Perhaps because I'm in FSX? I have attached the ini and log files in case they might prove useful. Thanks, Ernie FSUIPC4.log FSUIPC4.ini

Hi Pete, Just tried Thomas' LUA scripts with 4.966c and the BAT switch works correctly when it is present. Without the LUA scripts, the BAT switch is inoperative. Ernie

Hi Pete, Just a bump, so the offset issue I experienced doesn't get lost in the flood of 64-bit related posts. I reverted to 4.964, so I haven't had a try at Thomas' suggestion yet. Admittedly, I'm hoping that you can resolve the issue in a future version, so I don't need to add the Lua script. Thanks, Ernie

Thanks for the help Thomas, I'll give the script a go..

I'm using the freeware v0.5.0 although I've also tried v0.5.1.

Thanks for the link. I just tried it and have the same issue. I don't have a copy of 4.965 to see if the issue exists there also, so I don't know when the functionality changed. Ernie