FSDreamTeam forum
Products Support => Los Angeles support FSX/P3D => Topic started by: AirBorne on May 02, 2014, 01:08:56 am
-
Hello,
I've been trying to make a short flight from KLAX to KSFO with 777 PMDG and when I'm taxiing to RWY 25R about halfway the taxiway next to it the plane just crashes and the view goes outside, then the flight reloads. It's the fourth time it happend already and I haven't found a clue on it. Does anyone know what is wrong here?
Thanks!
-
It would be helpful to know what the crash message said, since the message is not exactly the same if you crashed onto an object, the terrain or an AI.
A possible reason might be an AI you can't see, because it's an FS9 model and you have the airplane shadows off, so FS9 AI models can't be seen, but will still cause a crash. Another possible reason might be a bump caused by a 3rd party mesh you have installed, which is causing the airplane to tip off.
The only thing sure, it's nothing related to the scenery, for the simple reason that, all our scenery objects have crash detection removed, which helps with fps, so you can't crash on them even if you try.
-
The message is just "CRASH", and it happens on B somewhere close to C5, no matter what direction i'm taxiing on B.
And visually speaking, there's nothing wrong, no signs of objects, terrain spikes, and the like whatsoever.
-
AI crash is disabled, since it's known for a long time, since the earlier versions, the crashes occur even when you're a little bit far from the other plane.
-
I just checked again, it seems to happen right in the spot where a road passes underneath the taxiways and runways that side of the airport. And the plane doesn't jump or behaves erratically, it just crashes.
-
If you mean the crossing between taxiway C and the road underpass, I've just checked it now, twice, once with the default 737 and once with the PMDG 777, and there's no crash.
Nobody ever reported it before either.
Have you set the Mesh as suggested in the KLAX manual, with Resolution at 5m/pixel and Complexity at 100 ?
-
Yes I did, just to make sure.
MESH_COMPLEXITY=100 (has always been like this)
MESH_RESOLUTION=23 (changed today in order to check, it was 25 before)
But still happening.
-
MESH_COMPLEXITY=100 (has always been like this)
MESH_RESOLUTION=23 (changed today in order to check, it was 25 before)
But still happening.
Doesn't happen here, but I have Mesh Resolution to 22 ( 10m ), try that. However, 5m should be fine, and it's what we tested, but of course this might change depending which 3rd party mesh you have.
-
I have FS Global Ultimate. It's still happening, very wierd indeed.
Happens on both sides, on all outer taxiways when passing over the bridges. Visually-wise, there's nothing strange at all (like seen before in KDFW)...
-
I was able to cross it in a small single engine airplane. Perhaps the 777 is striking its wingtip or something in an invisible object? Now I just tried to cross the small plane closer to the edge of the bridge (in the edge lights area) and in fact it crashed.
-
There's no invisible object anywhere in the scenery, and the crash doesn't happen in the scenery. It can only be caused by a combination of settings and/or 3rd party meshes. Those meshes aren't usually pre-processed and smoothed out as the default mesh is and, due to how FSX works, higher resolution mesh will *always* take precedence, regardless of the layer ordering in the Scenery Library.
Not all airplanes reacts in the same way to a terrain hump, so it's absolutely normal you might not see on all airplanes, but again, it's nothing related to the scenery.
A way we might prevent it in *theory*, would be supplying KLAX with a FLAT mesh of an higher resolution than any 3rd party mesh out there but this, on top of being a waste of memory (potentially causing OOM that users would attribute to KLAX, when if fact it would be needed to correct other 3rd party meshes faults), it doesn't really work in reality, because when using such higher resolutions, rounding issues and artifacts will creep in, causing terrain "spikes" that will cause crashes all the same.
-
FYI - I am experiencing the same issue. I see a protrusion that looks like rocks. It is at the intersection of C and C4 taxiways heading East. I taxied over it by mistake (OK maybe I was under the idea that it was a visual anomaly alone, but it wasn't). I think there is an issue with flattening the area - I have FSGlobal Ultimate with terrain set to max and I run VRS TacPack so turning collisions off is not an option.
-
FYI - I am experiencing the same issue. I see a protrusion that looks like rocks.
That's because you have set your Mesh resolution too high, and not as suggested in the KLAX manual ( the "Design Notes" section ). It must be at 10m/pixel and not higher, because at higher resolutions, FSX will display such artifacts that result from oversampling data and rounding errors.
-
FYI - I am experiencing the same issue. I see a protrusion that looks like rocks.
That's because you have set your Mesh resolution too high, and not as suggested in the KLAX manual ( the "Design Notes" section ). It must be at 10m/pixel and not higher, because at higher resolutions, FSX will display such artifacts that result from oversampling data and rounding errors.
Sounds good. Thanks for the quick reply. Now on to my KLAX-VHHH flight ;)
-
Hello
I must sadly report the same issue, and it happens with both PMDG 737NGX and default 737's, and exactly when you pass over bridge at taxiway C, between C6 and C5, and in any direction.
If you stay at taxiway Bravo you have no chrashes.
I have FS Global installed, but no other scenery or local meshes for the area, and i allways fly with crash detection on for the realism.
The mesh resolution and complexcity is as per the manual 5m/pixel and 100. I have tried the 10m solution with no result.
Turning off Crash detection solves the problem, so i suspect it to be another crashbox issue.
I hope for a nice solution, because KLAX is just a smashing scenery !
Take Care
JP
-
Turning off Crash detection solves the problem, so i suspect it to be another crashbox issue.
It's not a crashbox issue. No object in FSDT KLAX even have a crashbox to begin with, and thing you are crashing on it's the mesh, NOT the scenery.
As I've said in my previous reply, there's no invisible object anywhere in the scenery, and the crash doesn't happen in the scenery. It can only be caused by a combination of settings and/or 3rd party meshes. Those meshes aren't usually pre-processed and smoothed out as the default mesh is and, due to how FSX works, higher resolution mesh will *always* take precedence, regardless of the layer ordering in the Scenery Library.
Not all airplanes reacts in the same way to a terrain hump, so it's absolutely normal you might not see on all airplanes, but again, it's nothing related to the scenery.
A way we might prevent it in *theory*, would be supplying KLAX with a FLAT mesh of an higher resolution than any 3rd party mesh out there but this, on top of being a waste of memory (potentially causing OOM that users would attribute to KLAX, when if fact it would be needed to correct other 3rd party meshes faults), it doesn't really work in reality, because when using such higher resolutions, rounding issues and artifacts will creep in, causing terrain "spikes" that will cause crashes all the same.
-
Hello Again. and thanks for Your Quick reply.
To have it absolutely clear. If this is a Mesh problem (with FSGX 2010) How should the crash be shown in FSX (Crash or Object Collision or..?) it triggers me that changing the mesh setting does not produce any change, but turning off crash detection solves the problem.
I think i have to adress the problem for the folks at Pilots, because im not the only one having the issue, and have a very standard configuration.
I have no problems at other FSDT airports like KDFW,KJFK,KFLL,LSGG etc. but it is SO tiresome to prepare a flight just to be wiped out few minutes after gate departure :(
Take care
JP
-
If this is a Mesh problem (with FSGX 2010) How should the crash be shown in FSX (Crash or Object Collision or..?)
There's no such thing as a "crash on mesh" message in FSX so, it might appear either as just a "crash", or an "object crash", without this mean anything.
but turning off crash detection solves the problem.
Of course it does. Where you expecting any differently ? It's obvious that, if you disable crash detection, you will never crash into anything, *including* over a mesh.
You can do a simple test:
- Does the crash happens if you DISABLE the 3rd party mesh from the Scenery Library ?
-
Hello Again
I have now tested KLAX without ANY other scenery product active, and the problem still exsist. i Have closely looked through the Scenery/World/Scenery folder, but nothing to be found.
I enclose a PNG shoving the location, the crash ocures when the wingtip is close to the Concrete foundation (Part of the tunnel).
Thank You for any Suggestions.
JP
-
I enclose a PNG shoving the location, the crash ocures when the wingtip is close to the Concrete foundation (Part of the tunnel).
Alright, that's useful. Have you tested it with different planes ? Do they all crash the same ?
-
I have tried it with the PMDG 737NGX and the Default 737, both with same result.
Today i tried it with the Default Beach Baron. When i stay ON the taxiway (wingtip far from the concrete wall) i do not crash.
When i enter the Green Area adjacant to the taxiway (without the wingtip are passin direct over the concrete Foundation of the tunnel) FSX crash.
So it is enough it is close to the wall, and not colliding with it.
-
I have tried it with the PMDG 737NGX and the Default 737, both with same result.
We just tried it now, with the default 737-800, but couldn't replicate the problem. Are you *sure* you tried with the default 737 ? I know for sure the PMDG 737 is more sensitive to small ground bumps.
If you are sure the crash happens with the default 737, check the AFCAD in use, with the GSX customize airport positions menu option, the customization dialog will show you the name of the AFCAD in use.
-
Hello Again Umberto
The jpg i enclosed IS the default 737 plane, as where the Beech Baron tested. There are no diff. if i try it with the PMDG 737NGX or the default, and the crash occurs on the last 1/3 of the taxiway over the tunnel heading east.
I was not able to make a crash with the default ultralight no matter how close i got to the concrete wall though.
I have checked the Afcad, and it is KLAXV2/KLAX_AP.bgl
-
I have checked the Afcad, and it is KLAXV2/KLAX_AP.bgl
Then, the problem can only be caused by a 3rd party mesh. As I've said, we tested it in every possible way, moving close to the wall on either side, being on the centerline, having the wingtip over the bridge, and there are no crashes whatsoever.
Disable every 3rd party mesh you use and try again.
-
Sorry to hear there is no solution, but as i said earlier, i have tested KLAX with a completely "Clean" scenery config. (enclosed)
I have made my own solution though (jpg), and while doing my own Little fix-file with Instant scenery, i noticed that the elevation differs a lot in the area where the crash ocures (obects sink through the tunnel roof), so maybee that have bearing to the problem.
Case closed from my part :-\.
Take Care
JP
-
This is just awesome, eheheheh! How did you do that, what tool(s) have you used?