r00t 3:16 wrote:
Yea that could be (I had a feeling it was pointer but was not 100% sure)
But the problem is WHERE .. alot of changes to the HL2MP sdk so it could be
anywhere
I find it very rare that 2 people would hit the exact same address
violations with an error in our code.
Unless it is code that is the exact same on both machines, which would be a
sdk file ..
Does that sound about right?
It sounds like some engine or interface function somewhere has changed
the parameters being passed into it and this didn't show up during the
compile.
If a bunch of other people used previous SDK source code and a parameter
in a function changed that didn't cause a compiler error, it's likely
that several people would have the exact same problem.
One of the benefits of keeping an unmodified version of the previous SDK
is that you can quickly do a diff between the old version and the new
version to find things that have changed. This won't help you in this
case unless you already have an unmodified version of the older SDK. I
suggest you start making "backup" versions of the SDK so that you can
find differences between old versions and new versions more easily.
--
Jeffrey "botman" Broome
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders
