Tick/Update method

Troubleshooting General Help
21

Yes, I know what you mean.
That’s why other people use the name() or standard Java serialization.
For instance, I could just as easily use my hashmap inside the enum (de)serializer. This hashmap uses the name of the enums as lookup. But since string hashing is butt slow I don’t use it. And serialization depends on reflection which is slow too, so I don’t use it either.

In my special case I still use ordinal during (de)serialization to binary files.
Details:
I use enums to represent Unicode property names. The scheme doesn’t change a lot and usually only elements are added. So the only problem might be that the Unicode consortium declares one particular enum element as deprecated - but in that case the binary file will just not include this value anymore and a little bit of dead code is left in the source code. I think that’s okay. And if it becomes a problem, then I can use standard serialization or enum names in a future version - it’s not much of a change (a few lines only).

I think that Kecon will have to deal with that problem somehow similar: A 0-based index which is used for anything else than just a meaningless id will make problems. It’s not only the ordinal() that has this problem. It might also depend on the usage of that 0-based value. For my usage it’s okay to use ordinal.

22

By definition you’re overloading your simulation with a fixed update rate if your processing takes longer than the update time. With a fixed update time you typically have some kind of “meter” that shows you the current “load” of your processing as (timeActuallyProcessing / tickTime), where values over 1 are overloads.

23

Yes, and then you could resort to slow motion, which is essentially what I proposed.
I wasn’t the first one though, but the implication of my description is the same like saying: “slowmo!” :chimpanzee_smile:

24

How do you guys are managing the particle casters for a slow motion effect? I’ve done things that are not satisfying me.

25

I don’t handl yanything for slowdown actually. For sounds it is pretty awkward, for animations it is mostly not visible (yay spaceships have very little animations :slight_smile: ) and for particles I would just directly ignore it, as my particles are usually short stuff like explosions or weapon trails

26

The problem is that float has poor resolution.
If you multiply slowmotion as a factor, then this problem increases.

I’ve seen otherwise good animations break due to slow motion.
I can imagine, that particles have the same problem too.