Re: [hlds_linux] Command rate / update rate limitation.
-- [ Picked text/plain from multipart/alternative ] Please Alfred, can you give me an answer? Thanks you in advance. 2007/6/17, AnAkIn . [EMAIL PROTECTED]: well, sorry didn't want to mean you or anything... I think I already asked Whisper but he doesn't remember about HL1 netcode or something... I would like a answer from Alfred. 2007/6/17, David Williams [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ok then smart ass why don't you field the initial question, seeing as you know so much? i was after all trying to help. With what is my understanding of the code. right or wrong i at least did more than you did. all you could do was try and embarrass me. way to go. i would have much preferred it if you had explained why i was wrong more clearly as i feel no it doesn't revert to the max value if you change it to 500 alone is not adequate. if it doesn't revert to the max value then wtf does it do? do you even know? i think whisper should pipe up. he seems to have the best understanding of the netcode. i know alfred won't he has better things to do like fix the buggy crap the valve linux dev team puts out as stable code AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] No. In HL1 Engine, if you type the cvar without a value, it doesn't give any description. It just say the current value of the CVar. Only in Source Engine you have a description when you type the CVar. Try it. And no it doesn't revert to the max value if you change it to 500. That is only in Source Engine. 2007/6/17, David Williams [EMAIL PROTECTED]: if you type the command and hit enter (giving no value) it display a short description. And cl_updaterate shouldn't be 101, because if do cl_updaterate 500, and then ex_interp 0, i'm able to get ex_interp 0.002. And after 500 it doesn't auto set to a lower value than 0.002. Or maybe that normal... cl_update rate is capped at 101. if you enter in a value of 500 it just reverts to the nearest legal value. which is 101. so when you set ex_interp to 0 you getting what you would get if you set cl_updaterate to 101. the guy who wrote that page is wrong or it's a typo. just type rate with no value and see for yourself AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] Well, you probably think that when you type cl_cmdrate in console, it says min and max ? this is only in source, not in hl1 engine. There is no descriptions with cvars in hl1 engine. 2007/6/16, AnAkIn . [EMAIL PROTECTED]: client console command descriptions ? where did you see that ? And cl_updaterate shouldn't be 101, because if do cl_updaterate 500, and then ex_interp 0, i'm able to get ex_interp 0.002. And after 500 it doesn't auto set to a lower value than 0.002. Or maybe that normal... From this article : http://www.gotfrag.com/cs/story/5577/ He says that the rate is capped at 2... I would like that Alfred answer... AnAkIn 2007/6/16, David Williams [EMAIL PROTECTED]: yes the maximum for cl_cmdrate and cl_updaterate in hlds clients is 101 and for rate it is 3. this is clearly stated in the client console command descriptions. AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] Hello, I would like to know if there is a limitation in the HL1 Engine of the command rate (cl_cmdrate) / update rate (cl_updaterate), excluding sv_maxupdaterate/sv_minupdaterate. And also for rate, again excluding sv_minrate/sv_maxrate limitation. Thanks you in advance. AnAkIn -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
Re: [hlds_linux] Command rate / update rate limitation.
-- [ Picked text/plain from multipart/alternative ] No. In HL1 Engine, if you type the cvar without a value, it doesn't give any description. It just say the current value of the CVar. Only in Source Engine you have a description when you type the CVar. Try it. And no it doesn't revert to the max value if you change it to 500. That is only in Source Engine. 2007/6/17, David Williams [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 if you type the command and hit enter (giving no value) it display a short description. And cl_updaterate shouldn't be 101, because if do cl_updaterate 500, and then ex_interp 0, i'm able to get ex_interp 0.002. And after 500 it doesn't auto set to a lower value than 0.002. Or maybe that normal... cl_update rate is capped at 101. if you enter in a value of 500 it just reverts to the nearest legal value. which is 101. so when you set ex_interp to 0 you getting what you would get if you set cl_updaterate to 101. the guy who wrote that page is wrong or it's a typo. just type rate with no value and see for yourself AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] Well, you probably think that when you type cl_cmdrate in console, it says min and max ? this is only in source, not in hl1 engine. There is no descriptions with cvars in hl1 engine. 2007/6/16, AnAkIn . [EMAIL PROTECTED]: client console command descriptions ? where did you see that ? And cl_updaterate shouldn't be 101, because if do cl_updaterate 500, and then ex_interp 0, i'm able to get ex_interp 0.002. And after 500 it doesn't auto set to a lower value than 0.002. Or maybe that normal... From this article : http://www.gotfrag.com/cs/story/5577/ He says that the rate is capped at 2... I would like that Alfred answer... AnAkIn 2007/6/16, David Williams [EMAIL PROTECTED]: yes the maximum for cl_cmdrate and cl_updaterate in hlds clients is 101 and for rate it is 3. this is clearly stated in the client console command descriptions. AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] Hello, I would like to know if there is a limitation in the HL1 Engine of the command rate (cl_cmdrate) / update rate (cl_updaterate), excluding sv_maxupdaterate/sv_minupdaterate. And also for rate, again excluding sv_minrate/sv_maxrate limitation. Thanks you in advance. AnAkIn -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGdHOrL/HqkPK+q6kRAsdLAKDQaEBjJgMldKJlhjUFEhzQn37dzwCfVqG7 zUqU8mX7QIKY8oiX+ztBm3g= =s2Gi -END PGP SIGNATURE- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Command rate / update rate limitation.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ok then smart ass why don't you field the initial question, seeing as you know so much? i was after all trying to help. With what is my understanding of the code. right or wrong i at least did more than you did. all you could do was try and embarrass me. way to go. i would have much preferred it if you had explained why i was wrong more clearly as i feel no it doesn't revert to the max value if you change it to 500 alone is not adequate. if it doesn't revert to the max value then wtf does it do? do you even know? i think whisper should pipe up. he seems to have the best understanding of the netcode. i know alfred won't he has better things to do like fix the buggy crap the valve linux dev team puts out as stable code AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] No. In HL1 Engine, if you type the cvar without a value, it doesn't give any description. It just say the current value of the CVar. Only in Source Engine you have a description when you type the CVar. Try it. And no it doesn't revert to the max value if you change it to 500. That is only in Source Engine. 2007/6/17, David Williams [EMAIL PROTECTED]: if you type the command and hit enter (giving no value) it display a short description. And cl_updaterate shouldn't be 101, because if do cl_updaterate 500, and then ex_interp 0, i'm able to get ex_interp 0.002. And after 500 it doesn't auto set to a lower value than 0.002. Or maybe that normal... cl_update rate is capped at 101. if you enter in a value of 500 it just reverts to the nearest legal value. which is 101. so when you set ex_interp to 0 you getting what you would get if you set cl_updaterate to 101. the guy who wrote that page is wrong or it's a typo. just type rate with no value and see for yourself AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] Well, you probably think that when you type cl_cmdrate in console, it says min and max ? this is only in source, not in hl1 engine. There is no descriptions with cvars in hl1 engine. 2007/6/16, AnAkIn . [EMAIL PROTECTED]: client console command descriptions ? where did you see that ? And cl_updaterate shouldn't be 101, because if do cl_updaterate 500, and then ex_interp 0, i'm able to get ex_interp 0.002. And after 500 it doesn't auto set to a lower value than 0.002. Or maybe that normal... From this article : http://www.gotfrag.com/cs/story/5577/ He says that the rate is capped at 2... I would like that Alfred answer... AnAkIn 2007/6/16, David Williams [EMAIL PROTECTED]: yes the maximum for cl_cmdrate and cl_updaterate in hlds clients is 101 and for rate it is 3. this is clearly stated in the client console command descriptions. AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] Hello, I would like to know if there is a limitation in the HL1 Engine of the command rate (cl_cmdrate) / update rate (cl_updaterate), excluding sv_maxupdaterate/sv_minupdaterate. And also for rate, again excluding sv_minrate/sv_maxrate limitation. Thanks you in advance. AnAkIn -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGdS96L/HqkPK+q6kRAuMdAJ4tz/gJxqwBJuc2xEPYgJMWTKMkyACeNI/P lwppGqaKLnAEeSdtOwlKsrM= =DnmY -END PGP SIGNATURE- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Command rate / update rate limitation.
-- [ Picked text/plain from multipart/alternative ] well, sorry didn't want to mean you or anything... I think I already asked Whisper but he doesn't remember about HL1 netcode or something... I would like a answer from Alfred. 2007/6/17, David Williams [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ok then smart ass why don't you field the initial question, seeing as you know so much? i was after all trying to help. With what is my understanding of the code. right or wrong i at least did more than you did. all you could do was try and embarrass me. way to go. i would have much preferred it if you had explained why i was wrong more clearly as i feel no it doesn't revert to the max value if you change it to 500 alone is not adequate. if it doesn't revert to the max value then wtf does it do? do you even know? i think whisper should pipe up. he seems to have the best understanding of the netcode. i know alfred won't he has better things to do like fix the buggy crap the valve linux dev team puts out as stable code AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] No. In HL1 Engine, if you type the cvar without a value, it doesn't give any description. It just say the current value of the CVar. Only in Source Engine you have a description when you type the CVar. Try it. And no it doesn't revert to the max value if you change it to 500. That is only in Source Engine. 2007/6/17, David Williams [EMAIL PROTECTED]: if you type the command and hit enter (giving no value) it display a short description. And cl_updaterate shouldn't be 101, because if do cl_updaterate 500, and then ex_interp 0, i'm able to get ex_interp 0.002. And after 500 it doesn't auto set to a lower value than 0.002. Or maybe that normal... cl_update rate is capped at 101. if you enter in a value of 500 it just reverts to the nearest legal value. which is 101. so when you set ex_interp to 0 you getting what you would get if you set cl_updaterate to 101. the guy who wrote that page is wrong or it's a typo. just type rate with no value and see for yourself AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] Well, you probably think that when you type cl_cmdrate in console, it says min and max ? this is only in source, not in hl1 engine. There is no descriptions with cvars in hl1 engine. 2007/6/16, AnAkIn . [EMAIL PROTECTED]: client console command descriptions ? where did you see that ? And cl_updaterate shouldn't be 101, because if do cl_updaterate 500, and then ex_interp 0, i'm able to get ex_interp 0.002. And after 500 it doesn't auto set to a lower value than 0.002. Or maybe that normal... From this article : http://www.gotfrag.com/cs/story/5577/ He says that the rate is capped at 2... I would like that Alfred answer... AnAkIn 2007/6/16, David Williams [EMAIL PROTECTED]: yes the maximum for cl_cmdrate and cl_updaterate in hlds clients is 101 and for rate it is 3. this is clearly stated in the client console command descriptions. AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] Hello, I would like to know if there is a limitation in the HL1 Engine of the command rate (cl_cmdrate) / update rate (cl_updaterate), excluding sv_maxupdaterate/sv_minupdaterate. And also for rate, again excluding sv_minrate/sv_maxrate limitation. Thanks you in advance. AnAkIn -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGdS96L/HqkPK+q6kRAuMdAJ4tz/gJxqwBJuc2xEPYgJMWTKMkyACeNI/P lwppGqaKLnAEeSdtOwlKsrM= =DnmY -END PGP SIGNATURE- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit:
Re: [hlds_linux] Command rate / update rate limitation.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yes the maximum for cl_cmdrate and cl_updaterate in hlds clients is 101 and for rate it is 3. this is clearly stated in the client console command descriptions. AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] Hello, I would like to know if there is a limitation in the HL1 Engine of the command rate (cl_cmdrate) / update rate (cl_updaterate), excluding sv_maxupdaterate/sv_minupdaterate. And also for rate, again excluding sv_minrate/sv_maxrate limitation. Thanks you in advance. AnAkIn -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGdCEWL/HqkPK+q6kRAowSAJ4lb8RGcVp2k8n5ipetuSUUwoZtAACgzBow W9Gs7lqqd20UzlHVNYDXK8w= =uR/M -END PGP SIGNATURE- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Command rate / update rate limitation.
-- [ Picked text/plain from multipart/alternative ] client console command descriptions ? where did you see that ? And cl_updaterate shouldn't be 101, because if do cl_updaterate 500, and then ex_interp 0, i'm able to get ex_interp 0.002. And after 500 it doesn't auto set to a lower value than 0.002. Or maybe that normal... From this article : http://www.gotfrag.com/cs/story/5577/ He says that the rate is capped at 2... I would like that Alfred answer... AnAkIn 2007/6/16, David Williams [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yes the maximum for cl_cmdrate and cl_updaterate in hlds clients is 101 and for rate it is 3. this is clearly stated in the client console command descriptions. AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] Hello, I would like to know if there is a limitation in the HL1 Engine of the command rate (cl_cmdrate) / update rate (cl_updaterate), excluding sv_maxupdaterate/sv_minupdaterate. And also for rate, again excluding sv_minrate/sv_maxrate limitation. Thanks you in advance. AnAkIn -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGdCEWL/HqkPK+q6kRAowSAJ4lb8RGcVp2k8n5ipetuSUUwoZtAACgzBow W9Gs7lqqd20UzlHVNYDXK8w= =uR/M -END PGP SIGNATURE- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Command rate / update rate limitation.
-- [ Picked text/plain from multipart/alternative ] Well, you probably think that when you type cl_cmdrate in console, it says min and max ? this is only in source, not in hl1 engine. There is no descriptions with cvars in hl1 engine. 2007/6/16, AnAkIn . [EMAIL PROTECTED]: client console command descriptions ? where did you see that ? And cl_updaterate shouldn't be 101, because if do cl_updaterate 500, and then ex_interp 0, i'm able to get ex_interp 0.002. And after 500 it doesn't auto set to a lower value than 0.002. Or maybe that normal... From this article : http://www.gotfrag.com/cs/story/5577/ He says that the rate is capped at 2... I would like that Alfred answer... AnAkIn 2007/6/16, David Williams [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yes the maximum for cl_cmdrate and cl_updaterate in hlds clients is 101 and for rate it is 3. this is clearly stated in the client console command descriptions. AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] Hello, I would like to know if there is a limitation in the HL1 Engine of the command rate (cl_cmdrate) / update rate (cl_updaterate), excluding sv_maxupdaterate/sv_minupdaterate. And also for rate, again excluding sv_minrate/sv_maxrate limitation. Thanks you in advance. AnAkIn -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGdCEWL/HqkPK+q6kRAowSAJ4lb8RGcVp2k8n5ipetuSUUwoZtAACgzBow W9Gs7lqqd20UzlHVNYDXK8w= =uR/M -END PGP SIGNATURE- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Command rate / update rate limitation.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 if you type the command and hit enter (giving no value) it display a short description. And cl_updaterate shouldn't be 101, because if do cl_updaterate 500, and then ex_interp 0, i'm able to get ex_interp 0.002. And after 500 it doesn't auto set to a lower value than 0.002. Or maybe that normal... cl_update rate is capped at 101. if you enter in a value of 500 it just reverts to the nearest legal value. which is 101. so when you set ex_interp to 0 you getting what you would get if you set cl_updaterate to 101. the guy who wrote that page is wrong or it's a typo. just type rate with no value and see for yourself AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] Well, you probably think that when you type cl_cmdrate in console, it says min and max ? this is only in source, not in hl1 engine. There is no descriptions with cvars in hl1 engine. 2007/6/16, AnAkIn . [EMAIL PROTECTED]: client console command descriptions ? where did you see that ? And cl_updaterate shouldn't be 101, because if do cl_updaterate 500, and then ex_interp 0, i'm able to get ex_interp 0.002. And after 500 it doesn't auto set to a lower value than 0.002. Or maybe that normal... From this article : http://www.gotfrag.com/cs/story/5577/ He says that the rate is capped at 2... I would like that Alfred answer... AnAkIn 2007/6/16, David Williams [EMAIL PROTECTED]: yes the maximum for cl_cmdrate and cl_updaterate in hlds clients is 101 and for rate it is 3. this is clearly stated in the client console command descriptions. AnAkIn . wrote: -- [ Picked text/plain from multipart/alternative ] Hello, I would like to know if there is a limitation in the HL1 Engine of the command rate (cl_cmdrate) / update rate (cl_updaterate), excluding sv_maxupdaterate/sv_minupdaterate. And also for rate, again excluding sv_minrate/sv_maxrate limitation. Thanks you in advance. AnAkIn -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGdHOrL/HqkPK+q6kRAsdLAKDQaEBjJgMldKJlhjUFEhzQn37dzwCfVqG7 zUqU8mX7QIKY8oiX+ztBm3g= =s2Gi -END PGP SIGNATURE- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
