majapahit

'unrecognized aircraft' / PMDG NGX unofficial KLM livery VoxATC works fine with my PMDG NGX setup with default and 'official' KLM 738 Livery but I found a KLM 737-700 livery on Avsim and then this error pops up, aborting initialization any ideas what triggers this (in the aircraft.cfg?) ?

I use FO most of the time, since I am busy enough with voice commands to FS2Crew FO (a different guy remember to set up 'first officer available' in 'VOXATC Settings', enter your ATC callsign here also AND you seem to have to have an IFR Flightplan loaded, a VFR flightplan is no good or the red/green 'FO' will not show up in the VoxATC window after Initialize by default you enter 'K' the get 'FO' from red to green you can interrupt FO flow by 'K' again, THO I often have trouble getting FO alive with 'K' but with enough 'RightControl' (PressToTalk) pushes FO will come alive Do NOT dial in your first COMM1 manually as CO, when FO doesnt want to come alive, because this seems to trigger not to be able to get FO alive until after TakeOff, I you'll have to Voice until then 2cts

ah ha, anyway die time frame zal in voorkomende gevallen inderdaad te klein zijn, en dan moet je de fase van FS2Crew handmatig zo manipuleren dat je de informatie tijdig erdoor heen gejast krijgt. Net echt. N.B. gebruik jij ook VOXATC, ik krijg foute vectors als ik ILS 21 EHBK maastricht aanvlieg?

thought you would be dutch

N.B. met zo een lage en dus hele late Transition Alt heb je ook nog niet eens een local pressure gehoord van een (simulator) Control, waar de FS2Crew flow geent is op een TransAlt van 18.000ft, dus dan heb je een hele tijdspanne om ergens een local pressure aangegeven te horen. Tenzij je op vatsim zit, waar je de local pressure op tijd aangeleverd krijgt, kun je - wat ik doe - dus gewoon op B drukken om FSX/P3D de pressure in te laten vullen en is wat je roept.

Met commando's zo dicht op de grens van de 'fasen' wat gebeurt bij de approach checklist let je inderdaad goed op de fase die de Main Panel aangeeft. En je doet gewoon een manual klik als de vlieg fase niet helemaal overeen komt met het gangbare FS2crew protocol. Een 4000 transition alt bij EHAM brengt namelijk de gehele 'flow' op het randje. De approach checklist is slechts een FO opsomming (en zal altijd kloppen) en de bedoeling van jouw uirroep zelf (die ik meen geen enkele consecquentie heeft) de uitroep slechts in de cockpit (en de voice recorder) dat je jouw kant overgeschakeld hebt van STD naar werkelijke luchtdruk. Ik start ook vaak een vlucht met motoren aan. Ik klik dan gewoon naar fase 'set TO flap' en roep de flaps naar de FO waarna ik ook klaar ben voor de verkorte Shft-P pushback. En je midden in de de taxi flow begint. 2 centen

LINDA doesnt work with FS9so that solves that dillemma :Pig:fsuipc.ini is in the FXS/modules folderso for FS9, that will be in the different FS9/modules folder(the syntax, overall, will be the same, i guess)editPMDG 737/MD11/747 A/C:Linda specifically is great with NGX, because it has a ton of parameters (every button, every system switch)many for MD11, somewhat less for 747, because their design gets simpler & simpler(and still is a cut above most any other)(on the NGX, I have the rocker underneath the Throttles assigned to open/cut Fuel, as per starting and ending procedure of Jet operation in Push & Start, and Shutdown Procedure after Parking Brake Set, at the gate)FS9 737, as I remember was a very nice setup, with any mouse toggle assignable to button operation through FSuipc macros

LINDA specifically provides GUI for- all FSX default 'control' codes (see FSuipc docs for list)- any key press to button- NO axis, though- PMDG codes, i.c. all NGX, many 747, many J41- iFLY 737- more, but limited, list of A/C, or find your own Variables with LUA's Trace facility (and post in forum)- VRinsight hardware, i.c. MCP Combo & instruments, etc- to Joystick Button (I have 2 attached, but can be a dozen or so)- interface to FSuipc Macro & LUA / very important facility, does my 737 NGX Gear lever- write you own Any LUA- can provide complex sequential commands, if you put it in a fsuipc macro, or a Lua codeetcall my axis are through Fsuipc regular interfacei used to delete everything in FSX 'controls', BUT the POVs, (and backup the Standard.XMLfound in .. ProgramDataMicrosoftFSX) because you have to assign 8 commands for that, untilof course, i found time to do that, and then backed up that portion of fsuipc.ini,in case of any mishaps -looks like://(joystick J)210=RJ,32,C65734,0211=RJ,33,C65856,0212=RJ,34,C65672,0213=RJ,35,C65857,0214=RJ,36,C65735,0215=RJ,37,C65855,0216=RJ,38,C65671,0217=RJ,39,C65854,0//(joystick Y)590=RY,32,C65734,0591=RY,33,C65856,0592=RY,34,C65672,0593=RY,35,C65857,0594=RY,36,C65735,0595=RY,37,C65855,0596=RY,38,C65671,0597=RY,39,C65854,0(line#, R(epeat), Joystick Y, button 39, C(ontrol) 65854, parameter 0)fsuipc.ini, just like fsx.cfg, rarely (like in once every 2 years)gets a mysterious bad file write& than you have to generate a new one from scratchbecause it’s a hidden EOF error somewhere2cts

you have to figure out fsuipc yourselfstart with keeping the manual open "FSUIPC4 User Guide.pdf"and assign throttle and a mixture axis to the C172then do 'Joystick Callibration' for that C172then do the B737now you need 2 throttles(it gets interesting if you have a rudder and footbrakes also)after this, you're on your wayI have the Saitek Yoke '3 way mode button' Disabledand assigned to F9 F10 F11my faq:"Use either the Saitek '3 Mode' with their Saitek software,ORredefine all definitions to FSUIPC ('disable' all FSX joystick control)&to free those 3 'mode' position Yoke button to FSUIPC(the driver reserved the 3modes button to Saitek software only & is hidden to FSuipc):Windows Saitek YOKE driver MODE 123 =C:WindowsSystem32SaiD0BAC.pr0 <= for mode123 <= (rename) / delete this file & restart windowsnow the 3modes button shows up in a FSuipc "trigger"EDITI always make a backup for Any change in my fsuipc.iniI have a ton of backups in my /modules dirwhen you're proficient at reading the fsuipc.ini fileyou can correct mistakes / little corrections, or cut and paste sectionsby editing fsuipc.ini in a editortrick for 'on the fly' editing is1. make sure nothing major is going on in FSX, like 'paused' or 'parking brake' (fsuipc keeps writing to fsuipc.ini)2. make you corrections in the fsuipc.ini(like changing the name of your profile, or deleting a sub profile, or moving an assignment from profile to default etc)3. go to fsuipc from within FSX, be in 'button' or 'axis', where there is a 'reload' button4. 'reload' definitions or axis or buttons, and the fsuipc.ini will be reloaded (with the edited file)2cts

Strict Standards: Declaration of group_forum_breadcrumb::sendOutput() should be compatible with that of output::sendOutput() in /opt/webdocs/newsite/forum/hooks/group_forum_breadcrumb_d29bf565a59f776807044fd19e49258a.php on line 107 http://forum.simflig...pdated-modules/is the FSUIPC site/forumdownload the latest full first and installit has all the Docsit is a Free version, so can take all you time trying (profiles disabled perhaps, = 1 profile)then update with the latest module / .DLLalsofind out about LINDA (its freeeeeeeeeeeee, yippie!)http://forum.avsim.n...orum/424-linda/thats a GUI 'profiles' module working together with FSuipcthats a whole new world / must implementfigure out what combination of profiles works best for youyou'll be busy

better, it auto loads, because it can read what AC you're loading any button any sliderbut not you RAT7 xtra buttons i'm afraid, fsuipc wont be able to recognize that mouse extra buttons, only joystick and specialty FS Hardwareof course you can still use your RAT7 mouse the ordinairy way

I have a basic for startup C172 1throttle 1mixturethen a profile for different i.c. has Spoiler or not, variprop or not, 2throttle, 3throttle etcI end up with few basic setups and many special setupsbecause I always define (Resize&place) gauges to buttons, and these are allways at different numbers for every plane f.i. with 2 throttles quads & MD-11you profile 3 throttles etc, and this is loaded automaticallywith many planes I have a 'curve' defined for sliders (Throttels)NGX runs away with minimum throtlle / many do, so the throtlle is defined to start flatRudderbrakes same, start flat, or you brake way to hard, same with rudder, start minimaletc slider = 'throttle' (or anything)it depends if you like to switch to moving 3 sliders all of a sudden when with a MD-11 or notor 4 sliders with a 747, or 2 with a Beechcraftand if you are into 'programming'like MD-11 had a lot of 'Mouse-macro' possibilities, you want that / or notadding hardware with 'buttons' all of a sudden gets really attactiveI have a Yoke, but allways my Joystick attached, use it for Slew & Taxi Views etcetc/?/

for the fun of it:2 spare sliders, so, instead of reverse buttons, two full reversers, for NGX only (reverse buttons 'toggle' Cut)use WideFS (network), have FDC (flightdeck) run over networkcan (used to, run PlanG now, simconnect) run Flightsimcommander from networkhave FS Flightkeeper (log) run from networkhave RadarContact run from networkhave rather complicated View setting assigned to different aircraft (no W or A, but dedicated)though, I use LINDA now for lots of assignments, for my VRInsight Combo,Linda does not provide complicated assignment, this is then done with a FSuipc MACRO (sequential Commands etc)I still have Parking Brakes assigned to Slider (2 zones)and NGX Gear Up / Lock / Down set to Slider (3 Zones)have Spoilers Arm set to Button (easy), have Spoilers set to Slider (fsuipc)Flaps on slider, (but inaccurate on NGX, too many, use Up/Dwn switch), for 2/3/4 flaps planes (auto finds incements)etcetc(i have 2 xtra throttles, so 9 sliders in all)like I said, it grows on you

you can do all kinds of setup tricks with FSuipcif you dont know it you dont miss itit grows on you

reverse should bekeypress to be heldso it will throttle to full reverse2cts (i just stumbled on this topic, a bit late)

needs to be in ()you have that?so(^L)in your hidmacros.xml would show:<Sequence>(^L)</Sequence>2cts (if that was the problem)

saw a post concerning AP behaviourI might be in error, but I have a MCP Combo paneland I think I see the behavior as exactly as if aFSX Bendix-King Radio AP were installed (C172 etc, bottom of stack)i.c. set altitute, autoclimb & VS readout, adjustable VS (as VS), and leveling off(BTW, this cant be RL behavior can it?, anyway)so I added a (the) Bendix-King Radio AP panel in my panel.cfg (at left-bottom of screen)for good measure I added the C337 GPS as a panel (at upperleft of screen, with some margin)FYI, here's the panel.cfg code[Window Titles]Window00=GPSWindow01=ManualWindow02=Control WindowsWindow03=INFOWindow04=Bendix AP //<< AddWindow05=GPS //<< Add..ADD..[Window04]Background_color=0,0,0size_mm=91, 26 // must be = x,xwindow_size_ratio=1.000position=6visible=1ident=1440 //window_size= 0.321, 0.150 //window_pos= 0.020, 0.170zorder=555 //window_pos=0.0,0.0 //window_size=1.000,1.000gauge53=Bendix_King_Radio!Bendix-King Radio AP, 0,0,91, 26 // 0,0,x,x[Window05]Background_color=0,0,0size_mm=128,93 //must be = x,ywindow_size_ratio=1.000window_pos= 0.03,0.016 //position=0visible=1ident=1600 //window_size= 0.321, 0.150 //window_pos= 0.020, 0.170zorder=556 //window_pos=0.0,0.0 //window_size=1.000,1.000gauge00=GPS_530_3D_337!gps_500, 0,0,128,93 // 0,0,y,y

just upgraded to LINDA - v1.11crashes with:"Access violation at address 0061A1BB in module 'linda.exe'. Read ofaddress 000001B0."revert back to LINDA - v1.1.. no crash?my system as per the signaturegreat addon

I figured to double MINS dial with Autobrake found there's 'show' for EFIS MINS still missing(& BARO)thx, mt

failures are OFF

// cold dark - aligned IRS / CMDA not working, CMDB does?ok, so I amparked at the gate, engines off, ground power, then cold & darklater when ready for return flight, refueledturn APU onIRS turn OFF turn NAV'dual fmc' messagechk POS; copy GPS to IRSsetup FMC, load / route, all seems to worktaxi and lineupFD AT LNAV VNAV switched ONrotate, climbout,want to switch CMDA on, NOT workingCMDB workingwhat am I Missing?

for my MCPhttp://forum.avsim.n...lcome-to-linda/the first picI can remember with version NGX module changing, HDG or ALT had the same 'HDG plus' or 'ALT plus' and I had to change ++A to 'HDG plusfast' etc.I also noticed, it was better to 'Remove' first & 'Save', before setting a new value & Linda had to be working properly allready.Nowadays I actually use Mode2 definitions and thats a lot of 'bindings' to make and test (Panel popups on USER Mode2 etc doubling with Lights)For NGX I have the flaps doubling on EFIS MINS - because flaps NGX wont define properly on a FSuipc definition Throtlle Quadrant Axis (and in NGX procedure flow it was the spare DIAL left, when I set landing minimum already before takeoff )2 cts

start by rebinding a dial (like ALT)fist 'remove setting' (or whatever its called) // SAVEset proper (again) (1Up/1Dwn, only need 1 test setting) // SAVEtestif 1 dial works now .. do the rest, if not, you got a real problemyou dont have VRInsight software loaded? you shouldnt

my pmdg737NGX can now toggle to 2 modes- sync with/drive the NGX MCP (for input)- display the flightparameters (speed, VS, alt) (when your drinking coffee in the VC)so yours should too

means there is a bad connect with lua.exe / actions.luasure the proper aircraft definitions is loaded in Lua? hit the SYNC to show Orange same, bad connection hereagain: sure the proper aircraft definitions is loaded in Lua? Lua should do this Auto, but perhaps needs a resetor rebind the missing commands and see what happenswhat really should happen is (kind of) is a rediscovery by lua of its own settings (in my opinion)reload / recopy / restartand all of a sudden (with me) it will work again