Babylon project (provisional name)

[CobaltUDK]

Yes, I forgot to use AnimationLODDistanceFactor too. But game stat are worse, perhaps because the enginee does more work when updates the animation, instead do it every tick.

The 1 ms each 100 sleeping bots is the game stat when I destroy the bots... so if I have 200, after destroy them the game stat is 2 ms faster. I think that is nothing about animations or skeleton updates, because the mesh is hidden, tick disabled, animations stoped, no collision, no movement, etc. There are something in Pawn.uc eating a bit of resources. Perhaps only Epic know it

[Chosker]

well even then, the Pawn has a lot of functions you could try to ignore on your Pawn's disabled state. just go through the Pawn class file and check any native functions/events that could seem relevant to ignore. maybe even on the Actor class too

either way, what does the GameplayProfiler tell you about it?

[CobaltUDK]

Profiler shows times of 0.0 in the most of pawns sleeping, but in some shows 0.1, in the tick function (and all of them has the tick disabled, in theory...).

I will try to ignore more things to see what happens. Anyway with a prevision of about 1000 bots sleeping, I think that store/destroy will be the best solution. In the best situation, 1000 bots sleeping can take 4 or 5 ms and it's too much if you want to be under 16 ms.

[Chosker]

that's 0.0 or 0.1 per pawn, but what about the aggregate function calls? (i.e. the total for all pawns)

even if you destroy all bots, further optimizations to the living bots wouldn't harm

[CobaltUDK]

I don't see any anormal in that, the most consuming function are calccamera, getplayerviewpoint, etc. My question is why some of the 176 bots that has "settickisdisabled(true)" are still processing the tick.

Edit: found the problem in the sleep state, now are 0.2 ms for every 100 bots sleeping. 2 ms for 1000 sleeping bots are still too much, if I cant reduce to almost 1 ms, I will try the store/destroy method.

[Chosker]

yep, a lot of functions aren't called by the Tick and are still happening very frequently or even every frame

[CobaltUDK]

It's the only way I know to make a open world game with UDK, using stream levels, dynamic foliage, untick, destroy instead hide actors, etc.

Here a test using a cloak:

[Chosker]

[hears voices in Spanish]

caught me off guard!

(I'm Spanish/Mexican and live in barcelona)

[CobaltUDK]

Spanglish in Babylon, yes.

[CobaltUDK]

Another apex test:

[plegenda]

Cobalt, still need voices?

[CobaltUDK]

Not for now, I have 3 voice styles, but probably will need more in the future.

[CobaltUDK]

Companions not only help you fight enemies, also collect objects for you (later you can ask for them) and light the torch if it's dark.

Still has some bugs to correct, animations that are truncated, etc.

[CobaltUDK]

[UnrealEnterprise]

Cool! At this speed how quickly do aircraft reach map edges?
Any ideas about how you might handle that type of case?