quepsi83

Hello again Keven. Let me shout... Err... maybe not... LOL. It is a H A P P Y D A Y at my hangar. "All is well with the Immersion FX package for the Q400". It works like a charm... from engine start smoke... prop vortices during t/o roll... volumetric lighting... contrails..." OMG... Considering I'm a retired engineer... it reminds me of the days when the client called to say "It works like a charm, Keith" Maybe this might help someone else... I dunno. I cleansed the previous install. Reinstalled the sim and applied the patch. Re-installed the FX pgk. Followed the suggested flow (like I always did). Lit up the APU started #2 then went outside to check and... and... and... there was that smoke effect. LOL Thanks again for your help, Keven. Keith

Happy New Year Keven. At the Majestic User Area there is no mention of OR ability for me to d/l the 1.018e update you mention above. FWIW... I have the 1.018b patch installed. In fact I reinstalled everything... including the 1.018b patch. Granted... I'm at the office right now and haven't been able to test any further... but will update this topic if the 'b' patch ISN'T the fix. I only have the Pilot's Edition... NOT the Pro Edition. If the 'e - Echo' patch is hidden somewhere else - that YOU know about, please advise. Thanks, Keith Sorry. I meant 1.019b not 1.018b Keith

I too have no effects. The pkg appears to have installed correctly into the "aircraft.cfg" [smokesystem]. Steps I follow... a) start FSX/Accel with the default C172 at a default (non-payware) airport, cold 'n dark b) start FSInn (VATSIM Client) c) start FSGRW d) use FSX menu to GO TO AN AIRPORT (Default or Payware) then SLEW the C172 to a gate e) select the DH8D (after slewing) and preflight... the plane performs the same as prior to buying this addon FX I've tested in dry, ovcst and rain conditions. No effects at all. I also own the 777 Immersion and I have ALL the effects. The same weather FSGRW... everything the same... the B777 Effects work just as expected. Let me ask this... "Am I supposed to press the letter I or something to get this thing to work?" Thanks, Keith

The following failure dialog suggests I contact support... "Stripe error: Your card was declined." Let me know the solution either via forum reply or by email. This order is for the Triple 7 Immersion package. Thanks, Keith 1085341

Hello all. Observing that the last post to this thread took place in 2013 and it is (now) March 26th 2015 as I re-group... I (now) have the exact problem as depicted in the original poster's image... a gauge within the JS4100 WX gauge. Yep! This gauge worked flawlessly, on a Win XP Professional 32-bit platform several years ago. After a break from simming for a few years, i recently re-acquired all of my hangar equipment and reinstalled all of my many sceneries. My (personal) observation is as follows... a) Back when I ran the sim and the Reality WX gauge on the JS4100, my PC was running XP Professional 32-bit. b) The (new and current) PC is running Win 7 Ultimate 64-bit, liquid-cooled, 12Gb RAM(what the what), GTX 760 nVidia, yada yada yada. In other words, this is a fully tweaked and stable-running dedicated gamer running the original FSX Acceleration package (as back when on the XP platform) d) I can confirm that my pre-break-from-simming Flight1 purchased ATR 72-500 has ceased to work... while my LDS B763 works like a charm e) ALL of my PMDG products... the NGX.. the B748i... the B777x and the JS4100 work like a charm (sans the WX500 gauge in the JS4100) After writing financial mgmt software for over 20 years, I'm not unfamiliar with coding and software logic and/or hicups, platforms and OS issues and... KEY: "Software Support" After trying everything posted on the interweb - to solve the WX500 gauge issue in the JS4100 - on (my) configuration, I can only look in the direction of WHY it/they worked on WIN XP 32-bit (the ATR 72-500 and the WX500 gauge) and no longer on the newer platform. Unless one is the (original developer/programmer) with acces to source code and logic, I (personally) do not expect the solution providers or suggesters to have a clue as to the innards of muti-prepared PC's and OS combinations and the 'hiccups' that pop-up along the way. Having vented this observation, I've decided to put "//" in front of the gauge CALL in the panel.cfg and be done with it... just like I took a swig of Junkyard M@@nshine before uninstalling the ATR 72-500. You dont have to go the junkyard route... just believe that - if the developer can't put a stop to the bleedng - bail out 'now' before it's too late. Three greens (with all functioning planes). Keith

Well Mike... LOL, The demolition equipment came to the rescue once more... (fingers crossed). As of this reply... and the last I might add... a complete de-installation... including anything to do with the 777 appears to have worked. I just did my normal routine of letting FSX start with the default trainer then (just) selected the default PMDG 77W and "viola"... we have wheels again and sounds and "The hills are alive with the sound of PMDG. Thanks Mike. Venting (thinking via web) and the demolition pre-disposition appears to have returned me to a previous place of comfort. Takc care, Keith

Mike. "Yep! You're correct!" When these doozies rise up, they're a royal PITA... LOL Here's my entries for the PMDG product line in the DLL.XML... <Launch.Addon> <Name>PMDG Interface</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDG_Interface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>RAASPRO</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>.\RAASPRO\RAASPRO.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>PMDG Options</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGOptions.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Events</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGEvents.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Sounds</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGSounds.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG HUD interface</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> The dll.xml was not modified in any way before or after the gremlins struck... And, in the FSX.CFG file, the rebuilt entries for the PMDG product line are... D:\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_Interface.dll.rieceqequzithcoclknucnabrkoiznrrouhhcawa=1 D:\Microsoft Flight Simulator X\RAASPRO\RAASPRO.dll.alznetirckhtecehcuiuanaiiqwkerhrlkilzboo=1 D:\Microsoft Flight Simulator X\PMDG\DLLs\PMDGOptions.dll.oaanartkkbwtnzrzolochqkbozohezklikkncrnw=1 D:\Microsoft Flight Simulator X\PMDG\DLLs\PMDGEvents.dll.cutuiqzockuiauhtnqtrqkbcbzlieolwbhoaobet=1 D:\Microsoft Flight Simulator X\PMDG\DLLs\PMDGSounds.dll.bozibhcnzwibazicuhhoqozllbqtlzahlkklwbii=1 D:\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_HUD_interface.dll.uuotuheunhcburowuhhnbowibackeekwhuruqwit=1 D:\Microsoft Flight Simulator X\GAUGES\PMDG_777X.DLL.iwcaiccihwlooqbuoubrbwcucrhkqhkqzwcontqz=2 When compared to an older .cfg file, the entries are identical. Only differences are the UIDs attached after the .dll.blah-blah.blah I'll now break out the demolition equipment and remove the Tripple Seven CLEAN and start again. Thanks man, Three greens on steam your next flight. Keith

Mike. Thanks for the quick response. 1) I (have) fsx automatically load a default C172 trainer upon startup... have done it for years as a workaround to FSInn throwing hiccups all over the place. My last 150 or so hours have been that routine then loading a saved (B777) flight.... THEN... loading a panel state I created named "WORKING". Again, this has woked effortlessly. 2) Yes. After removing the FSX.CFG entries, I systematically loaded the JS4100, NGX, B744/8i and the B777 so that the CFG file could receive the new .DLL validations. Forgive me... been there... done that... a million times. 3) The last suggestion about the loading the Ultralite... was replaced by loading the Cessna 172 Trainer for the reason in #1 above. Something happened between yesterday and this morning IMHO regarding RAAS Pro notification. I'm just walking in the park of all possibilities regarding (this) as the only anomally in over 150 hrs of B777 sim time and over 7 years of running FSX. I'm just saying... Keith Oh, Mike. Forgot to linger on the fact that FSX Add-on menu doesn't throw up the complete set of options (for the B777) like it does for the MD11 and so forth. Normally, I should be able to go in there and Load a Previous Panel State. Right? Well... as of this morning and even after a complete reinstall... No can do... it won't display anything but the About PMDG I referenced earlier in the original post Keith Here is the most recent debug log file that was created a few minutes ago... Creating systems: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 38a39 40 41 42 43 44 45 46 47 48 49 50 51 51b 52 53 54 55 54 55 54 55 56 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 ..systems created. Setting keyboard hook... Setting key event handler... Starting updates... 01 Simulator installation path: D:\Microsoft Flight Simulator X\fsx.exe 02 Determining airframe: ...airframe not detected Update systems: 01 02 Determining airframe: 777-300ER Update systems: 01 02 Update systems: 01 02 Update systems: 01 02 Update systems: 01 02 Update systems: 01 02 Update systems: 01 Flight load callback: PMDG\PMDG 777X\PanelState\Startup at Piarco GA TTPP.FLT.sav Corresponding panel state not found 02 Update systems: 01 .air file path: SimObjects\Airplanes\PMDG 777-300ER\B777-300ER.AIR Aircraft title: PMDG 777-337ER Air India Aircraft tail number: VT-ALJ 02 Initializing systems: 01 02 Init AIRAC Navaids: 17387 items Init AIRAC Fixes: 240662 items Init airports/runways from combined file: 12989 airports Init displayed fixes Init suitable airports Init preferred altn airports 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 29a30 31 32 33 34 35 36 37 38 49 40 41 42 43 44 45 45b 46 47 50 50 50 51 51 ..systems inited. Using startup state: PMDG\PMDG 777X\PanelState\WORKING.sav Loading this state. Keith

Good day. I flew the B77W yesterday (Sunday). No issues. This morning I load it from yesterday's (arrival) saved airport list and i get a beautiful plane with no wheels and a dark cockpit... meaning inactive screens. I hear click spots when I click and so forth. The JS4100, the NGX and the B744/8i all load and work fine. I always start FSX from (one) airport with a native FSX Piper Used Trainer - BEFORE - loading anything else. This has worked for like forever... jus tlike yesterday. Within the 3d cockpit, I can click ( and hear ) click sounds. Pressing the menu key on the lower CDU - doesn't activate it. FSX's Add-on menu shows RAAS Professional and PMDG ->> About ->> *About PMDG. There are no additional sub-selections. I de-installed the B777 package and re-installed from a clean d/l using my order number. Additionally, I removed (ONLY) the B777 and RAASPro entries from the FSX.CFG file and allowed them to be re-applied/validated on the next startup of FSX. That worked as expected. The entries are now back in the CFG file. Meaning I loaded the JS4100, NGX, B744/8i and the B777. All but the B777 load and operate as before (this morning). I didn't touch the DLL.XML entries. FWIW, Yesterday as well as this morning's problems, I kept getting a message that RAAS Professional was outdated... with the option to d/l... but that is an exercise that went nowhere... cause RAAS Prof is bundeled within the install of the B777. I no longer get that warning since re-installing the B777 not too long ago. I specifically put the 'lil gremlins out (from the man cave) last night so they wouldn't/couldn't play with my Simulator. On the real side though, does anyone know of a solution or has experienced this situation? Here's a Dropbox link to what I (now) get upon loading any B777... https://www.dropbox.....20.06.png?dl=0 Thanks, Keith Rocke Vatsim 1085341 -7000+ hrs HCFARTCC

Just like making a PDA response without elaborating... isn't necessary.I would have the same reaction if I had gotten such a response from a Dev guy... and (so far) there hasn't been a response from a Dev person. So, please... there is no need to quote/reply.Cheers,Keith

"PDA responses".So, anyway, playing along with this response, let me ask...Are you saying that the NGX requires a different AM setting than the JS41 or MD11 or B744/8i or QW757 or LDS763 or C-130H or Carenado C340/C337 or E/S C750?Are you too busy to expand on your reply considering I just got the email notifying me that MrKen quoted me (from my original post)?Let's see where this goes. The joy of being on a forum.FYI: The sim has been tweaked and the O/S tuned up based on helpful suggestions amassed by techies who wrote volumes to get their collective points across... and those tweaks have taken me through over 1000 online hours.Cheers,Keith

Gd'Day all. Not wanting to start a new topic as this current topic says it all... So, with a clean install of the NGX and application of SP1, I flew one (1) flight with negligible hitches or hiccups... that was VVNB-WSSS here. As is normal for this seasoned FSX simmer, I restart the box (Yep!) after each flight.So, now I'm heading up to Ahmedabad here.True to form (Ok! I was surprised). At about FL270, FSX suddenly froze up! Second instincts had me pulling up the Task Manager and looking at the Performance Tab. Something familiar was displayed.Of 12 cores on this i7 980X, cores eleven (11) and twelve (12) were busting through the ceiling. This is exactly what happened with the pre-SP1 incarnation of the NGX. The HotFix never touched this issue. That's why I sent the NGX off to the maintenance hangar and I began flying the MD11 (a true friend and confidante)... LOLOk! So, after about 3 minutes of this frozen state - maybe 2.5minutes give or take - here comes the 738NGX... huffin and puffin... as though it never missed a beat.There is a lesson I've learned through all of this. "Never pull the plug when the sim/FSX and the NGX freezes! Never!" I've lost too many pirepable flights by thinking the BOX/FSX/Win7 Ultimate 64-bit is at fault.One thing I can guarantee. During these flights - where there is that initial FREEZE UP - the rest of the flight is as smooth as a baby's 'tukas' give or take whatever ASE decides to cook up.So, my (unavoidable question).Didn't SP1 fix this problem?I run the cockpit in a network configuration. The ONLY apps on the FSX machine is FSX and FSInn. The O/S is on a SSD. FSX is on a 300GB VelociRaptor. The Video card is an nVidia GeForce GTX 480. The whole internal is water-cooled (i7 and GTX480).All other (needed) software is run from Megalon (the 2nd box in the network). Need I say, I have no other problems with any other PMDG product? I fly the JS4100, MD11, B744/8i - all with nary a hitch.I even put on my tennis shoes before writing this post/reply - I'm a PMDG cult menber...Cheers,Keith Rocke

Hello everyone. Is there a re-painter willing to create a Continental Air Lines 75th Anniversary for both the B738WL as well as the B739WL? That would totally round out my collection of Liveries? If I missed a forum post where such a Livery is available, please advise and be gentle??? I've been really busy flying the NGX. Cheers, Keith

Oh! Then let's proceed to filling up with Jet-A and "Turn 'n Burn" Cowboy... Cheers, Keith

Here's what I did... step by step. Let's see where this goes. Not wanting to re-install my Liveries and thinking that the possible changes would be to the AIRCRAFT.CFG files, I... Copied all of the NGX's from SimObjects/Airplanes to my empty Drive E: Then I copied and renamed all the aircraft.cfg files with the prefix "BEFORE_HOTFIX_" I left the original aircraft.cfg files intact Then I installed today's Hotfix Sure 'nuff... the liveries are gone after the HotFix Comparing the [LIGHTS] section of the aircraft.cfg files from the "BEFORE_HOTFIX" to the "POST_HOTFIX" Hopefully I haven't missed any other edits. But, I can see there some changes were made to the LIGHTS parameters Furthermore, I discovered there are two (2) SMOKESYSTEM headers in the 900ngxwl of the POST_HOTFIX aircraft.cfg file So, I've performed the 'cleanup' myself and am now OFF to find and airport where it is already nighttime. If anyone else has discovered this issue, I suspect that posting their findings might be helpful to the entire community and the developers? Kind regards, KeithCOA382