mtjoeng

Jeppe$en Flitestar/Flitedeck, no altitude though on my setup

exactly

I have a G15 you assign - new and free - keystrokes to any desired action or note same and already defined keystrokes and actions then you need to program you keypad with those keystrokes with the Logitech software you 'record' those keystrokes again within the software, and assign

FYI I have a Saitek Yoke also With all new windows & plug-and-play ('Found New Hardware") Saitek USB driver install, drivers for Saitek are automatically installed and Mode1,2,3 button can only be accessed with Saitek's software to free Saitek's Mode1,2,3 button for FSUIPC, rename/delete C:\Windows\System32\SaiD0BAC.pr0 (to SaiD0BAC.pr0.BAK f.i.) unplug/plug the USB and then they'll show up in FSuipc the obvious definition being VC,Panel,SpotView check, when Saitek is 'found' by FSX, the FSX / 'Controls' option definition / Buttons & Axis of the Saitek, that's by default a regular mess. And you have to delete all (especially Axis definitions) from the FSX Control, or chk them 1 by 1 if your FSX cortrols setup has gone corrupted, delete Users\admin\AppData\Roaming\Microsoft\FSX\Controls\Standard.XML and FSX will write a new one if your 'default flight' (that you changed from the Delta wing) has gone corrupted, delete in your FSX.cfg \Users\admin\AppData\Roaming\Microsoft\FSX\fsx.cfg the line SITUATION=\flight simulator x files\.FLT and FSX will start again with the default Delta wing mt

hi researching the offset programming at the moment reading a thread concerning Door open (when loading the plane was the request), you mention "Gear down, parking brake off, engines not combusting? If all those conditions are true, and the doors are not open, then open them." I cant think of a way to do that (silly me) for - at least the simple - thing to do this would be to have multiple conditions on the definitions line but I cannot find this documented =condition1=x condition2=y ,Command ? what am I missing? another topic mentioned in this same thread, is the "InitialButton" going into the [buttons] section and cannot be put in a [buttons.feelthere xxx] section?? for a first button when loaded could be 'reset eyepoint' (and 'Doors open" of course :)) for this is by default too low, allways (perhaps because my default situation is the beechking 350) thx mtjoeng

you taxi a 737 by Throttle up, and as soon as it moves you throttle down, close to idle in 'joystick calibration''seperate throttles per engine' there is a button 'slope'

Thx for fixing mt

latest 4.522 FSX /SP2 win7 on the box mt

hi was browsing thru the "FSUIPC4 for Advanced Users.pdf" and saw the /delay parameter so I put this in my Feelthere 737 Flaps [Axes.FeelThere Boeing] 7=FY,256/1000,D,23,0,0,0 after, when FSUIPC rewrites the .ini it looked like this [Axes.FeelThere Boeing] 7=/1000 the flaps still work, and with the delay, probably because [Axes] 7=FY,256/1000,D,23,0,0,0 is there is this meant to be? is Default definitions always read together with the Specific and compared (by line number)? (or visaversa) grt m tjoeng

dear Carst lookup the Maual for WideFS because it sounds like you dont know where its used for sincerely a WideFS user, using it for FS Flight Keeper

apart that comments will be removed, and might have been part of the problem :( (it cuts off the line somewhere, and leaves some redundant characters) after a clean edit, without comments the 1st Rewrite fsuipc does, is from 7=B66C0&1!0 8=B66C0&1=0 to 7=B66C1&1=x0 8=B66C1&1 then 7=B66C1&11=x0 8=B66C1&1 now 7=B66C0&1111=x0 8=B66C0&1111 (EDIT: seems to consolidate on this one, 1111) so it adds 1's (trying to correct unexpected code? convert to Hex?) and I wonder when it runs out of 1's keeps the toggle working though, also after continues reloads of the ini :D ?? (Edit: perhaps it want the code to be =B66C0&1111=x0 =B66C0&1111 from the start?) mt

It's the little guy in your garden wears a red hat, and usually pushes a wheel barrow wears a beard also, most of the time :D he's quite friendly actually takes care of my fsuipc.ini also I think More people will have a use for this when more VRinsight MCP's are sold It's an all-in-one does-any-plane panel, sells for around 330euro 340 GBP 440 USD have this now for a week or so, works great with the two prop Cheyenne, that has a big radio stack and ILS and of course addon Jets Both the Dials and Buttons do Key Presses only (and their simplified version of Mouse Presses) though, bit of a bummer So needs plenty of - carefully planned - Key Presses. And those dials on the left, I've made - thanks to your fsuipc - to do double functions now :P thanx mtjoeng

well, I have a liitle Heinzelmännchen in my computer, and its running FSuipc hard added another toggle, between Radar Altitude and Cockpit Altitude (pressure): 6=B66C1&1=0 54,26,M5:55,0 7=B66C1&1=0 55,26,M5:56,0 8=56,26,x0D0066C1,x01 18=B66C1&1!0 55,26,M5:57,0 19=B66C1&1!0 54,26,M5:58,0 and my little Heinzelmännchen changed this now to: 6=B66C1&11111111=x0 54,26,M5:55,0 7=B66C1&11111111=x0 55,26,M5:56,0 8=56,26,x0D0066C1,x01 18=B66C1&11111111 55,26,M5:57,0 19=B66C1&11111111 54,26,M5:58,0 the other inner/outer dial now changed to: 40=90,26,x0D0066C0,x01 41=B66C0&11111111 87,26,M5:24,0 42=B66C0&11111111=x0 87,26,M5:25,0,26,0 43=B66C0&11111111 86,26,M5:23,0 44=B66C0&11111111=x0 86,26,M5:26,0 seems to keep changing with every rewrite (deletes comments also :x ) of the [Keys.Piper PA31T Cheyenne] portion ?? and both work :mrgreen: :mrgreen: using 4.520 sorry, missed that mt

40=90,26,x0D0066C0,x01 ;from the dropdown edited ini: 41=B66C0&1!0 87,26,M5:24,0 ;outerL ctrltabW 42=B66C0&1=0 87,26,M5:25,0 ;innerL ctrltabW 43=B66C0&1!0 86,26,M5:23,0 ;R 44=B66C0&1=0 86,26,M5:26,0 ;R Works! toggles now between inner and outer dial then FSuipc magically rewrites the ini: 41=B66C0&111 87,26,M5:24,0 42=B66C0&1111=x0 87,26,M5:25,0,26,0 43=B66C0&11 86,26,M5:23,0 44=B66C0&1=x0 86,26,M5:26,0 thats fantastic any documentation about this syntax B66C0&1!0 B66C0&1=0 &1111? this got me curious now thx mt

Its the example "FSUIPC4 for Advanced Users.pdf" page 19, and I was wondering what x00030001 was not in Hex :) not to mention, I figured, x5100 could cycle from 1 to 0 and back :D (and would ask if it could :D ) saw the list, please bear with the novice. Thought it belonged to the Project Magenta GC Controls specific It's the example (of which I can't see the syntax, exactly) Sort of suggesting, to see if it was anywhere in the ballpark. At least it came to somewhere in that same list :D this then: 32=90,26,x0D0066C0 ;togglebits ctrltabZ 33=B66C0&1!0 87,26,M5:24,0 ;outerL ctrltabW 34=B66C0&1=0 87,26,M5:25,0 ;innerL ctrltabW If the above would be better, I even dont quite grasp why B66C0&1!0 B66C0&1=0 is there. &1=0 is the declaration, and 1!0 is the 'toggle between 1 and 0? anyway, doesnt work 32=90,26,x0D0066C0 wont toggle, neither 32=90,26,x0E0066C0 (word) 32=90,26,x0F0066C0 (Dword) the knob sticks to (34=B66C0&1=0 87,26,M5:25,0) InnerKnob where is this syntax from? It should all fit into: n=key,shifts,control,parameter , but from this to Cx510066C0,x00030001 or B66C0&1!0 / B66C0&1=0 is rather a big leap. (I had 6 months of ALGOL (yes, a long time ago) at university, then the usual Pascal with my first computer the the Osborne 1(!) running on CP/M(!), and more recently, of course the amateure (in the good sense) PHP to maintain my website:) So never the Hex and Offset stuff (in my world (I'm a manager, trained in construction) that's close to Macro Assembly, and I considered that a deadly virus). It should all be rather basic stuff, perhaps you can suggest what I should read, to get a grasp of these basics, so I can at least get familiar with the syntax. Would really appreciate that. I could've asked my brother - a mathematician - but unfortunately he has passed away :( Thx, mt

errr 32=90,26,x510066C0,x00030001 ;togglebits ctrltabZ 33=B66C0&1!0 87,26,M5:24,0 ;outerL ctrltabW 34=B66C0&1=0 87,26,M5:25,0 ;innerL ctrltabW like this :?: mt

I've honed my 'condition' problem to the Cheyenne Trimble GPS knob, with an Outer en Inner ring. This is new to me, and I'm quite lost with Key 'condition' My VRinsight MCP accepts keystrokes for all its dials and buttons So this one dial can be pushed also, this I want to use to toggle the output of the dial to the outer or inner ring so, define dial's turn right, I'll define the key CTRL-TAB-W (87,26) and use same dial's push, to toggle a flag condition either to point to OuterDial-R macro, or InnerDial-R macro the dial's push (toggle flag 1005) will be CTRL-TAB-Z (90,26), for virtualbutton 15,16 (4111) and so, I suppose, things would look something like: [Keys.Piper PA31T Cheyenne] .. 32=90,26,1005,4111 ; CTRL-TAB-Z=90,26, toggle flag virtualbutton 15,16 33=Wxxx=yyy 87,26,M5:24,0 ; CTRL-TAB-W=87,26 , macro 24 OuterDial-R 34=Wxxx=zzz 87,26,M5:25,0 ; CTRL-TAB-W=87,26 , macro 25 InnerDial-R and I'm stuck with xxx yyy and zzz and I've looked at the descriptions of offsets 3210, 2910 and the like, but I'm quite lost appreciate your pointers what xxx yyy and zzz should read unless I've missed something, and all above is redundant (oops) thx MT

hi digital aviation cheyenne has 5 main panels MAIN_PANEL .. MAIN_PANEL_ALT4 I would like to share buttons for the WeatherRadar (CoPilot's) with the Trimble (Main), depending on the panel showing any chance to have the active panel_ID as a button define condition? thx mtjoeng in a state of confusion :shock:

FYI PMDG_MD11_Kbd.ini in de \PMDG directory in ..\FSX the FCP part: [FCP] APPR/LAND=Shift+Tab+O AUTOFLIGHT=Ctrl+Tab+Z SPD Push (hold)=Tab+V SPD Pull (set)=Ctrl+Tab+V SPD Bug Increase=Shift+Tab+8 SPD Bug Decrease=Shift+Tab+7 FMS SPD=Ctrl+Shift+F HDG Push (hold)=Shift+Tab+H HDG Pull (set)=Ctrl+Tab+H HDG Bug Increase=Shift+Tab+2 ALT Push (hold)=Shift+Tab+W ALT PULL (set)=Ctrl+Tab+W ALT Bug Increase=Shift+Tab+4 ALT Bug Decrease=Shift+Tab+3 VS/FPA Toggle=Shift+Tab+/ FEET/METER Toggle=Shift+Tab+T HDG/TRK Toggle=Shift+Tab+D HDG Bug Decreasee=Shift+Tab+1 IAS/MACH Toggle=Tab+R V/S Bug Increase=Shift+Tab+6 V/S Bug Decrease=Shift+Tab+5 these are my settings, defined from the dropdown Add-ons menu /PMDG

If it should work, thats good news :D Think it was actually (not on the 'dropdown part of macro name', the 1st line, comments on the sublines seemed not to interfere) Think they did, I'm now in a long flight, so I'll chk tomorrow, and take everything apart then. This LevelD has a ton of keymappings, so I'll check all definitions again for duplicates. I'it because of my new VRinsight MCP panel, that add 50+ buttons :mrgreen:, so i'll give it another comb thru Keeps me busy Thx later marcel tjoeng

Hi Hope I'm wrong - seems a 'combination-multi' mouse macro can only reference to 1 module? for instance from a LevelD763: Module2="B767Afds.GAU" 14=MastercautionTT2 14.1=R2:X1cc0*X8bcc ;Mastercaution Module3="B767main.GAU" 14.2=R3:X4010*Xa1cc ;G/SInhibit this doesnt work but could it somehow? thx

FDC Live Cockpit FS Flight Keeper FS Real Time PFE Pro Flight Emulator Radar Contact FSMap Air Hauler Hifi XPax Flight Tracker

had this ones delete the ini and start over, I did

A mesh is loaded like a scenery So - figure out where (directory) your install wrote the files to there prob are different directories for 'usa''South Amrica''Europe''Asia' etc. and check or edit in your scenery library tab, these directories and a scenery index will be created p.s. you dont readily 'see' a mesh (especially in the high mesh default of FSX' USA area) unless at a significant location like LOWI Inssbruck, in between mountains or slew to nearby high mountains, pause, and check/uncheck the scenery in the 'World/Scenery Library' tab p.s.s. why am I answering this? this has nothing to do with FSUIPC

Xpax uses simconnect, as I can remember check your simconnect (use the AI traffic test)