cant find file in package

[Skywolf]

i have made a level but when i want to open it it says: cant find file in package: starship.deco. i have only used the textures of the startship package and saved my level as starship.unr. when i open it in unrealED i have to open the starship texture package first before i can open my level. any idea how i can make my level working?

[Skywolf]

btw: every level that uses the texture package cant run and copying the package from the cd to the game doest work

[[]KAOS[]Casey]

don't name your map the same name as a texture package, or really any other package name. the package loader gets confused

just rename the .unr and you should be fine.

[Skywolf]

explains why nali castle is named to nalic not nalicast

thanks i has to know this

i still dont know why this happens, textures are in a other folder than the levels :-?
but there are many more things about uneal that i cant understand so this is not the first time (and not the last time i gues)

[GreatEmerald]

Unreal isn't aware of folders. It sees all the folders as one, huge folder. It is also not aware about the extensions, so .unr is the same as .utx. So when you try to launch your map that has the same name as your texture package, the game thinks that the texture package IS your map package, although there are no textures in it whatsoever.
That also explains why it's Vortex2.unr.

[creavion]

Thats right. I opened recently by mistake a map file in the texture browser (dont ask me who this could happen, I dunno), the result was the mylevled textures of the map were shown in the texture browser with the map name. Nothing bad happened after all, no crash or something like that.
I also know a lot of people who named e.g. a texture package as like a static mesh package and wondered about the problems and wondered even more after I told them that this should not be made...
The folders just serve as orientation. I mean you can also load a static mesh package (still speaking of UEngine 2, but it does not matter) in a texture package.

[GreatEmerald]

And one good way to make sure things like that don't happen - use the Legend naming scheme. Maps have normal names, textures end with T, sounds end with A, Static Meshes end with S, music ends with M, animations end with K etc. essentially every package file ends with the middle letter of the extension - utx with T, usx with S, ukx with K etc. That way there's no way you could confuse the engine.