advanced rendering for AutoCAD
Hey guys,
I've had nxt installed on my 64 bit windows 7 computer for a while now, but all of a sudden it won't work. I uninstalled it and tried to reinstall, but I get an error during the set up that read:
Module C:\Program Files\AccuRendernXt\ArMat Thumb64.dll failed to register. HRESULT-2147024703 Contact support
Any help would be appreciated
Thanks
John
Tags:
Haven't seen this before. How did it stop working? (Haven't seen this before either.) I assume you've tried restarting the machine?
Yup, uninstalled, restarted, just downloaded the latest build, tried to install, same error. I was using and old build before, 271 I think. But I don't know what happened. Everything worked fine last time I used it, a couple months ago. And yesterday when I tried to start it I got a failed to load error.
Here's the ACAD error I get:
c:\program files\accurender nxt\aracobjects_18_64.arx cannot find a dll or
other file that it needs.
c:\program files\accurender nxt\aractexturedmesh_18_64.arx cannot find a dll or
other file that it needs.
c:\program files\accurender nxt\aracad_18_64.arx cannot find a dll or other
file that it needs.
Unknown command "NXT". Press F1 for help.
What happened when it initially failed?-- i.e. before you attempted a reinstall. Did you get an error message in AutoCAD?
This is very likely some sort of system problem. You could try installing some other program to see if you get a similar message.
When it initially failed I got the ACAD error I just posted
I'm turning this one over to Scott to research-- I don't think it's us (although I'm not positive.) I do think it's some sort of system error such as a bad windows update.
No worries, you were right with the system problem. I did a restore back a couple weeks ago and it's working now. I had tried to install my ACAD 2013 like you recommended and it didn't work either. After the restore, nXt is working again. And as a matter of fact, the restore removed a windows update. SO I think you may be on to something.
Thanks
K-- I'll let Scott know the problem was resolved. Something must have hiccuped during the Windows Update (my best guess.)