On 6/22/07, Giel van Schijndel <[EMAIL PROTECTED]> wrote:
The Watermelon schreef:
>
> a minor fix to avoid excessive harmless asserts by projectile validity
> check macro when using memory debugger like MSVC when debugging.
>
I assume the problem you're trying to fix with this patch is that
psAt
On 6/22/07, Ari Johnson <[EMAIL PROTECTED]> wrote:
> On 6/22/07, Giel van Schijndel <[EMAIL PROTECTED]> wrote:
> > Ari Johnson schreef:
> > > On 6/22/07, Dennis Schridde <[EMAIL PROTECTED]> wrote:
> > >
> > >> We just released Warzone 2100 version 2.0.7.
> > >> This doesn't bring many stunning new
On 6/22/07, Giel van Schijndel <[EMAIL PROTECTED]> wrote:
> Ari Johnson schreef:
> > On 6/22/07, Dennis Schridde <[EMAIL PROTECTED]> wrote:
> >
> >> We just released Warzone 2100 version 2.0.7.
> >> This doesn't bring many stunning new features and is mainly intended to fix
> >> several remaining c
Ari Johnson schreef:
> On 6/22/07, Dennis Schridde <[EMAIL PROTECTED]> wrote:
>
>> We just released Warzone 2100 version 2.0.7.
>> This doesn't bring many stunning new features and is mainly intended to fix
>> several remaining crashes and add a few config options for convenience.
>>
>> Summary
On 6/22/07, Dennis Schridde <[EMAIL PROTECTED]> wrote:
> We just released Warzone 2100 version 2.0.7.
> This doesn't bring many stunning new features and is mainly intended to fix
> several remaining crashes and add a few config options for convenience.
>
> Summary of changes:
> - Access to the new
We just released Warzone 2100 version 2.0.7.
This doesn't bring many stunning new features and is mainly intended to fix
several remaining crashes and add a few config options for convenience.
Summary of changes:
- Access to the new Lobbyserver (When joining a game, leave the IP field empty
to g
The Watermelon schreef:
>
> a minor fix to avoid excessive harmless asserts by projectile validity
> check macro when using memory debugger like MSVC when debugging.
>
I assume the problem you're trying to fix with this patch is that
psAttacker = NULL at some times, and dereferencing this to retrie
the component bit 'asBits[COMP_CONSTRUCT]' is corrupted after some time of
gameplay(running with 7 ai players with 20x speed should trigger it in few
minutes).
It seems both asBits[COMP_CONSTRUCT] and asBits[COMP_SENSOR] are
corrupted(random number between 100-255,construct should be in range of
a minor fix to avoid excessive harmless asserts by projectile validity check
macro when using memory debugger like MSVC when debugging.
Index: src/projectile.c
===
--- src/projectile.c(revision 1555)
+++ src/projectile.c(worki
