A list of common issues and frequently asked questions for the GIMI tools.
Before attempting anything on this page, make sure you are using the most up-to-date versions of the plugins, character data, and programs. Most issues I see are from people using older versions of the tools.
Three most common issues are:
- Double check you have the correct Genshin game .exe location in the d3dx.ini file. Genshin has two .exe, one for the launcher and one for the game itself - you want the latter
- If the green text is not showing up, make sure you are using the Development version. The for-playing version does not have green text
- Make sure you are running both the GIMI loader and Genshin as administrator
There is no problem if the 3dmigoto loader console window closes after the game loads, that is the intended behavior.
If you get a message like "Unable to verify if 3dmigoto successfully loaded", that does not mean the program failed to inject just that the loader cannot tell. You can close the window without issue if it appears to be working in-game (in fact, you should since leaving this window open can lead to computer slowdowns).
3dmigoto can be run with other types of Genshin modding tools or loaders - just run the 3dmigoto loader first, then whatever other program you have after.
I have occasionally noticed an issue where 3dmigoto will fail to inject even if everything is setup correctly - in those cases, re-attempting the injection fixes the issue.
If you do not see anything in the folder, make sure you are loading in data from the ModelData folder and not the Mod folder (currently, loading files from Mod folders not supported). The correct folder should contain vb and ib .txt files
If you get this error when loading a model, you are using an outdated plugin. The old plugin only supported Blender 2.80-2.92
Almost all other errors are due to an issue with the model you are trying to load. Most common is 4D normals, which is due to the collect script dumping a component of the model and incorrectly labelling it as a normal.
Before troubleshooting, double check you have done everything in the following list:
- Objects you are trying to export in the Blender scene are named ObjectHead, ObjectBody, ObjectDress and ObjectExtra, and there is only one of each (how many you have depends on how many the original model had)
- You are exporting back into the ObjectData folder the original model came from (NOT the Mod folder), and are exporting it as Object.vb. Double check the folder you are exporting to has hash.json
- You are trying to export the same number of components as the model you are replacing originally had
- None of the objects you are exporting in the scene are completely empty (need at least one face on all objects, can shrink it down to hide it)
- All of the objects have the 3dmigoto custom properties, either by merging with an object that was originally imported using the plugin or by using the custom property transfer script (https://github.com/SilentNightSound/GI-Model-Importer/blob/main/Tools/custom_property_transfer_script.txt)
- UV maps are named TEXCOORD.xy, TEXCOORD1.xy, TEXCOORD2.xy...etc., up to the original number the model had
- The model has vertex colors, and the color component is called COLOR
Now, on to the most commonly seen issues. You can get more details on what is going wrong when exporting by opening up the console window:
This is the trickiest part of troubleshooting - there are many, many things that can go wrong when importing a model into game. I will try and cover some of the most common categories of problems that occur
Ensure 3dmigoto is actually running, and that you have placed the mod in the correct Mod folder. Also make sure to press F10 in-game to reload any changed mods. Finally, if all else fails try emptying your ShaderCache and ShaderFixes folders, since sometimes those can cause issues when loading mods.
This is due to vertex limits on the model. Anything with blend weights/vertex groups has a quirk where the vertex limits need to actually be raised in the 3dmigoto dll in order for it to work properly. I raised it for most characters, but have missed a few - still looking into methods of setting it for all objects.
This is caused by the game attempting to load more than one file to the same hash. This usually is a result of using two mods for the same character at the same time, but an older version of the tools also had a bug where shared face components were overwritten in multiple places.
To fix, remove any duplicate mod folders. If you are sure that you have removed them all and the warnings still show up, go into the .ini file the warning mentions and delete or comment out the lines.
Unlike warnings, errors usually indicate that the program has failed to load in the mod. The cause can vary, but some common ones are:
- Incorrect names (name in .ini file does not match file in folder, like different extension)
- Textures have wrong format (look at original to see what format, usually dds and must have heights/widths that are powers of 2 and have integer ratios like 1024x1024, 2048x2048, 1024x2048, etc.)
- Did not paint/transfer any vertex groups on the new model, when the old model had vertex groups
This is because the object in blender imported by the 3dmigoto and the one you are replacing it with are using different coordinate spaces. Even if they seem to line up in blender, you may actually need to rotate and translate relative to the 3dmigoto model to get the correct orientation. Most commonly, rotate character models 90 degrees so they are facing upwards, then select all and apply all transforms.
Example of correct orientation between original (Kazuha) and new (Noelle)
Very likely due to vertex group issues. The vertex group number, order and positions need to match up between the new model and the old. Confirm that all the vertex groups are there in the new model, that they are in the correct order (e.g. 4 6 7 8 5 should be 4 5 6 7 8) and that there are no gaps (e.g. 4 7 8 9 -> 4 5 6 7 8 9).
" 
Still vertex group issues - double check the above, as well as ensure that the weight for the new model in that section matches up with that of the original model
This can be due to a large variety of reasons. Most common ones are:
- Not naming the uv map as TEXCOORD.xy
- Reversed normals
- Damaged or incorrect ObjectTexcoord.buf
- Forgot to replace textures with new ones, so it is still loading up the old ones from the original model
This is most likely due to the texture map you are using having no alpha channel. Refer to the walkthroughs on this repo for details, but basically make sure you have a transparent layer on top of any texture files (the top layer is used to control emission and makes things bright, the bottom layer is used to draw the model colors and patterns).
This is due to an incorrect vertex COLOR value. Three methods to fix:
- Copy over the COLOR data from a part of the model that has correct outlines on the original (see https://youtu.be/z2nvJzkwHHQ?t=4753 for details)
- Change outline thickness with this script: https://github.com/SilentNightSound/GI-Model-Importer/blob/main/Tools/genshin_set_outlines.py (place in mod folder, command is
python .\genshin_set_outlines.py --thickness twhere t is from 0 to 255; 0 is no outline, 255 is max outline. Most game models use somewhere between 80-130, but you should experiment to see what looks best for your specific model) - Remove the outlines by using this script: https://github.com/SilentNightSound/GI-Model-Importer/blob/main/Tools/genshin_remove_outlines.py
You probably won't come across any of these in normal use, but I just want to show off my collection of cursed images
Incorrect strides in .ini file
Mismatched IB and VB
Overriding on VB instead of IB
Section coming soon, the model dumping script is still experimental.