jmig

It was the VC++. Once I downloaded and installed it, FSUIPC worked with my key. Thank you for your help. John

I have been having a lot of issues with MSFS 2020. Today, I reinstalled Windows 11 and MSFS. Upon reinstalling FSUIPC7, my key would not register. The installer claimed that it was invalid. I checked the key and it is the same as what is listed on Simmarket under my orders. I bought the key when FSUIPC7 first came out and can send you the information from SimMarket as verification. I downloaded the temp key you have posted on this site, so i should be good to the end of the month.

Thank you for you patience and help, John. I have it working now, John

I do recall reading that README some time back. I guess I just forgot about the VIEW commands. I apologize. I went back and used MSFS's key binding for all push buttons on the joystick and throttle. Included are the repositioning of the cockpit camera; FWD,BACK,LEFT,RIGHT. I use a spring loaded double throw toggle to raise and lower the eye view. This switch is set up in FSUIPC and is working fine with MSFS. I think I mentioned this before, but my goal is have all of the basic functions assigned to the same keys in both P3D and MSFS. DSC is another matter left to another day or...week. My cockpit was once a beautiful cross between a F-16 and F18. Now that I am only using virtual reality via a Reverb G2, I am having to redesign. It no longer matters that the correct switches are in the correct cockpit positions. I am trying to make sure the most needed functions are right at hand and easy to find. I attempted to read up on the differences in running Macros and Lua scripts between FSUIPC6 & 7 last night, but I was too tired. I hope to do so today. I have a doctor's appointment later this morning. I should have time to read in his office. I use both for Profile aircraft that go beyond the basics. I still do not understand what a FULL log is? Later today, I will start a new session and log. I will check each of the "log me" check boxes. Is that what you want? If not, please be more detailed in your needs. What I would like from you is a YES or NO that FSUIPC is functioning correctly in MSFS. That way if an assigned button doesn't work I will know it is between MSFS and FSUIPC not FSUIPC. I can work with that and develop workarounds, as needed. These cockpit struggles help keep my old brain functioning. I will send the log later today. Thanks, John

Mr. Dowson, I know you see the same questions over and over. I know you get, what seems to you to be, idiot questions. I also assume that you know the various manuals almost by heart, considering how many times you have read them. Sometimes, you must feel like beating your head against a wall because of the RTFM questions asked of you by people like me. Still, as your own Mary Poppins said, "A spoonful of sugar helps the medicine go down." Respect must go both ways. I have read your manuals, at least most of them numerous times. I even have older copies of the primary and advances manuals printed. While I was once a real life pilot, flying both for USAF and as a GA pilot, I am currently going on 74 years of age. I once knew Dash-1s inside and out. Now, it is sometimes a mental struggle to learn something new. But, I try to persevered. For the record, I do not know the difference between a continuation log and a full log. I started a new log because you requested a logging of Buttons & Keys as well as Events. That in my mind suggested a new log, without all the previous stuff to confuse and obfuscate. I am sorry if I made your day harder by sending the new log. I also, was not aware of the camera controls not working in FSUIPC. That is because, as you alluded to, I have not read each and every forum post. Since it is late where you are, I hope your day tomorrow is better. I shall continue to puddle alone. Eventually, I will figured it out. I always have in the past. Thank you for your time and a wonderful little program you and your Dad built. John

Thank you John for such a rapid response. I update FSUIPV7 to 7.2.0 and ran MSFS, as suggested. At least some of the buttons seem to be working. However, none of the Camera View assignments are working. I am enclosing the log file. Unless, you find something wrong, I will assume it is on my end. I know I have a lot of controllers connected. The reason not all of them were working is because MSFS does not like one of them. Whenever I go to Controls, something is killing MSFS. The culprit is on a new 10 usb powered hub, but I don't know which one. So I turn them off and on, trying to isolate the one killing MSFS. That is another reason I want to work as exclusively as possible with FSUIPC. It is a real PITA for me to assign MSFS controls directly. The Virtual Joystick is a Pokeys 55 which handles direct to windows commands, i.e., WINDOWS Y. It is used mostly with DCS. I fly VR with a Reverb G2. There are no buttons or switches on it connected via usb. FSUIPC7.log

I am having all sorts of issues with FSUIPC and MSFS. I can not seem to get MSFS to use the button and switch settings. I have the same basic settings working with FSUIPC6 and P3D. However, I can set a switch or button with MSFS or Lorby Axis and Ohs and they work. Do the same thing in FSUIPC7 and the switches do not work in game, even though I can see them in the ini. It is frustrating. I don't want to use MSFS or Lorby to set switches. I have been using FSUIPC at least since FSX, maybe longer. I have attached the ini and log files. Thanks, John InstallFSUIPC7.log FSUIPC7.ini FSUIPC7.log

GIT is the Go-flight Interface Tool by PollyPot Software https://www.pollypotsoftware.org.uk/ It can read and write to Go-Flight modules. John

Pete, I do not own the C-182. I watched a review YouTube video on the airplane. At the end, the reviewer clicked on the door handles to open each of the two doors. Clicking on the door handles of the default aircraft does nothing, as I am sure you well know.

Thank you for the update and information, John. John

In trying to set up pots to control the trim, I noticed there is no axis for either the aileron (roll) or rudder (yaw) trim. Is this an oversight or does the new sim not offer these trims in an axis mode. I noticed that you cannot set them via the sim's controller settings either. John

The new Carenado C-182T allows you to open its doors. Carenado must have found a way around the sim controlling the doors.

Update to the update. It is working 🙂 Thank you so much for pointing me the right direction and the correction on the UW vs UB. You may not have an idea of how good I feel at the moment. I finally got one of these FM scripts to work. John

Update. I founld the Line 17 error and fixed it. Now I am getting a different error. I am afraid that I have no idea what this means. I will keep looking, however. 238843 *** LUA Error: C:\Users\john\Documents\Prepar3D v4 Add-ons\FSUIPC6\PBNC.lua:41: '<eof>' expected near 'end' 239281 *** LUA Error: C:\Users\john\Documents\Prepar3D v4 Add-ons\FSUIPC6\PBNC.lua:41: '<eof>' expected near 'end' 240203 *** LUA Error: C:\Users\john\Documents\Prepar3D v4 Add-ons\FSUIPC6\PBNC.lua:41: '<eof>' expected near 'end' 241156 *** LUA Error: C:\Users\john\Documents\Prepar3D v4 Add-ons\FSUIPC6\PBNC.lua:41: '<eof>' expected near 'end' 247500 === Closing session: waiting for DLLStop to be called ... 260859 === DLLStop called ...

Thank you, sir, I (think) I made the changes you suggesed. However, it didn't work. Here is the modified script and the FSUIPC log. -- Paramenters -- 1 Park Brake off -- 2 Park Brake on -- 3 Canopy Switch OPEN -- 4 Canopy Switch CLOSE -- Variables Park_Brake = 0x0BC8 -- FSUIPC Offset Values 0=OFF 32767=ON Canopy_Set = 0x3367 -- FSUIPC Offset Values 0=OFF 1=ON - Parking Brakes Set if ipcPARAM == 1 then ipc.writeUW(0x0BC8,0) end if ipcPARAM == 2 then ipc.writeUW(0x0BC8,32767) end -- Canopy Switch OPEN if ipcPARAM == 3 then ipc.writeUB(0x3367,1) end -- Canopy Switch CLOSE if ipcPARAM == 4 then ipc.writeUB(0x3367,0) end end FSUIPC6.log