-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add material Scan/Update function. This will help a lot. #25
Comments
I beg you, this tool is good and BAD at same time. Really, it has very dumb side too. I try explain: When moved over EQS, it will apply with SAME shader for PC and Android. This is why i call program very bad and dumb. And we have biggest problem with EQS: EVERY SHADER IN LIST MUST CHANGED MANUALLY to correct it. facepalm This is why i ask for material scan function. You have already added it for version 1.20 -> 1.30 to apply color part. Why can you not make this material scan function useful for updating shaders? I just need scan function to update PC or Android side. Then i am happy because it saves A LOT TIME. If you do it by yourself with your worlds, i am sure you will love it. Come on, why can you not make it possible? Right now, EQS is for a part very dumb tool because it cannot even keep away from PC or Android side and just apply at both sides as new add? That is just not good way. I really hate it to change ALL incorrect shaders. HOURS work. EQS may handy for change shaders, but the begin is VERY time consuming, makes the tool less great for some people. And VERY bad for big projects with a lot shaders. Really. This is why i need material scan function. Seriously, the dumb side of tool is not even funny. I should program this way if i use it for myself. You should know it very well. Tools can do some automated tasks to save time. But there is nothing right now to make work easier and faster. We cannot select all rows. It's not there. That is big weakness of EQS tool. Please. Add the material scan / update function. That is all i need. I think many people will love it. |
Material scan function. It's very useful feature because EQS works with material setting for every platform.
But i don't mean to scan whole project and collect all materials. That is not needed here. I need only what is already in the list of EQS, they can scanned for changes and update it.
This will help to solve problems in 1.3.0 i mentioned earlier. You said in Known Issues everything must done by hand for first time. That is fine for me. The only complaint is that 1.3.0 add features and also applied changes we don't ask for it. Black color by default.
Most materials have not black color. Most have white color. So it's not good update in my eyes, because not all creators read the warning and just want update it to 1.3.0.
In general way, tool may add new features, but tool is not allowed to change or add things by itself without "permission" of creator. A good tool should not do it, it must ignore what is not set correct.
You know very well it takes a lot time to fix all materials settings in EQS if project is pretty much big. Creators are literally FORCED to rebuild EQS list again in 1.3.0 due "forced" black color. This is something that can take a lot time.
EQS can apply and change materials. So it has already feature for it. Means you can reverse the feature: read materials and apply color in the list. It happens more than you think we change materials in project but we also must update list with it, otherwise it will go wrong.
The scan function is just go through the list in EQS and read material, and grab color / GPU instancing setting there and apply in the list. That is it. It saves a lot work and time too. If you use it by yourself, you know this scan function will make many people happy.
Maybe it's more "Update all materials" button, with scan function. Read everything and apply it to EQS database.
This is good request, so please make it possible. It will help too in future updates EQS if you apply more features.
The text was updated successfully, but these errors were encountered: