There are still some fairly consistent problems being logged in system.log .
While I don't think they are generally very harmful, they probably don't help with game stability either.
So if we can do something to fix them, really we should.
Bad rope data still occurs:
And missing textures that aren't actually used but are still referred to:
We'd first need to know WHICH ships are affected by this.
The texture errors can probably be fixed relatively easily by HEX-editing the GM models.
The rope data would be more tricky; @Hylie Pistof is the expert on that subject.
One thing we have done in the past is to automatically cycle through all ships in the game to find out what problems lie with which specific ships.
The code to do that is still in console.c:
While I don't think they are generally very harmful, they probably don't help with game stability either.
So if we can do something to fix them, really we should.
Bad rope data still occurs:
Code:
Bad rope data for rope: (rope num = 110) (begin group=0, end group=-1)
Begin pointer = 0? end pointer = 323841252
Bad rope data for rope: (rope num = 210) (begin group=-1, end group=0)
Begin pointer = 323841252? end pointer = 0
And missing textures that aren't actually used but are still referred to:
Code:
Can't load texture resource\textures\SHIPS\RNDC.TGA.tx
The texture errors can probably be fixed relatively easily by HEX-editing the GM models.
The rope data would be more tricky; @Hylie Pistof is the expert on that subject.
One thing we have done in the past is to automatically cycle through all ships in the game to find out what problems lie with which specific ships.
The code to do that is still in console.c:
Code:
if(!Checkattribute(pchar,"cheatship")) Pchar.cheatship = 0;
int con = sti(Pchar.cheatship);
if(con<SHIP_TYPES_QUANTITY)
{
GiveShip2Character(pchar,ShipsTypes[con].id,"Test Ship",-1,ENGLAND,true,true);
Pchar.cheatship = con +1;
}
TraceAndLog("*************************** Ship : " + ShipsTypes[con].id + " , Index : " + con + " ");