Hey guys, who of you had this problem some time?
There's a maximum object limit and everytime I add some objects, map crashes.
The problem: I need to add them!

Does anybody know a way to set this limit higher so that I can add more objects?

Its impossible.

But you could combign some of your objects together to save some object placement space.

thats probably not whats crashing your map though, the object limit is very, very, very high.

DarthRogueKnight wrote:Its impossible.

But you could combign some of your objects together to save some object placement space.

thats probably not whats crashing your map though, the object limit is very, very, very high.

I don't know, some people can get carried away...

Post you debug log anyway.

You don't know for sure it's the amount of objects crashing the game. As StarkillerMarek said, you should post your error log. Or better yet, look over it yourself and fix the problem(s) if you find it/ them.

I'll post my errorlog soon, but I'm sure it is the limit why my map is crashing.
Whenever I add many objects, nothing new, I added the same ones before and these ones are orking, map crashes.
Executer94 told me the limit is about 800 objects and I think I've got something about that.

[Skirata]Darman[M] wrote:I'll post my errorlog soon, but I'm sure it is the limit why my map is crashing.
Whenever I add many objects, nothing new, I added the same ones before and these ones are orking, map crashes.
Executer94 told me the limit is about 800 objects and I think I've got something about that.

Even if you are just under the limit, your map might lag and the load time wait will be long.

Yeah. I know.
Always when I add more objects as possible, this appears in errorlog:

[Skirata]Darman[M] wrote:Yeah. I know.
Always when I add more objects as possible, this appears in errorlog:

Hidden/Spoiler:

Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\StringDB.cpp(54)
String pool is full: 32768 pool is not big enough!

Please post the entirety of the error log.

Sorry the whole errorlog is too long I can't post I here, but I'm really sure that's the error, you can trust me.

[Skirata]Darman[M] wrote:Sorry the whole errorlog is too long I can't post I here, but I'm really sure that's the error, you can trust me.

Well than tough luck, you can't have them.

[Skirata]Darman[M] wrote:Sorry the whole errorlog is too long I can't post I here, but I'm really sure that's the error, you can trust me.

That's not the error, you can trust me.

I see it all the time, and it has nothing to do with any of my problems.

From the BFront2.log errors explained sticky thread:

ERRORS YOU CAN ALWAYS IGNORE You should definetly look this over next time you post an error log, removing all the clutter yourself helps people help you.

Not to mention that if you follow the instructions, your error log will almost never be too long.

And being more exact about what you did last also helps.
"Some" isn't very descriptive. Try using "regular prop" "animated prop" "turret" and so on (at least I hope you know what those are and where they're determined), it helps people help you better.

regular props or turrets, it's always the same error.

Knowing what you know now, let's go back and listen to the third post:

StarkillerMarek wrote:Post your [BFront2.log] anyway.

DarthRogueKnight wrote:

[Skirata]Darman[M] wrote:Sorry the whole errorlog is too long I can't post I here, but I'm really sure that's the error, you can trust me.

That's not the error, you can trust me.

I see it all the time, and it has nothing to do with any of my problems.

As someone who has had endless trouble with that specific problem, I can guarantee that when you start seeing errors about memory pools, that means that you're overloading something--Most likely objects. It will not necessarily always cause a crash, depending on how big the overload is, and how much RAM your computer has.

My only suggestion is to cut down on objects, especially ones of the same kind. I can't guarantee that will fix it though. The Object Limit is an inherent property of the game, not really a setting. The engine simply can't handle rendering all that information at once. Memory Pool errors can be a bit of a hassle to deal with. (This is why I always had a backed up working version of my project to return to, if such a thing were to happen).

Thanks, I do.

@[Skirata]Darman[M]
Post your entire BFront2.log or else i'm locking this topic because this is going nowhere.

If you're 100% sure that you hit an object limit then you already know what needs to be done and there's nothing more we can do here.

[Skirata]Darman[M] wrote:Sorry the whole errorlog is too long I can't post I here, but I'm really sure that's the error, you can trust me.

I think (no matter how long the error log is) you can still post it. Just "hide" it and it should be fine. Also you can narrow it down some with the comment mswf said. If you know it's the objects though then, just delete some that aren't as important. (There has to be some if it is something to do with the object limit.)