Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
LF2 2.0a Crashes but 1.9c doesn't
#6
(05-20-2015, 06:30 PM)Doctor A Wrote:  That did surprise me O_o. I can't see a reason for why they changed the limit, but it simply exists because objects are stored in a container that only allocated memory for 400 on-screen objects. Sometimes, you can exceed the limit by a number or two, but this will often cause random behaviors.

Does LF2 ever delete the objects in memory once they "fly off" the screen and are sure to never appear again?

(05-20-2015, 06:30 PM)Someone else Wrote:  The limit wasn't changed. The check to see if it was exceeded was removed.
To be clear the limit that was changed from 1.9 to 2.0 was the limit of loaded object data files, not the amount of objects currently in the game which remains 400.
This may be possible to patch somehow. I'll write a post if I can fix this.

Oh, I see. And that would be awesome if there is a patch to this. Would help a ton. :D
Reply
Thanks given by:


Messages In This Thread
LF2 2.0a Crashes but 1.9c doesn't - by Blade - 05-20-2015, 02:36 AM
RE: LF2 2.0a Crashes but 1.9c doesn't - by YinYin - 05-20-2015, 07:31 AM
RE: LF2 2.0a Crashes but 1.9c doesn't - by Blade - 05-20-2015, 04:15 PM
RE: LF2 2.0a Crashes but 1.9c doesn't - by Blade - 05-20-2015, 07:14 PM
RE: LF2 2.0a Crashes but 1.9c doesn't - by A-Man - 05-21-2015, 05:26 PM
RE: LF2 2.0a Crashes but 1.9c doesn't - by A-Man - 05-20-2015, 06:30 PM
RE: LF2 2.0a Crashes but 1.9c doesn't - by Blade - 05-20-2015, 11:49 PM



Users browsing this thread: 2 Guest(s)