itemGFX
Posted: Sat Jan 31, 2004 5:12 pmif itemGFX crashs when every u try to load it what do u do? cus i don't want to mess around for hours to work it out if some one knows 
Page 1 of 1
Posted: Sat Jan 31, 2004 5:12 pmPosted: Sat Jan 31, 2004 6:27 pmmake sure you got the latest version and check what CallStack.log has to say about it
Posted: Sat Jan 31, 2004 6:35 pmcrashest just after i put a loc in the address box does not matter if it the right one for neocron or not. can't find a CallStack.log anyway think it might be that a patch has just come out and it not been updated but i don't think thats high likey 
if some one can tell me how many pix i got to play around with to draw drone icons so if i can't get it to work for me i can send u some drawings or somthing
if some one can tell me how many pix i got to play around with to draw drone icons so if i can't get it to work for me i can send u some drawings or somthingPosted: Sat Jan 31, 2004 6:43 pmhttp://www.mightymax.org/
says in there patch log:
v0.3d:
Added a checkbox to enable/disable the callstack logging
Added a button to change the shortname (like the "l" for LowTech parts)
hopefully fixed a fatal which appeared while loading the itemsdatabase on some systems. (That *should* solve your prob Tycho C)
v0.3c:
Added a CallStack.log. Hopefully that will track the fatals down
--thats all I can say about it realy cause I don't use this thing, it seems to be a modification to neocron and I'm always a bit scared that it overrules the graphic updates that neocron does every now and then...
with a little logic this thing should be trackable if there was some more detailed error in that log file their talking about
says in there patch log:
v0.3d:
Added a checkbox to enable/disable the callstack logging
Added a button to change the shortname (like the "l" for LowTech parts)
hopefully fixed a fatal which appeared while loading the itemsdatabase on some systems. (That *should* solve your prob Tycho C)
v0.3c:
Added a CallStack.log. Hopefully that will track the fatals down
--thats all I can say about it realy cause I don't use this thing, it seems to be a modification to neocron and I'm always a bit scared that it overrules the graphic updates that neocron does every now and then...
with a little logic this thing should be trackable if there was some more detailed error in that log file their talking about