|
From: Cobalt <co...@te...> - 2016-03-14 20:27:23
|
Hi 6: Im so bad with entity lists...one of my weak points for sure. "Also, I dont know if the creepcam code does anything special, but I have decided to go with the darkplaces internal cam. Saves me a whole bunch of bonkers cam code.Though it does seem to have some position bug if you set the distance to far away. " I guess you refer to the .clientcamera field in DP ? If so, its basicly a modified hack of SVC_VIEWPORT that handles network stuff alot better. If you get a chance , try installing Creepcam using the code on Git I linked to earlier. It has an install.txt that guides you along on how to install. The Version 2 was an attempt at putting it in basic coop mode with a respawn timer so you can follow other players fighting monsters and such when you die in between respawning. We also have it chasing monsters, so you can watch them fighting at times its kind of neat. I use it in my Arena mod to chasecam the Frikbots and its priceless in debugging them, for example...as its got a chase_active type view and a focal length, plus its the only one that puts the enemy in perspective when in a battle. Some bugs like not readjusting focal length depending on waterlevel, I am still futzing with, but aside from this crash loop its pretty stable and flexable code. Spike has commented that this Camera is not so great because it handles networking very poorly and is laggy, but I have not seen it lag much unless the guy you are following is also very laggy but thats to be expected. Its got a cam ticrate of 0.2 seconds by default, but I suppose that could even be set to an adjustment via an impulse tied to the mousewheel or something while chasing, if its a factor in better performance. Thanks for the tips on the loop crash. Actually I didnt get your response through the email list, I saw it in the archives when I was skimming through them by chance, so for some reason I guess this list is not so reliable. Cobalt |