Just to let you know the team are aware of this issue and will try to fix it in a future update.



                                                                

Peter
Forum Administrator

www.reallusion.com

Awesome. Thank you so much. I will await the update then.

UPDATE:

I have checked the status of this issue and it appears it has indeed been solved but the fix will not appear until the next update which is 3.2. Obviously the FT being changed to solved before the update is ready is not ideal so I do apologies for the confusion caused.


                                                                

Peter
Forum Administrator

www.reallusion.com

I think when an issue is marked "Solved", there should be a note of acknowledgement from RL of some sort to inform the user as to what the solution was, for example.

---

76% of original size (was 661x19) - Click to enlarge

Hi Magique...The forum is intended for user to user discussion. While myself and other members of the team will help out here when we can, this isn't where you get technical support. For support queries you should use the Feedback Tracker for non-critical issues, and the Technical Support department for the more urgent issues.

While you may not always get a direct reply on the FT, rest assured that all issues reported are looked at and feedback will be given when appropriate.

Regarding the issue in FT 6274, I will check about this and update again when I know more.


                                                                

Peter
Forum Administrator

www.reallusion.com

Peter,
Why has the following issue been marked as solved?

https://www.reallusion.com/FeedBackTracker/Issue/Applying-Game-Eyes-Messes-Up-Eye-Positions

I never got any feedback from the support team or any fix provided. Is there a patch for this issue that I don't know about? Just for the record, the comment that someone made about using Maya to fix the issue is not a solution for me or most anyone else.

What? Solved? That's crazy. I see that someone claimed they had a workaround by using Maya, but I never posted that and that certainly doesn't solve anything for me. I don't have Maya and I'm pretty sure most people don't. I'm going to go into that issue and try to get it opened again. I was enver asked if it was solved.

I have same exact problem (except I didn't start with Ayaka, just standard CC1).  I was going to vote for this in FT but it says it is SOLVED -- WTH?  Doesn't look solved to me...

Reallusion Certified Director / Reallusion Best Visual Award / Reallusion Certified Content Developer
See all the G-Tools Plug-Ins available for iClone here: G-Tools Plug-Ins

Peter,
Now that we have a feedback tracker to report issues, we seem to be completely ignored. I reported an issue ages ago using the tracker and copied it here and have gotten no support whatsoever in either place.

Yeah that was my final workaround... I made all the mod on a CC1 character than create new personal presets for the costume, for the morphing and for textures. I set a new CC3 model and apply all the saved presets from the CC1 characters. This way i have a CC3 characters with the aging system, but you see, it's a workaround not very nice... :/