Jump to content


ARK Volunteer PC Tester
  • Content count

  • Joined

  • Last visited

  • Feedback


Community Reputation

58 First Tame


About cad

  • Rank
    Cloth Armor

Personal Information

  • ARK Platforms Owned

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi @gcalberto and @invincibleqc, the base HP of a Pegomastax is 120. A long time ago it was 160, and right after taming, the game somehow still assumes the outdated value of 160. After some time, the game recalculates the value (server-restart or putting levels in HP) and the currently valid base-value of 120 will be used. As long as the game has this bug, a pegomastax will always show way too high numbers for HP right after taming and stat extractors won't show the correct numbers.
  2. Hi, the breeding-value is the value that the offspring will have if it inherits the stat of this creature. It can be different to the current stat because of some boni the offspring could get (e.g. damage or food) or if the parent-creature is already leveled (these increases are not inherited). Hi, that means the OCR (the recognition of the numbers) isn't correct. You can try to adjust the labels where it reads the numbers (sometimes the labels overlap with the stat-name, especially in German, where "Bewegungsgeschwindigkeit" is a very long word). See https://github.com/cadon/ARKStatsExtractor/wiki/OCR for more infos.
  3. It's a .NET-application, so if you somehow can install the .NET-framework, it should run. There's also mono that allows to run .NET-applications on other OS like linux, maybe you can install mono on the chromebook (mono-project.com).
  4. Hi, go to the "Experimental OCR'-tab, on the right there is a button "load OCR config…", click on that and choose the file "ocr_2560x1440_100.json", which is the one you need for your resolution.
  5. Hi, there are multiple things you want to do: Automatically put in the values so you don't have to write them manually. This can be done by using the OCR, which will make a screenshot and then tries to read the numbers in the inventory. For this you need to load a specific config-file that was made for the resolution and the UI-scaling you use. The configs are in the folder json/ and start with `ocr_` followed by the resolution and the UI-scaling. If you don't find a file for your resolution, you can create one yourself, but that needs some work. See https://github.com/cadon/ARKStatsExtractor/wiki/OCR for more infos. OCR is not perfect and you might have to correct the values. using the export-function of ARK (look at creature, hold E, choose Options - Export Data) and import that file into Smart Breeding. This has the advantage of having always the correct numbers and it also has the color-infos and the parents (if they were imported in the same way). To configure this importing, see Settings - Import Exported See the creature levels directly ingame with an overlay For this you need a working OCR-config-file that can read the values (see above), and you need to enable Settings - General - Overlay - Automatically extract inventory levels Making the extraction work in general If the extraction does not work even if you put in the values manually, then you probably have not set the stat-multipliers according to the server settings.
  6. Hi @IanHighlander, thanks for the report! This will be fixed in the next release.
  7. Hi, you need to have loaded the correct ocr-config-file. You can also use the export-feature ingame and import the exported files which yields always the correct values and may be easier to use. If the stats are red, you probably have not set the stat-multipliers to the values of the server you're playing on. Consider to join the discord-server where people can probably help you faster than here.
  8. Ah, this issue. As I said, the new release will have this fixed, so it's not necessary to use the "exact"-method and guess the numbers. All you have to do is enter "99%", and ASB will figure out the correct value. It needs this starting value of 99%, without that, there wil be too many possibilities. Sorry for the delayed release of this fix, I'm still working on other things I want to release as well (translations), I hope it's ready in around 24 h.
  9. Taming effectiveness already checks all possible values that are in the given range. If you set the min and max to 0% and 100%, respecitively, all possible levels are shown. Setting a large range gives more results, though, so the best is to narrow this range to have an easier extraction. Regarding the Imprinting bonus, it's more complicated. The total wild levels depend on that which changes all possible levels. The large amount of possibilities the user had to choose from would be very confusing. Even now when the displayed imprinting bonus the game displays is entered, in some rare cases the exact imprinting bonus cannot be determined uniquely and the extraction can fail. The rounded number is given in the game, so it's not a big deal to enter it to massively reduce the possibilities.
  10. I put it on the todo-list. The loss by spoiling is a guess anyway (it depends on the stack-size), but an adjustment to the guess would be possible. What %-value do you mean, taming-effectiveness or imprinting?
  11. This rex has the following stats: Rex (Lvl 249, Impr: 77.75984%): HP: 21626.1 (42, 15); St: 1722 (31, 0); Ox: 525 (25, 0); Fo: 12826.3 (27, 0); We: 982.2 (35, 0); Dm: 436.3% (43, 0); Sp: 115.6% (30, 0); To: 26830.5 (233); With the new release you can extract it without issues. I'll probably release it on sunday (need to fix some other things first). It's probably the best to wait with other dinos that don't work until then.
  12. Thanks for that. I found the part that caused the issue, the next release will handle this correctly (without the need of the "Exactly, don't adjust"-checkbox).
  13. It's a rounding-issue with high-level creatures. Set the Imprinting-Bonus to `99.36` % and click on `Exactly, don't adjust`. The extractor adjusts it to `99.36115` % (which is the mean of the most probable exact values) which will make it fail. I'll see if I can tweak the algorithm to handle cases like this better.