**Bug** The progress meter in 100.00

Work like any mmo developer: make bug a feature :smirk: (just joking, but anyway, it’s cool to have 100% cleared to take a picture and show friends etc)

4 Likes

In the general case, it’s impossible to know in advance how many enemies (or their exact health) that will spawn in a wave. At least CIU handles bosses correctly so you longer have the “progress bar goes back down” problem you had in CI3 every time the boss spawns more health.

But otherwise, this is just a floating-point rounding issue. Acknowledged, but not worth fixing.

1 Like

“This isn’t even my final form!!!”

But in all seriousness I actually never minded that bug, lol. Gave the bosses an unpredictable flare the first few playthroughs.

CIU is a different beast with a greater emphasis on replay, so I agree that it doesn’t really belong here tho.

Then how do you make the waves? I mean, if you know that wave X consists of Y many chickens of Z type then you can easily calculate the amount. You can even dynamically make it compatible with difficulty skills buffs. If that easy thing is not possible to do in the game engine then how is it even working?

So what do I see in this video? It literally goes back down.

1 Like

There are certain (rare) waves that don’t have pre-defined types (e.g. the Yolk-Star spawns random terminators).

This is mostly an implementation restriction on my part. Yes, it could be done to work for 100% of cases, but it would disproportionately complicate the code and make it fragile if it ever changes in the future. I prefer to have it work for 99% of the cases but only require 50% the programming effort.

Well, ok. CIU handles most multi-stage bosses correctly. The Multiplicity boss is wrong because it’s technically many separate bosses and not a single multi-stage boss.

3 Likes

We can just not count the terminators as a progress. So, the third addition to my topic ([spoiler]Progress meter improvement (yet again)) would be that there’s another way for progress bar to work - excluding the spawnable enemies. So for example in the henterprise fight, it only counts the damage done to the henterprise and not the chicks that it spawn. They are not required to kill in order to destroy the boss.

Is it really? You’re working on C++ DirectX 9.0 program all by your own. You make everything by yourself (with the exception of sound library, but we know how much time was wasted on it). C++ is definitely not the language that I would describe less programming effort. To make it work great you need insanely good code (which I have no doubts that yours is great since +20 years of experience on CI games alone). C# is much more programming friendly.

But it is set somewhere in the wave code, right? I mean, I don’t know how your wave code looks (I would like to), but you must have specified somewhere that after defeating the first one it spawns 2 another. So it should be possible to maybe just in the beginning of the code make a variable that stores the combined amount of health of all the chickens. And it doesn’t have to be static so you can change it with difficulty skills.

2 Likes

I think the current boss meter is as fine as it is, showing JUST the right information, nothing more or less.

  • Multiplicity boss should show like that so we know the exact health of the starting boss, as well as the (estimated) health total of the two Infinity bosses afterwards, easier to keep track (I focus on one Infinity at a time so I know the estimated health % to reach).

  • Yolk-star also shows as good as it is, a single 100% health boss shell, than followed by the yolk inside so it’s easier to keep track for both phases.

  • Mother-hen Ship (CI3) and Big Chicken (CI3): not necessary for “regain health” when you can just put a single 100% health bar (plus the red-flashing effect is added as well).

5 Likes

You don’t have to bump a 13-day topic after you have already created a new topic and iA replied to it.

1 Like

Ok, turns out that the v.35 fix about this issue was incomplete. I’ve made some changes. I think it will work now, test it again in v.38

Fixed in v.38
:medal_sports: Bug

I also had the same problem, but no medal while i reported it?

Did you report it before @TuongLamVN? Where is it?

But why give me a Medal if other reported what the bug its un fixed?

1 Like

In this topic I reported the progress hud in v34
You “fixed”
Now someone said what the bug stills
Im only said, why give me the Medal?

1 Like

You get a medal for initially reporting a bug (but only when that bug is fixed).

If a fix is released but it doesn’t work and someone reports that it doesn’t work, that someone gets another medal.

1 Like

Im only ask…
Idk if minasameh or ToungLanVN reported first what the bug still

@TuongLamVN The second medal is yours: :bug: (v.35 fix was incomplete) Increased precision of HUD Progress Meter to avoid rounding 99.99% to 100% (@TuongLamVN :medal_sports: Bug)

(I copy-pasted it incorrectly and I gave it to @SonicCrazyExe by accident. It’s fixed now.)

2 Likes

I dont want a Medal if me dont reported it…
I said, the Medal not for me, its for TuongLamVN or minasameh

1 Like

Nice, now yes

Both?

It was in v36 topic.