I confront the same problem with my Windows8.1 DirectX11 or Windows10 DirectX12 laptop PC.
Manufacturer customiz display driver installed in laptop PC may cause these problems.
I would like to talk my experience stopping the customized display driver temporally. And trouble may be resolved at that time.
1) Make recovery point (To be able to recover)
2) Open "Device Manager" and select display adapter.
3)  <Stop  driver>.    Caution!:   Not  click <Delete  driver>.
It may result nullfying dispay controller program, customizing screen size, output display-port and multi-display setting etc.

4) To recover and return to normal use of PC, click <Activate  driver>. 

Please remind "make recovery point and never delete display driver"

 

Has anyone solved their issue with Direct x 12. I am having the exact same problem and cannot find where the Motion Directory is.

brian_34 @Roberto, have you tried and had any success with the new patch yet? 

justaviking (2/3/2016)

---

In my opinion (base on more than a little experience in the software industry), when you overload a system it should slow down.  It may slow to a snail's pace.  It might even appear to halt for all practical purposes.
But it shouldn't crash.

Sorry, this week I was on biz trip and I did not check the Forum very often.
So, the issue I had was solved, as I reported in the IC6.3 official Tech Issue thread.
The reason was quite simple: a non .iMotion file ended up in the Motion directory. No idea how that file went there. But that was enough to crash iClone when I was navigating the Content->Motion GUI, because iClone reads ahead the .iMotion files in order to display the thumbnail. If a different file format is there, it seems to be killing for iClone.
Anyway, problem sorted and therefore I can confirm that iClone 6.3 works fine with Win 10 Pro and DirectX12.

Regarding the file size, I agree with Peter that a bigger size can create issues.
But, working on bigger size you can also learn how to handle it.
The experience with the last project taught me what I should do: split into takes! And the new feature introduced with 6.3 (Remove animation but keep the position at a certain frame) helps dramatically :)
Right now I am working on a project with about 70 characters, so the size is really huge (bigger than 1GB), but I can still wok on it because I break into different takes: when one take is done, I remove all the animations, and works on the next one.

Dennis (Justaviking) mentioned about slowing down... and in fact it is what happens right now with this monster project (the size being due to the high number of characters).
But it does not crash: the project can render and I can work on the animations.
Again, I learnt how to handle such a big project.
Rules to works on huge proiects:

1. work in Quick Mode!
2. eventually hide everything but the asset(s) you are working on
3. create short takes (my ones are about 1500 frames maximum)
4. eventually display the assets in Wireframe

So, I can also say that with a powerful PC even 1GB or more can be sustained.

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

I thought the reason we went to 64-bit was that we could load and work with larger projects. I have actually a 2GB project (file size) that loads and doesn't cause crashes. This is on a Windows 7 64-bit desktop. I believe the graphics card also plays a big role in stability: more VRAM is better. I was thinking for my next system to be a powerful laptop, but it seems from people's experiences to be kind of a dicey proposition.

---

Respectfully, I take issue with that position as a matter of principle.

In my opinion (base on more than a little experience in the software industry), when you overload a system it should slow down.  It may slow to a snail's pace.  It might even appear to halt for all practical purposes.

But it shouldn't crash.

Usually that is a sign of sloppy memory management, insufficient handling of array sizes, and stuff like that.  If you exceed a hard-coded limit, the system ought to give a graceful and meaningful message, such as "Your project is to big, remove some assets."

I'm not saying it's necessarily iClone's fault (graphic drivers, etc. come into play too), but if other software on the same system handles project of equivalent size, it does cast some suspicion in that direction.

As Reallusion works to give us great new features and expanded capabilities, I hope they also pay attention to good coding practices so we can continue to create incredible animations that are limited only by our imagination and the speed of our hardware.  I'm sure they will.

(Of course, for now, the obvious and practical solution is to find ways to limit the size of the iClone project.)

---

iClone 7... Character Creator... Substance Designer/Painter... Blender... Audacity...
Desktop (homebuilt) - Windows 10, Ryzen 9 3900x CPU, GTX 1080 GPU (8GB), 32GB RAM, Asus X570 Pro motherboard, 2TB SSD, terabytes of disk space, dual  monitors.
Laptop - Windows 10, MSI GS63VR STEALTH-252, 16GB RAM, GTX 1060 (6GB), 256GB SSD and 1TB HDD

Just to add from our experience when crashing occurs it is normally related to the size of the project. If a project is large (say over 500MB) then this will likely signal some crashing. As it gets larger crashing will occur more frequently until eventually the project will refuse to load. If I recall rightly Roberto had previous problems with a project that turned out to be over 1GB in size. That is simply too large to maintain stability on even the most powerful system.

A good test is to load up one of our sample projects, most of which are under 100MB in size. If you don't experience any crashes using these sample projects then it is likely memory issues are causing the crashing due to project size. The most likely candidate is video memory but system memory will play a part too.

If in doubt, please contact us via the Support Form and supply your dxdiag.txt as mentioned in my previous post and we will happily try to help you out.

http://www.reallusion.com/CustomerSupport/UserEx/QForm.aspx


                                                                

Peter
Forum Administrator

www.reallusion.com

                                                                

Peter
Forum Administrator

www.reallusion.com

My gtx 980m gigabyte laptop crashes A LOT with iclone and cc. 3dx is pretty stable.
After effects, Maya, max, modo, daz, poser -- no crashes. Ever. In 4 months. I crash reallusion products 4+ times every day.

@Roberto, have you tried and had any success with the new patch yet? 

Hey guys, thanks for all the responses last year. After a lot of hard work, I think it was my Gaming laptop that was the problem. Do any of you guys have a laptop model that your currently using with iClone and DirectX 12 that you recommend?