Hye JimBob,The reason I mentioned PHL is because I'm from Philly too :). Therefore, I stick around PHL and PNE a lot. I actually live 2 miles from PNE, and am a student pilot there as well. Good thing there's none of those "holes" on the real life runways at PNE, as I wouldn't want to hit one in the middle of my takeoff run.

I'm learning how to use TTools, so set a bunch of aircraft to fly touch and go's out of vancouver (cyvr). It was too funny watching the ai aircraft bouncing and smoking as the taxied up to the hold point. None of them crashed, but there was a lot of bouncing going on. I've started a flight at a "bouncing spot" at an airport before that crashed me right away. Happened 2 or 3 times in a row so had to choose the airport again with a different gate. Who knows, but I've heard quite a few people mention it...rgds,billg

Joe, and others, I just taxied PNE 24 and both PHL 27R & L repeatedly and did not find what you are describing. I first used the Carenado Beech Bonanza, then the PMDG Beech 1900, at both airports. I did repeated taxi's and runs (higher speed). I never encountered what you describe. I have flown FS out of KPNE many times with many aircraft, and normally use 24. It heads me out toward my what used to be my home airport, So Jersey Regional (KVAY), between Medford and Lumbertown, NJ. Used to be 7MY when I flew real life out of it. I lived in Medford Lakes, NJ for 13 years until 1998, when I moved to Orange County, Ca.Frank P

JoeI tried the two airports and three runways you mentioned and found the bumps, but they are barely noticeable. I had to watch from the external view to even find them.David

Hi,I tried Runway 24 at KPNE also. I hit some bumps on there about midway along the runway while going 80 kts. But nothing much different than I have encoutered at other places here and there. It was enough to make some smoke, but my aircraft/landing gear wasn't damaged. I never get bouncing aircraft. I don't know what's up for the people who's aircraft get full blown crashes from the bumps. I kind of wonder if it has anything to do with where your 'Terrain Complexity' slider is set. Seems most people talking about this problem say they have lower end systems and have their sliders turned down. I have a pretty good system and have mine at Terrain Complexity(Mesh): at 85%. This probably isn't the problem but I thought I'd throw it out there anyway.Regards,Jim

AllcottI just went taxiing around KPHL at excessive speeds and then I drove over the bumps at over 100 kts with several planes and nothing happened. So this doesn't seem to be speed related to speed. Also I have stress damage enabled and full realism. This is a real mystery.David

OK,Based on all these posts I'm starting to believe that this is an A/C specific problem. I'll take some time this week and see if I can exactly locate some areas at PHL that seem to be "bumpy" and try them with A/C other than what I normally use.If I can determine anything worthwhile I'll start a new thread ( Rough taxiways crashing my planes - Part II ) and hopefully I can post an exact lat/long for folks to try. As always thanks to all for the help !!JimBob"Master of the Senior Moment"

Just a thought, if you are having these problems with a downloaded aircraft. Try comparing the installed aircraft.cfg and .air files with the same files in the origional zipped download package to see if there are any significant differences.David

David,As I mentioned in my original post I started doing that sort of stuff with the aircraft.cfg files. Thats what got me messing around with the contact points and gear compression numbers. I have had some success but not to the degree that I would have liked.The point about the air file is not lost. I'm sure I can alter a/c.cfg files til I'm blue in the face but much of that "stuff" interacts with the details in the air files ( I think )so I have to have some sort of grip on them. I'm really trying to take a more organized approach so that if I do get lucky and actually fix something I want to know what I did. It's the "old" programmer/system's designer personality coming out in me.Thanks for the interest .... hope this is not all a waste of time !!!JimBob"Master of the Senior Moment"

Hi JimBob".... hope this is not all a waste of time !!!" Why does this remind me of "the opperation was a success but the patient died"? Hmmm....probably not enough coffee. The reason I thought about comparing the installed files to the "pre-installed" was to see if they were being altered somehow during/after installation. It makes sense that these files could be the source of the problem, but why only for some people? Are identical files effecting various systems differently or are the files not identical on some systems. Anyhow, thanks for your continuing efforts and no, I don't believe it's a waste of time. Wish I had the knowledge to delve into these things.David"Master of my Dog named Jet"

David,I'm sorry, I didn't make my last post clear enough. When I said "waste of time" I was not referring to your suggestion(s) but the effort required as far as the entire problem goes. When one is trouble shooting software and does not have access to the actual code, documentation of same or someone who knows his ^%^%$ it sorta becomes like watching a baseball game through a knothole. You might see it and then again you might not !!Sorry for the misunderstanding !!!JimBob,"Master of the Senior Moment"

Well, I'm glad to see others at least saw the bumps. Whether a particular aircraft crashes or not on the bumps is not my concern. There shouldn't be bumps in the middle of what is supposed to be a smooth surface in the first place. The aircraft that I have to found to crash most is the POSKY A330. Now I'm not saying there is any flaw with their FDE; from the ammount of jostling I watch this particular aircraft do, the real thing would probably snap its nose gear as well if it hit bumps of this magnitude. I tried capturing a video clip of my experiences with a POSKY A330 at KBOS once, but even a short 6 or 8 second clip came out being like 6 MB. I couldn't find any way to compress the file size any.My ultimate point is, whether I snap nose gear or just smoke tires over the bumps, there shouldn't be any in the first place. I don't find it realistic to watch my aircraft bouncing along a "smooth" surface. I also don't want to have to turn off crash detection just so I can use the sim at all. MS certainly did something wrong if I have to make compromises to get basic use out of the software.You can probably tell I'm starting to get fed up with these scenery holes everywhere. They've been bugging me since day one.Joe Wagner

I suspect what you're experiencing is not "holes" per se, but boundaries in the scenery system that requires that a new level of detail (LOD) be loaded. FS uses an LOD system to ensure that the highest resolution data is around your aircraft and only loaded when needed. As you travel down a runway or taxiway you eventually start to approach an area of lower resolution and FS needs to load the next higher level. It loads the data and then sends a message to your aircraft that says, in effect, "the terrain has changed". Your aircraft must then recalibrate it's new altitude above ground, even if the actual change is tiny (a few millimeters). This is the same thing that happens when you go in and out of slew mode. (Press the 'Y' key a few times while in Spot Plane view to see what I mean.)All of this is well and good except that during this calibration process the aicraft reads values for ground attitude from the AIRCRAFT.CFG file and feeds them to the sim. The problem is that these default values may differ greatly from the simulated values that are impacted by the visual model's contact points and the aircraft loading. Depending on how the aircraft's landing gear spring coefficients are set you might see quite a bit of bounce, often enough to damage the aircraft. Microsoft probably tweaked the default aircraft's settings enough to remove most of the bounciness.The good news is that this can be solved with third party aircraft by the same sort of tweaking. I would guess that most payware vendors are already working on updating their coefficients. Hopefully they will post the updates here.

Sounds darn logical to me !!! Well, at least I was half or maybe more so a quarter way into the ballpark but I don't know anywhere near enough about this stuff to tweak at that level. Let's see what else I can find to screw around with .....JimBob"Master of the Senior Moment"

I have found a possible solution for this problem.This problem happens to me under the following conditions:Using add on airport.Using add on Aircraft.Taxing out of an area of dense scenery.My solution:The problem seems to be caused by some sort of conflict between the original "STOCK" airport and the add on. I fixed it by deleting the "STOCK" airport.Using AFCAD2 I did the following:Go to the country where the airport is.Open the relevant City.A list of airports in that city will show up on the right side of the AFCAD screen. The "Type" column contains the word "MOD" or "STOCK".Open the stock version of your problem airport. Right click in an empty area of the grid. From the resulting popup, select properties. At the bottom of the resulting display, you will see the file location and name which contains that airport. Example "C:Program FilesMicrosoft GamesFlight Simulator 9SceneryEURWsceneryAPnnnnnn.BGL", where "n" is a number. This is the file you will need to remove.Warning, there may be other airports in this file. If there are other "STOCK" airports, do the following:Open each one in AFCAD and then do file, save as and save it in the same directory that the original ".bgl" file was in. Repeat this for all stock airports in the ".bgl" except your problem one.You can now get rid of the original ".bgl" ,(APnnnnnn.bgl), identified above. I suggest you just rename it by changing the ".bgl" file extension to ".agl"If you back into AFCAD for the city in question, you may find that some of the airports are duplicated with a value in the "Level" column of 7. If this happens than delete the file you just created for that airport.That's all there is to it.