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
Support for extended nodes #43
Comments
|
My major concern with this request is that maps containing such extended nodes are expected to be run on ZDoom (or maybe PrBoom+) anyway and as such might have additional requirements to the engine (e.g. Boom support) that Crispy cannot fulfil. |
|
Fair enough, and truthfully, I can't think of any maps offhand that don't work in Crispy Doom right now but would work if only extended node support is added. Such a thing is possible and there are probably a few maps in existence that fix this criteria, but I can't imagine there are many. |
|
Actually, it seems that adding support for DeepBSP nodes is nearly trivial. It only required to exchange some variable types in the existing functions. ZDBSP nodes, however, are a different story. they are stored in an entirely different format. But, in the end, the code is all there and I could simply copy&paste it from e.g. PrBoom+. |
A "risky" request as you might say: support ZDBSP (and maybe DeePSea) extended nodes, to allow gigantic maps like in http://www.doomworld.com/vb/post/1301335 to be played. (ignore that that wad has other problems...)
Info about ZDoom's nodes are at http://zdoom.org/wiki/Node#ZDoom_extended_nodes. Don't know about DeepSea but I'm sure there are details somewhere. I know PrBoom+ supports both kinds of extended nodes as long as they're uncompressed.
The text was updated successfully, but these errors were encountered: