Here's how VSLib is coming along. The documentation is like 1% done lol. I still haven't uploaded the actual library yet. I'm waiting for some updates from Valve to add the features that are quite needed.

http://zombiescanfly.com/vslib/

Awesome! Looking forward to testing that!

How do you plan on recording dynamically created particles? Not possible without some kind of entity spawn listener.

I see. So your script basically takes a bunch of origins and angles via a think function and then exports them "frame by frame" to play back a certain animation?

How does the exporting work? Do you just copy the origins/angles to a SMD file via a filesystem class? I'll give the code a look when I get home-- I'm kinda curious :)

May I ask, how does the recording and playback work?

Wow vsscript2smd looks awesome! Definitely gonna give that one a whirl as well.

What we really need is OnGameFrame(). I updated the VScript suggestions thread asking for something that fires more often.

Ah yes, that would be much more elegant. Code updated, thanks :)

Originally posted by Rectus:

One question about the cubemap textures (i hope this isn't too OT either). Is there any gain from packing them into the vpk? It's the same textures that get packed into the .bsp, right? I've seen them inclued in a few campaigns, but never noticed any missing reflections when I've tested my vpks without them.

If it's already embedded into the BSP, then you do not need to separately include it. You can use Pakrat to scan the BSP:

https://developer.valvesoftware.com/wiki/Pakrat

A cool idea for Campaign Packager is to scan the VMF itself for models, materials, sounds, etc. Then it can recursively search through and include related files. If you need a VMF parser, I wrote one in c++ a while back which I can share. Maybe you can convert the code to Perl?

Anyhow, I used Campaign Packager and it worked flawlessly for me. Gonna be super helpful :) Thank you sir!

Is that so? And you were testing on a listen server I presume?

I wrote this simple stock a while back. You can use it to print the distance between two vectors to see that it is adequate. Also make sure the duration is > 10 (so you can look around for it). The line is always 1px thick regardless of distance, and renders last over everything else, so you should be able to see it.