Rameric5

Hi John, Absolutely. I was going to send the screenshot of the modules folder showing everything in it but it was too big. Now that you mentioned it, I do remember something about not using Program Files, probably from this very forum. My work week is about to start so I will try your suggestions in 4 or 5 days. Thanks again for your help. Eric

Hi John, I did as you said and removed the 32 bit parts of the PFC.dll download (pfc.dll and pfcfsx.dll) and kept the PFCcom64.dll in the modules folder and P3d is still not recognizing PFC. You should NOT have that in your FSUIPC6 installation folder. The PFC serial driver was just placed in the modules folder along with FSUIPC6, not in any installation folder. I had also tried removing it from that folder with the same lack of results. In my several attempts at doing stuff to figure this out I double clicked on the PFC_Serial_Driver_FSX folder and that opened up another folder of the same name except with a PFC logo as opposed to the regular yellow folder icon. I right clicked on that and clicked "run as administrator". A license agreement window popped up. After accepting the license agreement a "Ready to Install" window came up. Once I hit "install" the above message appeared. As requested, I'm including the FSUIPC6.log files. Thanks, Eric FSUIPC6.log FSUIPC6_prev.log

Hello, I have Prepar3d v4.5 and recently had problems with the program causing me to uninstall and reinstall the program; meaning I pretty much had to start over. I have a PFC Jet Console with a serial port connection. I couldn't get the hardware to work. I updated to FSUIPC 6 (from 5) and downloaded the PFCDLL driver. I also have the PFC_Serial_Driver_FSX (all in my Modules folder) but still no go. When I try to install the serial driver I get this message: "Internal error: An attempt was made to expand the "app" constant before it was initialized". This message occurred both before and after updating FSUIPC. So, what am I missing here? Thanks. Eric

Thanks Pete. Evidently it had to be re-extracted into the modules folder. It didn't help that I totally forgot that I needed to place it in that folder to begin with. But now I'm seeing the PFC check box when I open P3d. Success! Cheers, Eric

First off, apologies if this has been covered before. I did a topic search and was unsuccessful finding a solution on the forum. I recently had problems with P3d v4 and had to delete and reinstall it. I already had the serial driver for PFC installed on my computer but had to reinstall it into P3d. However, when attempting to do so I got the message: "Internal error: An attempt was made to expand the "app" constant before it was initialized." I seem to remember having this problem before with this or something else but damn if I can remember what the solution was. Any help? Thanx. Eric

That's all I need to hear. It makes so much sense now the more I think of it. I checked out those brainboxes links that you sent and feel that may be a little above my "pay grade". There's a big Microcenter store down the highway and I have a computer guy here (who actually rebuilt my computer) who I think will give me the best fit for what I have in terms of serial port cards. I'll mention the PCI and PCI Express and see what he says. Thanks again Pete. Eric

Apologies if it came off as a criticism of the driver. My point there was that something is wrong somewhere in the system. I wouldn't know one way or the other. I have no doubt that it's not the driver if, as you said, there hasn't been problems before. I'm beginning to think that perhaps my problem lies with my connection. My computer doesn't have a serial port and I'm using an adapter going to a USB connection on my computer. Something's probably lost in the translation. As it stands, I may have to contact PFC if, for no other reason, to see if that may be the culprit. Eric

Whew, I tried calibrating with FSUIPC and it was even worse. It was almost like it had problems understanding the inputs from a PFC device. Like it had to translate a different language first. There was no continuous stream of input numbers and it delayed quite a bit. I believe you're right. I think there's a problem here with this PFC driver (or maybe even my console). I'm not going to worry about contacting PFC since, due to past experience, I don't think they want to be bothered; especially with questions about a legacy serial device. I'm going to try a couple of more things and, like I said, I have another throttle quadrant that I can use. I should be able to get something that works well enough. Again, thanks for the info, the help and your time Pete. Cheers. Eric

I'm glad to hear there's a FSUIPC calibration option. I may have to try that. OK, here's what I have now though: Set Parked Limit= 4, Armed Detente= 11, Flight Detente= 32 and Fully UP= 80. When the speed brake lever is full up/forward, the input value is 1and the slider scale is about 3 and-a-half ticks down from the top. The flight model shows spoilers down. Scaled output is 4800. With the lever pulled back to input value of 7, the slider moves up to the 1st tick, the Scaled Output shows "ARM" and the spoilers raise slightly. At an input value of around 19, the Scaled Output shows 7111, the slider jumps back down to 4 and-a-half ticks and the spoilers raise some more. At an input value of 22, the slider moves to 5 and-a-half, the spoilers raise a little more and the Scaled Output is 9348. At an input of 28, the slider is 7 ticks down, the spoilers are up about 45 degrees and the Scaled Output is "FLT". Finally, at an input of 80, the slider is on the bottom tick (#9), the spoilers are up about 60 degrees and the ailerons come up slightly as well. The Scaled Output is 52590. Believe it or not, this is better than what it had been doing but obviously there's something wrong at that lower end where the arming comes into play. NOW I'm starting to have similar problems with the flaps (almost working in reverse). That didn't seem to be a problem before. I believe you had something when you said I may need to reverse it. I notice that the box that says RVS is checked on both the spoilers and the flaps in the calibration window but they are greyed out and won't let me uncheck them. Could that be my problem? Thanks as always. Eric

Actually, I should have been more clear. The "full up" position I was referring to is the speed brake lever itself, not the actual spoilers. The "third of the way down" that I was referring to was the little slider square on the calibration scale. In other words, when the lever is full up or forward (spoilers completely lowered) the calibration slider scale is one third of the way down (armed or flight detente), not all the way at the top as it should be. The slider only moves up after I pull back or down on the speed brake lever. I just wondered if perhaps changing something in FSUIPC.INI might correct this calibration scale being off or allow it to be reset. If not, I have another non-PFC throttle quadrant that I can use. I just like the PFC one better because it usually can be calibrated with an "armed" position (when I used it before with FSX) while the other one apparently cannot be. Anyway, thank you Pete for all of the help and info that you provided. There are almost always options. Cheers! Eric

I honestly can't remember what the 8 FSUIPC listings were now but I know none had the .ini suffix. It is entirely possible (although I don't know how likely) that I unchecked the "Hide file extensions" box and didn't realize/remember it. The important thing is, thanks to you, I found the file now. I'm going on a trip for a few days and I'll do that line deleting thing that you explained when I get back. As for the PFC calibration problems, I downloaded the serial driver for PFC from the Schiratti/Dowson website a few days ago. I didn't have problems calibrating the throttles, reversers and flaps using the PFC calibration utility but the full up position for the speed brake shows as being about a 3rd of the way down on the slider. When I pull back the lever the slider jumps up to the zero position. When the lever is more than half way pulled back then the slider moves down again and when the lever is pulled all the way back the slider never reaches the lowest point. It gets kind of close but not quite there. I tried moving the speed brake back and forth SEVERAL times but it doesn't change anything. Looking at the wings on the flight model (QW 787-8) the spoilers come up a little when they should be armed and lower after passing the armed position not to come up again, or would come up more as I pull back on the lever and then go back down again. Also, in the interest of not creating confusion here. I'm only using the PFC throttle quadrant and console. My yoke and rudder pedals aren't PFC. If you have any suggestion I'm all eyes (ears). Thanks Eric

Thanks Pete, the "Hide extensions for known file types" box was already unchecked. However, I had to switch "Don't show hidden files" to "Show hidden files" further up the page and FSUIPC.INI appeared. Now, will the advanced users guide show me specifically what I have to change to make the yoke button work again or is it something that one has to kind of already know what they're doing? I tried changing the words from "PAN_UP/PAN_DOWN" TO "ELEVATORTRIM_UP/ELEVATORTRIM_DOWN" but obviously that didn't work. I'm also wondering whether or not I can use FSUIPC.INI to deal with calibration problems I'm having with the speed brake lever on a PFC throttle quadrant? Thanks again. Eric

Hi all. I'm a registered user of FSUIPC5. I have Prepar3d v4 using Windows 10. I was using FSUIPC to assign buttons on my yoke. Initially I assigned trim up/down to the left side toggle button. I switched to pan up/down and then decided to go back to trim up/down. Everything is greyed out and I get a message in one of the window boxes: "This button has mixed actions already! Please edit in FSUIPC.INI file". I go to my modules folder and see 8 FSUIPC listings, none of them ending with the suffix .INI. I do a search of my computer files and it can't find an FSUIPC.INI. I see several references to this file in the forum but all seem to know where it is. Am I looking in the wrong place or is it just missing? Thanks. Eric