CHBTheDoctor

Thanks for the fast reply. I expected your answer, so the idea doing it via LUA is more than I hoped for :idea: Maybe I give this a try this weekend...

In the documentation of addon aircraft there are sometimes recommendations for the simulator realism settings like P-Facvtor, Torque etc. These recommendations may be different from addon to addon, so - would it be possible to set them from FSUIPC ? - would this make sense ? If yes, with a registered copy of FSUIPC we could read those settings from an aircraft section so that every addon aircraft gets its correct value. Would be a nice to have... Thanks, CHB

That's nevertheless interesting, so this could be useful when looking for other problems... Ok, thanks for your help, as I said, when it's happening again I'll tell you. Currently I'm happy, FSUIPC and A2A Accusim nicely integrate the controllers for my A2A Mustang setup... ...so I'm off, WARBIRD flying :mrgreen:

F**k, a HeisenBug (try to observe him, he vanishes...) I put the V4.8.3.4 back into Modules, but everything is ok with ShortAircraftNameOk (sigh). The only thing that changed since then is the A2A Core Accu-Sim DLL, I updated from Core Accu-Sim v.1.3.1 to Core Accu-Sim v.1.4 (just for the record) I attached my (zipped) FSUIPC.ini but I don't see much sense in investigating this further, as I said, a HeisenBug. When such a thing happens again, I know what info you need and will collect it. Until then we should close the case and I go on with V 4.8.3.4. Nevertheless, I switched the console window on for the second try, maybe something interesting for you... Console Started ... ********* FSUIPC4, Version 4.834 by Pete Dowson ********* User Name="XXXXXXXXXXXXX" User Addr="XXXXXXXXXXXX" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX on Windows 7 Module base=61000000 203 System time = 11/06/2012 20:43:57 203 FLT path = "C:\Users\XXXX\Documents\Flight Simulator X-Dateien\" 219 Trying to connect to SimConnect Acc/SP2 Oct07 ... 266 FS path = "G:\Flight Simulators\FSX\" 531 LogOptions=00000000 00000001 531 Wind smoothing fix is fully installed 531 G3D.DLL fix attempt installed ok 531 SimConnect_Open succeeded: waiting to check version okay 531 Trying to use SimConnect Acc/SP2 Oct07 6459 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 6459 Initialising SimConnect data requests now 6459 FSUIPC Menu entry added 6490 C:\Users\XXXXX\Documents\Flight Simulator X-Dateien\Cessna in Egelsbach.FLT 6490 G:\Flight Simulators\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR 17145 Weather Mode now = Custom 17145 c:\users\XXXX\documents\flight simulator x-dateien\_Fall City 1WA6.FLT 80107 System time = 11/06/2012 20:45:17, Simulator time = 08:48:56 (15:48Z) 80138 Aircraft="Cessna Skyhawk 172SP Paint1" 82041 Starting everything now ... 83305 Advanced Weather Interface Enabled 162663 G:\Flight Simulators\FSX\SimObjects\Airplanes\WoP3_P51D\p51d.AIR 163084 Aircraft="P-51D 'McSwine'" Error, no table returned 197030 Sim stopped: average frame rate for last 34 secs = 30.7 fps [/CODE] FSUIPC4.zip

Thanks for looking into it, tell me what information you need, I'll go for it this evening after work...

In FSUIPC.DLL V4.8.3.4 I found a problem with ShortAircraftNameOk My FSUIPC.ini normally has entries like these: [General] ... UseProfiles=Yes ShortAircraftNameOk=Yes .... [Profile.Single Prop Mustang AccuSim] 1=P-51D [/CODE] But whenever I started FSX I found that my planes lost contact to their profiles, like this Aircraft.cfg: [CODE] [fltsim.0] title=P-51D 'Kwitcherbitchin' ... [fltsim.1] title=P-51D 'Blondie' ... [/CODE] I could attach the currently loaded plane to its profile and it was added to the profile [CODE] [Profile.Single Prop Mustang AccuSim] 1=P-51D 2=P-51D 'Kwitcherbitchin' [/CODE] and the profile worked again for that plane... I took a close look and found that: [CODE]ShortAircraftNameOk=Yes[/CODE] was always reset to: [CODE]ShortAircraftNameOk=No[/CODE] when I started FSX or reloaded FSUIPC.ini. I rolled back to V 4.8.3.1 and the resetting was gone. Maybe you should have a look at it, until then I continue with V 4.8.3.1

...it works. :mrgreen: Somehow my [General] section got messed up :oops: I let FSUIPC generate a default FSUIPC.ini, assigned a single axis, this gave me the [JoyNames] section. [JoyNames] AutoAssignLetters =No --->from new ini 0=WingMan Formula Force GP 1=CH Throttle Quadrant USB 2=Saitek X52 Flight Controller 3=Saitek Pro Flight Rudder Pedals 4=Saitek Pro Gamer Command Unit ---> old ini 0 =WingMan Formula Force GP 1 =CH Throttle Quadrant USB 2 =Saitek X52 Flight Control System 3 =Saitek Pro Flight Rudder Pedals 4 =Saitek Pro Gamer Command Unit S =Saitek X52 Flight Control System W =Logitech WingMan Formula Force GP USB P =Saitek Pro Flight Rudder Pedals T =CH Throttle Quadrant USB C =Saitek Pro Gamer Command Unit As you can see the naming changed a bit, so I changed it to [JoyNames] AutoAssignLetters =No 0=WingMan Formula Force GP 1=CH Throttle Quadrant USB 2=Saitek X52 Flight Controller 3=Saitek Pro Flight Rudder Pedals 4=Saitek Pro Gamer Command Unit S =Saitek X52 Flight Controller W =WingMan Formula Force GP P =Saitek Pro Flight Rudder Pedals T =CH Throttle Quadrant USB C =Saitek Pro Gamer Command Unit and used this in my old ini file which I copied from my old Modules folder into the new Modules folder... ...and thats all, works as before :D Thanks Pete, for your help. Regards Christian

That assures me that I will get it right in the end. No I didn't, but I copied my full FSX folder from it's original disk to a new one. So I inherited the old user-rights from XP. I'll check the [general] section, maybe it's gone down the drain. I use the mapping facility already, and for my global settings, it's still working. No I won't :mrgreen: . I keep backups of it whenever I make changes to it and I still have the original untampered disk... Thats what I expected, so I can concentrate on my fooling with the INI file. In fact, I did some testing with the Win7RC, and there FSUIPC worked flawlessly. When I'm done, I will post it here. Thanks for your clarifications and help.

I'm in the process of migrating FSX to Win7 and FSUIPC is part of it. Now I found two things not working: - the menu entries for loading flights below the FSUIPC entry in Addon menu - the profile sections for a group of planes (I have several of them, like SingleProp, TwinProp, TwinTurboProp etc.) under WinXP this FUIPC.ini file worked just fine. I'm only starting to analyse the problem and most probably I made some mistake, but maybe you have an idear what could be wrong to give me a shortcut. Migration was done like this: - installed clean FSX/Acc and acivated it - renamed FSX directory, copied my old installation to the original name ( :!: when you do this it's possible that you have to activate write-permission for your FSX directory, I tried to edit an aircraft.ini file only to see that I couldn't save it until I set write-permission) - copied all the config-directories to their new place (a pain :( ) - started FSX, worked fine, but FSUIPC was deactivated - reinstalled FSUIPC, activated it, copied newest beta to Modules folder - Checked controller nameing ( :!: this can be different between WinXP and Win7 ) - deleted all axis and button settings for all controllers in FSX itself (only keeping POV for view) So in the end: - global buttons worked just fine (I have long list of it, with all bells and whistles, like conditions...) - global axis setting worked fine - no menu entries for loading flights - all profiles are dead. (I checked the log, the loaded plane is shown, the spelling is correct as in the profile, yet the profile is not active) This evening I will go on and install FSUIPC again from scratch, then building a test profile by the book

Your welcome Paul, but remember, no reverse when you have a dead engine, because this goes always to all four virtual levers, kicked me off the runway like nothing :mrgreen:

Hi Pete, I took a look at the numbering problem. I renamed FSUIPC4.ini and let it be regenerated from scratch. Then I put in some axis and buttons and keypresses. These are (numbered) sections that where generated: [JoyNames] AutoAssignLetters=No 0=Saitek X52 Flight Controller 1=Saitek Pro Gamer Command Unit 2=Saitek Pro Flight Rudder Pedals 3=CH Throttle Quadrant USB [Buttons] ButtonRepeat=20,10 1=P3,11,C66224,0 2=P3,10,C66531,0 [LuaFiles] 1=display vals 2=liar 3=reverse [Axes] 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=3U,256,D,4,0,0,0 [Keys] 1=220,8,66224,0 2=123,8,66531,0 So it´s a mix of numbering starting from zero and others from one. Don´t get me wrong, this is no problem for me, but I think this made me assume that zero would be ok in the [Keys] and [buttons] section as well. BTW: how do you handle comments at the end of a line like 56 =P0,9,C66080,0 ;Gear 57 =P0,8,C66079,0 58 =P0,11,C65758,0 ;Flaps 59 =P0,10,C65759,0 60 =P0,13,C66243,0 ;Cowl Flaps 61 =P0,12,C66244,0 ;Comment this ? I happily used them (and it did no harm) but today I tried it with a INI-value at work and found, looking at the string that was read in with the debugger, that such a line is completely read, including the ";"separated part. If a line starts with ";" it´s of course completely ignored when reading INI-values. Regards, Christian

As I said in the other thread, the 0=... lines are not from you, I put them in manually (assuming zero would be the starting number).

Yes. didn't I say that in the documentation? To be honest, I can´t say, but it is not really necessary, it's global. I misunderstood it´s meaning. Silly me :oops: Yes it´s perfectly clear now... ...and easy of course. I´m thinking overcomplicated some times. 0=.... line is easy to explain: Yes I edit the file manually and when I´m handling INI-files in my own projects I´m used to count from zero on (it´s bits and bytes of PLC communication and within my files it´s much easier to do "machine-centric counting", on the user interface it´s all nice and friendly counting from one). Thanks, this will help me a lot. Regards, Christian

Ahhh, I understand. The ShortaircraftNameOk=Substring facility is still in place even for the profiles :oops: So THIS: [Profile.B377 Stratocruiser] 0 =Boeing 377 Pregnant Guppy, Paint 1 1 =Boeing Stratocruiser, PAN AM 2 =Boeing Stratocruiser, BOAC 3 =Boeing Stratocruiser, AOA 4 =Boeing Stratocruiser, NWA 5 =Boeing Stratocruiser, QEA 6 =Boeing Stratocruiser, Transocean 7 =Boeing Stratocruiser, UNITED AIR LINES 8 =Boeing Stratocruiser, TWA 9 =Boeing Stratocruiser, USAF 10 =Boeing Stratocruiser, USAF1 11 =Boeing Stratocruiser, MATS 12 =Boeing Stratocruiser, CATHAY 13 =Boeing Stratocruiser, USCG 14 =Boeing Stratocruiser, PAN AM 1 15 =Boeing Stratocruiser, Early BOAC will be equivalent to [Profile.B377 Stratocruiser] ShortaircraftNameOk =Boeing Stratocruiser 0 =Boeing 377 Pregnant Guppy, Paint 1 this ? Anyway, my TwinProp profile looks like this, so some Aircraft.cfg scanning wouldn't be a total waste of time :) [Profile.Twin Prop] 0 =Douglas DC-3A UAL 1 =Douglas DC-3 Lufthansa D-CADE 2 =Douglas DC-3 Bavaria Airways D-CADE 3 =Douglas C-47 RAF KG374 4 =Douglas C-47 Operation Vittels 5 =Douglas C-47 6 =Douglas C-47 Sugarpuss 7 =Douglas C-47 RAF KG444 8 =Douglas C-47_BBMF 9 =MAAM-SIM Douglas C-47A Delivery 10 =MAAM-SIM Douglas C-47A RAAF A65-34 11 =Douglas C-47A 224046 12 =MAAM-SIM Douglas C-47B CNAC 13 =MAAM-SIM Douglas C-47B 'Hump' 14 =Douglas DC-3 BEA 15 =MAAM-SIM Douglas DC-3 BPB 16 =R4D NATS BM 17 =R4D NATS CC 18 =Douglas XC-47C 19 =Douglas DC-3 20 =Douglas DC-3 Paint1 21 =Douglas DC-3 Paint2 22 =Douglas DC-3 Paint3 23 =Douglas DC-3 Paint4 24 =Douglas DC-3 Paint5 25 =Douglas DC-3 Warbirds 26 =Douglas DC-3 N.A.C 27 =Douglas DC-3 N.A.C - PIWAKAWAKA 28 =Douglas DC-3 AEROCOR 29 =Douglas DC-3 SPANZ 30 =Douglas DC-3 N.A.C Freighter 31 =Douglas DC-3 LC47 - Metal 32 =Douglas DC-3 LC47 - 17221 33 =Douglas DC-3 LC47 - 0008 34 =Douglas DC-3 LC47 - TA 05 35 =Douglas DC-3 WB 36 =Douglas DC-3 Viewmaster - Metal 37 =Douglas DC-3 Passenger - Metal 38 =Douglas DC-3 Freighter - Metal 39 =Douglas DC-3 N.A.C Fieldair 40 =Douglas DC-3 United 41 =Douglas DC-3 Passenger - Metal SDT 42 =Douglas DC-3 Paint Alaska ANG 43 =Douglas DC-3 Lufthansa (frühes Farbschema) 44 =Douglas DC-3 Lufthansa (spätes Farbschema) 45 =Beech Baron 58 Paint1 46 =Beech Baron 58 Paint2 47 =Beech Baron 58 Paint3 48 =Beech Baron 58 w G1000 49 =Beech Baron 58 50 =Heinkel He219 A-0/R2 51 =Heinkel He219 A-0/R6 52 =Heinkel He219 A-2/R1 TH 53 =Heinkel He219 A-2/R1 HK 54 =Heinkel He219 A-5 CZE 55 =Heinkel He219 A-7/R2 CL RAF In any case I'll try to concentrate on the parts which are not dealt with in FSUIPC itself and there on the boring things like copying, rearranging, building insane lists of repaints :mrgreen: It's just for convenience and fun, but I will listen carefully for your remarks, because in the end it should be usefull. Regards, Christian

Hi Gypsy Baron, just in case you haven´t done it already, this is my B-377 section of FSUIPC4.ini: [Profile.B377 Stratocruiser] 0 =Boeing 377 Pregnant Guppy, Paint 1 1 =Boeing Stratocruiser, PAN AM 2 =Boeing Stratocruiser, BOAC 3 =Boeing Stratocruiser, AOA 4 =Boeing Stratocruiser, NWA 5 =Boeing Stratocruiser, QEA 6 =Boeing Stratocruiser, Transocean 7 =Boeing Stratocruiser, UNITED AIR LINES 8 =Boeing Stratocruiser, TWA 9 =Boeing Stratocruiser, USAF 10 =Boeing Stratocruiser, USAF1 11 =Boeing Stratocruiser, MATS 12 =Boeing Stratocruiser, CATHAY 13 =Boeing Stratocruiser, USCG 14 =Boeing Stratocruiser, PAN AM 1 15 =Boeing Stratocruiser, Early BOAC [Axes.B377 Stratocruiser] 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=0Z,256,D,4,0,0,0 3=0U,256,D,21,0,0,0 4=0V,256,D,28,0,0,0 5=0S,256,D,22,0,0,0 6=0P,0,F,66416,0,0,0 7=2X,256,D,7,0,0,0 8=2Y,256,D,8,0,0,0 9=2R,256,D,3,0,0,0 10=3X,256,D,5,0,0,0 11=3Y,256,D,6,0,0,0 12=3Z,256,F,66420,0,0,0 13=3R,256,F,66423,0,0,0 14=3U,256,F,66429,0,0,0 15=3V,256,F,66426,0,0,0 [JoystickCalibration.B377 Stratocruiser] ExcludeThrottleSet =Yes ExcludeMixtureSet =Yes ExcludePropPitchSet =Yes SepRevsJetsOnly =No ;ApplyHeloTrim =No ApplyHeloTrim =Yes FlapsSetControl =0 FlapDetents =No ReverserControl =66292 Reverser1Control =66422 Reverser2Control =66425 Reverser3Control =66428 Reverser4Control =66431 MaxThrottleForReverser =256 AileronTrimControl =66731 RudderTrimControl =66732 CowlFlaps1Control =66162 CowlFlaps2Control =66163 CowlFlaps3Control =66164 CowlFlaps4Control =66165 SteeringTillerControl =0 MaxSteerSpeed =60 Aileron =-16380,-512,512,16380/8 Elevator =-16380,-512,512,16380/8 ElevatorTrim =-16383,-512,512,15602/24 SlopeElevatorTrim =5 Rudder =-16319,-512,512,16383/8 SlopeRudder =2 Rudder Trim =-16384,-512,512,16383/8 SlopeRudder Trim =5 LeftBrake =-15000,16383/24 SlopeLeftBrake =5 RightBrake =-15000,16383/24 SlopeRightBrake =5 PropPitch=-14433,16383/8 Mixture=-14432,16383/8 Throttle=-12000,16383/8 [Buttons.B377 Stratocruiser] 0 =P3,16,K113,8 1 =P3,16,K113,8 2 =P3,16,K113,8 3 =P3,16,K113,8 4 =P3,16,K113,8 5 =P3,16,K113,8 6 =P3,16,K113,8 7 =P3,16,K113,8 8 =P3,16,K113,8 9 =P3,16,K113,8 10 =P3,16,K113,8 11 =P3,16,K113,8 12 =P3,16,K113,8 13 =P3,16,K113,8 14 =P3,16,K113,8 15 =P3,16,K113,8 16 =P3,16,K113,8 17 =P3,16,K113,8 18 =P3,16,K113,8 19 =P3,16,K113,8 20 =U3,16,K114,8 21 =U3,16,K114,8 22 =U3,16,K114,8 23 =U3,16,K114,8 24 =U3,16,K114,8 25 =U3,16,K114,8 26 =U3,16,K114,8 27 =U3,16,K114,8 28 =U3,16,K114,8 29 =U3,16,K114,8 30 =U3,16,K114,8 31 =U3,16,K114,8 32 =U3,16,K114,8 33 =U3,16,K114,8 34 =U3,16,K114,8 35 =U3,16,K114,8 36 =U3,16,K114,8 37 =U3,16,K114,8 38 =P3,18,K113,8 39 =P3,18,K113,8 50 =P3,18,K113,8 41 =P3,18,K113,8 42 =P3,18,K113,8 43 =P3,18,K113,8 44 =P3,18,K113,8 45 =P3,18,K113,8 46 =P3,18,K113,8 47 =P3,18,K113,8 48 =P3,18,K113,8 49 =P3,18,K113,8 50 =P3,18,K113,8 51 =P3,18,K113,8 52 =P3,18,K113,8 53 =P3,18,K113,8 54 =P3,18,K113,8 55 =P3,18,K113,8 56 =P3,18,K113,8 57 =P3,18,K113,8 58 =U3,18,K114,8 59 =U3,18,K114,8 60 =U3,18,K114,8 61 =U3,18,K114,8 62 =U3,18,K114,8 63 =U3,18,K114,8 64 =U3,18,K114,8 65 =U3,18,K114,8 66 =U3,18,K114,8 67 =U3,18,K114,8 68 =U3,18,K114,8 69 =U3,18,K114,8 70 =U3,18,K114,8 71 =U3,18,K114,8 72 =U3,18,K114,8 73 =U3,18,K114,8 74 =U3,18,K114,8 75 =U3,18,K114,8 76 =U3,18,K114,8 77 =U3,18,K114,8 78 =P3,20,K113,8 79 =P3,20,K113,8 80 =P3,20,K113,8 81 =P3,20,K113,8 82 =P3,20,K113,8 83 =P3,20,K113,8 84 =P3,20,K113,8 85 =P3,20,K113,8 86 =P3,20,K113,8 87 =P3,20,K113,8 88 =P3,20,K113,8 89 =P3,20,K113,8 90 =P3,20,K113,8 91 =P3,20,K113,8 92 =P3,20,K113,8 93 =P3,20,K113,8 94 =P3,20,K113,8 95 =P3,20,K113,8 96 =P3,20,K113,8 97 =P3,20,K113,8 98 =U3,20,K114,8 99 =U3,20,K114,8 100 =U3,20,K114,8 101 =U3,20,K114,8 102 =U3,20,K114,8 103 =U3,20,K114,8 104 =U3,20,K114,8 105 =U3,20,K114,8 106 =U3,20,K114,8 107 =U3,20,K114,8 108 =U3,20,K114,8 109 =U3,20,K114,8 110 =U3,20,K114,8 111 =U3,20,K114,8 112 =U3,20,K114,8 113 =U3,20,K114,8 114 =U3,20,K114,8 115 =U3,20,K114,8 116 =U3,20,K114,8 117 =U3,20,K114,8 118 =P3,22,K113,8 119 =P3,22,K113,8 120 =P3,22,K113,8 121 =P3,22,K113,8 122 =P3,22,K113,8 123 =P3,22,K113,8 124 =P3,22,K113,8 125 =P3,22,K113,8 126 =P3,22,K113,8 127 =P3,22,K113,8 128 =P3,22,K113,8 129 =P3,22,K113,8 130 =P3,22,K113,8 131 =P3,22,K113,8 132 =P3,22,K113,8 133 =P3,22,K113,8 134 =P3,22,K113,8 135 =P3,22,K113,8 136 =P3,22,K113,8 137 =P3,22,K113,8 138 =U3,22,K114,8 139 =U3,22,K114,8 140 =U3,22,K114,8 141 =U3,22,K114,8 142 =U3,22,K114,8 143 =U3,22,K114,8 144 =U3,22,K114,8 145 =U3,22,K114,8 146 =U3,22,K114,8 147 =U3,22,K114,8 148 =U3,22,K114,8 149 =U3,22,K114,8 150 =U3,22,K114,8 151 =U3,22,K114,8 152 =U3,22,K114,8 153 =U3,22,K114,8 154 =U3,22,K114,8 155 =U3,22,K114,8 156 =U3,22,K114,8 If you have a look at the [buttons.B377 Stratocruiser] section, you can see four sets of 0 =P3,16,K113,8 ..... 19 =P3,16,K113,8 20 =U3,16,K114,8 ..... 37 =U3,16,K114,8 joystick #3 is my "CH Throttle Quadrant USB" and each axis has a lower detend with a corresponding button, which is clicked when the detend is reached. So each axis produces a series of F2 key presses when it is in its lower detend (which moves the virtual levers 25% of the reverse way), and produces a series of F3 key presses when the detend is left. So with pulling one of the CH levers to reverse I get 25% reverse, two get me 50%, all get me 100%. Regards, Christian