After not using Marmoset in a while, I opened it, updated, but none of my scenes will open. They open, I suppose, but nothing shows. Restarted everything still no dice. Any ideas?
Here are some potential problems with not combining a mesh: * Some engines have problems with lighting when you have open edges on a mesh. You get light leaking. * Some engines will be creating LODs automatically for your buildings. Having open edges can confuse the LOD algorithm and create a bad LOD. * If your engine uses…
Do you use the OS open dialogue, or the PS open dialogue? the PS one is a little slower to open at times, but i have never had it resize itself on me. Instead of File > Open, just double click on the blank gray space, much faster :P
Randomly, all of the sudden since a couple days ago anytime I try to open Quixel it refuses to open, it just opens Photoshop but not Quixel. Why is this happening? Edit:Now it is working...Sometimes it works and sometimes it doesn't, its really weird
Found the solution, though if files are moved and the projects become unusable. The solution if anyone comes across this renaming or moving files around (for whatever reason) is to. Open the scene file in word and go through each of the folders to find the missing texture map+location. I renamed my AO and forgot to reload…
So after feeling stupid for a while and looking trough the internet, I still can't understand to open a ZPR file which is supposed to be from how I understand it a new way of saving everything including settings and such, but how to open? Please help
I want to first select all open edges, but polySelect -eb doesn't select open border edges which I have numerous on my mesh, followed by merging those edges (MEL)polySelect -eb (missing a value)? polyMergeEdge -fe
Hello again! I tried to open the file. But my max is to old to make it. Now i am trying to replicate the scene by your description, with OSL Uber Bitmap Node.
That's really all I understand so far. Everything I try to open in 1.6 isn't opening and from what I understand is only pertained to opening files that were made in past iterations of the program. I've restarted my computer, just in case, and all drivers are fully up to date. Is this some weird bug that only I'm getting or…