Various error report

[SVS002]

in VndbCharNameMapper ,i found the some case the extension mistake take the name in another vndb and apply this mapping for mistake visual novel.

in image is the game in v49438 , i have checked the raw sentence in another thread and see the thread i am using to translate. i found have the word of this game is same the name of another character in v9641 and this has applied this mapping name.

So i am thinking the extension may confuse between visual novel, if can, can you make ini file character in same file game putting. If can't, i have an idea,the textactor have saved game file of it,can u using this: make mapper file in format v?? = (the name of game the texactor are using)

[voidpenguin-28]

Hi, can you share your ini config for VndbCharNameMapper?

[SVS002]

Hi, can you share your ini config for VndbCharNameMapper?

[voidpenguin-28]

Thank you. The reason this is happening is because you have the VnIds for both visual novels assigned. This makes the extension use mappings from both visual novels.

To resolve this you will need to use 'VnIds=v9641' when you are reading v9641, and 'VnIds=v49438' when you are reading v49438.

This extension has no way to distinguish between different VnIds when running a visual novel.

[voidpenguin-28]

This extension has been updated to v1.2.0, which includes a new feature that should address some of your concerns here. https://github.com/voidpenguin-28/Textractor-ExtraExtensions/releases/tag/VndbCharNameMapper-v1.2.0

This update introduces the capability to add App Name to VnId mappings to the VnIds config value. In other words, specific app names can be mapped to specific vnids.

TL;DR: With this new update, if you apply the following to the VnIds config value, it would resolve your above concern. You can add the app name for 'v9641' into there as well.

VnIds="v9641|kss=v49438"

More detailed information on this feature below.

---

• You can define key-value pairs which map a specific app to a specific VnId.
  • This can be useful if you have multiple VnIds defined but want a specific app to use a specific VnId.
• The key would be the app name, the value would be the VnId
  • Key value pairs are delimited by an equal sign ('=')
  • The app name is the name of the executable used to run the visual novel. The easiest way to find this name is to look at the app name dropdown in Textractor.
  • 
    • "Farthest2015" is the app name in the above example.
    • Note: The file extension (ex: ".exe") should not be included in the app name
  • It is okay to mix together VnIds with app name mappings and VnIds without app name mappings
    • Ex: "ABC123=v1234|v1278|DEF456=v1188"
• Example:

  VnIds="ABC123=v1234|Farthest2015=v1278|v1188"
  VnIdDelim=|

• How mappings are applied:
  • If an app mapping is found for the current app, then the VnId tied to that app name will be used for name mappings.
  • If no app mappings if found for the current app, then all non-mapped VnIds will be used for name mappings.
    • Ex: If VnIds="Farthest2014=v1234|ABC123=v1278|v1188|v1199", and the current app is named "MoeMoe". Then only VnIds v1188 & v1199 will be used for name mappings.

[SVS002]

* Ex: If _VnIds="Farthest2014=v1234|ABC123=v1278|v1188|v1199"_, and the current app is named "MoeMoe". Then only VnIds v1188 & v1199 will be used for name mappings.

i thought the " will be removed after each times reopen textactor so is it necessary to add \ before " ?

Ps: if can combine both vndb mapping and api, the problem of minchar may don't isn't problem.

[voidpenguin-28]

In this case, the double quotes are fine because they are just being used to wrap around the value text, so no need to add \

I am working on the api integration with this extension, but it will time some time as I take care of other priorities.

[SVS002]

This extension has been updated to v1.2.0, which includes a new feature that should address some of your concerns here. https://github.com/voidpenguin-28/Textractor-ExtraExtensions/releases/tag/VndbCharNameMapper-v1.2.0

This update introduces the capability to add App Name to VnId mappings to the VnIds config value. In other words, specific app names can be mapped to specific vnids.

TL;DR: With this new update, if you apply the following to the VnIds config value, it would resolve your above concern. You can add the app name for 'v9641' into there as well.

VnIds="v9641|kss=v49438"

More detailed information on this feature below.

• You can define key-value pairs which map a specific app to a specific VnId.

  • This can be useful if you have multiple VnIds defined but want a specific app to use a specific VnId.

• The key would be the app name, the value would be the VnId

  • Key value pairs are delimited by an equal sign ('=')

  • The app name is the name of the executable used to run the visual novel. The easiest way to find this name is to look at the app name dropdown in Textractor.

  • 

  • "Farthest2015" is the app name in the above example.

  • Note: The file extension (ex: ".exe") should not be included in the app name

  • It is okay to mix together VnIds with app name mappings and VnIds without app name mappings

  • Ex: "ABC123=v1234|v1278|DEF456=v1188"

• Example:

  VnIds="ABC123=v1234|Farthest2015=v1278|v1188"
  VnIdDelim=|

• How mappings are applied:

  • If an app mapping is found for the current app, then the VnId tied to that app name will be used for name mappings.

  • If no app mappings if found for the current app, then all non-mapped VnIds will be used for name mappings.

  • Ex: If VnIds="Farthest2014=v1234|ABC123=v1278|v1188|v1199", and the current app is named "MoeMoe". Then only VnIds v1188 & v1199 will be used for name mappings.

Some game start with jp text. reopen it make the text in ini change

[voidpenguin-28]

This is now fixed in v1.2.1: https://github.com/voidpenguin-28/Textractor-ExtraExtensions/releases/tag/VndbCharNameMapper-v1.2.1

Note, the hex values (ex: \xe7) will still appear in the ini file (since that is controlled by the Textractor app), but the extension will now properly read those hex values as Japanese characters.

[SVS002]

This is now fixed in v1.2.1: https://github.com/voidpenguin-28/Textractor-ExtraExtensions/releases/tag/VndbCharNameMapper-v1.2.1

Note, the hex values (ex: \xe7) will still appear in the ini file (since that is controlled by the Textractor app), but the extension will now properly read those hex values as Japanese characters.

Can u make it for another extension like api because some time,we give the system a jp word and said it translate or keep the way calling when translate.

Is it this error caused by my lap?

[voidpenguin-28]

Is that error caused by the vndb extension or the gpt extension?

[SVS002]

Is that error caused by the vndb extension or the gpt extension?

honest i don't identify what thing caused.

[voidpenguin-28]

Can you test the vndb extension without the gpt extension to see if the error happens? If it doesn't happen, try testing the gpt extension without the vndb extension.

[SVS002]

Can you test the vndb extension without the gpt extension to see if the error happens? If it doesn't happen, try testing the gpt extension without the vndb extension.

Sorry i know why it happen, some time text too much and the api can't load it so it cause that error

[voidpenguin-28]

Are you running into this error often?

[voidpenguin-28]

When you get the chance, test out this beta release and let me know if you get any errors. This makes a slight adjustment to the previous release which could maybe solve this issue. VndbCharNameMapper-v1.2.1b.zip

[SVS002]

Are you running into this error often?

No but if i mistake press skip and make the so much text load, it will cause it but i don't think it is too much usually.(vndb don't cause it, only api)

[voidpenguin-28]

Oh ok, thanks for the update. Yes, it's probably related to processing too much text at once.

Adjusting the HistorySoftCharLimit & MsgCharLimit may reduce this issue.

Since I'm in the middle of a working on updates for the gpt extension, the hex-coding fix will be applied in the next release for that extension.

[SVS002]

Oh ok, thanks for the update. Yes, it's probably related to processing too much text at once.

Adjusting the HistorySoftCharLimit & MsgCharLimit may reduce this issue.

Since I'm in the middle of a working on updates for the gpt extension, the hex-coding fix will be applied in the next release for that extension.

i meet that error,do you know why?

[voidpenguin-28]

Which version of the extension are you using? There was an update 2 days ago, which I recommend trying out.

[SVS002]

Which version of the extension are you using? There was an update 2 days ago, which I recommend trying out.

the lastest version, it hapeen when i read through over 10, i can't count how much but it hapen when after send enough times.

[voidpenguin-28]

Thank you. Looking into it.

[voidpenguin-28]

Figured it out. It's caused by the Gemini API whenever it returns a quota reached error (when you send more requests than the free version allows per minute).

{
  "error": {
    "code": 429,
    "message": "Resource has been exhausted (e.g. check quota).",
    "status": "RESOURCE_EXHAUSTED"
  }
}

A fix to prevent this from crashing the app will be available in the next release. Finishing up a few more changes beforehand.

[voidpenguin-28]

This issue should now be fixed in v1.3.0. As stated in the other Textractor thread, the name/gender mapping feature has been implemented. https://github.com/voidpenguin-28/Textractor-ExtraExtensions/releases/tag/GptApiTranslate-v1.3.0

[voidpenguin-28]

Closing thread, since these concerns have been resolved. Feel free to open a new thread for any future issues.