majapahit

try FSXSE, its really stable, P3D is back to beta it seems, they broke it

the only reason I use P3D is the ATC that keeps going when I'm websurfing on the other screen and yes FSXSE is way easier to get fast and stable

your welcome (I figured this out 10 years ago or so, when I was still young and smart)

I see your "I'm using the default PMDG assignments Shift+Control+F1/F2/F3/F4.” now so ignore <custom control>, ignore PDMG_NGX_SDK.h you may look at that if keypress doesnt work a proper dowson forum link is http://forum.simflight.com/topic/76194-fsuipc4-parameters/ concerning for ‘what is the code for a shifted key to enter in the ‘control sent when range entered) // (and/or exited)’ page 20 "FSUIPC4 for Advanced Users.pdf" for the keycodes F1 F2 F3 F4 = 112 113 114 115 page 21 for the <shifts> value(s) 1/2/4/8/16 .. etc the small print is .. 9 for shift+… 10 for control+… 11 for shift+control+… THUS your shift+control= 11 WITH the formula on the forum “(param is Keycode + 256*Shift code, or JsBk)” simple: Keycode + 256*<Shiftcode> THUS Keycode + 256*11 // when shift+control THUS <shftctrl+F1> // F1+256*11=112+256*11=2928 <shftctrl+F2> // F2+256*11=113+256*11=2929 F3 // 2930 F4 // 2931 (I hastily calculated) as previous in general find axis enter range 1 xxx to xxxx etc 'control sent when range entered' 1 range ON/UP / 2 OFF/DOWN w. 2 axis select drop down <Key press & release>, because you tested this right?, and it moved the fuel lever, yes? and in the parameter box you enter 2928 2929 2930 2931 for the four instances 2 lever up and two levers down SPECIFICALLY you have to do this quite carefully i can remember Set up to 10 ranges .. number right of Up/Dwn arrow must be 1 hold lever down = press FROM set lever middle = press TO you define range 1 from lever 1 select drop down <Key press & release>, because you tested this right?, and it moved the fuel lever, yes? and in the parameter box you enter 2929 // IF your fuel cut of is F1 (hastily chk) you now have entered the command for range 1, (which is coming from Up, thus command is WHEN coming DOWN) CHKBOX "down" (and "Up" for why not) then up arrow in arrow boxes left of range = xxx (was 1) this up arrow so you'll enter range 2, number 2 appears repeat for upper range lever A BIT (or rather A LOT to make sure) ABOVE MIDDLE = FROM bottom of upper range 2 lever to TOP = TO, top of upper range 2 dropdown <Key press & release> and parameter CHKBOX "UP" (and "DOWN" for why not, this is for more than 2 ranges, also be sure there's a little or large GAP in the middle of the 2 ranges) repeat above now for lever 2 and in the parameter boxes you entered all of 2929/2929/2930/2931 for the four instances 2 lever up and two levers down hope this works for ya

(theoretical) find axis by axis assignments set up 2 ranges (or whatever) fsuipc upper right range 1 xxx to xxxx etc range 2 then 'control sent when range entered' 1 range on / 2 off or something enter a <custom control> as per the list found PMDG\PMDG 737 NGX\SDK\PMDG_NGX_SDK.h the THIRD_PARTY_EVENT_ID_MIN in the list which is the base number is 69632 i think fuel switch is called because thats under // Control Stand EVT_CONTROL_STAND_ENG1_START_LEVER (THIRD_PARTY_EVENT_ID_MIN + 688) EVT_CONTROL_STAND_ENG2_START_LEVER (THIRD_PARTY_EVENT_ID_MIN + 689) you find the right one (take a peak at LINDA LUA file will say)

Think I had put PMDG VC textures through NGXPerfMan to 'low resolution' (tad blurry) well, did it again, perhaps not the right path previous time P3D options lighting shadows and graphics now back to high FPS from ~18 to 45-55 waddayaknow

after some more searching I put P3D on 'high' CPU setting PMDG 'performance' texture on 'low' no shadows that helped a lot ~17-18, which to me is the bare minimum I think 7970 cannot render the (bigger) textures of P3D fast enough

PMDG 737ngx fresh FSX-SE install 27 fps, fresh P3D v3 install 13 fps, WTH? Recently found out about the existence of FSX Steam Edition. I had stopped flying FSX when I started flying DCS A10. So I figured I should start flying PMDG 737NGX again, and also obtained P3D hoping for progress since the - in hindsight - mediocre days of FSX ‘stutter’ graphics. Fresh install of both FSXSE and P3D, fresh install of PMDG 737NGX. Used FSXSE to tinker my setup hardware, Warthog HOTAS and VR MCP, when installing P3D v3 I copied the hardware setup and about the same scenery settings (2048 vs 4096 bits scenery, Ultra dense scenery, sparse Autogen, 5% traffic, FSUIPC, simconnect, TrackIR, 2 monitors), and OPUS real live weather (real life fog and clouds are a hit on frame-rate) at the same airport Rotterdam X runway, PMDG 737ngx virtual cockpit does ~27 fps on the FSX-SE install, only ~13 fps on the P3D v3 install (which results in the horrible ‘mini stutters’ at take-off) WTH? My setup is previous generation OK-ish - Asus w. Intel 2500K overclocked @4200, AMD 7970, 16 GB RAM, Win7 x64 on Samsung SSD, flightsims on new hard drive. What am I missing? or is Prepar3D another ‘high-end systems only’?

I had a like problem, using MCP 1 original, LINDA 2.7.0 Standard v1, PMDG_737NGX_v4_4 everything worked (super) BUT the LVLCHG button, how does that happen? oh o, kaput maybe? after also tinkering with direct FSUIPC assignments and many trial and errors, and just giving up (just do the mouse click, how annoying) I came upon looking in the PMDG aircraft setup (because I wanted to add the HGS to a 700 model) via the FMC that, per every different 737NGX model per the Tail Number (listed in the ..\FSX(SE)\PMDG subdirectory) there's a menu that assigns 'keyboard shortcuts' for specific 737NGX commands FOR INSTANCE if the default Ctrl-V is defined in the FSX keyboard control commands, but has a duplicate in the PMDG aircraft 'keyboard shortcuts' for an AP Panel button that's the problem (and easily fixed, when you's aware of this) 2cts

the REX Weather Architect? 50% sale at simmarket (2 more days @ ~20 USD) http://secure.simmarket.com/rex4-weather-architect-fsx-fsxse-p3d.phtml

Disregard above post by me (can't edit?) / this new 737NGX definitions file works OK in my Prepar3D setup. Must be something kaput in my FSX setup. Great update

have a MCP1 also, can confirm all above, all is fixed & No more settings lags (had me worried there for a while // here, there was a long post about my trial and error about my MCP1 A/T_ARM switch not working, but, all-in-all I now can make it work with “NGX AP ATHR toggle” instead of "on" and "off" // by the way, "all taxi toggle" and "all landing lights toggle" that's a treat EDIT2: when from LINDA, I set either (or both !?) MPC1 A/T_ARM switch positions to “NGX AP ATHR toggle”, this makes the switch work so it seems, at least in my download(s), that “NGX AO ATHR arm” and “off” don’t work? 2 cts

installed windows 10 when my 8.1 registry became corrupted, installed P3D, wow really fast, installed FSX wow really fast, installed add-ons wow what heaps of problems MS raised the 'security' levels(s) with Win10 couple of notches, when one installs an add-on and want to check the dll.xml and the exe.xml they are NOT there. MS 'temporarily' sends 'suspected' program changes to a 'secure place' (haven't stuck to Win10 long enough to find out where that is and NO mentioning of this behavior on google-searches)) and these will appear in the <user> section a couple of reboots later, that's to late for my convenience. This is a real problem when one depends on a lot of add-on's. So I went back Win7 until I read somewhere that someone figures out this Win10 behavior. Win10 will not allow disabling/removing of User Account Control Settings UAC - that's the real problem, and rather unfortunate, for the FPS framerate in plain vanilla FSX and P3D were up almost 50% (!) (MS cleaned up their DirectX-old when introducing DX12 perhaps) 2cts

Think I figured out what happens (with my rig). I had low (very) FPS at the landing threshold, like minus 10 FPS After some searching, via PMDG Performance Manager I set VC Model and Display from 'high' to 'Low' With last test, both landing and Flap Output to LCD were on par. Seems when I was stretching my CPU capacity when landing due to the PMDG VC calcs I was also stretching output to the VR MCP, pmdg data output maybe/prob be a low priority thx coming to think of it if you're building LINDA 2.01 dunno if that includes the 737NGX module but since 737NGX has slooooooow flap movement it could be considered that LCD output doesnt show FL:<reached> but FL:<set> for instance, when flaps bound to an axis (like me) one can monitor 'dailing in' of the flaps on the LCD it takes the mind of flap position reached check/tasking, never mind the sloooow travel setting flap position implies, it will get there somehow/anyhow (equally so when one hits F7 flap notches, you would then see - hopefully - the flap numbers pass by) 2cts?

That would be great 'However, I said without a MCP1 for testing compatibility cannot be guaranteed' I can beta test for you 'all updates to the LCD slow or just the flaps' only noticed flaps, reeealy slow, I'll test other, perhaps its the PMDG NGX that has slow flaps, but i count after move light out AP 'A' and/or 'B' and LandingGear 'UP'/'DN' I saw we're ok I'll have another look (some default planes) thx