Fix major trace ray bug

The trouble with trace rays and the resulting limitations revolved around
the mistake of defining the trace ray flags as constant. This constant
would be overwritten at a later point compromising the intended effect.
Thus, the trace ray would intersect with bounding boxes along other
problems. This is now fixed, rendering the previous spell fix unnecessary.
This commit marks a major improvement.

_work/data/Scripts/Content/freeAim/_intern.d

@@ -433,8 +433,7 @@ func int freeAimSetupAimVob(var int posPtr) {
 /* Shoot aim-tailored trace ray. Do no use for other purposes. This function is customized for aiming. */
 func int freeAimRay(var int distance, var int focusType, var int vobPtr, var int posPtr, var int distPtr,
         var int trueDistPtr, var int maxPosPtr) {
-    // Flags: (VOB_IGNORE_NO_CD_DYN | POLY_IGNORE_TRANSP | VOB_IGNORE_PROJECTILES | POLY_TEST_WATER)
-    const int flags = (1<<0) | (1<<8) | (1<<9) | (1<<14); // Do not change (will make trace ray unstable)
+    var int flags; flags = (1<<0) | (1<<9) | (1<<14); // VOB_IGNORE_NO_CD_DYN | POLY_TEST_WATER | VOB_IGNORE_PROJECTILES
     var zMAT4 camPos; camPos = _^(MEM_ReadInt(MEM_ReadInt(MEMINT_oGame_Pointer_Address)+20)+60); //0=right, 2=out, 3=pos
     var int herPtr; herPtr = _@(hero);
     // Shift the start point for the trace ray beyond the player model. Necessary, because if zooming out,