Sabretooth78

I've encountered a specific situation where the FO will not set flaps either as part of the After Start Procedure or when called on to do so during the approach. (Similarly, Flaps 2 as well, although IIRC he did set Flaps 3/Full but I could be misremembering). This situation arises when you use the "useCustomFlapLeverParameter=1" option in the AB_ND_GDI.ini file. As for the background as to how I discovered this, I have the Thrustmaster Airbus Quadrant and Add-On, and I bought 3rd party custom detents for the thrust levers and spoilers. There is "official" Aerosoft guidance for tweaking the throttles in AB-ND_GDI.ini so as to support the new (more realistic) locations of the "climb" and "flex" detents. The problem is, you have to disable support for the Quadrant in the Aerosoft configurator, and that "broke" my flaps. But when I used the line above (default is set to 0), FS2Crew didn't work properly with respect to the flaps. In the meantime, I've been able to get it to work well enough with custom detents set up through FSUIPC, which work well enough when extending at least (retracting, I can't figure out how not to skip over Flaps 2 for some reason). It's annoying, but considering I usually never touch the lever myself anyway, it works well enough for the rare occasion the FO becomes incapacitated. Still, thought it might be helpful to report in case for some reason it's not a known issue.

I have SF installed in v5 HF2 and have for a couple of months now with no apparent issues.

Wow, I had completely forgotten about that, but you're right. Heck, I even once bought MS Streets & Trips (probably still have it somewhere) just because it was so much better than the online competition. But, that's what MS does with seemingly every other project since Windows 95/98 - drop the ball. Let's hope MSFS can fully escape its pedigree - remember how FSX was supposed to "showcase" another flop, Vista? At least it has probably already surpassed the Zune.

If I had any complaints it would be that the toe brakes squeal a bit (but I haven't been bothered enough to try and fix it) and they tip easily when applying brake pressure. My solution to the instability was to fasten it to a 3x2 sheet of 1/2" finish board. Now they don't tip, they're heavy enough not to move on hardwood (plus I stuck a piece of that grippy toolbox liner stuff under it) and it spaces it just perfectly far enough from the wall.

Double post...

I can't say enough good things about the MFG Crosswind. Not cheap but worth every penny. As a bonus their bare-bones construction and no greasy rails makes them great in a home with pets and cleaning out the associated detritus that invariably collects around them. I used to have the Thrustmaster TFRP pedals but quickly tired of having to periodically take them apart and clean/regrease the rails.

Watching those videos actually took me back to the excitement I had the first time I actually landed (as opposed to crash) the default Cessna in FS4. If I'm not mistaken, it was a situation that set you up on the ILS 27R approach at KOAK. Felt like months before I got to that point lol. And that was flying by numeric keypad!

Clearly there is work left to be done. In my closest city (Buffalo, NY) the skyline is unrecognizable in the sim; the tallest building (an ugly, easily modeled 40 story/529 ft/161 m concrete box) is modeled as a 1 story office building! Parts of a high-level bridge south of downtown are modeled as an apartment row for some reason - as are several toll booths (which are about to meet the wrecking ball IRL anyway). And I'm sure there are many, many more examples. So if it can't get something like that correct, I'm not surprised that it can't get something as complex and intricate as a church can be. Which is fine by me - as long as we see continual improvement and refinement.

This occurs at "handcrafted" KMCO on the taxiway 'J' span over a highway (so also presumably 'E' and 'F'), so if it happens there it's probably a fairly widespread problem. Imagine my shock to see a tractor trailer climb up over the side of the bridge and come barreling towards me at full speed as I putter along in my C152.

I was able to fairly easily create profiles for my CH Eclipse yoke and MFG Crosswind pedals, and now have full functionality at least until the SimConnect issues with FSUIPC7 get ironed out. My question in the meantime is, does anybody know where these profiles are saved to your PC? I'd like to back them up somewhere in case I need them for some reason.

My first session bombed out while attempting to switch airports; it then bombed out after the "Press Any Key" screen on the next load. Funny enough, it's been fine since, so I'm not sure if it's something I did or what...

They are particularly annoying with TrackIR, as you look around and one of the buttons happens below your idle and hiding mouse cursor. I'm trying to train myself to move the cursor into a corner or onto a second monitor, but that only makes things more annoying should you need to change a dial and your cursor is now several hundred if not thousand pixels away!

Fair enough - Rome wasn't built in a day! Ultimately those updates are the key. If MS doesn't pull another FSX here, there's no reason this doesn't become the sim of choice for the next 10-20 years. Regarding the issue of "underwater boats" - the way I see it, such is the problem when you raise the bar so dramatically - the closer you get to "ultimate" realism, the more glaring those little imperfections become. I'd be willing to bet it's an actual psychological phenomenon similar to the "uncanny valley". We would have killed for more sunken boats in FS4! Similarly, during my trial last night, I was bothered by a couple of "lines" across the Niagara River and the texturing of the Horseshoe Falls just looks jumbled. Things that would be much less noticeable in previous sims. Just because I may point them out doesn't mean I don't appreciate the overall look and feel; that I can fly into a sunset and actually feel blinded, etc. Oh, and there were loads of people insinuating, if not outright stating, that this new sim was going to instantly obsolete P3D and especially XP. At least on the FSElite comments, where the "I'm not buying anything new for [P3D/XP/FSX]" comments have long become something of a meme. Unless they've all since eaten crow and redacted, they'll still be there for all to see.

I thought the same thing about the p-factor. How do you feel about rudder input? I did a couple of hours last night in various locations. Either I need to revisit my sensitivity settings (I have MFG Crosswind) or I felt like rudder was almost not necessary during flight - almost as if "auto turn coordination" was enabled. My desk has a shelf underneath it (and above/behind the pedals) and I was tempted (and almost able to) land with my feet up. Scenery needs some work too. I haven't checked the area around TNCM (it is one of my favorites) but rather stuck around my hometown. For instance, the Buffalo, NY metro looks great (some inaccuracies but nothing big) but the downtown area bears no resemblance to reality - the building heights are way off on most of the taller structures (as in footprints being correct but heights way too short) in the sim. I suspect this is true of many mid-size and large cities not covered with photogrammetry, but I would need to investigate further. As great as it looks, I still found myself wanting for my US Cities X. Also, is it just me, or is there a complete lack of navigational hazards, particularly radio towers? There are a multitude of them along the Lake Erie shoreline south of Buffalo and I don't recall seeing one. I also spent some time flying around the hills of central Pennsylvania and usually there are plenty to be found on the various hilltops.

Please lighten up. Your reaction is a bit much, as if I made a personal attack against you. It's an honest question directed to the developer. I'm sure there are many airlines worldwide where that would be a reasonable option to go along with the several other SOP-specific options that are already present in this and the other FS2Crew products. If the developer doesn't see reason to add it, then so be it. I can continue saying "no" at 10,000 feet without becoming indignant. It's their prerogative, not yours.

Is there a possibility of making the FO's initial request of "would you like to release the cabin?" a configuration option? Possible choices being say "10000 feet", "at cruise", or "Off". My reasoning is that I typically fly SWA flights when I'm using the NGXu, and from my experience they don't turn off the seat belt signs until reaching cruise - so I'm always saying "no" when he asks around 10000 feet and then kind of feel bad for him when he replies with his rather sheepish "ok" lol. I do usually reply "yes" when he asks again within 1000 feet of cruise, unless I'm in turbulence or some other condition which would preclude turning the signs off.

OK, so it sounds like my issue in both cases is because I didn't re-run the approach brief or checklist. Good to know - I'd rather it be because I'm doing something wrong than a bug! I made a summary "handbook" of sorts of the calls and flows and for some reason I put "cycle to <landing>" after running the After Takeoff Checklist, even though now I look and I don't even see that in the manual, so I don't know where I got that from. Yeah, I realize save files can be goofy, but sometimes it's necessary either to recover from a CTD, or in this particular case, practice a tricky approach without having to go through the whole process of getting the aircraft into the air. For the record, FS2Crew seems to perform pretty well off a save file; at least in the instances I've done so I haven't noticed any ill effect. The only issues I've had with such were I think with the NGX where the FO wouldn't respond audibly but would still seem to perform all the actions, so as long as you're familiar with the flows and timing you'll be OK.

I've noticed a possible bug with the flap selection on the A320 after my last couple of flights - most recently with version 3.6. The FO will set flaps 1 and 2 when requested, but will not set flaps 3 or full when either: loading mid-flight from a save file (and then cycling forward to the appropriate flow) attempting a 2nd approach after a go-around (and cycling forward to the "landing" flow) Everything has always worked perfectly for the initial landing attempt. Also, the green bar shows that the system is "hearing" the commands. This only seems to happen on subsequent landing attempts. It's as if the FS2Crew system gets reset and recognition of those commands is dependent on some action that's not being performed because its flow is being skipped.

I've seen this on my last few flights and I was going to report it. I suppose the sim must be reporting "snow" even though I didn't see any. That said, your explanation makes sense. That being said, is there a way to instruct the FO to retract them fully from 15? I commanded both "flaps up" and "flaps zero" and he ignored me so I did it myself. I'm assuming "that's the way it's supposed to be"?

I know I saw it in the documentation for something I added recently. Can't recall which; thought it was a little ridiculous, but also didn't think the setting would hurt much either so I went with it. I know there are some airports that require 5 m, mostly due to taxiway bridges and such. Probably more of an appearance issue than functionality I would imagine. A relief in the sense that it's a known bug, a pain-in-the-xxx considering that it's something that can't really be fixed, even if on an individual basis. I've seen some occasionally (most recently some smallish ones just southwest of SLVR) but I'd have to defer to someone who is more of a "settings expert" to answer that. Having a basic knowledge of how it in other applications, I think it's possible that pushing that slider to the left might actually cause more of them, or at least cause those that do occur to perhaps be a little more prominent?

Yes, as have I, although nothing like this yet. Turned it off and it still happens... As I was beginning to suspect from the ORBX thread, this was indeed the case. I actually had the mesh resolution set to 2 m! Changed it to 5 m - still happened. Changed it to 10 m - no longer happened. There was also a problem with FlyTampa KBOS in this regard I believe as well. I hit it once on a RWY 9 takeoff. Turned out there was a fix for it in their support forum. Creating a flatten to extend the airport polygon didn't help, either.

I hear you! 😣 Unfortunately it's not that - all ORBX files (including AEC) were already disabled - and the airport otherwise "appears" normal at all times, unlike as is usually the case where those Vector AEC issues are quite apparent. (I tried turning the ORBX fix "on" and it quite visibly broke things - floating runway, etc.) I believe I may have found the culprit through a little research: https://orbxsystems.com/forum/topic/161013-from-the-inca-shores-to-rapa-nui-bonus/ It seems to be that the terrain mesh complexity can't be set higher than 10 meters or else you hit "invisible" terrain. What I experienced does seem consistent with a crash (with detection turned off) where the plane just bounces off in some completely improbable manner...and I usually set mesh complexity to 5 for the sake of some add-on airports that require it. I guess I should be happy that I hard landed and didn't instead get flung to 1000 feet up at 300 kts as is usual when you faceplant. I'm curious if creating a slightly longer airport polygon would correct this. I hate having to remember to change a sim setting just to use a particular item of scenery. I'll have to wait until later to confirm this - I'll report back.

I ran into an issue landing at SCIP last night; wondering if anybody else has experienced this: On final approach (Captain Sim 757), all is fine and stable, until crossing the fence/runway threshold. Then, just as I'm preparing to flare and cut the throttles, the aircraft suddenly drops 50-100' onto the runway (well short of the TDZ) for a 600-700 fpm landing. Needless to say, quite a frustrating way to end a 5 hour flight! The initial attempt was made flying into Carlyle Sharpe's otherwise excellent "SCIP - Isla de Pascua & Mataveri Intl - Easter Island" scenery (https://library.avsim.net/download.php?DLID=185106) This is completely repeatable loading from a FSUIPC autosave file. It also seems to occur with the FSoftware Easter Island scenery. I did a little searching through my scenery folders and didn't find any obvious conflicts (particularly ORBX) nor was I able to pin down the culprit file(s). It was already well past when I should have been in bed, so my testing wasn't exhaustive (file isolation, different plane, etc.) but I intend to try to dig a bit more this afternoon. Using ORBX Vector and Pilot's FS Global 2010 mesh. It doesn't occur when attempting a landing at the default airport. Anybody else see/seen this and any suggested leads?

I've noticed since the 1.2.3.4. update that FS2Crew no longer automatically clicks the external power pushbutton at initiation of pre-flight, and that the automatic control of the doors no longer seems to be working (i.e. I have to close them manually through MCDU3). It seems as though something in the SDK might have changed, requiring an FS2Crew update? This was the update that added Connected Flight Deck. Thanks and please advise!

I may be coming in too late, but there are a couple ways to fix the hill issue: Officially, email TropicalSim support and they will provide a fix (at least they did me). As for why it's not been officially disseminated; I can't say. Unofficially, while I was awaiting a response from TropicalSim support, I diagnosed the problem and interim fixed it myself - last post on this thread over at ORBX: https://orbxsystems.com/forum/topic/160332-tist-st-thomas-elevation-issue/?do=findComment&amp;comment=1412315