Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Super Annoying Stuff
#1
:mad: 
I tried to add some moves to my new character.. and now the game ends with a error stating "lf2.exe has stopped working" after the loading of broken_weapon.dat.. please help meh!
Reply
Thanks given by:
#2
thats suspicous

did you by any chance edit anything related to the things that are loaded after broken_weapon?
like backgrounds
or stage
Reply
Thanks given by:
#3
I believe, that if you have too many frame elements within a frame, then it can cause a crash.
Or if you use frames that have framenumbers higher than 399.
Age ratings for movies and games (and similar) have never been a good idea.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.
Reply
Thanks given by: Electric2Shock
#4
Or maybe there are many type: 3 objects that have the same id.

IDK.
[Image: icyboards-ad-468x60.gif]
Reply
Thanks given by:
#5
no.. nothings's changed in stage/backgrounds.. IDK whats wrong.. :/
Reply
Thanks given by:
#6
does it work again if you undo your change? (not just take the data out)
Reply
Thanks given by:
#7
oh yea it worked.. now here's the code that caused crash!!
    DC-Code:
<frame> 270 charge
   pic: 54  state: 3  wait: 3  next: 271  dvx: 0  dvy: 0  centerx: 39  centery: 79  hit_a: 0  hit_d: 0 hit_j: 0
 sound: data\SNDDATA_2238.wav 
   wpoint:
      kind: 1  x: 52  y: 24  weaponact: 31  attacking: 0  cover: 0  dvx: 0  dvy: 0  dvz: 0 
   wpoint_end:
   bdy:
      kind: 0  x: 25  y: 26  w: 37  h: 53
   bdy_end:
<frame_end>
<frame> 271 charge
   pic: 55  state: 17  wait: 3  next: 272  dvx: 0  dvy: 0  centerx: 39  centery: 79  hit_a: 0  hit_d: 0 hit_j: 0
 opoint:
      kind: 2  x: 42  y: 51  action: 20  dvx: 0  dvy: 0  oid: 123  facing: 0
   opoint_end:   
wpoint:
      kind: 1  x: 79  y: 2  weaponact: 20  attacking: 0  cover: 0  dvx: 0  dvy: 0  dvz: 0 
   wpoint_end:
   bdy:
      kind: 0  x: 25  y: 26  w: 37  h: 53
   bdy_end:
<frame_end>
<frame> 272 charge
   pic: 55  state: 17  wait: 3  next: 273  dvx: 0  dvy: 0  centerx: 39  centery: 79  hit_a: 274  hit_d: 274  hit_j: 274
  opoint:
      kind: 1  x: 45  y: 45  action: 4  dvx: 0 dvy: 0  oid: 203
   opoint_end:
   wpoint:
      kind: 1  x: 39  y: 12 weaponact: 20  attacking: 0  cover: 0  dvx: 0  dvy: 0  dvz: 0 
   wpoint_end:
   bdy:
      kind: 0  x: 25  y: 26  w: 37  h: 53
   bdy_end:
<frame_end>
<frame> 273 charge
   pic: 55  state: 17  wait: 3  next: 272  dvx: 0  dvy: 0  centerx: 39  centery: 79  hit_a: 274  hit_d: 274  hit_j: 274
   wpoint:
      kind: 1  x: 39  y: 30  weaponact: 20  attacking: 0  cover: 0  dvx: 0  dvy: 0  dvz: 0 
   wpoint_end:
   bdy:
      kind: 0  x: 21  y: 80000  w: 43  h: 62
   bdy_end:
<frame_end>
<frame> 274 charge
   pic: 55  state: 15  wait: 0  next: 999  dvx: 0  dvy: 0  centerx: 39  centery: 79  hit_a: 0  hit_d: 0  hit_j: 0
   wpoint:
      kind: 1  x: 39  y: 30  weaponact: 40  attacking: 0  dvx: 100 dvy: -1 cover: 1
   wpoint_end:
   bdy:
      kind: 0  x: 10  y: 38  w: 54  h: 21
   bdy_end:
<frame_end>



this is the code for charging MP, the opoints are the charging waves around him and nothings wrong in it..
Reply
Thanks given by:
#8
The codes you provided doesn't make fatal error but in frame 271 the x: and y: don't match between opoint and wpoint.
Reply
Thanks given by:




Users browsing this thread: 2 Guest(s)