Oh man .... this is so sad.
I pressed the file through the UTCMS inspector and it found no LevelInfo in there. Or if it found it was faulty. It also reported that Your map uses no other than the official textures, sounds etc.... No LevelInfo - no map.
This isn't the first time UED would do stupidities like this. My best guess for what has gone south is that You have loaded some other map in editor and then loaded Your own map without exiting the editor first. In cases like this, there are always some crap left in editor memory from the first map. The worst of them is ofcourse the LevelInfo which is crippled if You load maps on top of each other. I always restart the UED when I start editing my maps. If I need to copy things I use intermediate files (import-export) for that.
There is a good reason why UED behaves like this (texture caching for one) but the execution is poor especially when You change maps.
I tried to salvage the map by several ways:
- giving it an texture package "Level None.utx" which had this MyLevel texture
- Doing this with Sound and Music types as well
- Made an empty map and renamed it to "Level None.unr" and then tried to start Your map
- Renamed Your map to "Level None.unr"
- Renamed Your map to "None.unr"
None of these helped... and then I pressed it through this UTCMS and it gave the reason: No LevelInfo in the file.
Then - I looked the map with UTPT (Unreal Tournament Package Tool) and that revealed that both import and export tables were corrupted (filled in with zeroes).
No data is incurable but this one would be extremely difficult to restore. Loosing contents of those tables (they tell the map loader where different things of the map are in the UNR file) is like formatting Your HD. It can be cured but it is very hard.
Once more - I REALLY wish there would be an easy way of doing it. It it could be done by a program I would gladly have spent the 5 hours in doing that (if nothing else, just to show myself I can do it).
Backups Rule !
Now, to cheer You up, I tell about one accident that happened to me when I was a newcomer in IT business ... more than 15 years ago:
It was a NOKIA PC (Yeah, NOKIA has also manufactured PC:s) left by a customer for file repairs and it had a GIGANTIC 40Mb hard drive. The OS was MsDos V1.2 (or somethig like that). As I was very curious I started to "try" the different commands available in there. Format sounded pretty dangerous so I passed by it ... recover.exe ... mmm... that was interesting. The session was like (I can still remember the green phosphor screen):
C:\> recover <ret>
MsDos Recover V1.2
Missing drive letter
C:\> recover C <ret>
MsDos Recover V1.2
Press any key to start recovering drive C <ret>
Recovering ......(dots appearing)
Finished recovering drive C. Press any key to continue <ret>
C:\DOS\COMMAND.COM not found ... press any key to continue <ret>
After finding out that there REALLY was no more COMMAND.COM around I decided to reboot the machine:
Non system disk - press any key to continue
After I rebooted the machine with a floppy (5 inch, 640Kb) I realized what recover actually does. The darn thing had moved each and every file, including directories into the root directory of C: and then renamed them FILE0001.rec, FILE0002.rec .... FILE0957.rec. One thousand or so files with no idea what they were originally named. All data was there .. yeah .. including the customer database. Spent three weeks "recovering" that thing. Had no backup - either
.