[Kinsi]

Hey there,

in the source engine there is an (artificial) limit on how big BeamRingPoints can be, 4096 to be exact. It is likely 4096 as that equals to 12 bits, however i am wondering if it would somehow be possible to patch this limit out / up it to a bigger number(say 32768, or more if possible).

In general, bigger beamrings are possible (I've spawned two dummy entities and moved them apart from each other by way more than 4096 and it rendered just fine), unfortunately i cannot move the dummy entities outside of the -16k - 16k boundaries of source's world (Eventhough a client is able to fly outside of them just fine with noclip?) because of cbaseent's sendtable origin limit. If working around this would somehow be possible, that would be a solution for me as well.

Is there anyone around who's possibly interested to try this out? locally im on windows, however the target system is linux.

Thanks!

[psychonic]

Technically, you can. However, you would need to patch it on both the server and the client, negating just about any usefulness.

[Kinsi]

Almost thought so. Well yeah that sure does not make sense to do then, so thats not the route to go.

Is there any workaround to set an entity's origin outside of the limits though? Plain setting it outside of boundaries will error obviously, but since im able to actually move outside of the limits w/ noclip just fine, and physics entities outside of the map falling will fall below the origin limits as well it has to be possible .. somehow .. right?

[asherkin]

Originally Posted by psychonic Technically, you can. However, you would need to patch it on both the server and the client, negating just about any usefulness.

It is a float, so I think this one is using the variable encoding - I could only find the limit defined on the server table definition, not the client.

[petre]

Yes PLEASE someone with some knowledge have a go at this, 4096 is way too small for my needs