Element 3D Crashes on Windows 10 and CC 2018

Everything Element 3D belongs here

Element 3D Crashes on Windows 10 and CC 2018

Postby tino on 02/27/2018, 9:45 am

Hello there,

I can't get Elements3D to work. I set up a new system and it worked for some days. However now, after some annoying Windows updates, CreativeCloud updates etc. it doesn't work anymore.
I can't follow back every step to the moment when it worked. I switched from Mac to Windows hoping to solve this problem but this plugin is still the only plugin that just doesn't want to work properly.

I use two graphic cards. The first one I use for display. the second is only for rendering/calculation.
1. the intel UHD Graphics 630
2. NVidia GTX 980

Every other plugin like NeatVideo i.e. understands the setup and can use the GPU. So I don't want to make any system changes - solutions that were told me. And why is this Plugin writing a .dmp File of >80MB everytime the plugin crashes?

I am disappointed really as I have this plug for over 2 years and I could never implement it in my workflow.
Has anyone else had this problem? Why i.e. isn't it possible to select the graphic card I want this plugin to work with?

I'd be glad if the inventors could find a solution.

Systeminfo:
Build: Element x64 2.2.2 (2160.hotfix)

OS: Microsoft Windows 10 Pro 64-Bit 10.0.16299
CPU: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
RAM: 65388MB
GPU Vendor: Intel
GPU: Intel(R) UHD Graphics 630
GPU Driver: 22.20.16.4758
GPU RAM: 0MB
GPU Code: 101

My system:
Intel i7-8700K CPU 3.70GHz
64bit Windows 10 v1709 (Build 16299.248)
Intel UHD Graphics 630
NVidia GTX980
Adobe After Effects 15.0.1 (Build 73)
Attachments
Unbenannt2.JPG
Second error after entering scene setup
Unbenannt2.JPG (19.95 KiB) Viewed 10539 times
Unbenannt.PNG
First error on Plugin Startup
Unbenannt.PNG (6.11 KiB) Viewed 10573 times
tino
 
Posts: 4
Joined: 10/21/2015, 9:55 am
System Specs: Build: Element x64 2.2.2 (2160.hotfix)

OS: Microsoft Windows 10 Pro 64-Bit 10.0.16299
CPU: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
RAM: 65388MB
GPU Vendor: Intel
GPU: Intel(R) UHD Graphics 630
GPU Driver: 22.20.16.4758
GPU RAM: 0MB
GPU Code: 101

CL Error:

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby JPT7505 on 02/27/2018, 10:17 pm

WWindows updates often cause havoc with the gpu driver. Have u tried reinstalling it?

And you can't always get what you want out of everything. Sure I'm positive they would like the option for users to select their graphics card but who knows how much hell they would have had to go through to allow it?

If you're not happy with the product you have every right to not purchase it.
JPT7505
 
Posts: 906
Joined: 02/9/2011, 8:17 am
System Specs: CPU: Intel i7-7820X CPU @ 3.60GHz
RAM: 128gb

GPU: Quadro M6000
GPU RAM: 12288MB

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby hans123 on 02/28/2018, 3:56 am

Hello Tino,

be shure to not use the INTEL Graphics Card for E3D, because this Card is not supported.
Go to >>E3D >>Scene Setup and have a look wich Card is in use (top right).
And if E3D use the NVIDIA Card, download the Driver from the NVIIA webpage and install
this driver (perform a new install), like JPT7505 described.

Hans
hans123
 
Posts: 1125
Joined: 12/28/2012, 1:37 am
Location: Paris / France

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby tino on 03/9/2018, 1:37 pm

Hi,

thank you JPT7505 and hans123 for your answers.
The support of VC is trying to help me. We still couldn't find the solution as it is complicated to describe.

I get E3D to recognize my GTX980 however the system still crashes.
GPU update nor After Effects reinstall has helped till now.
tino
 
Posts: 4
Joined: 10/21/2015, 9:55 am
System Specs: Build: Element x64 2.2.2 (2160.hotfix)

OS: Microsoft Windows 10 Pro 64-Bit 10.0.16299
CPU: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
RAM: 65388MB
GPU Vendor: Intel
GPU: Intel(R) UHD Graphics 630
GPU Driver: 22.20.16.4758
GPU RAM: 0MB
GPU Code: 101

CL Error:

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby brown565 on 06/11/2018, 6:46 am

I'm having the same issues with a new PC (Windows 10) and AE CC 2018 as soon as I try to start Element 3D. Can't even find the .dmp file where it says it should be located. Ugh.

The upper right window in Scene Setup lists a GeForce GTX 1060 6GB/PCIe/SSE2 with 674/6144 MB Video RAM.

Any ideas/updates?

thanks,
Craig
brown565
 
Posts: 3
Joined: 05/16/2016, 7:28 am
System Specs: Dell Precision
Quadro K4200, 4096 MB Video RAM

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby JediCopilot on 06/11/2018, 7:08 pm

I'm with similar issue I guess... Every plugin works fine, optical flares, motion 2, trapcode... but Element 3D freezes and crashes AE everytime I drag him into the composition. >-|| >-|| >-|| >-||
JediCopilot
 
Posts: 1
Joined: 12/27/2017, 11:01 am
System Specs: GTX 1070, 2 SSDs, core i7 7700k, 32 ram.

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby rigidpixel on 07/5/2018, 5:05 am

I am having the same crash issue. E3D worked fine until this past update (If that's what is the error). I reinstalled the GPU driver, but that didn't seem to help. Element scene setup is showing the GTX 1050.
I receive this error after adding the 'Element' effect to a layer.
E3D Error.JPG

I also receive this message when closing AE.
E3D error close.JPG


Are we just waiting for a Windows update? Any other ideas?
Thank you,
E
rigidpixel
 
Posts: 1
Joined: 07/5/2018, 4:55 am
System Specs: XPS 15 9560, GTX 1050
i7-7700HQ
16GB RAM
Windows 10, 1803

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby hupfield on 07/12/2018, 10:04 am

I had the same problem and got some great help from Matt Kramer at VC... here's what we did to fix the issue (after a few non-starts).
I'll post the messages he sent back to me:

Please send over the “System Info” from within the Element plug-in. Check out the screenshot for where to find these details. If the crash happens before you can access Element, like a crash as soon as you apply Element or after licensing, please turn Caps Lock on before applying Element, that should allow you to proceed without crashes.

image001.jpg
How to get system info from E3D


The first step is to update to the latest version of Element. You are a couple of versions behind. It is available in your VC download account.

Then, update to the latest Nvidia graphics driver. Here is the Nvidia link to look up your driver: http://www.nvidia.com/Download/index.aspx?lang=en-us

Finally, try and clear your AE and Element cache.

To do that in Element, turn on Caps Lock first and then apply Element to the layer. Then, go into your Scene Setup, click File, Preferences, and then clear those 2 cache buttons.

To clear the AE cache, go Edit—Purge—All Memory.


Good advice, as I didn't know I was not running the current version. Sadly that didn't work for me so he sent this...

Here's one thing you can try:

Extract the attached zip file and then take the “element2_init” file and put it into this folder: Documents/VideoCopilot (if you selected a custom path to the assets then put it in that location instead, Documents is default path, though)

Restart AE and then try to open Element again.


I'll see if I can attach that file in a separate post below. Hope this helps!!
hupfield
 
Posts: 2
Joined: 07/12/2018, 9:48 am
System Specs: Build: Element x64 2.2.2 (2147.hotfix)



OS: Microsoft Windows 10 Home Insider Preview 64-bit 10.0.17692



CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz

RAM: 32589MB



GPU Vendor: NVIDIA Corporation

GPU: GeForce GTX 1050/PCIe/SSE2

GPU Driver: 23.21.13.8871

GPU RAM: 4096MB

GPU Code: 0



CL0: Intel(R) HD Graphics 630 (47.6%) (GL Interop)

CL1: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (4.8%)

CL2: GeForce GTX 1050 (47.6%)

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby hupfield on 07/12/2018, 10:09 am

Here's the init file he sent me! This is what he said it does in relation to my issue:

It is related to a conflict between the Intel GPU and the Nvidia GPU. That sort of resets it so that the Nvidia card can be the primary again.

Hope this helps, it worked a treat for me!
Attachments
element2_init.zip
Init file that
(177 Bytes) Downloaded 646 times
hupfield
 
Posts: 2
Joined: 07/12/2018, 9:48 am
System Specs: Build: Element x64 2.2.2 (2147.hotfix)



OS: Microsoft Windows 10 Home Insider Preview 64-bit 10.0.17692



CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz

RAM: 32589MB



GPU Vendor: NVIDIA Corporation

GPU: GeForce GTX 1050/PCIe/SSE2

GPU Driver: 23.21.13.8871

GPU RAM: 4096MB

GPU Code: 0



CL0: Intel(R) HD Graphics 630 (47.6%) (GL Interop)

CL1: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (4.8%)

CL2: GeForce GTX 1050 (47.6%)

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby jbird on 07/30/2018, 2:53 pm

Hello there,
This thread seems to have stalled out, so I thought I'd chime in and say I'm having some issues as well.
Element crashes the moment I point it to a directory containing an obj or E3d file..Otherwise it works with simple things like extrusion or primitives.

It causes an AE crash with no specific dialog box.

Specs from element System info:

Build: Element x64 2.2.2 (2160.hotfix)

OS: Microsoft Windows 10 Pro 64-bit 10.0.15063

CPU: Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz
RAM: 98219MB

GPU Vendor: NVIDIA Corporation
GPU: Quadro M4000/PCIe/SSE2
GPU Driver: 23.21.13.9174
GPU RAM: 8192MB
GPU Code: 0

CL0: Quadro M4000 (100.0%) (GL Interop)

-There’s no specific file that duplicates the crash, I can simply invoke the crash by clicking on the starter pack directory within the setup window.

-importing any model into Element crashes AE. Primitives work fine, as well as extruding text paths…
All .obj or e3d models crash, although it may not be the models specifically, because simply clicking on the starter pack folder in setup will invoke a crash.

So far we’ve:

Reinstalled After Effects.

Reinstalled Element

Clean install of updated Nvidia driver

Deleted preferences

Checked and adjusted any permission issues we could find

Rolled back recent windows updates.

Any ideas?
jbird
 
Posts: 4
Joined: 07/30/2018, 2:44 pm
System Specs: OS: Microsoft Windows 10 Pro 64-bit 10.0.15063

CPU: Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz
RAM: 98219MB

GPU Vendor: NVIDIA Corporation
GPU: Quadro M4000/PCIe/SSE2
GPU Driver: 23.21.13.9174
GPU RAM: 8192MB

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby AlHoot on 08/6/2018, 6:09 am

Same problem with GTX 970M 6GB
only win I upgrade the windows 10
hate element and windows
AlHoot
 
Posts: 7
Joined: 08/17/2017, 1:53 am
System Specs: Build: Element x64 2.2.2 (2155.hotfix)

OS: Microsoft Windows 10 Pro 64-bit 10.0.15063

CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
RAM: 32643MB

GPU Vendor: NVIDIA Corporation
GPU: GeForce GTX 970M/PCIe/SSE2
GPU Driver: 23.21.13.8831
GPU RAM: 6144MB
GPU Code: 0

CL0: GeForce GTX 970M (50.0%) (GL Interop)
CL1: Intel(R) HD Graphics 530 (50.0%)

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby JPT7505 on 08/6/2018, 8:36 pm

Try display driver uninstaller than do a clean driver install.
JPT7505
 
Posts: 906
Joined: 02/9/2011, 8:17 am
System Specs: CPU: Intel i7-7820X CPU @ 3.60GHz
RAM: 128gb

GPU: Quadro M6000
GPU RAM: 12288MB

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby TGlinskas on 08/7/2018, 7:10 am

JPT7505 wrote:Try display driver uninstaller than do a clean driver install.


I second this. It's usually a good idea to do a clean install of the video driver. The NVidia driver installer has a check box setting for doing a clean driver install. Generally you don't have to reboot either.
TGlinskas
 
Posts: 47
Joined: 07/27/2016, 9:43 pm
System Specs: Build: Element x64 2.2.2 (2160.hotfix)

OS: Microsoft Windows 10 Home 64-bit 10.0.17134

CPU: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
RAM: 32707MB

GPU Vendor: NVIDIA Corporation
GPU: GeForce GTX 1660/PCIe/SSE2
GPU Driver: 25.21.14.1935
GPU RAM: 6144MB
GPU Code: 0

CL0: GeForce GTX 1660 (100.0%) (GL Interop)

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby AlHoot on 08/12/2018, 11:17 am

Hi all
The problem was with the intel driver when I update the intel graphics driver and reinstall the nvidia driver every thing work perfectly
AlHoot
 
Posts: 7
Joined: 08/17/2017, 1:53 am
System Specs: Build: Element x64 2.2.2 (2155.hotfix)

OS: Microsoft Windows 10 Pro 64-bit 10.0.15063

CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
RAM: 32643MB

GPU Vendor: NVIDIA Corporation
GPU: GeForce GTX 970M/PCIe/SSE2
GPU Driver: 23.21.13.8831
GPU RAM: 6144MB
GPU Code: 0

CL0: GeForce GTX 970M (50.0%) (GL Interop)
CL1: Intel(R) HD Graphics 530 (50.0%)

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby humannajafpoor on 12/2/2018, 7:04 am

hupfield wrote:Here's the init file he sent me! This is what he said it does in relation to my issue:

It is related to a conflict between the Intel GPU and the Nvidia GPU. That sort of resets it so that the Nvidia card can be the primary again.

Hope this helps, it worked a treat for me!

Thanks a lot. I was searching 3 weeks to solve this issue.
Now E3D works fine :)
humannajafpoor
 
Posts: 1
Joined: 12/2/2018, 6:56 am
System Specs: Build: Element x64 2.2.2 (2160.hotfix)

OS: Microsoft Windows 10 Enterprise 64-bit 10.0.17134

CPU: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
RAM: 16248MB

GPU Vendor: NVIDIA Corporation
GPU: GeForce GTX 1050 Ti/PCIe/SSE2
GPU Driver: 25.21.14.1701
GPU RAM: 4096MB
GPU Code: 0

CL0: Intel(R) HD Graphics 630 (47.6%) (GL Interop)
CL1: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (4.8%)
CL2: GeForce GTX 1050 Ti (47.6%)

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby condor on 12/27/2018, 4:27 am

I had the same issue on my notebook with Nvidia M2200, there are my done steps to have E3D working on my notebook. I am with AE CC2019 16.01 (B.40).

1. Updated Nvidia drivers
2. Updated E3D to build 2160
3. Downloaded the "element2_init" file (see hupfield´s post with the link) and stored to my c:\Users\YOUR_NAME\Documents\VideoCopilot\ folder
3. Disabled Intel GPU in Windows Device Manager
4. Launched AE 2019, added a Solid layer, applied Element from the Effect menu, clicked on the Scene Setup button, added a the alarm clock model to the scene
5. Enabled Intel GPU in Windows Device Manager
6. Closed the Scene Setup
7. Closed the AE CC2019
8. Launched again AE2019 and repeated the step #4.

Everything is OK and now no error message is given. Maybe it is not necessery to do steps #3 and #5, but I did.

I hope it will helps you as well as me.
condor
 
Posts: 1
Joined: 12/27/2018, 4:11 am
System Specs: Build: Element x64 2.2.2 (2160.hotfix)
OS: Microsoft Windows 10 Pro 64bitový 10.0.17134

CPU: Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
RAM: 32647MB
GPU Vendor: NVIDIA Corporation
GPU: Quadro M2200/PCIe/SSE2
GPU Driver: 24.21.14.1195
GPU RAM: 4096MB
GPU Code: 0

CL0: Quadro M2200 (90.9%) (GL Interop)
CL1: Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby jbird on 01/3/2019, 11:11 am

After 3 months of not being able to use element because of a chronic crash, I have solved the issue.
The issue: When invoking the element model library, it crashed ae every time.
What I did first, to no avail: New Nvidea Driver, New element install, fresh AE install, upgrade AE, Most everything that one would typically do in these cases. but nothing worked.
Solution, Windows 10: go to C:/ProgramData/VideoCopilot
Deleted file: model cache 2

relauched AE/element: It worked!
Your milage may vary
jbird
 
Posts: 4
Joined: 07/30/2018, 2:44 pm
System Specs: OS: Microsoft Windows 10 Pro 64-bit 10.0.15063

CPU: Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz
RAM: 98219MB

GPU Vendor: NVIDIA Corporation
GPU: Quadro M4000/PCIe/SSE2
GPU Driver: 23.21.13.9174
GPU RAM: 8192MB

Re: Element 3D Crashes on Windows 10 and CC 2018

Postby mastermamo on 07/4/2019, 1:59 am

hupfield wrote:Here's the init file he sent me! This is what he said it does in relation to my issue:

It is related to a conflict between the Intel GPU and the Nvidia GPU. That sort of resets it so that the Nvidia card can be the primary again.

Hope this helps, it worked a treat for me!


I have been experiencing black textures on all models and zero model visibility on my AE GUI for 2 months now. Reached out to VC and got zero response.
I tried everything even going down the route of a new OS install. Nothing worked until I came across this thread.

The .init file did the trick.

Thank you for sharing the file. You are a superstar

Much appreciated

M
mastermamo
 
Posts: 6
Joined: 07/1/2015, 9:47 am
System Specs: Mac Pro
2.66Ghz Quad Core
32 GiG DDR3 RAM
Nvidia GTX 660Ti GPU


Return to Element 3D