Jump to content
The simFlight Network Forums

mtjoeng

Members
  • Posts

    223
  • Joined

  • Last visited

Everything posted by mtjoeng

  1. What I can remember when keeping up with the SB4 release is, programmer's ('non-profit' ahum) that know their way around this kind of internet interfacing are not rare, they'r a freak of nature. Appearantly the engine behind SB4 was 1 guy (same with FSCopilot 'team'), who got busy, and the slack taken up by 1 other guy Of course (same FSCopilot) the website is run by a whole tribe of webmasters and moderators (ahum) they manage known 'workarounds' of issues because everything stops of course, when #1 is doing a #1 :D the main culprit is (my opinion), M$, with their 'thrifty' paranoia as a bussiness model I'd say, just keep sending emails 1 will stick eventually (at the inside of the privy) :twisted: mt
  2. I had ongoing problems with FSInn/Copilot sometimes it helped, to change the order of the copilot's .DLL in de DLL.XML I would still irratically loose proper connection, keyboard input, traffic dicplay etc etc, in random order (memory leaks?) this happened especially when installation gets more complex with FSX SP2, Vista 64, and notebook Vista 32, with WideFS, and lots of simconnect utils. A great util when it works, and a pain with 'strange behaviour' I uninstalled FSCopilot, when Squawkbox 4 was released Boring interface, no nifty accessoiries, rock solid mt FSX / Vista
  3. works (somewhat obscure interface, when one is unfamilier. Just keep punching the buttons :D ) over WideFS output FSUIPC > WideFS, output Widefs > Com4 , Pair Com4 <> Com2, input Map Software Com2 wow, great invention thx mt
  4. hi The User Guide concerning GPSout states: "A virtual serial port program (freeware) from MixW is available from my Support Forum. You can use this to generate a pair of linked virtual serial ports to connect between GPSout and a receiving program on the same PC, or between WideClient and the receiving program on a client PC." Can't find it on the Support Forum? Been to MixW site, but what I saw there was a tuning module for a Ham radio (or something) Any chance I can get a copy of this port program? somewhere / want to try a GPS Map :) Or am I missing something (cant find my glasses sometimes either:) thx mt FSUIPC 4.50 / Vista x64 x86 / FSX SP2
  5. "Key Press & Release" found it, oops fixed, set and running thx mt
  6. Why would you want to? You can assign keystrokes to buttons and switches, asnd you just confirmed that you can operate it by a keypress combination. I have my Trim up and down with an axis, but it takes quite long, and I figured I wanted to try a center position to set FMC Trim (and I'm running out of buttons :x ) added LogAxes=Yes unfortunately, log stated allmost the same, when CTRL-TAB-T is pushed: 594129 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2 594129 .. Key not programmed -- passed on to FS 594129 KEYDOWN: VK=9, Waiting=0, Repeat=N, Shifts=18 594129 .. Key not programmed -- passed on to FS 594129 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW 594395 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=18 594395 .. Key not programmed -- passed on to FS 594395 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18 594395 .. Key not programmed -- passed on to FS 594395 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW 594441 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=18 594441 .. Key not programmed -- passed on to FS 594441 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18 594441 .. Key not programmed -- passed on to FS 594441 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW 594441 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=18 594441 .. Key not programmed -- passed on to FS 594441 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18 594441 .. Key not programmed -- passed on to FS 594441 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW 594488 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=18 594488 .. Key not programmed -- passed on to FS 594488 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18 594488 .. Key not programmed -- passed on to FS 594488 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW 594535 KEYDOWN: VK=17, Waiting=0, Repeat=Y, Shifts=18 594535 .. Key not programmed -- passed on to FS 594535 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18 594535 .. Key not programmed -- passed on to FS 594535 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW 594535 KEYDOWN: VK=84, Waiting=0, Repeat=N, Shifts=18 594535 .. Key not programmed -- passed on to FS 594800 KEYUP: VK=84, Waiting=0 595081 KEYUP: VK=9, Waiting=0 595175 KEYUP: VK=17, Waiting=0 596079 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 67648 (0x00010840) NAV2_RADIO_SET 599153 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 71056 (0x00011590) NAV2_RADIO_SET "passed to FS" and no record of anything my FMC trim does get set though this end of story? thx MT
  7. hi PMDG MD-11 has a 'define a keyboard command', 'Set Take Off Stab Trim', and I've set this to CTRL-TAB-T it sets the Trim to the calculation from the FMC so is there any way (?) to make this to a FS control in the dropdown list? I've added LogEvents=Yes LogButtonsKeys=Yes LogWrites=Yes LogReads=Yes to my INI loaded a routine test flight, pushed CTRL-TAB-T and the end of the log grew to this: 123023 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 71056 (0x00011590) NAV2_RADIO_SET 126049 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 67648 (0x00010840) NAV2_RADIO_SET 129091 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 71056 (0x00011590) NAV2_RADIO_SET 131400 KEYDOWN: VK=17, Waiting=0, Repeat=N, Shifts=2 131400 .. Key not programmed -- passed on to FS 131400 KEYDOWN: VK=9, Waiting=0, Repeat=N, Shifts=18 131400 .. Key not programmed -- passed on to FS 131400 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW 131634 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18 131634 .. Key not programmed -- passed on to FS 131634 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW 131681 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18 131681 .. Key not programmed -- passed on to FS 131681 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW 131728 KEYDOWN: VK=9, Waiting=0, Repeat=Y, Shifts=18 131728 .. Key not programmed -- passed on to FS 131728 *** EVENT: Cntrl= 65827 (0x00010123), Param= 0 (0x00000000) NEXT_VIEW 131728 KEYDOWN: VK=84, Waiting=0, Repeat=N, Shifts=18 131728 .. Key not programmed -- passed on to FS 131899 KEYUP: VK=84, Waiting=0 132133 KEYUP: VK=9, Waiting=0 132196 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 67648 (0x00010840) NAV2_RADIO_SET 132196 KEYUP: VK=17, Waiting=0 135222 *** EVENT: Cntrl= 65709 (0x000100ad), Param= 71056 (0x00011590) NAV2_RADIO_SET and I can somewhat see the keys pushed but there's no event that shows the Trim set to FMC value what am I missing? thx, MT FSUIPC v4.427
  8. no clue there was a subset with fixed numbers thx, mt
  9. ok, now I know why it does what it does I'll get used to it thx, mt
  10. ident=OVERHEAD_PANEL / PANEL_ID_TOGGLE hi should it be possible to call a panel_ID that has a name as an ID? thx mt FSUIPC.dll 4.4435
  11. uptill the latest update v4.435 I could do comments behind a ";" on a seperate line and would allow for empty lines with v4.435, I get a "!1" ("!n") before any line starting with a semicolumn and Fsuipc tries to 'cleanup' empty lines is this on purpose? or something in the General section preference? does the exclemation prefix do something / is meant for something? though a bit of a chaos, I'd rather prefer my old way, that allowed empty lines & I could better keep track of changes by commenting the section my INI: [buttons] ButtonRepeat=40,0 !2=;//P0 Saitek Yoke 1-20 23-51 !3=;SPOT views !4=;VC 0-view 1=CP(+Y,8)Y,0,K189,8 ;minus 2=CP(+Y,8)Y,0,K189,8 3=CP(+Y,8)Y,0,K189,8 4=CP(+Y,8)Y,0,K189,8 5=CP(+Y,8)Y,0,K189,8 6=CP(+Y,8)Y,0,K189,8 7=CP(+Y,8)Y,0,K189,8 8=CP(+Y,8)Y,0,K189,8 9=CP(+Y,8)Y,0,K32,10 ;ctrl space 10=W0366=1 CP(+Y,10)Y,0,C65550,0 ;1x 11=W0366=1 CP(+Y,10)Y,0,C66530,0 ;66530 EYEPOINT_RESET 13=W0366=1 CP(+Y,10)Y,0,C65655,0 ;ZOOM_IN 65655 14=W0366=1 CP(+Y,10)Y,0,C65655,0 ;ZOOM_IN 65655 15=W0366=1 CP(+Y,10)Y,0,C65655,0 ;ZOOM_IN 65655 16=W0366=1 CP(+Y,10)Y,0,C65674,0 ;VIEW_FORWARD 65674 17=W0366=1 CP(+Y,10)Y,0,C65674,0 ;VIEW_FORWARD 65674 18=W0366=1 CP(+Y,10)Y,0,C65674,0 ;VIEW_FORWARD 65674 19=W0366=0 CP(+Y,10)Y,0,C66530,0 ;66530 EYEPOINT_RESET 23=RY,2,C65656,0 ;ZOOM_OUT 65656 24=RY,3,C65655,0 ;ZOOM_IN 65655 25=CR(+Y,8)Y,4,C65607,0 ;65607 ELEV_TRIM_DN ;CP(+Y,8)Y,4,K53,9 ;shft 2 26=CR(+Y,8)Y,5,C65615,0 ;trimUP ;CU(+Y,8)Y,4,K53,9 27=;CP(+Y,8)Y,5,K54,9 ;shft 6 28=;CU(+Y,8)Y,5,K54,9 29=CR(+Y,9)Y,4,C65607,0 ;65607 ELEV_TRIM_DN 30=CR(+Y,9)Y,5,C65615,0 ;trimUP 31=CR(+Y,10)Y,4,C65607,0 ;trimDown 32=CR(+Y,10)Y,5,C65615,0 ;trimUP !5=;miniPANEL in mode9 PANEL_HUD_NEXT 66404 PANEL_HUD_PREVIOUS 66407 33=CP(+Y,9)Y,7,C66404,0 34=CP(+Y,9)Y,6,C66407,0 !6=;PAN_LEFT 65671 PAN_RIGHT 65672 35=CR(+Y,10)Y,7,C65672,0 36=CR(+Y,10)Y,6,C65671,0 37=CR(+Y,8)Y,7,C65672,0 38=CR(+Y,8)Y,6,C65671,0 39=PY,8,K120,8 ;mode1 40=PY,9,K121,8 ;mode2 41=PY,10,K122,8 ;mode3 42=PY,14,C66389,0 ;TOGGLE_AIRCRAFT_EXIT 66389 //24=RY,14,C65896,0 ;AP SPEED 43=PY,15,C66389,0 ;TOGGLE_AIRCRAFT_EXIT 66389 //25=RY,15,C65897,0 ;AP SPEED 44=PY,15,K50,8 ;TOGGLE_AIRCRAFT_EXIT CARGO "2" .. etc or am I missing something THX mt FSX/SP2 VISTA64 FSUIPC v4.435
  12. what am I missing: Left/Right landinglight Switch, down/up seperate macro's #5 #6 working put together #3 #4, only first line works, i.c. 3.1 / 4.1, i.c only LeftLandingLight moves down/up [Macros] Module="PMDG_MD11.DLL" .. 3=LLdown 3.1=RX3270*X8bcc ;LeftLandingLight 3.2=RX3290*X8bcc ;RightLandingLight 4=LLup 4.1=RX3270*X8bcc,31 ;LeftLandingLight 4.2=RX3290*X8bcc,31 ;RightLandingLight 5=llLdwn=RX3270*X8bcc ;LeftLandingLight 6=llRdwn=RX3290*X8bcc ;RightLandingLight ? thx mt
  13. any chance of binding sevaral macro's to 1 key? I just figured out what mouse macro's do, what a clever option it even fixes bugs in the aircraft release (not working key definition) on PMDG MD-11 there are lots of buttons, that operate by mouse so I run out of fysical buttons for instance, landing lights has 3 positions with seperate L and R light switch, and a Taxi light, also 2 down positions mouse macro detects a 'down' and an 'up' trigger in PMDG-key-define-options one can only define Toggle On/Off lights (2-at-once) (bugger), what a pity so a nice compromise would be to have a switch 'dwn' macro, but with the - edit - option to bind 2 macro's to 1 button (for instance, L/R landing Lights, or to popup several sub-panels at once. MD-11 has maaaany subpanels, or the de-icing switches) in regular button definition, one can serialize several actions, by defining the the same button in the macro file, I find a similar line numbering and it would be nice, for instance, be able to edit the macro file, or something like that, to bind several actions together so they can be triggered by 1 button action an extension of this would be to be able to add (a) mouse macro('s) (mix and match) to a regular button definition for instance, one can lower the landing gear, and this also triggers/calls the macro that switches on the taxi light on the nose wheel how nice that would be, please consider (if I missed something, I am sure you'll let me know) thx mt Vista64, latest FSUIPC4, FSX/SP2
  14. works ;F11 0-view =W0366= 1_onground 0_airborn 56=W0366=1 CP(+A,10)A,0,C65550,0 ;1x 57=W0366=1 CP(+A,10)A,0,C66530,0 ;66530 EYEPOINT_RESET 58=W0366=1 CP(+A,10)A,0,C65674,0 ;VIEW_FORWARD 65674 59=W0366=1 CP(+A,10)A,0,C65674,0 ;VIEW_FORWARD 65674 .. ;F11 0-view =W0366=0_airborn 83=W0366=0 CP(+A,10)A,0,C66530,0 ;66530 EYEPOINT_RESET THX
  15. in the fsuipc4.ini the (working) comment denominator is ";" 2cts
  16. this is a standard feature in ASX (and prob the new ASA) over a network (simconnect/FSX), I can set the wind for destination airport /or anywhere/ to turn either specific direction or even directional spread, and even with a certain radius around the airport (like 10 or 80 miles) , from my notebook 2cts
  17. I had no idea now, I do Good idea I'll look into that Can remember I looked into camera views when FSX was just released .. and too complicated, at the time (and in too much of a hurry to go flying) By now, indeed, fellow simmers must have figured it out Thx MT
  18. F11 is standard Spot View in FSX some planes, when viewed from outside spot, more than others, have different results to View Up (Shft-UpArrow) When flying, and switching to "F11",I want to be behind the plane with 1 button (approach) in Spot View (F11) (to chk flaps and gear down) On touchdown, with that same button, I want to be Behind, and than Shft-UpArrow couple of times, to see the runway Exit KingAir 350, when Shft-UpArrow x5 and I can see over the plane and see "1st exit" unfortunately, with my new MD-11, I have to do 25x Shft-UpArrow to be at the exact same angle to see "1st exit" from behind and over the plane that's what this is about thx mt n.b. concerning your reply, I'll try the FS-code equivilent for Shft-UpArrow (View Up, I think), will take a while, waiting for my Q9550
  19. then perhaps your FSuipc never really started and your installation is wrong in your Users\[****user]\AppData\Roaming\Microsoft\FSX there supposes to be a dll.xml and there has to be a line loading FSUIPC Modules\FSUIPC4.dll also in your \modules folder there has to be a fsuipc.log that shows a log of activity if thats missing you are not even loading fsuipc perhaps your dll.xml is corrupted (sometimes you cannot even see this, when its a hidden bad bite or something) and you have to - backup - first, delete the dll.xml so fsx will write a new one TAKE CARE, this file also configures other simconnect related apps, so take a note whats in it and BACKUP and compare the new one with the old one, to see whats missing, if any perhaps you run a fsuipc Install again from the orininal exe, this writes the proper line to the dll.xml cheers
  20. I was talking my enthousiastic-hyperbole :shock: Im not a native english speaker so some - to me obvious - theatrics, might be lost in translation sorry :mrgreen:
  21. if you dont have anything defined yet delete the fsuipc.INI in the \modules folder I have bad frame rates, when there are errors in the .ini (or somehow corrupted .ini file)
  22. thats a pity, it's not that hard do some 'define' something in the Fsuipc interface, and than window to the fsuipc.ini in the \modules folder and see what that does and you'll figure out how it works else you waste opportunities of this utility
  23. what about you start you SB seperate After your WideFS and see if it works properly?
  24. hi want a new spot view (either airborn or onground) and I want to do a lot of Shft+Up in F11 view, to be exactly, 25 but it wont do this it will not do more then 7-9 am I missing something? no hurry greets, mt also I have a slider with 2 ranges for Gear Up/Dwn: 20=CR,256 21=CR,B,-16384,-14303,66080,0 22=CR,B,-12666,16383,66079,0 any chance of putting a condition in there: 'when airborne' the spot view: ;F11 0-view =W0366= 1_onground 0_airborn 56=CP(+A,10)A,0,K8,8 ;backspace 57=CP(+A,10)A,0,K32,10 ;ctrl space 58=CP(+A,10)A,0,K38,9 ;shft Up 59=CP(+A,10)A,0,K38,9 60=CP(+A,10)A,0,K38,9 61=CP(+A,10)A,0,K38,9 62=CP(+A,10)A,0,K38,9 63=CP(+A,10)A,0,K38,9 64=CP(+A,10)A,0,K38,9 65=CP(+A,10)A,0,K38,9 66=CP(+A,10)A,0,K38,9 67=CP(+A,10)A,0,K38,9 68=CP(+A,10)A,0,K38,9 69=CP(+A,10)A,0,K38,9 70=CP(+A,10)A,0,K38,9 71=CP(+A,10)A,0,K38,9 72=CP(+A,10)A,0,K38,9 73=CP(+A,10)A,0,K38,9 74=CP(+A,10)A,0,K38,9 75=CP(+A,10)A,0,K38,9 76=CP(+A,10)A,0,K38,9 77=CP(+A,10)A,0,K38,9 78=CP(+A,10)A,0,K38,9 79=CP(+A,10)A,0,K38,9 80=CP(+A,10)A,0,K38,9 81=CP(+A,10)A,0,K38,9 82=CP(+A,10)A,0,K38,9 or ;F11 0-view =W0366= 1_onground 0_airborn 56=W0366=1 CP(+A,10)A,0,K8,8 ;backspace 57=W0366=1 CP(+A,10)A,0,K32,10 ;ctrl space 58=W0366=1 CP(+A,10)A,0,K38,9 ;shft Up 59=W0366=1 CP(+A,10)A,0,K38,9 60=W0366=1 CP(+A,10)A,0,K38,9 61=W0366=1 CP(+A,10)A,0,K38,9 62=W0366=1 CP(+A,10)A,0,K38,9 63=W0366=1 CP(+A,10)A,0,K38,9 64=W0366=1 CP(+A,10)A,0,K38,9 65=W0366=1 CP(+A,10)A,0,K38,9 66=W0366=1 CP(+A,10)A,0,K38,9 67=W0366=1 CP(+A,10)A,0,K38,9 68=W0366=1 CP(+A,10)A,0,K38,9 69=W0366=1 CP(+A,10)A,0,K38,9 70=W0366=1 CP(+A,10)A,0,K38,9 71=W0366=1 CP(+A,10)A,0,K38,9 72=W0366=1 CP(+A,10)A,0,K38,9 73=W0366=1 CP(+A,10)A,0,K38,9 74=W0366=1 CP(+A,10)A,0,K38,9 75=W0366=1 CP(+A,10)A,0,K38,9 76=W0366=1 CP(+A,10)A,0,K38,9 77=W0366=1 CP(+A,10)A,0,K38,9 78=W0366=1 CP(+A,10)A,0,K38,9 79=W0366=1 CP(+A,10)A,0,K38,9 80=W0366=1 CP(+A,10)A,0,K38,9 81=W0366=1 CP(+A,10)A,0,K38,9 82=W0366=1 CP(+A,10)A,0,K38,9
×
×
  • 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.