I'm one of the people currently experiencing the issue in which custom levels would formerly freeze on the loading screen, and after Update 9 revert to The Original Classic when done loading. This is occuring on both my computer and my brother's, after following the instructions on the level editing guide and loading a sample level without modifying it. One thing I noticed when using Unity to design my level is that certain objects (for instance, the ObstacleSelection and VehicleSelection objects) contain Mono Behaviour components with their Script parameters marked as 'Missing (Mono Script)'. Given that this occurs both in objects and the prefabs provided by the Assets Package downloaded from the Turbo Dismount website (as currently linked to in the level editing guide - http://turbodismount.com/editor/td_editor_package_v2.zip for reference), I'm wondering if Unity is trying to reference scripts that were not included in the latest version of the Assets Package and Turbo Dismount is failing to load the level as a result.

To those of you currently not experiencing this issue, would you mind answering a couple of questions to help me find out if my assumption is correct?

1. Did you download the Assets Package before or after people started reporting this issue?
   
2. Do your ObstacleSelection and VehicleSelection objects contain Mono Behaviour components that are missing their scripts?
   
3. What scripts does your Assets library currently contain? On my project I have LevelInfo, NodeInfo, NPCVehicleCatcher, NPCVehicleData, NPCVehicleSpawner, PathInfo, PathNode, TDLevelTool, TDResource, TDResourceInspector, TransformExtensions and TurboDismountMiniJSON. Do you have any that are missing from my list?

If you answered yes to questions 2 or 3 then it would seem the current version of the download is what's causing the problem. If the developers are okay with such a thing, would it be possible for someone to upload their working copy of the Assets Package (or point people to a mirror/older version of the package) as a workaround until the developers can sort out the official download?

Alternative solution is that those scripts are meant to be missing and the problem is caused by something else, but it's at least worth a shot ;)