Back to the Vavoom Forum Archives


Sat, 12 Jan 2008 16:29:26

Crimson Wizard

I do not know if it is some kind of VavoomC or engine restriction. If there's an optional parameter in some function in Player class, and this function is mentioned in replication block as "unreliable if (!bIsClient)", then when this function is called Vavoom terminates with "Segmentation violation" error. When I made this parameter non-optional, there was no error.
Wed, 16 Jan 2008 20:12:12

Janis Legzdinsh


Back to the Vavoom Forum Archives