-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Titanfall Map Decompile Error "Couldn't find static prop struct for appId 1454890, version 12, size 84" #161
Comments
I can confirm that this failure to write lumps also affects NEOTOKYO maps, and is version-specific to BSPSource 1.4.3. Version 1.4.2 does not fail to do decompilation in this way. |
@POLY-021: I don't really now to what degree Titanfall 1 was ever supported. There is code to at least load the bsp files of titanfall, but not really any to handle writing the data to a vmf. I'm not familiar with Titanfall, but I think their map format greatly differs from normal source games, so I'm not sure if the maps could even be convert to vmf files that the normal hammer editor can use. @SC1040-TS2: I don't know NEOTOKYO, but if it's not a game based on Titanfall, your issue will probably be something unrelated to this. Can you share what exact error you're getting with 1.4.3 but not with 1.4.2? |
Afaik Titanfall 1 wasn't ever really supported, iirc ata4 got some info on lump names from cra0 back in 2014.1 I've made a Skimming through bspsrc, I can see trying to support Titanfall next to all the other Source Engine formats being a lot of work. Titanfall 2 isn't too dissimilar to Titanfall 1, but my decompiler currently breaks trying to link brushes to entities. Apex Legends (mentioned in #59) removes almost all the lumps used when decompiling Titanfall 1 & 2 maps.
NEOTOKYO3 uses a standard VBSP v20 format, similar to Team Fortress 2 Footnotes
|
That's good to know. In that case, I don't really have much motivation to try to add some kind of support. Currently, bspsrc assumes a common ground between all bsps with contains things like brushes, brushsides, texdata, etc. (Basically what's in BspData.java). So trying to support Titanfall in bspsrc current state would indeed probably be a lot of work.
I already got a suspicion that it has to do something with staticprops not being read correctly. #164 has the same issue. The 'generic' static prop version definitions in bspsrc seem to be incorrect for the majority of games. I really need to get an overview of what kind of engine branches there are and how their staticprop versions are defined. Thanks for mentioning your bsp_tool though. That's going to be very helpful in cross referencing all the static prop definitions. Do you perhaps also know how accurate the |
The VDC wiki definition looks accurate to me, tho it’s been a while since I implemented static prop definitions in bsp_tool |
I'm attempting to grab static props from Titanfall 1, and BSPSource does have a "Titanfall" option for the BSP format. However, when I try to export, it doesn't export things properly and spits out a 0 kb file. Any help?
The text was updated successfully, but these errors were encountered: