GtkRadiant icon indicating copy to clipboard operation
GtkRadiant copied to clipboard

Surfaceparm-issues when converting map to other game

Open admafi opened this issue 8 years ago • 9 comments

When you convert a bsp from one game to another, surfaceparms can get mixed up. Means, surfaces can suddenly be slick or hurt when they shouldn't. This is probably a known issue, however is there a possible fix for that?

admafi avatar Dec 09 '17 13:12 admafi

Pretty sure there's not a whole lot you can do and it's stipulated that such things happen in the readme.

I gather a translation might be possible but it's in bits so it will take some clever conversion engineering.

Could also run into issues with custom info parms feature. How would the conversion know if the original had used such thing?

ensiform avatar Dec 09 '17 20:12 ensiform

Theoretically we can use surfaceparms names from games.h to deduce correct flags. But that still wont be 100% reliable solution.

Garux avatar Dec 13 '17 11:12 Garux

BSP does not store surfaceparms by name, only as a bitflag integer.

ensiform avatar Dec 13 '17 23:12 ensiform

games.h do that though!

Garux avatar Dec 14 '17 08:12 Garux

Does what exactly? I thought it was a list of strings that maps to the integer value

ensiform avatar Dec 15 '17 14:12 ensiform

Does store surfaceparms by name, not only as a bitflag integer.

Garux avatar Dec 16 '17 12:12 Garux

Would be nice if there was at least a workaround

admafi avatar Dec 28 '17 13:12 admafi

Well I mean it wasn't ever designed to be used for perfect porting purposes, given that ports are kinda grey area legally.

ensiform avatar Dec 28 '17 20:12 ensiform

I'd suggest a plugin maybe, to which you would tell the game you loaded the map from, and what surfaceparm you'd like to convert to. That's not something we (GtkRadiant) will be writing any time soon though, but it sounds easy enough.

TTimo avatar Jan 07 '18 03:01 TTimo