Jump to content
The simFlight Network Forums

hm

Members
  • Posts

    95
  • Joined

  • Last visited

Everything posted by hm

  1. Hello Pete, Well, the errors in the instructions were typo's and not actual copies from thr FCUIPC.ini. I found a parameter in the SD YAK-40 inifile "Flaps step 0.2". So I thought 100 steps are needed to get 20, and I programmed the Set Flaps with "100". Thre was no movement. So I changed the value in the YAK-40 inifile to "Flaps step 20.0" and bingo! I can now use the Flaps Inc instruction to go to 20°. The final instruction sequence is now : 21=CP(F+0,10)(F-0,31)0,4,C65758,0 ; Flaps incr 22=CU(F+0,10)(F-0,31)0,4,C1003,31 ; Set flag 31 23=W0BE0>8192 CP(F+0,10)(F+0,31)0,4,C65603,0 ; Flap at 20, do "Full Flaps" 24=CP(F+0,10)0,5,C65595,0 ; Flaps up 25=CP(F+0,10)0,5,C1004,31 ; Reset flag 31 I can't ask Mr. Suprunov for some explanaition. He was for years a pilot of a YAK-40 and had an A-rating for Airbus. He died this year in Moscow in the night of 25 april. Why the "Set Flap" to a value is not working will stay a mistery... Hugo Hugo
  2. Hi Pete, Indeed the flaps haven't detentes, like on the real one the flaps can by set to any angle. I changed the "Key buttons" to controlls, which are working well. The rows below are working but with the "old annoyance". You wonder why the value must be 9635: it is because at that moment the "technician or KGB-man?" says "Flaps set 20", he doesn't at lower values. 21=W0BE0<9365 CR(F+0,10)(F-0,31)0,4,C65758,0 ; Flaps incr 22=W0BE0>9364 CU(F+0,10)(F-0,31)0,4,C1003,31 ; set flag 31 at 20° Flaps 23=CP(F+0,10)(F+0,31)0,4,C65603,0 ; Flap at 20°, do Full Flaps 24=CP(F+0,10)0,5,C65595,0 ; Flaps UP 25=CP(F+0,10)0,5,C1004,31 ; Reset flag 31 Because I found this not working on the Suprunov YAK-40 21=CP(F+0,10)0,4,C65698,9365 ; set flaps 20? is not working (with this airplane?) 22=W0BE0>9364 CP(F+0,10)(F-0,31)0,4,C1003,31 ; set flag 31 at 20° Flaps, would work when the previous row would work. 23=CP(F+0,10)(F+0,31)0,4,C65698,16383 ; does not "Full Flaps" but "Flaps Up" (with this airplane?) The last row does the same as: 3=CP(F+0,10)(F+0,31)0,4,C65698,0 ; which works... Thank your for your quick answer so early after returning from vacation... Hugo
  3. Hello, One of my favoriths is still the SD YAK-40, but I have a small problem with it, it has continuous setting of flaps, but only 0°, 20° and full flaps are used, so I made some button programming : 21=W0BE0<9365 CR(F+0,10)(F-0,31)0,4,K118,8 ; F7 (Flaps down) 22=W0BE0>9364 CU(F+0,10)(F-0,31)0,4,C1003,31 ; set flag 31 at 20° Flaps 23=W0BE0>9364 CP(F+0,10)(F+0,31)0,4,K119,8 ; Flap at 20°, do F8 (Full Flaps) 24=CP(F+0,10)0,5,K116,8 ; F5 (Flaps up) 25=CP(F+0,10)0,5,C1004,31 ; Reset flag 31 As long as the flaps are < 20° and I push button 4 the flaps are going to 20°. If I release the button 4 at 20° the flag 31 is set. Next when I push button 4 again, the flaps are going to full. When I push button 5, the flaps are going up and the flag is reset. This works nicely but with one annoyance: I have to push button 4 until they come at 20° and they are going slooow. Does somebody know a trick so I have only to "pulse" the button 4 ? Thanks in advance, Hugo
  4. Hi Pete, That's quick! I had no problems with it in FSUIPC, in FSX however... Well my first message was only showing a part of the programming, hence these points in the rows after the commands I mentioned. But solved now...well I seems to attract the weird things, do you still remember that weird thing with the tab and alt flags for button programming: "to late to change" ... Regards and al the best for 2012, Hugo
  5. Hi, No both sections are the same for the general [buttons] section : FSUIPC : [buttons] ButtonRepeat=20,10 PollInterval=50 InitialButton=0,7 0=CU(-0,7)0,6,C1003,10 1=CU(-0,6)0,7,C1003,10 2=CP(-0,7)0,6,C1004,10 3=CP(-0,7)0,6,C1003,11 4=CU(F+0,11)0,6,C1004,11 5=CP(-0,6)0,7,C1004,10 6=CP(-0,6)0,7,C1003,12 7=CU(F+0,12)0,7,C1004,12 8=CP(F+0,11)0,7,C1004,11 9=CP(+0,6)0,7,C1003,13 10=CU(F+0,13)0,7,C1004,13 11=CP(F+0,12)0,6,C1004,12 12=CP(+0,7)0,6,C1003,13 13=CU(F+0,13)0,6,C1004,13 14=W0BE8=0 CP(F+0,10)0,0,K32,8 15=W0BE8 CR(F+0,10)0,0,C65588,0 16=CP(F+0,10)0,1,C65570,0 17=CR(F+0,10)0,2,C65607,0 18=CR(F+0,10)0,3,C65615,0 19=CP(F+0,10)0,4,C65758,0 20=CP(F+0,10)0,5,C65759,0 21=CP(F+0,11)0,0,C65752,1 22=CP(F+0,11)0,1,C65751,0 23=CR(F+0,11)0,2,C65771,0 24=CR(F+0,11)0,3,C65769,0 25=CP(F+0,11)0,5,C65589,0 26=CP(F+0,12)0,1,C65858,0 27=CR(F+0,12)0,2,C65777,0 28=CR(F+0,12)0,3,C65775,0 29=CP(F+0,12)0,4,K83,8 30=CP(F+0,12)0,5,K83,9 31=CP(F+0,13)0,0,C1005,31 32=CP(F+0,13)(F+0,31)0,0,C66224,0 33=CP(F+0,13)(F-0,31)0,0,K112,11 34=CP(F+0,13)0,1,C66293,0 35=CP(F+0,13)0,2,C66244,0 36=CP(F+0,13)0,3,C66243,0 FSUIPC4 : [buttons] ButtonRepeat=20,10 PollInterval=50 InitialButton=0,7 0=CU(-0,7)0,6,C1003,10 1=CU(-0,6)0,7,C1003,10 2=CP(-0,7)0,6,C1004,10 3=CP(-0,7)0,6,C1003,11 4=CU(F+0,11)0,6,C1004,11 5=CP(-0,6)0,7,C1004,10 6=CP(-0,6)0,7,C1003,12 7=CU(F+0,12)0,7,C1004,12 8=CP(F+0,11)0,7,C1004,11 9=CP(+0,6)0,7,C1003,13 10=CU(F+0,13)0,7,C1004,13 11=CP(F+0,12)0,6,C1004,12 12=CP(+0,7)0,6,C1003,13 13=CU(F+0,13)0,6,C1004,13 14=W0BE8=0 CP(F+0,10)0,0,K32,8 15=W0BE8 CR(F+0,10)0,0,C65588,0 16=CP(F+0,10)0,1,C65570,0 17=CR(F+0,10)0,2,C65607,0 18=CR(F+0,10)0,3,C65615,0 19=CP(F+0,10)0,4,C65758,0 20=CP(F+0,10)0,5,C65759,0 21=CP(F+0,11)0,0,C65752,1 22=CP(F+0,11)0,1,C65751,0 23=CR(F+0,11)0,2,C65771,0 24=CR(F+0,11)0,3,C65769,0 25=CP(F+0,11)0,5,C65589,0 26=CP(F+0,12)0,1,C65858,0 27=CR(F+0,12)0,2,C65777,0 28=CR(F+0,12)0,3,C65775,0 29=CP(F+0,12)0,4,K83,8 30=CP(F+0,12)0,5,K83,9 31=CP(F+0,13)0,0,C1005,31 32=CP(F+0,13)(F+0,31)0,0,C66224,0 33=CP(F+0,13)(F-0,31)0,0,K112,11 34=CP(F+0,13)0,1,C66293,0 35=CP(F+0,13)0,2,C66244,0 36=CP(F+0,13)0,3,C66243,0
  6. Hi Pete, I made the logs like you requested. I started a flight and immediatly halted, nothing touched. Ok, here are the logs : ********* FSUIPC, Version 3.998q by Pete Dowson ********* Running on Windows Version 5.1 Build 2600 Service Pack 2 Verifying Certificate for "E:\Flight Simulator 9\MODULES\FSUIPC.dll" now ... SUCCESS! Signature verifies okay! Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="Hugo Marien" User Addr="h.marien@pandora.be" FSUIPC Key is provided WIDEFS not user registered, or expired Module base=61000000 WeatherReadInterval=4 LogOptions=00000001 DebugStatus=15 2402 System time = 09/01/2012 16:50:39 2402 E:\Flight Simulator 9\ 2402 System time = 09/01/2012 16:50:39, FS2004 time = 12:00:00 (00:00Z) 11528 FLIGHTS\OTHER\FLTSIM.flt 11575 AIRCRAFT\c172\Cessna172SP.air 11747 Aircraft="Cessna Skyhawk 172SP" 31699 C:\Users\Hugo\Documents\Flight Simulator Files\Belgium Keiheuvel Saab.flt 31855 AIRCRAFT\SibWings SAAB 91B Safir\safir.air 31949 Aircraft="91B Safir ZU-DES" 32323 Clear All Weather requested: external weather discarded 33524 AES Link established 42853 Advanced Weather Interface Enabled 61277 InitialButton Press: Button 0,7 61277 Button changed: bRef=0, Joy=0, Btn=7, Pressed 61277 [buttons] 5=CP(-0,6)0,7,C1004,10 61277 .... Condition (-0,6) = TRUE 61277 FSUIPC Control Action: Ctrl=1004, Param=10 61277 [buttons] 6=CP(-0,6)0,7,C1003,12 61277 .... Condition (-0,6) = TRUE 61277 FSUIPC Control Action: Ctrl=1003, Param=12 61277 [buttons] 8=CP(F+0,11)0,7,C1004,11 61277 .... Condition (F+0,11) = FALSE 61277 [buttons] 9=CP(+0,6)0,7,C1003,13 61277 .... Condition (+0,6) = FALSE 61511 Traffic File #103 = "scenery\world\scenery\traffic_000_woa_transavia_wi08" 61558 Button changed: bRef=0, Joy=0, Btn=7, Released 61558 [buttons] 1=CU(-0,6)0,7,C1003,10 61558 .... Condition (-0,6) = TRUE 61558 FSUIPC Control Action: Ctrl=1003, Param=10 61558 [buttons] 7=CU(F+0,12)0,7,C1004,12 61558 .... Condition (F+0,12) = TRUE 61558 FSUIPC Control Action: Ctrl=1004, Param=12 61558 [buttons] 10=CU(F+0,13)0,7,C1004,13 61558 .... Condition (F+0,13) = FALSE 61558 Traffic File #48 = "scenery\world\scenery\traffic_000_woa_el al israel airlines_wi08" 61636 Traffic File #14 = "scenery\world\scenery\traffic_000_uga_glex_fs9" 61683 Traffic File #36 = "scenery\world\scenery\traffic_000_woa_brussels airlines_su08" 61761 Traffic File #124 = "scenery\world\scenery\traffic_123_woa_iberia_wi07" 61932 Traffic File #137 = "scenery\world\scenery\traffic_172_woa_lufthansa (regional partners)_su07" 62041 InitialButton Release: Button 0,7 62119 Traffic File #105 = "scenery\world\scenery\traffic_000_woa_tui airlines belgium_su08" 62182 Traffic File #167 = "scenery\world\scenery\traffic_30_woa_ryanair_wi07" 62213 Traffic File #123 = "scenery\world\scenery\traffic_122_woa_vlm airlines_su07" 62338 Traffic File #146 = "scenery\world\scenery\traffic_194_woa_ga beechcraft king air b200_wi07" 62463 Traffic File #169 = "scenery\world\scenery\traffic_42_woa_lufthansa_wi07_fs9" 62556 Traffic File #134 = "scenery\world\scenery\traffic_155_woa_scandinavian airlines_su07" 62665 Traffic File #163 = "scenery\world\scenery\traffic_253_woa_tnt airways_su08" 62837 Traffic File #135 = "scenery\world\scenery\traffic_167_woa_bmibaby_su07" 62962 Traffic File #172 = "scenery\world\scenery\traffic_58_woa_british airways_wi07" 63227 Traffic File #223 = "scenery\world\scenery\traffic_lfqj" 63633 Traffic File #165 = "scenery\world\scenery\traffic_26_woa_american airlines_su06" 63664 Traffic File #171 = "scenery\world\scenery\traffic_54_woa_british mediterranean airways_wi07" 63835 Traffic File #175 = "scenery\world\scenery\traffic_70_woa_klm royal dutch airlines_su07" 64303 Traffic File #39 = "scenery\world\scenery\traffic_000_woa_corendon airlines_su08" 64397 Traffic File #84 = "scenery\world\scenery\traffic_000_woa_pegasus_su08" 65099 Traffic File #131 = "scenery\world\scenery\traffic_145_woa_thomas cook airline [belgium]_su07" 65505 Traffic File #143 = "scenery\world\scenery\traffic_186_woa_cathay pacific airways (cargo)_wi07" 65598 Traffic File #148 = "scenery\world\scenery\traffic_196_woa_turkish airlines_su08" 65707 Traffic File #160 = "scenery\world\scenery\traffic_233_woa_csa czech airlines_wi07" 65926 KEYDOWN: VK=18, Waiting=0, Repeat=N, Shifts=4 65926 .. Key not programmed -- passed on to FS 66035 KEYUP: VK=18, Waiting=0 70138 System time = 09/01/2012 16:51:47, FS2004 time = 15:08:33 (13:08Z) 70138 *** FSUIPC log file being closed Memory managed: 90 Allocs, 621 Freed ********* FSUIPC Log file closed *********** ********* FSUIPC4, Version 4.755 by Pete Dowson ********* User Name="Hugo Marien" User Addr="h.marien@pandora.be" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX on Windows 7 Module base=61000000 219 System time = 09/01/2012 16:59:23 219 FLT path = "C:\Users\Hugo\Documents\Flight Simulator X Files\" 234 Trying to connect to SimConnect Acc/SP2 Oct07 ... 234 FS path = "E:\Flight Simulator X\" 468 LogOptions=40000000 00000001 468 Wind smoothing fix is fully installed 468 G3D.DLL fix attempt installed ok 468 SimConnect_Open succeeded: waiting to check version okay 468 Trying to use SimConnect Acc/SP2 Oct07 1591 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 1591 Initialising SimConnect data requests now 1591 FSUIPC Menu entry added 1623 E:\Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT 1623 E:\Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 51075 Weather Mode now = Theme 51075 e:\flight simulator x\missions\Tutorials\Tutorial01\Tutorial01.FLT 51964 System time = 09/01/2012 17:00:14, Simulator time = 11:30:27 (18:30Z) 51980 Aircraft="Aircreation582SL Blue" 91588 E:\Flight Simulator X\SimObjects\Airplanes\Beech_King_Air_350\Beech_King_Air_350.AIR 91588 e:\flight simulator x\missions\Pilot for Hire\ExecutiveTour\KEDW_Tour.PLN 91588 Weather Mode now = Custom 91588 e:\flight simulator x\missions\Pilot for Hire\ExecutiveTour\Executive_Tour.FLT 91869 Aircraft="Beech King Air 350 Paint3" 122258 Starting everything now ... 122258 AES Link established 123491 Advanced Weather Interface Enabled 138716 System time = 09/01/2012 17:01:41, Simulator time = 07:04:48 (14:04Z) 138716 *** FSUIPC log file being closed Average frame rate for running time of 10 secs = 29.5 fps G3D fix: Passes 12297, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 5 Allocs, 5 Freed ********* FSUIPC Log file closed ***********
  7. Hi, Ik have made this kind of programming for FSUIPC4 in FSX: [buttons] ButtonRepeat=20,10 InitialButton=0,7 0=CU(-0,7)0,6,C1003,10 1=CU(-0,6)0,7,C1003,10 2=CP(-0,7)0,6,C1004,10 . . I expect that flag 10 would be set, when I don't touch a joystick key as it does in FSUIPC for FS9. But it doesn't. Is something changed between FSUIPC and FSUIPC4 for button programming ? Hm
  8. Hi, I have looked in the list to find an offset for "plane is pushback" but I don't find it. Does it exist? Edit: after 5 times going trough the list, I found it : 031F0 . Must change my glasses :rolleyes: Thanks in advance, Hugo
  9. Hello Pete, With the latest version FSUIPC 3.86.5, all seems all right again, for me in any case. Hugo
  10. Hallo Pete, Something is broken in the latest version. I have a lot of trouble with the button programming: the buttons are acting weird but there is no specific error, sometimes they are giving weird commands (change view instead of increment flaps etc.) ..., or are locked..., or only respond after multiple tries..., sometimes I can't to enter FS commands with the keyboard anymore..., sometimes joystick movements are not giving action any longer..., sometimes FS9 freezes. Weird things are going on. Returning back to 3.84.9 has solved my problems. Regards, Hugo
  11. Hi, I have going a few times trough the list, but I don't find it. Exists an offset for the view status (tower, spot, 2D cockpit, VC) ? Thanks in advance Hugo
  12. Hi, Some time ago I started some documentation about button programming with FSUIPC. The article however got never finished (my English is too bad. However, Pete was so kind to make some corrections and he published some tricks I programmed in his documentation). I have uploaded the "unfinished" Word document to my site from where you can download it. The link: http://users.telenet.be/desi-iii/ButtonProgramming.doc Hope the doc helps you. Regards, Hugo
  13. Hello Pete, Normally I made no long flights but now I am "active" in Australia and I also suffer from CDT's in long flights (+ 1 hour , but sometimes it was less). Like the guys on these thread, I reinstalled 3.70 and the CDT's are gone (at least in the flight I made today. + 3hours) If I can help you with test something, let me know. Regards, Hugo
  14. Hi Pete, I also had problems with 3.714 (Active Sky wouldn't connect to Fs2004) but 3.715 has solved the issue. Simply to let you know. Regards, Hugo
  15. Hi, What Pete wants to say is that FSUIPC sees only the change of the button state and remembers this during the whole button scan. So in your case and I suppose now that the rotary switch is on joystick 3, button 1. 1=P3,1,your command,param If you turn the rotary FSUIPC will see the change from OFF to ON and execute the command. In the next scans, your rotary will be ON but there is no change of state, so there is no execution of the command. This change is remembered during a whole scan, example: 1=P3,1,command 1,param 2=P3,1,C1006,10 3=CP(F+10)3,1,command2,param 4=CP(F-10)3,1,command3,param I am using the SAME change of state of the SAME button for the execution of these 4 rows, the OFF-ON state transition of button 1 of joy stick 3 does: 1 executes command 1 2 toggles a dummy switch (OFF->ON or ON->OFF) 3 if the internal switch is set, do command 2 4 if the internal switch is not set, do command 3 Thus, every time the button 1 of joystick 3 goes from OFF to ON, command 1 is executed, but command 2 is only executed the 1st, 3th, 5th... time, command 3 only the 2nd, 4th, 6thtime. It totally disregards if the switch is ON or OFF, it only reacts when the switch is going from OFF to ON, except for the status of the internal dummy switches , here (+F10) or (-F10) Regards, Hugo
  16. Hi Pete, Only to say that a "." (point) is giving a bad link here: "Announcement: Other Downloads and Updates [7th November 2006]" Regards, Hugo P.S. Thanks for still supporting the FS9 FSUIPC version! (FSX does not run "well" on my computer)
  17. :oops: shame on me, Thunderbird is not the browser but the email client of Mozilla. The correct text (except for my poor English) must be: I don't think the "Reload" button with Firefox helps (like I experienced, it only refreshes the cached content of the the html page, but if a link on that page points to a file with a name that is already cached, the file itself is not reloaded if you are clicking the link). For Firefox you need to empty the cache as follows : Tools -> Options -> Privacy -> Cache and select the button "Clear cache now". I had made the same mistake twice in the text and did only one replacement :roll: . Hugo
  18. Hi All, I don't think the "Reload" button with Firefox helps (like I experienced, it only refreshes the cached content of the the html page, but if a link on that page points to a file with a name that is already cached, the file itself is not reloaded if you are clicking the link). For Thunderbird you need to empty the cache as follows : Tools -> Options -> Privacy -> Cache and select the button "Clear cache now". Regards, Hugo
  19. Hi Pete, Sorry, you were right. IMHO a better place for the "cache warning" is the beginning of the page because it doesn't come in view if you simply want to download a new version of FSUIPC. Regards, Hugo
  20. Hi Pete, I have downloaded version 3.60 from http://www.schiratti.com. Is this really version 3.60? The FSUIPC.DLL is still dated jan 01 2006. Regards, Hugo
  21. Fs-Force has a much better support for a Force feedback joystick as the standard FS2004 support and it displays the trim setting for a few seconds with "running numbers" if you are manipulating it in a small black popup window in the right lower corner of the screen :) Regards, Hugo
  22. Hi, I think you are referring to FS Force (purple text on black field ?). Regards, Hugo
  23. What seems odd are the big fonts used in the FSUIPC window. Are you missing some fonts ? Regards, Hugo
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.