Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Locales with a comma as decimal place don't work - ie 20,00 instead of 20.00 #15

Closed
Darthbeiber opened this issue Nov 10, 2017 · 27 comments

Comments

@Darthbeiber
Copy link

HI idk why icons, cds, pots etc are not displayed ...
everything else works well, life bar, special rdm bar,

ty and great job.

@danakj
Copy link
Collaborator

danakj commented Nov 10, 2017

What job are you on when that is the case?

What's your character's name? (Is there non-ascii characters?) You can scramble the name or something if you're worried about anonymity, just wondering how to reproduce it.

@Darthbeiber
Copy link
Author

in all jobs, life/tp/mana bars work well and only icon not work
Misko Jhones is my character name

@danakj
Copy link
Collaborator

danakj commented Nov 10, 2017

Hm, probably not a name problem then. Is there anything interesting in the OverlayPlugin tab's log?

@Darthbeiber
Copy link
Author

When I get home, I'll take screenshots of my config, etc ...

@danakj
Copy link
Collaborator

danakj commented Nov 12, 2017

I had a thought. Cactbot uses the network log triggers for everything from the FFXIV plugin - since they are more reliable and quicker, with more info. That means if you have network parsing disabled that things like the potions and such will break.

The HP/mana bars come memory directly so they don't depend on that.

Make sure in the FFXIV plugin settings that "Disable Parsing from Network Data" is not checked.

@Darthbeiber
Copy link
Author

me ffxiv settings https://gyazo.com/585609d44c0fdaf914503f1c9f18b1fa FFxiv not found in automitic for me, i need swich me process, disable all addons exceppt ffxiv and put on all addons, al all work except buffs
me overplugin https://gyazo.com/21afb44099ea28f9328c7be3c40b321b
plugins https://gyazo.com/7b71b9ce2a11be563848b8cd08188a13

@Darthbeiber
Copy link
Author

https://gyazo.com/886de2ab9c5636b28d28a9e93b3a0b82 probably not automatic process is the problem

@Darthbeiber
Copy link
Author

https://gyazo.com/095b45c0b317b2e8770eb72fcbf776e4 the rpoblem i think

@danakj
Copy link
Collaborator

danakj commented Nov 12, 2017

Hm, ok let me try to translate those. If that error is that it can't find FFXIV_ACT_Plugin.dll, then https://github.com/quisquous/cactbot#potential-errors-and-workarounds has a suggestion.

@danakj
Copy link
Collaborator

danakj commented Nov 12, 2017

Oh, I think it's this one:

If you get an overlay plugin error similar to Error: (overlay): Exception in SendFastRateEvents: Could not load file or assembly 'FFXIV_ACT_Plugin, Version=(version), Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. then you likely need to unblock the ffxiv plugin. See the instructions above for unblocking DLLs.

@Darthbeiber
Copy link
Author

i make a new full install, and the same problem. now act dont have any problem.

@danakj
Copy link
Collaborator

danakj commented Nov 12, 2017

i make a new full install, and the same problem. now act dont have any problem.

I'm not sure what you mean there, the problem went away so it's all good? Or it changed?

Did you unblock the FFXIV_ACT_Plugin.dll?

@Darthbeiber
Copy link
Author

it still does not show the icons, but now I have unlocked all the files, and the ffxiv and overplugin do not give any faults

@danakj
Copy link
Collaborator

danakj commented Nov 12, 2017

Can you:

  1. start combat a striking dummy
  2. activate RDM embolden
  3. go back to act and click "End Encounter"
  4. right click on the encounter with the dummy
  5. go to "View Logs"
  6. click "Copy All" button in top right
  7. come back here and paste what you copied here?

@Darthbeiber
Copy link
Author

[04:00:48.110] 15:1072E940:Darth Beiber:1D64:Jolt II:40000EF3:Striking Dummy:750203:197A:3033A:8000BA:10:800557:1C:801D64:0:0:0:0:0:0:0:0:159353:165452:0:0:1000:1000:-834,4091:-607,7821:13,5907:30848:30848:14400:14400:1000:1000:-827,2372:-598,3194:11,6:
[04:00:48.110] FC:
[04:00:48.110] FC:
[04:00:48.110] 1A:Darth Beiber gains the effect of Dualcast from Darth Beiber for 15,00 Seconds.
[04:00:48.110] FC:
[04:00:48.110] FC:
[04:00:48.110] 1F:1072E940:Darth Beiber:30323:00:6200:5D01
[04:00:47.000] 00:08ae:You gain the effect of Dualcast.
[04:00:48.747] 0D:Striking Dummy HP at 99%.
[04:00:48.747] 0D:Striking Dummy HP at 98%.
[04:00:48.747] 0D:Striking Dummy HP at 97%.
[04:00:48.747] 0D:Striking Dummy HP at 96%.
[04:00:48.953] FC:
[04:00:48.953] FC:
[04:00:48.953] FC:
[04:00:48.953] FC:
[04:00:48.953] 1A:Darth Beiber gains the effect of Impactful from Darth Beiber for 30,00 Seconds.
[04:00:48.953] FC:
[04:00:48.953] FC:
[04:00:48.953] FC:
[04:00:48.953] FC:
[04:00:48.953] FC:
[04:00:48.953] FC:
[04:00:48.000] 00:082b:You cast Jolt II.
[04:00:48.000] 00:0aa9:⇒ Direct hit! The striking dummy takes 6522 damage.
[04:00:48.000] 00:08ae:⇒ You gain the effect of Impactful.
[04:00:49.979] FC:
[04:00:49.979] FC:
[04:00:49.979] 15:1072E940:Darth Beiber:1D60:Embolden:1072E940:Darth Beiber:500020F:4D7:0:0:0:0:0:0:0:0:0:0:0:0:0:0:30848:30848:14040:14400:1000:1000:-827,2372:-598,3194:11,6:30848:30848:14040:14400:1000:1000:-827,2372:-598,3194:11,6:
[04:00:50.187] FC:
[04:00:50.000] 00:082b:You use Embolden.
[04:00:50.000] 00:08ae:⇒ You gain the effect of Embolden.
[04:00:50.811] FC:
[04:00:50.811] 1A:Darth Beiber gains the effect of Embolden from Darth Beiber for 20,00 Seconds. (5)
[04:00:50.812] FC:
[04:00:50.812] FC:

@danakj
Copy link
Collaborator

danakj commented Nov 12, 2017

Ooh I see!

It says "20,00 Seconds" instead of "20.00 Seconds" like it would for me. Thanks! We'll have to go through and make sure all the checks we do for numbers support both formats.

@danakj danakj changed the title Dont show icons Locales with a comma as decimal place don't work - ie 20,00 instead of 20.00 Nov 12, 2017
@Darthbeiber
Copy link
Author

and any solution for fast fix?

@danakj
Copy link
Collaborator

danakj commented Nov 12, 2017

If you go through jobs.js and change things that look something like [0-9.]+ to be [0-9.,]+ then I expect it to work for that module.

Would have to do the same with all the triggers for the raidboss module to work, though.

@danakj
Copy link
Collaborator

danakj commented Nov 12, 2017

However that will not be perfect. According to https://stackoverflow.com/questions/7571553/javascript-parse-float-is-ignoring-the-decimals-after-my-comma the commas will not parse correctly, so we'll have to convert them to periods before doing parseFloat(). That will be harder for you to do one-off, but most things are actually whole numbers so you probably won't notice it for now. If things feel off by a second, then that is why.

@Darthbeiber
Copy link
Author

I have modified the jobs.js file with the changes you have posted, now the procs of the jobs are working, but the buffos are still not working.

@Darthbeiber
Copy link
Author

in what directory should the buff icons be?

@danakj
Copy link
Collaborator

danakj commented Nov 12, 2017

The icon images are in ui/jobs/jobs-icons.js, they are saved as js strings.

Do the boxes appear but the icons are not there, or nothing appears at all, or something else?

@danakj
Copy link
Collaborator

danakj commented Nov 12, 2017

And did you get the lines like this?

  gainRegex: new RegExp(':' + me + ' gains the effect of Embolden from \\y{Name} for ([0-9.]+) Seconds'),

That's the one for Embolden for example.

@danakj
Copy link
Collaborator

danakj commented Nov 12, 2017

5269d55 should fix this more robustly for the next release.

@Darthbeiber
Copy link
Author

yeahhhhhhhhhhhhhhhh finally work https://gyazo.com/394961bb880f3af4f07a3cf8893b438f ty dude.

I remplace all [0-9.]+ for [0-9.,]+
i remplace gainRegex: new RegExp(':' + me + ' gains the effect of Embolden from \y{Name} for ([0-9.]+) Seconds'),

and all work .

if anyone have the same problem y can upload me jobs.js

ty for all, <3

@Darthbeiber
Copy link
Author

bbut now, i know your code and probably make a good ui for ninja

@danakj
Copy link
Collaborator

danakj commented Nov 12, 2017

Awesome! Thanks for helping me fix it. Will be cool to see a Ninja UI!

If event.detail.jobDetail is missing anything you can take a look at the event.detail.debugJob which has all the bytes for job info in raw format. If you figure out what bytes are set to to describe what job states, then we can change the FFXIVMemory.cs to pull that data out into jobDetail to give it to the JavaScript nicely. I don't have a 70 nin so couldn't do this myself yet.

The ui/test/cactbot_test.html ui shows this debugJob string too so you can observe it and record what it does.

@danakj danakj closed this as completed Nov 12, 2017
SiliconExarch pushed a commit to SiliconExarch/cactbot that referenced this issue Jan 5, 2024
…s#15)

(sorry for the git bork/closed PR - one more time...)

This PR should address the encounter sync drift referenced in
quisquous#5635 and quisquous#6048, as well as the
missing zone-seal sync referenced in quisquous#5716.

There were a couple of separate but related issues that I found:

1. `encounter_tools` had not (yet) been updated to use `InCombat` lines
to start encounters, even though `make_timeline` is inserting an
`InCombat` sync at the start of a new timeline.
2. For fights that do not have zone seals, `encounter_tools` would fall
back on using `playerAttackingMob` or `mobAttackingPlayer` regex. While
this mostly still worked (with minor drift issues), it was also counting
faerie healing actions as the start of the fight. I confirmed this was
the case with the log in issue 6048. I don't have logs for the original
report from issue 5635, but I suspect a similar cause there, as I was
unable to repro in e6n when on non-pet classes.
3. I think there was a minor logic bug in `encounter_tools` re: pushing
the fight-starting log line into `logLines`. When encountering certain
log lines that should trigger a new fight encounter, `onStartFight()`
would reinitialize `this.currentFight` and set `.startTime`; but when
`storeStartLine()` was subsequently called, it would not push the
starting log line into `.logLines` because the fight already had a start
time set. This was causing make/test_timeline to sometimes not have
access to (and not be able to sync on) the log line that started the
encounter.

I'm wary about unintentional breakage, given the various different
events that should (or should not) start a timeline. cc: @xiashtra and
@JLGarber, would appreciate an extra set of eyes.
SiliconExarch pushed a commit to SiliconExarch/cactbot that referenced this issue Jan 6, 2024
…s#15)

(sorry for the git bork/closed PR - one more time...)

This PR should address the encounter sync drift referenced in
quisquous#5635 and quisquous#6048, as well as the
missing zone-seal sync referenced in quisquous#5716.

There were a couple of separate but related issues that I found:

1. `encounter_tools` had not (yet) been updated to use `InCombat` lines
to start encounters, even though `make_timeline` is inserting an
`InCombat` sync at the start of a new timeline.
2. For fights that do not have zone seals, `encounter_tools` would fall
back on using `playerAttackingMob` or `mobAttackingPlayer` regex. While
this mostly still worked (with minor drift issues), it was also counting
faerie healing actions as the start of the fight. I confirmed this was
the case with the log in issue 6048. I don't have logs for the original
report from issue 5635, but I suspect a similar cause there, as I was
unable to repro in e6n when on non-pet classes.
3. I think there was a minor logic bug in `encounter_tools` re: pushing
the fight-starting log line into `logLines`. When encountering certain
log lines that should trigger a new fight encounter, `onStartFight()`
would reinitialize `this.currentFight` and set `.startTime`; but when
`storeStartLine()` was subsequently called, it would not push the
starting log line into `.logLines` because the fight already had a start
time set. This was causing make/test_timeline to sometimes not have
access to (and not be able to sync on) the log line that started the
encounter.

I'm wary about unintentional breakage, given the various different
events that should (or should not) start a timeline. cc: @xiashtra and
@JLGarber, would appreciate an extra set of eyes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants