new F8 Console UI Issues (Double log lines not shown correct)

[BluePeer]

Description of the problem

like you see on the first and second screen
there is a issue with the Ignore multiple lines and the display of the number infront

if you mostly (change arround the messages)
create log messages that are double
means like example trigger a static message on press a button
the first is shown
the second is not shown (missing (2) next to the message
3 in a row sometimes shown same for 4 and 5 but only sometimes
sometimes it shows on 4 oder 5 multiple but not in every case
and the before not shown count get added after some other log messages (but not all time only sometimes)
to trigger a correct count mostly you need to rerender the full view with add/remove timestamp

if you change the timestamp, the view get a total different view

and in some cases the UI response (f8 press) to open is +1 Second (mostly first time)
and scroll with mouse wheel is huge low FPS (looks like 5 fps)

Reproduction steps

see above the examples

Expected behaviour

show correct numbers on multiple identical lines in all cases

Additional context

No response

Operating system

Windows

Version

alt:V build #16.2.25-rc.5, branch rc

Crashdump ID

No response

Confirmation of issue's presence

• By submitting this ticket, I affirm that I have verified the presence of this issue on the latest RC (Release Candidate) version available at the time of writing this ticket.

[MellKam]

This should be already fixed in the altv-ui repository, waiting for a new release to apply these fixes. Thanks for reporting it

[BluePeer]

This should be already fixed in the altv-ui repository, waiting for a new release to apply these fixes. Thanks for reporting it

i can confirm this for the most cases in
alt:V build 16.2.25-rc.13

but there is still a issue with multi display on for example error messages
it shows a X icon regular (not multicount) and if you use for example the timestamp flipper (on/off)
it switch from the icon to the multicount view (that get only update on flipp/rerender

[MellKam]

@BluePeer Can you please provide some simple example how can I reproduce this behavior? Cause I didn't quite understand what I should do to cause this.

[BluePeer]

start alt:V
press F8
enter "voiceVolume"

this creates the example used error message (repeait it 5 times) you will see only the X) press show time it switch to the at this time counter
use some additive "voiceVolume" no counter update reuse the switch, counter update

whatever triggers a alt.logError

[MellKam]

@BluePeer I just tested the Release and RC client and it looks like my fixes have not been applied yet. I'll ask to update it as soon as possible

[MellKam]

@BluePeer This issue should be resolved in the RC branch. Let me know if you still encounter it.