cg_gunX, cg_gunY, cg_gunZ, r_znear: can you build a release with this variables unlocked?

Yaicks! I can’t wait to be released! Thanks for hear me again zturtleman! You are great code developer!

PS: I can suggest values range between -20 to 40 in the cg_gun cases? And for r_znear a range from 0.3 to 4 it will enough.

Also I’ve remembered that the Rail Gun and BFG trail path are not coded to follow the position of the model gun (in the case of the BFG the projectile always shoot out from the center of the screen). And the Rail Gun are always fixed to a static point. Here’s a fixed example of this, look:

fixed CG code path for EV_RAILTRAIL: correct rail trail start position according cg_gun

If too much all this, never mind, with the r_znear fix and cg_guns unlocked are sufficient. (may be for future future re release maybe :wink:)