Model Verification
by Jared Hoberock · in Torque Game Engine · 03/03/2002 (10:39 am) · 5 replies
Why is it that when I load my mission, I get a message that says "Verification required for fps/data/shapes/player/player.dts? I also get that message for other models I put in the game.
Also, why is it that when I import a 3DS file into Milkshape and then export it to dts, I don't get the texture anymore?
Thanks,
D
Also, why is it that when I import a 3DS file into Milkshape and then export it to dts, I don't get the texture anymore?
Thanks,
D
About the author
#2
It was a big problem in Tribes1. People would make huge flags, or mines with spikes on them to make them stand out and essentially cheat. Dynamix issued a patch for it (which was easily thwarted).
T2 had the same thing and so does torque.
03/04/2002 (8:29 pm)
It verifies the client's models with the server to keep people from cheating and using spiked or enlarged models.It was a big problem in Tribes1. People would make huge flags, or mines with spikes on them to make them stand out and essentially cheat. Dynamix issued a patch for it (which was easily thwarted).
T2 had the same thing and so does torque.
#3
03/04/2002 (9:44 pm)
Chris, are you saying that the model verification method is easily thwarted ? If so, how ?
#4
I'm not sure if they made a new patch to thwart the thwarters.
I think the way to do it was by tricking the server. They would connect to a server, rename the original model files to a different name, then name the screwy models to the original's name. Then they would re-execute the client-side scripts. The server would think it already verified the models (like it was a level change), and it wouldn't check them again.
The only efficient way to do it would be to write a quick program to rename/execute the files for you.
I'm not sure if that's right or not, or if it even works any more. I've never tried it, just heard about it.
03/04/2002 (11:07 pm)
In Tribes1 it was.I'm not sure if they made a new patch to thwart the thwarters.
I think the way to do it was by tricking the server. They would connect to a server, rename the original model files to a different name, then name the screwy models to the original's name. Then they would re-execute the client-side scripts. The server would think it already verified the models (like it was a level change), and it wouldn't check them again.
The only efficient way to do it would be to write a quick program to rename/execute the files for you.
I'm not sure if that's right or not, or if it even works any more. I've never tried it, just heard about it.
#5
03/04/2002 (11:08 pm)
I don't think anyone has gotten past it for T2 though (or Torque). 
Torque Owner Jared Hoberock