Nothing in sight and the flight fails due to false collisions on the taxi. Should never fail for being on wrong taxi unless you offer the realistic progressive taxi from the controller or actually hit something. Ground controllers can and do help people when a progressive taxi is asked for. Both of these issues are faulty and unfair to pilots. Imaginary failures… Z, G, WF and failed on Z and after restart failed on G at DFW for no reason at all.
Not the greatest solution for some, but until this gets fixed, turn off the damage options!
Are you hitting cracks in the taxi pavement? Sometimes I have run across a part of the taxi where the pavement is cracked and rises up. When you hit the fault it causes a crash.
I suggest you turn off crash detection as mentioned above, as the contact points and object boundary/ terrain contacts can cause false collisions. Its best to keep them options off.
Thanks for the tips. I was right on the yellow ground marker but might have been on the wrong taxiway. The taxi was very wide and there was nothing on the ground or shown on the taxi the first time. The second time I went into the grass because I wasn’t paying attention and then back on to the taxi and it immediately failed it because of that. In comparison, once I completed the exit i was met with winter conditions in Minneapolis, overshot the runway because they gave me bad barometer settings for landing, and my landing gear didn’t go down. I survived the belly landing, got the plane completely off the runway and onto the taxi that way. Raised the gear and it worked s I drove to the parking area. A little worse than going in the grass. lol I appreciate the tips!