We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug A clear and concise description of what the bug is, a screenshot helps a lot.
Error: F3D encountered an unexpected exception: No mapping for the Unicode character exists in the target multi-byte code page.
F3D encountered an unexpected exception: No mapping for the Unicode character exists in the target multi-byte code page.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
You expect to see the model
System Information:
F3D Information Paste the content of f3d --version: 2.5.0
f3d --version
Additional context Add any other context about the problem here.
Discord thread: https://discordapp.com/channels/1046005690809978911/1306265861094506517
The text was updated successfully, but these errors were encountered:
this should be reproducable on windows by putting a config file named reï.json and pointing to it with --config.
reï.json
--config
I will try to reproduce it.
Sorry, something went wrong.
mwestphal
No branches or pull requests
Describe the bug
A clear and concise description of what the bug is, a screenshot helps a lot.
Error:
F3D encountered an unexpected exception: No mapping for the Unicode character exists in the target multi-byte code page.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
You expect to see the model
System Information:
F3D Information
Paste the content of
f3d --version
: 2.5.0Additional context
Add any other context about the problem here.
Discord thread: https://discordapp.com/channels/1046005690809978911/1306265861094506517
The text was updated successfully, but these errors were encountered: