source-sdk-2013
source-sdk-2013 copied to clipboard
Cannot scan map files inside vpks for embedded files.
Map files inside vpks cannot be scanned for embedded file check. How to reproduce:
- Make a map
- Include embedded files in it
- Package it in a vpk
- Load the map
Note that on the console it says: "Couldn't open vpk.vpk/maps/map.bdp for embedded file check"
You need to put vpk into a mod folder, not map
You need to put vpk into a mod folder, not map
This is something else.
What the original issue is is that if Bernardo embeds files into a .BSP pakfile and adds the .BSP to a .VPK directory, then proceeds to load the map, the engine will seemingly fail to parse the .BSP to view its embedded contents.
It seems that most developers will tend to not do this and instead store .BSPs in an unpacked Maps folder, since .BSPs must be kept out of the .VPK directory or else they will become unreadable.
Afaik in Alien Swarm it works fine.
вс, 18 апр. 2021 г., 10:29 SC1040-TS2 @.***>:
You need to put vpk into a mod folder, not map
This is something else.
What the original issue is is that if Bernardo embeds files into a .BSP pakfile and adds the .BSP to a .VPK, then proceeds to load the map, the engine will seemingly fail to parse the .BSP to view its embedded contents.
It seems that most developers will tend to not do this and instead store .BSPs in an unpacked Maps folder, since .BSPs must be kept out of the .VPK directory or else they will become unreadable.
Afaik in Alien Swarm it works fine. вс, 18 апр. 2021 г., 10:29 SC1040-TS2 @.***>: … You need to put vpk into a mod folder, not map This is something else. What the original issue is is that if Bernardo embeds files into a .BSP pakfile and adds the .BSP to a .VPK, then proceeds to load the map, the engine will seemingly fail to parse the .BSP to view its embedded contents. It seems that most developers will tend to not do this and instead store .BSPs in an unpacked Maps folder, since .BSPs must be kept out of the .VPK directory or else they will become unreadable.
Based on a small amount of VDC skimming, that may be due to some sort of file formatting issue I do not fully know about.