Votes
0
Product:
Character Creator 4
Version:
4.5
Status:
Released in 4.5
Issue 11531
Creating a morph slider with an .obj TargetMorph doesn't work and causes stability issues
I'm using the trial version of CC4. I'll provide my full experience with this issue for more context

Initially, I was trying to create a morph slider following these steps:
1. Load Neutral_F into a clean CC4 project
2. Clear all morphs
3. Export to .obj as "Nude Character in Bind-Pose"
4. Import the .obj into Blender 4.2 using the CC4 plugin
5. Make a few minor adjustments to the face using the sculpt tool
6. Export the character to another .obj using the CC4 plugin
7. Choose create slider ("+" icon) in the Morphs tab
8. Enter name + path
9. Choose "current morph" as source
10. Choose the .obj exported from Blender as target
11. Make sure the correct *.objkey is selected
12. Tick "Adjust Bones" and "Auto apply to current character"
13. Hit OK

The message box with the progress bar just disappeared at 42% and the morph slider editor was still shown. No error message was thrown, no morph slider was created.

I gave it a few more shots starting from step 7, with altered checkboxes. I basically tried all possible combinations of options checked / unchecked, but got the same result everytime.

If I tried saving the project or loading a new character after this issue occured at least once, the application crashed.

To exclude Blender or the plugin from being the problem (For maybe corrupting the file), I tried to create a slider with the exact same morph target, by using the .obj file from step 3 -> Same outcome.

Next, I closed and reopened the application and tried to create a morph slider from CC4 Camila to CC4 Kevin, same outcome.

I also checked if the .obj import is broken in general, so I imported the obj files I created in the process just using the regular import function but all of them worked.

Minimal steps to reproduce
1. Create a clean project
2. Load in any character
3. Export as .obj
4. Choose "Create slider" in the same project
5. Choose the previously obj as the target object
6. Tick checkboxes as explained before (or leave it as is, as it doesn't seem to matter)
7. Hit OK
8. Watch it failing at 42%
9. Save the project to watch the application crash
OS: Windows 10
Attachment:
  •  3
  •  301
BugMorph
Submitted bymaurerv Sep 14, 2024
1
COMMENTS (3)
maurerv Sep 19, 2024 
Hi Tina, 

that fixed it! I assume these folders are normally created during installation? Maybe because I moved my Reallusion Custom folder to a different disk for some more space that's why they weren't created? Also, It's strange I couldn't find any reports about this on the web.

Anyway, thank you so much... It was driving me crazy :D
Feedback Tracker Admin Sep 23, 2024 
We apologize for the inconvenience.

Yes, theoretically, the folders should be automatically created during the installation process, and this is where the error occurred, causing the bug. This issue will be fixed in future versions.

It's fine to move the Custom Folder using the Content Manager, but the Morph Slider is a special case. It can only exist in the Default Custom path set during the initial installation of the program. So even if you have configured multiple Custom Folders, the Morph Slider will still be saved in the same default path when you create it.

Tina
Feedback Tracker Admin Sep 19, 2024 
Hi maurerv,

Please go to your default Content path "C:\Users\Public\Documents\Reallusion\Reallusion Custom" and create a subfolder named "Actor," and then create another subfolder named "Avatar Control" under it.

After creating the folder, open CC and try to create a Morph Slider to check if it works properly.

The issue has been reported to the development team and will be fixed in future versions.

Thank you.
Tina
maurerv Sep 15, 2024 
Update: It also happens if I choose the feature "Create Head & Body Sliders". Here the progress bar actually fills up to 100%, the morphs are getting baked but no slider appears in the browser. And again, loading in a new character or saving the project afterwards results in a crash.
1