Planes falling into runway @ startup p3d

Hello everyone, I have not made an account here until now and have frequented this site/forum community for most of my needs for years and absolutely love the setup! With that being said I have some very exciting information on the: "Planes falling into the runway Issue" You all know that one!!! Now I am currently making sure other combinations of executions don't derail it into mayhem literally out of the blue clear sky LoL!!! So Ladies and gents here are the current findings and a quick footnote about the particular finding. Oh and you will need to have the view options of your file manager setup to show hidden system files and of course when editing system files or hidden files it helps to have Administrator privledges if not logged in as Administrator!!! 

Navigate within File Explorer to:

c:\users\user_p3d_is_used_from\appdata\roaming\lockheed martin\Prepar3d v4\

Now right when you open it up you may notice a folder called temp, I actually became aware of the game creating this folder when the issue arose today!!! I don't know if the game is attempting to take your last plane and airport of choice then restart another instance at per say the closest airfield upon crashing on take-off, I have not checked to see if it is doing this when you crash period or not. But then the cycle of never ending spawn die happens causing us to alt + f4   ctrl +  shift  +  escape  the game bye bye only to reload it again!!! Now I don't know either if the accu-feel is the culprit or not yet either, have to uninstall and clean registry, manually delete directories and really approach it more aware!!! I left the temp folder alone but if you go into it, and I am sure you can delete it and it won't harm your install, but upon going in the files in there are named: Program generated temporary scenario. That is what gets me assuming this is triggered upon a disastrous takeoff and causes the "crash loop". To stop the game engine from generating these scenario files that clearly get us sideways in a literal sense you need to:

Edit the Prepar3d.cfg file in the c:\users\p3duser\AppData\Roaming\Lockheed Martin\Prepar3d v4\    directory

Once you have Prepar3d.cfg opened in Notepad or text editor of your choice search for:      demo

put two forward slashes in front of both lines  "//" that the text editor finds, which are DEMO=0 or 1 and Startup_Demo=         . You can press ctrl + F once the document first loads to quickly access the find feature within the editor. Now SAVE and exit the text editor. Go up three directory levels where you will see the three folders listed

Local, LocalLow, and Roaming Then you enter the "Local" folder/directory, Lockheed Martin, Prepar3d and copy Prepar3d_Default.fxml and paste it in the same directory causing a backup copy to be made. Then open the Prepar3d_Default.fxml with your text editor and search for:     height  there will be two entries yet again but these are actual Property Names the engine uses statically and the values on these height variables will be -999999, somethin just isn't adding up with these figures LOL. That means the game engine has been planting us under the airfields!!! See models ignore collisions if normals pass through them 180 degrees from their face value and that's why none of us really caught it because it literally was trying to make up for -999999 units in a split second to get the normals for the tires positive and in contact with a surface, that's why we were getting all sorts of cartwheeling, and forward flips with sideways cartwheels because the entire weight of the plane would be transferred to the first vertex the tires contacted with!!!! So I changed both -999999 values to 4  ;Yep just 4 units which I am pretty sure is 4 feet in the game world! Now that positive whole number of 4 has worked well from tail draggers up to the b50 and c130s no issues!!! I was slammin wings into control towers and runnin up in hangers at 200 mph, hittin gas pumps and everytime it restarted perfect!!! Oh and I did my little airport terrorization at the same airport but with a different plane everytime all I did was hit alt and then select vehicle hehe🙂 It 100% absolutely fixed it!!!!!!!!!!! I have noticed upon further investigation that the DEMO= AND START_DEMO= fields have returned after my crash testing and do not know if that will cause the problem to return and therefore we must comment those out before simming but as I mentioned before I need to dig more to answer my own questions for self gratification LOL But seriously I have never seen a demo on Prepar3d what if while we load up for the next flight we are supposed to see our previous failure play on a loop in the background! I can tell you folks that I was reading alot of posts all over the internet and no one could quite pin this one down! Until I came across a post a gentleman was making a plane totally from scratch and the bug hit him, and he had some very knowledgable gents helping him, and they thoroughly believed that it was the height at which his landing gear contact points were set, man were they close, the poor dudes plane didn't have an issue and in fact the issue was a height variable out of whack!!! It just so happened to be the main one all objects use for a reference point. I hope we are able to make more sense of these findings and what it is that is causing the reference numbers to drop to -999999 oh and the sim ran smooth forever with this issue but now it runs smooth word not allowed sillllllk. I turned everything up MAXxxxed the ef out and the dang thing didn't miss a lick!!!!