NM5K

I did one last night going into KHOU.. Set the microburst at 4.8 miles DME, which put the mayhem about 1.5 miles from the runway.. Was doing OK for a while... Until the tailwind kicked in and my IAS to dumped down to about 80 sumtin.. Ouch.. Burned my biscuits.. :mad: Couldn't keep it afloat. I'll have to practice that. The burst is so severe I don't know if it's flyable without some really early aggressive steps before you get to the tailwind. I'm not getting any audio wind shear warning.. Only visual on the ND. Is that normal with the NGX? I was sort of expecting an audio wind shear warning with a red letter ND warning..

I just started using ASN recently to take advantage of the radar. So not sure at this point how to set up wind shear. Or if it can be done manually and saved..?? There may be some way. I got a predictive wind shear alert on the ND the other day when taking off out of KAUS.. I didn't realize that had been added to the NGX. "Looks like solid amber arrows pointing the direction, and shows "wind shear" on the ND.. When I first saw it, I thought I was having a bug of some sorts, and my sim was getting flaky.. lol.. But then I quickly realized it was normal when I saw the wind shear warning. And the weather wasn't stormy or anything.. So was kind of strange to get, and I didn't really notice the IAS bobbling around too much, so was a non event. I assume if it had been an active alert, the warnings would have been red instead of amber, and possibly an audio warning. There was no audio warning with the predictive alert. Just two yellow "beams" so to speak, pointing off in two directions ahead of me. Didn't last long, so didn't get to much time to check it out. I guess one way to increase the odds would be to set up heavy thunderstorms, and add wind, and strong gusts and turbulence.

Yep.. All there. It works normally for FSX. Just isn't seeing SE as installed for some reason. When I choose the NGX-SE tab for aircraft, the writing is lettered red like it isn't installed for SE. But it is, and all works normal in SE. The plane installer had no trouble seeing the SE folder, but it seems OC is for some reason. And OC is now up to date with the current version.

I did that, and it did update using that method. But.. It's still not seeing my Steam version as installed for some reason. It could be the way I named the folder.. I have FSX-SE installed in a "fssteam\steamapps\, etc, etc folder instead of steamapps\etc, etc . Thought maybe that could be the reason, but the NGX installer had no trouble seeing this when installing the planes, and they work perfectly fine under steam. It's just that OC is not seeing them, or seeing the path for some reason. But.. no biggie.. I set the lower res displays myself manually for SE, so it's no real issue now.

I've noticed something kind of strange with the OC here. And it's the first I've used it being as I don't have the T7. Also, I did do a full uninstall/reinstall for the NGX. Mine seems to work fine overall for FSX-MS, but it's not recognizing that I have the NGX for SE installed, even though it is, and works fine. The reason I noticed this is because I wanted to turn my display BMP's to low res in the SE version as I do in the MS version. I'm on a mediocre puter, and it seems to get me an extra 2 or so fps.. I run the other VC model and texture BMP's as high res. It let me do that for FSX-MS, but being as it does not recognize that I have the SE version installed, it won't let me do it for SE. I get all red lettering and such as if I didn't have SE installed. When I load OC, it gives me a message stating that there is an update, and I run the install, which sort of seems to work, but then when I restart OC, I get the same message again. I've told the AV to ignore OC, etc, so don't think that is the issue.. I hope.. Anyone else having this issue? Or is the SE version not yet supported in OC?

Sure got to give it a workout yesterday over Tejas.. Flew HOU to DAL, and then later DAL back to HOU. Plenty of rain to get used to it. I used the tilt a lot to see the mayhem below me when at cruise. I only use auto when the rain in getting into my path. Seemed to work great here.. And I cranked the gain fairly high most of the time.. You don't have to, but I like seeing even the weaker stuff.

I've been doing just that, and so far, using fairly short flights, see about what you are saying. I can run either SP1c, or SP1d using the same exact fsx.cfg, as I have multiple FSX installs on the same puter. The one I used for SP1c is a recent backup of my everyday sim, and still has SP1c installed. My everyday install has SP1d, and I also have it on the Steam version, but so far, I've limited my testing only to FSX-MS. I do see a bit more VAS usage with SP1d, but nothing terribly drastic. On one test I did a while ago, I flew to one local airport, KHOU, where I landed, and then I took off again, and flew to KIAH where I also landed. I did this with both versions. At the end of the two airport trip, SP1c VAS usage was appx 1496.000 and SP1d ended up as 1542.000. A little more, but nothing too drastic. On both of these trips, I did not use the radar at all, being as SP1c does not support it. My VAS at KHOU after landing was slightly less for each, as would be expected, being I'd only been to one airport. Then I fired up ASN and flew the SP1d to KHOU using the radar. Not much rain in the area, but plenty of fog, and fairly low vis. I was basically showing nothing on the radar, being not much actual rain, which would be expected. Fog does not show much at all on radar, as the droplets are too small and don't give much to hit on.. I've found that the usage of radar in SP1d basically amounts to zilch as far as increased VAS or memory usage as far as fsx.exe. What does increase the VAS is ASN. And of course, one can't expect a free lunch with a program of it's type. During the flight ASN VAS usage was appx 315k or so.. After landing at KHOU where the vis was low, and I got visual of the runway at say 400-500 feet?? or so, the ASN VAS was up to appx 335k. The VAS for the SP1d was actually slightly lower than the usage for the flight with good vis and no radar usage.. Go figure.. So..at this time with limited and not overly scientific testing, I'm seeing about what you say should happen. ASN is using a chunk, so if one was not using ASN before SP1d, but installed it afterwards in order to take advantage of the radar, that's gonna be a 300+ chunk of VAS down the drain. And SP1d is using a little bit more too, but like I say, doesn't seem to be drastic.. If one was using ASN before with SP1c, there really should be little difference. Just the small increase in SP1d usage. Of course, not everyone's puter is the same, so I can only state what I'm seeing here. BTW, the weather I used on the first two tests was the exact same "startup flight" weather, and not using any real weather program. It was good weather with just a few clouds. I was using process explorer to watch the fsx.exe working and VAS usage. The radar hit is basically nada to puny in the plane itself as far as I can see. Same with terrain. The main hit is all in ASN's VAS usage, not the NGX itself.

I must have downloaded it after it had been noticed and fixed. I see that all the other files were originally born on the 4th, but my 600/700 exe was born on the 6th at 12:08 in the AM.. You must have d/led the first version pretty early. I didn't d/l it until yesterday about 9:30 AM. So I likely don't need to re-download it being it looks normal on my box..

I'm starting to think it only effects the engine off states.. IE: both short and long, or cold and dark. I just did a "long" state, and ended up with the fuel recall.. I don't think it's effected any of my engine running states. Only engine off. And I don't think it matters whether cold, long, or short.. Deleting the files wouldn't effect I don't think, as it's only going to read the startup state when firing up, or any one requested if you choose one after starting. BTW, the long state I used was the PMDG long panel state. I guess the next step would be the PMDG cold and dark, and then try new Cold, long and short states built from running states.. That's what cured my short panel state.. I'm kind of assuming it would cure the cold and long states too.. I think it cured the non running states the others have made. I guess the issue to you guys at PMDG is what caused it to do that with the engine off states.. But I guess no biggie being it seems to be fixable on our ends.

Strange.. I was looking through the panel state files and the dates, and it seems like the default panel state that is working is an old file. ?? For some reason, I was thinking that there was a new default file. But it seems there is only the older one.. Now I'm really cornfused.. lol.. I was loading a few of the panel states, and it seems some load, and some don't. So it may not be totally the age of the panel state that is the issue. Fer instance, I fired up the sim, with it loading a new "good" short panel state as it's startup state, and then I loaded the old PMDG short panel state.. Fired up the engines.. Fuel recall error.. I fired up my old homemade "short" panel state I had been using. Fired up the engines.. Fuel recall error.. Then I fired up one I made the other day for a video in Phoenix which had the engines running. It gave no recall errors.. Then I fired up another one that I was using when painting my Coleman jet several months ago, with the engines running. No recall errors.. Hummm.. So it seems it's not really how old it is whether it works or not. Something else must be causing an issue.. Some work, some don't. Strange it is.. But I have no problems as long as it thinks it's a "good" panel state.. Maybe some panel states need a good spanking.

Yep.. The default panel set with the engines on is a good file. Any old file seems to cause problems. I've been making a few new ones, which I started out with the default to begin with, and have had no more issues. Also found out about my throttle issue. The setting from over ride in ARM had been changed to NEVER.. I set that back to overide in ARM, and all is swell. Also, the EFIS panel settings are saving when using the new panel states. As of right now, I have no more issues, and everything is perfectly normal as far as I can tell. Once you make one good panel state from the default, any new saved "good" file can also be modified and saved for another good panel state file. Just don't use ANY old panel state file. I'm gonna flush all my old ones. When I re-installed, I placed all my old panel states back into the folder, but made sure not to overwrite any of the ones from the new install. But other than the new default running panel state, the various other panel states that came with the new install were the same from SP1c.. They had the same dates as the ones I had. None of those will work properly. You want to use ONLY that single good default panel state to make new ones.

It might be possible to shear the pin with strong yoke force if the A/P was engaged. I did it one time when I strongly bumped the yoke by accident.. Once that happens that side A/P will be kaput until you repair/reload the plane. That would be the indicator that the pin sheared.. If that side A/P still worked after that, it wasn't a sheared pin/bolt.

I'm cornfused now.. Was that the 737 winglet model files, or a livery.. Normally just a livery change is just textures, and I wouldn't think would cause that..?? I'm wondering why I didn't seem to see it, and wonder if I oughta re-download later on... I'll probably wait a bit till all the smoke clears in case there are other fixes.. The only other strange thing I've noticed is twice I was doing a landing, and on short final I turned off the speed hold and disengaged the auto pilot, but kept the autothrottle armed for possible TOGA. When I did that, I had no manual throttle control. :( I had to disarm the auto throttle to get my manual throttle control back.. But I'm going to test more today to see if it's something I did, or maybe an issue using an old panel state, A/T panel state setting, etc.. I had never seen that behavior before.. Always before, if I turned off speed hold, and kept A/T armed, I would see "ARM" on the PFD, and would have manual throttle control. But I did use my old panel state a short bit, so maybe that could have caused it. I'll tinker more in a bit to see how it acts with a known good panel state. I made a good "short" state to replace my old one that caused the fuel error.. Maybe it was causing more problems than just the fuel recall issue..??

Weird.. Mine is not doing that as far as I can tell. I did do a total uninstall and reinstall. And I tried both my SWA 700, and also a PMDG livery. Both were OK here. Also loaded the 800, and the strobe light was in the same normal location. I only checked the winglet versions.. Now the recall issue, I got even though I did uninstall/reinstall. Most of the non startup panel states were older files, even with the update. Only the one new date default startup state was OK. Any old one gave the recall error, and also showed an error on the FMC when loading, although it didn't list what the error was.. Just said Panel Error, or something like that up at the top of the page.. Of course, I doubt that issue is related to the strobes..

Seems to be the same issue as the "recall" thread. I was getting the fuel recall in both FSX and SE. It seemed to be any old panel state is causing that, including the ones that came with the latest update. I noticed they had old dates.. But the default start panel state is OK. If you start with it, and make new panel states, it seems OK. I first made one from the no lights default, and turned my lights on, etc, and kept the engines running. Saved the panel state, and then reloaded the new state. No fuel recall. Then I used it, and shut down the engines, and made a new "short" panel state.. Saved it, reloaded, and still no fuel recall. So it seems the default is OK, but any old panel state is no bueno. Have to use the default and make new ones from the default state.

I don't seem to be seeing that here. I loaded the 700 winglet in both FSX and SE, and unless I'm missing something, it looks normal here. The strobe is on the rear of the plane, and not floating behind it, and the reflection on the ground behind the strobe seems to look to be where it should be. Are you all actually seeing the strobe light itself floating behind the plane? Mine is on the plane where it should be.

As one mentioned, no image to see.. Is that a default PMDG paint, or a 3rd party repaint? I run a 900 as a pseudo BBJ3, and have never noticed any problems with the one I use. I tweaked the paint myself, and never have noticed anything irregular... IE: have not noticed any lines, and the windows line up. IE: no alpha layer problems, etc.. This is the plane I just flew around the world recently.. Same paint scheme as the private 600 I run..

I saw over 100 from STL to HOU a couple of mornings ago playing Southwest buoy.. That was SW of St. Louis, and it died down slowly as I headed south to Houston. Saw over 160 at one point from KBOS to EGLL a couple of weeks ago. Luckily it was a tailwind. Needless to say I made good time to London. That was the second leg of my round the world trip in my pseudo BBJ3 737-900.. I finished that RTW trip about 3-4 days ago. The last leg being Toncontin to Houston Hobby, which is where I started. The entire trip was KHOU-KBOS-EGLL-ESSA-UUEE-USSS-VIDP-VTBD-WIDD-YPDN-AGGH- NCRG-NTAA-SCIP-SEGS-MHTG-KHOU. I took my time and flew a leg when I had time. The tailwind I saw going across the Atlantic was the highest winds aloft I'd ever seen in the sim so far. I see over 100 quite often in the winter. Not that unusual really. Edit.. make that over 170 at one point.. I saved a few snapshots.. Going east out of Boston. Wasn't quite to cruise at that point..

They sure grew from the beginnings.. A guy that lives around the corner from me was one of their original employees from the old days. He put the people on the planes over at Hobby. Or at least I think that was his main job. They once had a picture in Texas Monthly where they had all the original employees standing on the wings of a plane, or something like that. He was one of them. Due to the stocks or whatever he obtained as an old employee, when he recently retired, he retired with a whole lotta $$$$$$$ in the bank. B)

They were still running the tan and red planes when I first started playing Southwest buoy.. When the canyon blue planes first came out, I wasn't all that keen on them.. But they grew on me, and I eventually liked them better than the old tan livery.. When I first saw the new "hot dog on a stick" planes, about the same thing. At first, I wasn't that keen on them, particular the huge size of the Southwest fonts on the side. But I think they look better in real life than they did at first on the drawings and such, and they are kind of growing on me now.. Or maybe I'm just getting used to them.. I suspect they will keep a small number of canyon blue planes as "retro" livery, same as they did with the tan ones.. So I imagine those won't totally vanish. They seem to be churning the new livery paints out fairly fast all considering. IE: I've even seen a 300 that was repainted. Wonder how the 500's will fare, and how much longer they will run those.. I imagine they will be repainted too, if they intend to keep running them any amount of time. I'm not sure if they have retired any of the 500's they have bought over the years. I know they still fly the heck out of them.. Real common to see at HOU, where a good number of flights a day are the 500's.

There is a FSX version out there. I have it, and several other of the SWA "State" liveries, but actually rarely fly them for some reason.. Also have the 700 version of the whale.. But... I tend to prefer the regular ole liveries.. The old canyon blue, and the new hot dog on a stick paint, which I've been running a good bit. I have N908WN rigged up for my 700, which I've already seen the real world version a couple of times on utoob..

I'm thinking you likely still had the FSX entries in the registry.

I've never really noticed too much light from the windows at any real distance. But you should be able to see into the cabin with a small amount of light showing up close. I think what he is seeing is fairly normal, if he's comparing it to default planes which I think have a good bit brighter looking cabin windows from the sides.