I'm not 100% up to speed on how the zone was changed so I might be wrong on this. But:
Looks like the they changed the name on the files ("highpasshold" versus "highpass") so my first thought doesn't apply.
Second thought, try changing the name of "highpass.s3d" (and related highpass s3d files, if you like) to "highpasshold.s3d" and remove or rename "highpasshold.eqg". The client searches for zones by name, first as <zonename>.eqg, then <zonename>.s3d. Good chance it will tolerate the old zone if you change the name and remove the EQG so it'll default to the S3D.
Third thought, if that doesn't work it'd be possible to take the old zone file and convert it up to an EQG and put it in place of highpasshold.eqg. Could make a client-side patch program for that without too much trouble if you don't want to distribute the file.
|