I hadn't thought to just set a timer for some reason.  Durr.  Sight and sound might be interesting to mess with sometime, but I think for my current purposes considering an enemy idle 12 seconds after the last time AIF_ATTACKING or AIF_RUNNING was set is sufficient.

For the sake of documentation, since you mentioned a few, are there any other flags that aren't enumerated in the scripting engine that you're aware of?

Thanks for the insight.

I'd probably go with call StartCinema when player moved a certain distance as the best choice I know of to keep scoped movement.

I considered something similar, but it doesn't take much movement to reveal big holes in the level.  On the other hand, there aren't a whole lotta places you'd even want to use a scope on level 5, and it seems to be the only level with problems.  Maybe I'm worrying too much about an edge case?

Anyway, I've mocked up a few different methods and posted them, along with the other feature I alluded to, in the Turok+ thread for y'all to try out for yourselves.  Le'me know what you guys think.

I have a scope mostly working by using a cutscene to change the FOV, and making the camera move along with the player.  There are two technical problems, though:

1. Sector properties are not updated when moving from one sector to another (e.g., fog color and distance don't change when entering/exiting a cave).  This one's not so bad, since players are unlikely to move too far while scoped anyway.  I could also disable the scope if you move too far, if I really wanted to minimize the issue.

2. Level geometry occlusion doesn't always update.  So, for example, if you zoom in, then walk around a corner, any level geometry that was originally blocked will still not be rendered (screenshot).  I think I've only seen this happen on level 5 (even the corridors of level 8 seem fine), but it's a pretty big error to expect players to just re-scope and ignore.

Currently, as a workaround, I have it so you can't move while zoomed in.  If you try, it just deactivates the scope.  This isn't terrible, but it's kinda clunky and feels like a lame compromise.

Anyone have any idea if there's some "proper" way to update the camera so sector properties and level occlusion actually get updated?  Here's how I'm doing it currently:

when activating the scope:
Camera.StartCinematic( CMF_NO_LETTERBOX | CMF_SHOW_HIDDEN_OBJECTS | CMF_NO_INITIAL_FADEOUT );
// at least one of these allows camera position to be updated in OnTick() after key acquisition cutscene
Camera.ClearLookAtActor();
Camera.ClearFinalView();
Camera.ClearViewTracks();
in OnTick(), while scope is active:
kStr s;
if ( Sys.GetCvarValue("r_fov",s) )
Camera.fov = s.Atof() / ScopeMag;

kPuppet @owner = self.Owner().Actor();
// update camera orientation
Camera.origin    = EyePos();
Camera.pitch     = owner.Pitch();
Camera.roll      = owner.Roll();
Camera.yaw       = owner.Yaw();
I tried using Camera.SetEyeView() to see if it would more robustly update the camera's position, but it did nothing on its own, and fixed neither issue when used in conjunction with setting Camera.origin.  I've also messed with some other camera functions, but haven't been able to get them to even do anything. :/

I think the tranquilizer has another mirrored texture wrapping error like the plasma rifle did.

Top is unmodded, bottom is with scope U coordinates doubled.

But honestly, failing all of this? I think just making it upgrade the shotgun and having it only consume 1 shot despite shooting more, would be the best compromise. I don't think players will care all that much, I don't think any of us really cared in Turok 2 that it was double barrel and only used 1 shell.

Either way, its a really cool proof of concept and I'm just excited that you got animations working which I'd like to ask how you did it, if possible? Animation support has been halting my more complex ideas.

Using only 1 shell is a cosmetic issue in T2.  In T1, it's a balance issue -- the difference in ammo efficiency between the double shotgun and auto shotgun would be pretty big if it only used 1 ammo.

Animations are just converted from T2's format to T1's.  They're mostly the same, so it wasn't that hard.  Converting from other formats, like obj or something, will require more research.

Hey Smoke any reason why some mods are not compatible with each other?  I use your mod and Level mods but every time i start the game via Editor Mode a box always pops out.

Like Jay said, if two mods try to override the same file, they'll conflict with each other.  I think Duke's maps only include main.txt to make "new game" start his map.  If you subscribe to Turok+ after the map (to make it take precedence in the load order), and load the map manually, it might work.

I advocated for reorganizing main.txt in the base game to reduce the chance of maps and mods conflicting over it, but never got a response.  We could do it ourselves, but it'd require everyone agreeing to the standard, and would be an additional hoop for players to jump through.  And there'd still be other files that could be in conflict (e.g., the defs files).  Kex just isn't very modular when it comes to its file structure, so it's kinda inherently prone to conflicts.