Quixel SUITE | Status & Stability Patch Download
Hey everyone!
As many of you have noted 1.9 has taken way longer to release that originally anticipated, which has in turn delayed all the stability fixes that are part of 1.9. I understand though that everyone is much more interested in a stable build than big new features, so we have put together a 1.8 stability branch that includes all current crash and bug fixes. To everyone who have experienced any of these issues, I am extremely sorry for the long wait on this.
The stability build is now available for download and to make it as light as possible it's in two parts:
Release.rar -- extract all contents directly to <SUITE PATH>\x64\bin\Release\
script.rar -- extract the "script" and "calibration" folders to <SUITE PATH>\script\
(You can quickly navigate to your installation path of the SUITE by right clicking on the desktop icon and choosing "Open file location")
This patch comes with many fixes but namely addresses the following:
Please let us know if there is anything that is still acting up for you, and we will do our best to fix it immediately. This thread will be updated with more fixes the moment they are made.
Thanks everyone!
- Teddy
As many of you have noted 1.9 has taken way longer to release that originally anticipated, which has in turn delayed all the stability fixes that are part of 1.9. I understand though that everyone is much more interested in a stable build than big new features, so we have put together a 1.8 stability branch that includes all current crash and bug fixes. To everyone who have experienced any of these issues, I am extremely sorry for the long wait on this.
The stability build is now available for download and to make it as light as possible it's in two parts:
Release.rar -- extract all contents directly to <SUITE PATH>\x64\bin\Release\
script.rar -- extract the "script" and "calibration" folders to <SUITE PATH>\script\
(You can quickly navigate to your installation path of the SUITE by right clicking on the desktop icon and choosing "Open file location")
This patch comes with many fixes but namely addresses the following:
- Solved special case for DDO crash on start
- Solved special case for NDO crash on start
- Solved "No input path was found" DDO error on start
- Solved rare project corruption issue (i.e. all Masks turning white and becoming uneditable)
- Fixed crashes when in color picker mode
- Solved issue with NDO editing UI not appearing on some setups
- Fixed exporter not working for very large maps
- Fixed issues related to transparent PNG color maps
- Fixed errors related to clearing mask
- Fixed bug where adding IDs through Dynamask would create black mask
- Fixed bug where ID would not show up in material ID editor
- Fixed bug where Shift+C-click would stop working if user cancelled operation
- Fixed issue where DDO.exe and NDO.exe would lead to errors when launched on their own
- Number of fixes to address preset loading and ID separation issues
- Fixed issue with undefined material IDs losing material link in custom presets
Please let us know if there is anything that is still acting up for you, and we will do our best to fix it immediately. This thread will be updated with more fixes the moment they are made.
Thanks everyone!
- Teddy
Replies
Megascans open beta is slated for release April 30. We are preparing content and a few 2D and 3D scan samples along with an official announcement. We really don't want to do any more big announcements without releasing some actual content to mess around with. I would be happy to share some updates in this thread however
We recently wrapped up GDC 2015 where a number of interactive demos were running; we're releasing some of the scans from these demos together with the announcement.
I can finally give you some more updates on what's been going on with Megascans the past few months...
The Megascans closed beta has been running since January, and a lot of love has been put into Megascans during this time as we prepare the service for public launch. Here are some of the beta scans we have been preparing for you (about 1/10 of the current library):
We are also trying to provide as many customizable BRDF calibration options as possible before launch:
All scans are currently undergoing a massive update as we have improved on the 2x2 m tiling pipeline with help from the beta testers.
Here are some of the works that have been created by the beta testers 100% with the Megascans beta:
As for samples, we are preparing a few 8K surface tileables, 4K leaf atlases, and game-ready 3D assets (with 12M high-poly source meshes). As for more free stuff, the beta will include a number of free high-res 2D and 3D scans for download, as well as a free environment pack (some of the scenes above have been created with the assets in this pack).
As for the GPU baker & 3D Painting features, these updates have taken almost over 4 months longer than we had planned for, and we currently can't say how much more time they will take given the remaining challenges ahead. Our original release plan was December, but so many unforeseen issues came up at once. These features have been developed with various beta versions of Unity 5, which has been a pretty rocky experience from update to update causing a lot of issues (our bad for jumping the gun, not Unity's). Really sorry about the delay on these features.
- Teddy
thanks for the update!
I still get the same bug as described here running this test scenario:
http://www.polycount.com/forum/showpost.php?p=2193387&postcount=2
:poly122:
This patch looks different from previous releases, will launching the suite also auto update the patch?
Of course megascans look awesome, that's a gimme. Eye candy always looks amazing.
It's going to rock once we can use it, but to use it we need stable releases, and communication can go a long ways as well.
Hope to keep hearing more from you.
Cheers,
~Tung
Fabric and leather materials will also be?
I am MUCH more interested in the ability to draw/paint on the mesh in 3DO. What's an update on that
Here are the latest files (same download link as before):
script.rar -- extract the "script" and "calibration" folders to <SUITE PATH>\script\
The core issue was that DDO expected material IDs to be specified when creating a project in order to establish links to actual materials during project generation, however with all IDs being undefined the program got confused as to which material to assign to which ID. This is now more flexible, and DDO will know how to link undefined materials by using the hex color only. Really sorry about this not being the default behavior before; it definitely should have.
Hey Tung! This patch has not been officially released yet, so it will need to be installed manually as per the instructions in the first post! We will roll out an official patch within the tool as soon as all issues are confirmed fixed.
Thanks for the kind words, and again my apologies for having been so absent online lately. Things have calmed down significantly now after GDC, and I'm incredibly glad to finally be back in the groove.
- Teddy
Chipers: As in scanned fabrics and leathers in the Megascans library? Yes, LOADS
- Teddy
Suite shortcut would do nothing
3DO would only open if it was opened in files and if the input browser was opened first
3DO input browser would not always be on top
DDO and NDO would open using file browser but would then crash
The two things the build has changed for me is:
Suite shortcuts now open as a file but it crashes before it can do anything
NDO and DDO shortcuts now say this:
3DO input browser seems to be always on top (which is a good thing)
Running both Photoshop and any of the files in admin mode does nothing and I am on the x64 version.
Ingemar: yes, all 3D scans have high poly Ztools available for download
- Teddy
Another question. I use Octane render. Is there a plan to make a calibration profile for Octane?
final_fight: Yes, quite a few. Just last week we scanned another 140 metals
- Teddy
http://www.polycount.com/forum/showthread.php?t=149487&page=4
A snippet: "Everything you download, you will own forever."
Hope that answers your questions
Excellent news '.. own forever' (old school I am I guess). Looking forward to the release as I'm sure you cannot divulge 'costs' .. even a little?lol
There must be thousands of man-hours involved with 'Mega..' drooling but awaiting and congrats with all the advances in a relative short time for Quixel.
I`ve uploaded the test case here:
https://www.dropbox.com/sh/t23dcy1ezqs6v2k/AABsVxWy0hdeMS-B1DUZeqq_a?dl=0
with one id map it generates the materials, the other doesn't. hex code for color is identical. difference is that there is one more color in the map that doesn't work... any ideas? am I doing something wrong?
on a side note: quixel suite is spamming my work folder by creating a subfolder for each created iteration/setup/project. I guess this is necessary to store the files created and it's a good thing when the suite crashes to be able to restore a project like that but would it be possible to save these temporary projects to a quixel\backup folder instead and only create a project folder when saved manually? (ask for folder, or set save folder in initial setup)
akaChris - Thanks for your report! Teddy is currently flying back from the states today so the answer may take a day or so, I´ll tell him soon as I can about this so he can have a look.
That seems really high, and I cant find it on their site, where are you getting that info?
Okay guys I have talked to Teddy, I just dropped him off at his house. So basically what all this boils down to is miscommunication, the pack was released without the knowledge of Quixel and has been removed from the marked place per Quixels request as I´m sure some of you have seen. It was supposed to be released during circumstances, at another time, at another price.
The price on the Epic market place does therefore not reflect the price of the subscription of Megascans.
Teddy had no idea that the pack was even released until I told him as I picked him up, as it was released some 20 hours ago when he was still making his way back to Sweden from the united states.
He was obviously very concerned as this gives the completely wrong idea regarding price.
So I hope everybody can feel calm again and if there is anything else you want to know don´t hesitate to ask!
Hopefully in the next few days, I came back from the US late last night and have just slept away the jet lag. A fun weekend of bug smashing ahead, I'll keep you posted
- Teddy
Shouldn't we be able to use Quixel's updater?
http://www.polycount.com/forum/showthread.php?p=2273773#post2273773
I even tried this update you got here with no fix.
Nothing more frustrating then paying money for something. Shouting from the rooftops in multiple posts about your issues... even providing screenshots and details.. and no response at all.
I'm not even going into the 100 different ways to crash this thing. Using this program is like walking on thin ice. Hell clicking reimport mesh crashes it. I'm willing to work around things that make it crash.. like not using it twice in a row or not clicking certain buttons. But cmon... at least let me see the damn preview.
Honestly im positing all this stuff here because i have not gotten any help from any other forum post.
Sorry for the delayed response. So it seems your mesh has two mesh groups, one for the pole and one for the rest (polySurface22 and TurtleDefaultBakeLayer). You should be able to see the two groups when plugging in the mesh into the Base Creator:
This means one material will be created per mesh group. This is why one part of the mesh is textured, and the pole remains untextured; in the DDO window you should see two tabs, one for each group (of which one has only been textured).
If your mesh is just supposed to be one whole object with just one UV, make sure to collapse down the two groups into just 1 group before you create the project, and it will share just 1 texture for the entire object.
Let me know if this helped
- Teddy
nothing urgent, but I tried the 1.8 stability patch and all the bugs here (from 1.8 original) are still present. Using metalness.
Any word on getting a fix for the 'Set' command missing issue, it happens when using the multi-normal option.
and then suite crashes
Error message System.ArgymentOutOfRangeEXception: StartIndex cannot larger than length of string.....
.... etc
please help
http://quixel.se/usermanual/quixelsuite/doku.php?id=ddo_samples
And have a look of how all the inputs should look like if you´re unsure.
There is also a lot of important information on the wiki: http://quixel.se/usermanual/quixelsuite/doku.php?id=inputmaps
about the format of the input maps.
Let me know if you still have any troubles!
I'm having trouble getting DDO to open in the Quixel suite. I click it and nothing happens.
NDO and 3DO both work fine.
I re-installed it and have tried opening DDO on it's own and still doesn't work. Not receiving any error messages either.
Thanks in advance
update : Fixed
We're using DDO to make textures for Unity 5 standard shader. We'd like the 3DO preview to match the results in Unity as closely as possible. Currently we use the Specular/Gloss workflow and calibration and this puts the gloss map in the specular A channel as expected for Unity. However, the visual result in Unity is much duller - to get a similar result we need to brighten the gloss map post export from DDO.
We've tried applying the 1.8 patches here with no effect. Just wanted to know if this is something wrong on our end, and if not, is it something you guys are aware of and fixing?
Thanks!
Could anyone enlighten me regarding this problem? Thanks in advance.
1) Will the 3do previewer be updated for the new megaScans library or will we need to use the previewer that's currently included with 1.8?
2) Will any of the previous smart materials/materials, etc be updated with this beta? (for example, will they be more pbr accurate and/or higher res. etc )
Thanks!
I was using 1.7 but kept getting crashes with DDO when I have UE4 selected, a window would come up saying something about resolution but I couldn't get it to go away.
I updated to 1.8 hoping it'd solve the issue but now I can't even open DDO, I check task manager and it says thinking but nothing happens. I've tried rolling back to 1.7 again as I really need to get the texturing done on my assets for my university game assignment but the progress bar just freezes.
Is anyone able to help or offer any suggestions on how to fix this? I'm using photoshop CC on windows 7
Thanks!
Hmm, Doesn't seem to be working even when making sure Suite.exe is closed in the task manager.
When I click NDO it opens instantly, but clicking DDO nothing happens except for a window showing up in the task manager called "Thinking..." which nothing ends up happening.