This is a slight annoyance that has come up.

Whenever I do a save in CC 3.11 of the currently loaded project, CC doesn't simply save, but opens the Save As dialog and prompts for a filename.

Anyone else noted this?

---

Hi, I'll try my best to explain:
In my company pipeline, I model the characters in CC3, than export in fbx for unity, and a colleague import them for the final build that we use for some demo works.
Many times i have to apply some modification to the aging of the characters, so i start with a CC1 base and then switch to a CC3 one.
I know nothing about unity, but my colleague reports that with the export made with this last release the characters have a weird bug and eyes re-located to a weird position.
Is there something I can do to fix this issue?
It seems to be an issue only with CC1 character converted to CC3.

I already reported this issue and created a feedback tracker for it. If you go to the issue you can vote it up. As of yet no one has even answered me since I posted the issue a while ago. Issue #6274.

since the aging in cc1 is materials, a easy solution would be just save the skin after conversion
and apply it to a cc3 base.



.

Apparently, and reported as FT #6252.

---

This has been bugging me too. But it seems the problem with ccProject is even deeper. So the question is:

Does anyone like the fact that .fbx, .iAvaar, ccAvatar and God knows what else are listed in the Recent Projects?
Anytime I import an .fbx or bring an Avatar to the CC stage it is getting memorized in Resent Projects. How so?
Yet if I save a project as CCProject it is not even getting listed in Recent!
Project is ccProject and it has nothing to do with anything I open while working in CC.

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... :/

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.

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

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.