ok,  this is pretty bad lol -   the teeth have become misaligned,  and the ability to rotate has been grayed out. this character is basically unusable now,  because if i try to send it back to character creator,  it will rip my updated texture.  Once the character is in iclone,  it's not backward compatible if you do custom texture / mesh work.

not a fan of this workflow.  my memory is getting eaten alive by having so many open software and so many pipelines, ct8 is   randomly locking up my computer on exporting heads with basic 'realtime' settings,   it's not getting 'easier'   it's getting messier.

imo - simplest fix is maybe a plugin in iclone that allows us access features from the other software without having to keep the other software up. Or maybe even some autolink function,  where if the user own compatible products,  the products autoconnect / link and opens new optional panels in iclone.  - we also need a hide / autohide function in iclone to recover some screen space from the panels when we are not using them.

• My Spotify  My Twitter  My Twitch
  
• My NFT    My Marketplace My Blog
  
• Music Sync Licensing

☯🐉

"To define Tao is to defile it" - Lao Tzu

In my case, iClone crashes as soon as I apply an animation to an avatar with a double-click, but also when I navigate the Content window in the Animation panel: I am forced to drag&drop the animation clips to the target avatar from Windows Explorer... quite boring....
I am in touch with RL, but they could not replicate the problem.
The fact is that the new patch has something PC-dependent that creates all sort of different problems but not steady through various users.
One thing, which i suggested to RL, is to add a way to get some diagnostic upon a crash, e.g. the name of the SW function that created the crash, or other related info.
At least they can have a clue about what's going on, because if the SW is so PC-dependent, it is a nightmare to debug problems occurring here and there but not replicated on other systems...


EDITED. problem solved!! :-)
The issue was due to a couple of non .iMotion files that, for some unknown reasons, existed in some of the motion packs.
Probably iClone tried to read and resolve them, in order to populate the content window with teh various motion thumbnails and crashes because teh format of those file was completely different!
If this is the case, RL should filter the file vs. the extension or at least put an header into them, so that the SW does not crash upon a different file but just ignore it.

My PC:
OS: Windows 10 Pro English 64-bit / CPU: Intel i7-9700 3.6GHz / MB: ASUS ROG Strix Z390  RAM: 32GB DDR4 2.6GHz / HD: 2TB+3TB  /  SSD: 2x512GB Samsung 860 EVO + 1x2TB Samsung
VB: Palit GTX2080 TI GamingPro 11GB / AB: embedded in the MB and VB (audio from the MOTU M4 I/F) / DirectX: 12

What I notice in iC6, in regards to DOF, is the it just doesn't seem to be very sharp.
When I select the Target focus point and compare it to DOF turned off it is noticeably sharper with DOF off than when I select my focus point and turn it on. Maybe it's just my system again who knows?



Click here to go to my YouTube Channel filled with iClone Tutes and Silly Stuff

Visit ANIMATED PROJECTIONS Powered by iCLONE

Intel Core i7 3960X @ 3300MHz Overclocked to 4999.7 MHz Sandy Bridge 24.0GB DDR3 @ 833MHz Graphic Display HP ZR30w 
GeForce GTX 980Ti 6GB  Microsoft Windows 7 Professional 64-bit SP1 ASUSTeK COMPUTER INC. P9X79 WS (LGA2011)

At least everyone can work in the latest patched version.  I can not open, import or save a project without iClone6 crashing after I installed the latest patch.

And for some reason when I go to import, iClone6 wants to look in something called, "... OneDrive\Documents" and then crashes.

I have done a clean uninstall, rebooted, then reinstall.  Same thing.   I ever upgraded from windows 8.1 to windows 10 thinking that might help. iClone6 still looking in the OnDrive directory for import and still crashing.

I sent in a help ticket.

Matthew

PC stats:
Intel Core i7-5930K Processor (6-cores, 15MB Cache, Overclocked to 3.9 GHz with Turbo Boost)

Windows 10
Graphics card NVIDIA GeForce GTX 1080 graphics, 8GB
Memory - 16GB Quad Channel  DDR4 at 2133MHz
DirectX - 12

256GB SSD 6Gb/s main HD + 4TB 6kRPM SATA 6Gb/s Storage

Hi Kelley,

that is not my case: I have some rendering done with previous IC6 patches and the DOF is there, quite ok.
I have the feeling that IC6 has some issues and it is very system-dependent: if we put together all the reported issues, we have quite a lot, but not all the problems happen to everybody, which makes life hard for RL to find how to fix them, if they can't reproduce.
But the result today is still a buggy product.
Hope next patch will be the lucky one...

Cheers

  Roberto



My PC:
OS: Windows 10 Pro English 64-bit / CPU: Intel i7-9700 3.6GHz / MB: ASUS ROG Strix Z390  RAM: 32GB DDR4 2.6GHz / HD: 2TB+3TB  /  SSD: 2x512GB Samsung 860 EVO + 1x2TB Samsung
VB: Palit GTX2080 TI GamingPro 11GB / AB: embedded in the MB and VB (audio from the MOTU M4 I/F) / DirectX: 12

When the lip sync is done it keeps the mouth at the last mouth position used for the rest of the animation. So now to make the mouth return to normal you have to end each lip sync with NONE.

I've had that DOF problem (results not matching Real Time) since 6.1, so that's not new to 6.3 at all.

You actually cannot get the same DOF blur you see in Real Time no matter what you try, which is a definite bug.

---

Alienware Aurora R16, Win 11, i9-149000KF, 3.20GHz CPU, 64GB RAM, RTX 4090 (24GB), Samsung 870 Pro 8TB, Gen3 MVNe M-2 SSD, 4TBx2, 39" Alienware Widescreen Monitor
Mike "ex-genius" Kelley

@RobertoColombo, thanks for the double check.

1. For me, I don't get any DOF on output, on a project created in previous version.
2. I'll try to create a new camera and reshoot. 
3. I get a satisfying result for test started in 6.3.
4. I'll post some visuals later. 

Embrace simplicity

Reduce selfishness

Have few desires

(Lao Tzu) 

You are (PARTIALLY) right!!
Just tried:

1. created a new prj with 6.3 (latest patch), added 2 avatar, one in front, the other in the back, applied DOF => it works fine
2. loaded a prj created with a previous version, applied some DOF => DOF is rendered, but very, very light compared to what I can see in the preview/editing window!

Here is the image, as seen in the preview/editing window (preview mode set to HIGH):


Here is the same frame, rendered as an image.


I can see the same issue when rendered both AVI and mp4 output.

Really too many issues with this 6.3 patch :crazy:

  Roberto

My PC:
OS: Windows 10 Pro English 64-bit / CPU: Intel i7-9700 3.6GHz / MB: ASUS ROG Strix Z390  RAM: 32GB DDR4 2.6GHz / HD: 2TB+3TB  /  SSD: 2x512GB Samsung 860 EVO + 1x2TB Samsung
VB: Palit GTX2080 TI GamingPro 11GB / AB: embedded in the MB and VB (audio from the MOTU M4 I/F) / DirectX: 12

DOF Not working on projects created in a previous version.
But it works if you do it from scratch in 6.3.
Can anyone confirm?

Embrace simplicity

Reduce selfishness

Have few desires

(Lao Tzu)