OpenArena Message Boards

To work around the "mature pak" method and make the control engineside for more versatility across mods and servers i'd have to rethink the system for oa3

- A shader comment keyword that gets parsed if r_mature is 0 (//NONMATURE), for replacing skins/textures for content (such as turning blood into blue or giving someone a bra)
- Before looking for LOD meshes, look for a mesh with a _n prefix first if r_mature is 0 (such as turning gibs into candy and giving someone a solid skirt)
- Do the same for sounds (such as skelebot's 'kiss my ass', the only objective sound effect in. Also this could bring back the use of 'holy shit' as an option). s_mature would be the cvar here

I could probably code all this and make it a patch.

I suggest to divide the commands about removing gore from those about removing nudity.

I have no problems playing a game with the gore level of Q3... but I have problems playing a game with naked girls...

... but about the "bloody" part, weren't there already some variables to limit the violence? I did not try them, but I'm quite sure in the wiki (probably in "manual" and "faq") they are mentioned...

Even if the gibs are invisible, they still make splatter noises. However the existing gib control seems cgame based, and my renderer-based approach could do stuff about blood-stained floor textures :P

also doing things engine-side could lead to more acceptance of some touchy distros having it in their repository since they could compile with r_mature permalatched to 0 and still have online compatibility.


I also have problems playing a game with naked girls.  It's not that of the nudity but that would affect the tone of the game overall usually turning things into a shameless smutfest atmospherically, losing the point of...*cough*gameplay*cough*.    However I don't consider OA to be one of those voyeuristic games of concern, it's more along the lines of a fighting game such as Power Instinct, and of course Darkstalkers

I find your post on nudity rather ironic, looking at your avatar... :P

Revisited this feature proposal and implemented.......

r_suggestiveThemes (default 1)

What it really does is just looks for a _safe prefixed model if available and loads that instead, if it finds one.  This _safe version is manually crafted to have less edgesplitting, uvmaps that cover up more, and the breast bones unweighted (no bouncing), leading to a less provocative appearance.  However this has more of a chance to mess up skins and introduce seams.  Because of that I don't really recommend setting it to 0.  I know some players here may raise an issue about the new character designs so I have made a optional choice for a less 'offensive' verison without much pak bloat added, and without the need for having separate 'mature' paks.

Skins are not altered at all, as this is only applying to mesh loading only.  

The mesh on the second picture seems to have just a bit too much cleavage to think there should also be some nipples somewhere.

Wow, cool!  :)

I agree :P

Maybe some little more cover for those boobs make the difference.
(i mean very little :P  :P )

 ;)

Ehm... does anyone read that it's the purpose of r_suggestiveThemes 0 to hide such stuff?

 :P :P

;)

(Note: this part has no relationship with r_suggestivethemes variable)
About that, Fromhell's idea is explained in this animated gif:
http://openarena.ws/board/index.php?topic=4409.msg44392#msg44392

About the new feature itself, it seems great... although I haven't completely understood its behavior: if there is the need that the model creator does create a "dressed up and not bouncing model", cannot he also create a custom "_safe" skin to perfectly fit it? Or maybe the "_safe" version isn't a complete model, but just a tweak of some parameters or something similar? Sorry, I'm extremely noob with models...

The skin texture is identical, as I do not want to duplicate textures.  No new .skin files.


Also I took that screenshot at a slightly bad angle.  Here's a more fair picture