Hello, I posted in a thread that was labled solved so I think I should start a new thread here.
I was able to use Quixel Suite during beta, and when it was time to enter keys to register my account, Quixel Suite would freeze, and then crash. And then now when i try to click on any of the icons, i get a crash and the report that i attached to this thread.
So far I have tried reinstalling the software. Uninstalling and deleting the software and re downloading, and installing, and nothing. Anyone know whats up? Thanks in advance!
EDIT i am currently using PS CS5
Maybe this information will help too. i recently did a factory restore on my laptop. i installed photoshop and updated it to the current update, and then downloaded quixel suite and tried runing it, but it keeps crashing. i really dont know what else to do =/
Replies
If you run the DDO - that all is well.
If the first press release info, or update launcher - you get this error.
After the error is no longer possible to run DDO. A window appears here with this error: "No input paths specified. Aboting butch"
(Quixel 1.6 + 1.7b / Photoshop CC2014/ windows 8.1 64 bit / )
i got the no input paths specified error a couple times before the crashing started. But now when I uninstall and reinstall quixel it just crashes... i dont even get the window of asking me to enter keys or try the trial (i wanted to see if the trial would work). It just crashes now with the attached image log.
Sorry for your troubles, this type of error is usally due to antivirus blocking the suite. could this be the case for any of you?
-Are there any non alphanumerical characters in the install path of the suite?
-Is the Suite installed on a network drive?
-Could there be any antivirus blocking the suite?
-Are there enough diskspace on PS scratchdisk(s)?
All crash issues related to entering license keys have been addressed and can be tested by installing the following patch: http://www.polycount.com/forum/showpost.php?p=2269254&postcount=1
Although I'm not sure SuperDuperYeah and rupee are having the same issue, known "reference construction" errors have also been addressed in the patch above. Feel free to try it out and let me know if the issue persists for you!
Kind regards,
- Teddy
This patch literaly fixed every problem ty Teddy
- Teddy