Quixel Megascans, the #1 scan library used by all major game and film studios, is finally available for Unity.
3D scanned objects, surfaces and vegetation, prepared for optimal performance and PBR pipelines, at your fingertips.
And our Valley collection, used in Unity’s ‘Book of the Dead’ demo:
Our Wasteland collection:
Industry veteran Josh Powers breaks down his environment building workflow, and shows us how he uses Megascans Unity Asset Packs, Megascans Bridge and Quixel Mixer to quickly create AAA quality scenes straight inside Unity.
Our Megascans collections enable small teams to create AAA quality environments extremely quickly.
Please feel free to post any support related issues in this thread!
I not Super Excited that a company as successful as yours is charging the FULL PRICE for the same asset for EACH Pipeline. It means you are charging $199.00 for just changing the shader code. I believe this is a Precedent that you don’t want to start in the Asset Store. Especially with someone like myself that has purchased all your software.
Hi,
Actually if you purchase either pipeline, you get the other one for free, it’s unlocked automatically on your asset store account. IF you’ve purchased the pack and this isn’t the case, please contact us directly via support@quixel.se and we will make sure the issue is resolved for you.
Hi,
Again as mentioned above, you should receive both pipelines on your asset store account when purchasing one of them. If this isn’t the case please get in touch so we can resolve the issue.
The reason the pipelines are separate on the asset store, is because the High-End pipeline materials require different texture packing options, as well as some other technical requirements which meant packing all of the content from both pipelines into a single package was not an option.
We absolutely wanted you to enjoy the ability to use both pipelines content with a single purchase, we’re sorry if this hasn’t been made clear, and we’ll update our descriptions to make sure of this.
Everything being purple indicates that you’re maybe trying to use the LT pack in a High-End project, could this possibly be the case?
The new SRP system from Unity typically only installs the shader packs required for whichever project template you’ve created, so just to be sure, please double check that you’ve created a High End project, and are using the High End collection.
I sorted it out. The gotcha for me was just that this asset store package is shown as needing “2018.1” and technically that is true, but there are other steps involved. SRP is new…and there are a few github projects relating to it. After you find the correct one…you then need to learn how to work with the package manager (for now manual editing of manifest files) so that all the dependencies of that pipeline get loaded up. Turns out…the easiest way around all of this is to use the Unity Hub…because of the “templates” feature…there is a template for SRP HD. So…get 2018.1, get the ‘Hub’, use the template, then unpack this beautiful asset.
Ah yes, i’m sorry i should have thought of this, i’ve been using the Hub to create all of my test projects and i had just assumed that projects created without it would work in a similar fashion. Thanks for the info!
Industry veteran Josh Powers breaks down his environment building workflow, and shows us how he uses Megascans Unity Asset Packs, Megascans Bridge and Quixel Mixer to quickly create AAA quality scenes straight inside Unity.
Stuck in an import loop. In using the Valley LT collection, during import, I get a prompt, no matter which option I pick, it just loops back and keeps asking the same question and never finishes the import. I’m using Unity 2018.1.0f2
Hi! In order for me to help you with this as quickly as possible, are you using the LT or Legacy/Standard project template?
If you’re using LT, you shouldn’t see this message at all, and it’s something i need to look into right away. If you’re using the Legacy/Standard template, then it could be that for whatever reason, it’s asking you for every asset in the pack, which i understand can be frustrating.
In either case, to alleviate this problem for the time being, i would advise you do the following:
Close Unity
Go to your project folder, and locate ‘Assets/Quixel/Scripts’ folder.
Delete the files: ‘MegascansPostLegacyCheck.cs’, and ‘MegascansPostLegacyCheck.meta’.
Restarting Unity should start importing the rest of the files, if it doesn’t and you need to reimport the package, make sure to NOT include the ‘MegascansPostLegacyCheck.cs’ file in the import.
Once your materials are imported, they might all be bright pink/appear broken, this will be due to a mismatch between their shader type, and your project type. In order to fix this, in the asset browser search bar, enter the following:
t:material “qxl”
Edit: I’ve written a script which switches the materials for you, just drop it into your ‘Assets/Quixel/Scripts’ folder, from there you can right click, and go ‘Quixel > Convert Materials To x’ where ‘x’ is the target shader type. It should be attached to this post.
This will allow you to select every material from the package, you can then change all of their shaders at the same time to the correct one for your package.
Please let me know if you have any trouble with this.
After the last post, we felt it might be a better idea to remove the automated conversion attempt on importing the asset packs. Instead, the asset packs now come with the MaterialSwitch script attached to this post.
Hello Everyone. After i import the Megascans_Importer_HD_V1.05.unitypackage. I got this error:
Assets/Quixel/Scripts/MegascansImporter.cs(558,42): error CS0234: The type or namespace name Rendering' does not exist in the namespace UnityEditor.Experimental’. Are you missing an assembly reference?
I use Unity 2017.4.3.
Thx for any answer.
And why importer code soooo ugly?