von

Pete, Yes it is FSUIPC Ver 3.80 Thanks for the quick reply. I will give it another try.

I am attempting to assign and calibrate two GoFlight TQ6 throttles for the PMDG737-800. What I need is just one power range from minimum (idle power) to maximum power, calibrated without a zone for reverse thrust. TQ6 has levers (buttons) for reverse thrust which I can assign to keyboard keys F2 and F1. My options to SET are Reverse, Idle and MAX. But, I always end up with a calibrated reverse thrust zone. Is there a way to eliminate the reverse thrust zone from each calibrated throttle? My throttles are currently assigned axis as detected by FSUIPC: Throttle 1 is assigned = Z axis Throttle 2 is assigned = V axis Is V ok to use?

Pete, Thanks for the information and quick follow up. I will go get the new 4.208 / 3.768 now. Happy Holidays

Ok, Thanks for the quick reply. Have a good day.

I have win XP Using FSUIPC ver 4.2 and 3.75 Using FS9 I can add a comments like this in the ini file: [buttons] 1=P2,4,C66079,0 ; Gear Down 2=P2,5,C66080,0 ; Gear Up 3=P2,0,K121,8 ; Track IR Pause (F10) 4=P2,8,K122,8 ; Track IR Center (F11) When I start the sim and go to the FSUIPC Buttons Tab to check the assignments discriptions display properly. When I press a button the box will fill in to tell me what the button assignment is. When I do the same comments using FSX (FSUIPC 4.2) the and press the button to see that it is properly assigned the box does not fill in. The function however, still works in the sim. Here, if I then remove the ; xxx comment then the button press will fill in the assignment information box.

Pete, Thanks again for your time and the detailed reply. Now I "know" what "substring" means and how it is used. I won't go looking into aircraft cfg files ... Non-programmer here but I really do try hard!

To Pete: I changed the FSUIPC ini file to this: ShortAircraftNameOk=Yes Only kept one set of button assignments: [buttons.Level D Simulations B767-300ER] 0=P2,6,K68,11 1=P2,7,K87,11 2=P2,1,K80,10 Level-D aircraft.cfg file: From this (incorrect one) title=[DXT3] Level D Simulations B767-300ER - Delta Air Lines (Old Livery)] To this: title=Level D Simulations B767-300ER - Delta Air Lines (Old Livery) Now all five of my Level-D aircraft load with the same FSUIPC (yoke) button assignments. Great! I got it going but I do not know if it is the correct way! >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> But when I select "specific aircraft" in FSUIPC to verify all the button assignments, they all come up with the same name in the FSUIPC title bar: Level D Simulations B767-300ER I expected to see: Level D Simulations B767-300ER - Delta Air Lines (Old Livery) .............................. So I guess the short name is everything before the second "-" in the line above. Can there be mutiple occurances of eg. ShortAircraftNameOk= in the FSUIPC ini file, like for your example for Airbus and Boeing? Would it be this sequence: ShortAircraftNameOk=Yes ShortAircraftNameOk=Airbus ShortAircraftNameOk=Boeing Or, is it one occurance of ShortAircraftNameOk=Yes or several lines to specify ShortAircraftNameOk=Airbus ShortAircraftNameOk=Boeing etc. But you cannot mix them? Are there any examples of the usages?

Pete, Thanks for the reply. After 4 hours trying my self I gave up and posted. The above name was all on one line in the ini file. My cut and paste messed it up a bit. I figured the [ ] brackets could be the cause .. I renamed the repaint "like" the ones that worked but still had problems in the end. I did search for the solution .. no luck, so grateful for your information. In the end I will have (hopefully) all DXT-3 repaints and they all share the same naming problem. I will give you solution a go and also put a stickie on my FSUIPC notes. Thanks again Pete, really appreciated.

My FSUIPC ver 3.74 and ver 3.75 do the same thing here. from the FSUIPC.ini file. I have three (32 bit) Level-D liveries. I asigned the same yoke buttons for all three and they work good. The first three beolw. [buttons.Level D Simulations B767-300ER] 0=P2,6,K68,11 1=P2,7,K87,11 2=P2,1,K80,10 [buttons.Level D Simulations B767-300ER - UPS2] 0=P2,6,K68,11 1=P2,7,K87,11 2=P2,1,K80,10 [buttons.Level D Simulations B767-300ER - Hawaiian Airlines] 0=P2,6,K68,11 1=P2,1,K80,10 2=P2,7,K87,11 [buttons.[DXT3] Level D Simulations B767-300ER - American_Airlines_N327AA_DXT3] 0=P2,6,K68,11 [buttons.[DXT3] Level D Simulations B767-300ER - American_Airlines_N327AA_DXT3] 1=P2,7,K87,11 [buttons.[DXT3] Level D Simulations B767-300ER - American_Airlines_N327AA_DXT3] 2=P2,1,K80,10 I added an American Airlines DXT-3 repaint and assigned the same yoke buttons. This does not work. There are more [ ] in the American and the layout is different between the 32bit repaints (first three) and the DXT-3 repaint. I cannot figure out to get the button assignments working on the American repaint.

Hi, Yes, I tried to register on their forum but it would not go through. I will keep trying. At first I thought you developers (various vendors) shared notes to keep compatible with each other.... to the extent possible. I tried programming switches and buttons for the first time. When I programmed a CH yoke buttons it all worked ok until I exited MSFS then restarted MSFS. The button assignments no longer worked. I read some of your manual .. sorted out a few thingslike some of the assignments in MSFS must be deleted proir to assigning the buttons/switches/keys within FSUIPC. I ended up backing up my FS9.cfg then deleting itso I could start fresh. I deleted the FSUIPC.ini to start fresh. Deleted the assignments in MSFS that I wanted to program with my very own "registered" FSUIPC ver 3.65 (proud owner here!). Everything is working great so far! I then looked into the new FSUIPC.ini file and seen how the buttons were coded with ASCII character decimal values, seen how the control codes were used (like C66079/C66080) for the flaps, and noted the difference in coding for shifted/unshifted keyboard keys are coded. I will have to be alone with your manuals and a lot of coffee for quite some time. From now on I am only making one change at a time, testing it and documenting the change (plus appropriate file backup) prior to fixing the next hole in the dam! Thanks for the support, you have a great product here. As I recently mentioned in the response to a post I did on another forum (about yoke buttons), I said, it seems to me that FSUIPC "registered" is the final fix to the unsolved problems. Time to go read the pages and get a good grip on all this. Best Regards, Vaughan Martell

Hi, Thanks for the feedback. I will continue "trying" to contact Go-flightthey are not answering their phone. Regards, Vaughan Martell

Hi, I purchased the registered version (3.65) of FSUIPC All, the problems "went away". Regards, Vaughan

Ok, I tried to register onto Go-Flights' boardhave not been able to yet. So, I called them and left a message to call me. In my previous posts I referred to your versions as old ver XX and it was typed wrongsorry. Any reference I made to old should be like version 3.60 or 3.615 New version should have been 3.65 I went back and edited my errors on those posts. In the meantime, I downloaded Go-Flights older software version that also has support for the Level-D 767. I will try it soon and see what happens. Thanks again for your help and understandingthru all my typos and confusion getting a grip on what's really wrong. Vaughan Martell

OK, I will contact Go-Flight and see if the "bad" DLL actually belongs to them and what I need to do. I really appreciate your help here. Initially you mentioned a "bad" DLL may not even work with the registered FSUIPC. When a non-software type like me loads a program onto the computer I assume all this stuff works together .. believe they say backward compatible. So, the natural assumtionI just try to keep all the software up to date and that should do it. Because your version was just loaded I assumed it may have a problem. I learned a lot here Pete. Your time was not wasted and I hope in my heart this post saves another user and you some time down the road. Best Regards Vaughan Martell

Ok, I found the dll that caused the problem. Has to do with Go-Flight modules, which I have been using for couple of years. The dll name is GFMcp2K4.dll When I removed that file and its .INI file to a temp. directory then I did not get your error box when MSFS first started up. I use the Go-Flight modules and their GF-MCP autopilot. The autopilot software was updated some time ago so their autopilot could be used with the Level-D 767 So, I have to figure out what I need to get to make your ver 3.6 work. My guess .... probably a bad one, is that I need an updated Go-Flight DLL. In that case, they would already know that there hardware will not work with FSUIPC ver 3.6 without new Go-Flight DLL? This is where things can get a little messed up if I do not know what versions work with what. I know you have a DLL module for Go-Flight MPC (was it , PRO?) for users who have registered version of FSUIPC. I should not need registered, right? Best Regards, Vaughan Martell

Ok, I got it now. The Beta versions could by-pass errors. Now I am seeing them. They were always there back to FSUIPC ver xx. I am sorry I did not understand at first, second etc. I will try sorting through the DLL's But, in all the years I have used MSFS and FSUIPC I had not had a problem like this. So, it came as a surprise. Best Regards, thank you very much for your time. And patients. Greatly appreciated. Signing out. Vaughan Martell

Hi, I will try to send the log file as an attachment. It is too big and I think I cannot send it as a .LOG file Found out I will have to ZIP it. If I can find a file to zip it up on my PC I will send it to you Vaughan

Hi again, Here are the two logs: First flight results: ********* FSUIPC, Version 3.615 by Pete Dowson ********* Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="" User Addr="" WIDEFS not user registered, or expired Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=40003605[40003605] First flight using FSUIPC version 3.615 InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=0 1047 System time = 11:54:36 1047 C:\Program Files\Microsoft Games\Flight Simulator 9\ 1047 System time = 11:54:36, FS2004 time = 12:00:00 (00:00Z) 1156 Client Application: "fs9" (Id=2432) 1156 C:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe 1156 Product="Microsoft Flight Simulator 2004 - A Century of Flight" 1156 Company="Microsoft Corporation" 5312 FLIGHTS\other\MEIGS.flt 5375 AIRCRAFT\c172\Cessna172SP.air 5562 Aircraft="Cessna Skyhawk 172SP" 9672 Module [M1] identified = "ActiveRadar.dll" 9672 Module [M1] "ActiveRadar.dll" access registration is okay 16047 C:\Documents and Settings\Vaughan\My Documents\Flight Simulator Files\LD-SAN-CD.flt 16172 AIRCRAFT\LVLD_B763\B767-300.air 16359 Aircraft="[DXT3] Level D Simulations B767-300ER - American_Airlines_N327AA_DXT3" 19625 Clear All Weather requested: external weather discarded 19906 Module [M2] identified = "B767at.GAU" 19906 Module [M2] "B767AT.GAU" access registration is okay 21000 Module [M3] identified = "B767Afds.GAU" 21000 Module [M3] "B767Afds.GAU" access registration is okay 21234 Advanced Weather Interface Enabled 27828 Traffic File #21 = "scenery\world\scenery\fslive" 42031 System time = 11:55:17, FS2004 time = 03:54:50 (10:54Z) 42031 *** FSUIPC log file being closed Memory managed: 4 Allocs, 161 Freed ********* FSUIPC Log file closed **** Second "same" flight using FSUIPC version 3.65 which gave the error bos before MSFS loaded. ********* FSUIPC, Version 3.65 by Pete Dowson ********* Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="" User Addr="" FSUIPC not user registered WIDEFS not user registered, or expired Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=0000B027[0000B027] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=0 1000 System time = 12:00:06 1000 C:\Program Files\Microsoft Games\Flight Simulator 9\ 1000 System time = 12:00:06, FS2004 time = 12:00:00 (00:00Z) 1109 Client Application: "fs9" (Id=4008) 1109 C:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe 1109 Product="Microsoft Flight Simulator 2004 - A Century of Flight" 1109 Company="Microsoft Corporation" 5250 FLIGHTS\other\MEIGS.flt 5312 AIRCRAFT\c172\Cessna172SP.air 8719 Illegal read attempt: offset 0238, size 3 [P4008] 8719Program or module not accredited for use with this unregistered FSUIPC 8734 Module [M1] identified = "ActiveRadar.dll" 8734 Module [M1] "ActiveRadar.dll" access registration is okay 8766 Illegal read attempt: offset 0238, size 3 [P4008] 8766Program or module not accredited for use with this unregistered FSUIPC 20000 ### IPC Message processed in 11281mSecs ### 26156 C:\Documents and Settings\Vaughan\My Documents\Flight Simulator Files\LD-SAN-CD.flt 26281 AIRCRAFT\LVLD_B763\B767-300.air 28969 Clear All Weather requested: external weather discarded 29234 Module [M2] identified = "B767at.GAU" 29234 Module [M2] "B767AT.GAU" access registration is okay 30266 Illegal read attempt: offset 0238, size 3 [P4008] 30266Program or module not accredited for use with this unregistered FSUIPC 30328 Module [M3] identified = "B767Afds.GAU" 30328 Module [M3] "B767Afds.GAU" access registration is okay 30578 Advanced Weather Interface Enabled 37187 Traffic File #21 = "scenery\world\scenery\fslive" 64125 System time = 12:01:10, FS2004 time = 03:55:02 (10:55Z) 64125 *** FSUIPC log file being closed Memory managed: 451 Allocs, 749 Freed ********* FSUIPC Log file closed **** Best Regards, Vaughan Martell

OK, I am not a programmer but I will follow your instructions. I went back to FSUIPC ver 3.615 Nothing else running MFSS loaded OK I do use FSTime, but it was not runningto be sure of everything I will: Have NO ActiveSky, NO clock, NO RadarContact running. By the way, when I do run these modules they are always started after I load MSFS> Start MSFS with FSUIPC ver 3.615, load a Level-D 767 flight that I have been flying for the past week. Then exit the MSFS and print the log. Next I will install FSUIPC 3.65 again. Then, do the same flight, print the log and send it to you. Best Regards, Vaughan Martell

Hi, Thanks for the reply. I was using version 3.615 this am (flying OK) Aircraft = Level-D 767-300 Everything worked OK I installed your new version 3.65 or old 3.60 and got the error box. I get your error box, click OK and MSFS then continues to load. What can I do to get your new ver 3.65 working. I have not changed any gauges, no changes. Months ago I added a gauge to open/close cargo and main doors. Best regards, Vaughan Martell

I have used the previous versions of FSUIPC (unregistered) in the past without a problem. Now, with new version 3.65 a message says it does not support the programs I have used for a long time with MSFS ver 9.1 So, I printed the following FSUIPC log. I need to know what it means and what I have to do? ********* FSUIPC, Version 3.65 by Pete Dowson ********* Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="" User Addr="" FSUIPC not user registered WIDEFS not user registered, or expired Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=0000B027[0000B027] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=0 2578 System time = 10:06:18 2625 C:\Program Files\Microsoft Games\Flight Simulator 9\ 2625 System time = 10:06:18, FS2004 time = 12:00:00 (00:00Z) 2953 Client Application: "fs9" (Id=2456) 2953 C:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe 2953 Product="Microsoft Flight Simulator 2004 - A Century of Flight" 2953 Company="Microsoft Corporation" 8312 FLIGHTS\other\MEIGS.flt 8406 AIRCRAFT\c172\Cessna172SP.air 18140 Illegal read attempt: offset 0238, size 3 [P2456] 18140Program or module not accredited for use with this unregistered FSUIPC 18171 Module [M1] identified = "ActiveRadar.dll" 18171 Module [M1] "ActiveRadar.dll" access registration is okay 18171 Illegal read attempt: offset 0238, size 3 [P2456] 18171Program or module not accredited for use with this unregistered FSUIPC 73500 ### IPC Message processed in 55360mSecs ### 100984 System time = 10:07:56, FS2004 time = 10:06:27 (15:06Z) 100984 *** FSUIPC log file being closed Memory managed: 759 Allocs, 759 Freed ********* FSUIPC Log file closed **** Best Regards, Vaughan Martell