Re: New Version: So Many Frustrations
steelers05- Thank you for giving us a heads up about your issues. We are trying our best to fix any bugs we hear about. We are actually holding off on releasing a patch until we can fix the DR issue, and we want to fix any bugs we can find in between. We need to have the product in much better shape after this patch. Just to note, it is easier to track these issues, if they are able to be separated in to one post for each bug. I have been manually creating bug reports for the issues on our forum, and then linking to the forum posts for each bug. Now that I’ve said that… I guess I’ll respond to each issue inline, lol. How ironic.
The bigges problem I am having is I will be working with a file and it works fine, but then reopen it just a few minutes later and several of my materials have their names changed and the rendering wont even start again. The renderings not starting was a problem with old models from past version, but this time I was using a new model and it worked at first but then did as I was saying and wont start rendering.
I have not heard of materials renaming themselves… this is concerning! Do you have an example scene that we could use to reproduce the issue? Or perhaps, would it be possible to record a video of this happening, using Jing, or some other software? Sometimes a video can reveal something that our troubleshooting will miss. As far as the issue of the render not starting after clicking the render button, I assume that this would be related to the material rename issue. If the materials are being renamed, then there may be a desynchronization between SU’s material editor, and the V-Ray material editor. This would result in a key error in your VfS error log, mentioning the name of the offending material. Posting a copy of your error log after this issue occurs would allow us to clearly see if that was the issue.
Another problem is that, I am importing models into my scenes with textures already applied and I go to preview them in the material editor and they often either dont show up or it crashes the entire program.
Where are you importing these models from, and how are you importing them. Are you actually using the import option in the SU file menu? Are you getting from 3D warehouse? Are you drag and dropping them in to the SU scene? Are you copy and pasting between SU windows? A bit more detail, or a video of this issue would help us diagnose this further. Also, do the models that you’re importing in to the scene have V-Ray materials applied to them? You are able to import models that already have V-Ray material data attached to them. It may be possible that there is some sort of desync that is going on, much like the previous issue. A copy of your error log after this error occurs would be useful in diagnosing this issue too. Have you tried running any of the debugging tools on this scene to see if that does anything?
Am i going to have to go back and reconfigure my entire library of imported 3d models so that they will work in this new version. I really hope not.
Our goal is to have this version able to understand older scenes without having our users go through any extra steps. We really don’t want users to be forced to rework their entire workflow for this version. That’s why we tried to keep it looking pretty much the same as our last version. We didn’t want anyone to get too lost when looking at the new UI. Please let us know about any issues you encounter using your old scenes and materials.
The user interface also seems to be a lot slower and lag.
The UI has all been redone, so there is a very powerful beast hiding beneath it’s ugly exterior. We plan on harnessing that power in an upcoming release. Until then we will try to make our UI more responsive, but I wouldn’t expect it to be much more snappy after the patch. I know this is a workflow issue, and we are trying our best to streamline things as much as we can.
I am not trying to cause an uprise on the forum because I totally understand the small team that is working on the product and I know you always get pressure for new releases to come out as soon as possible, but is it reasonable to expect a bug fix that will make this version as stable as the last one to be coming out sometime withing the next few weeks?
The only reason I’m on this forum at all, is to find issues like the ones you’re talking about, and fix them. So trust me, this isn’t seen as any sort of slap to the face. We know the software is “riddled with bugs” as one users so eloquently put it. We were given a false sense of security by our testing. We opened our doors to hundreds of users, but we got very little feedback. The feedback we got, apparently was not complete, which is unfortunate at best. As a result, you now have a version of VfS that is a bit buggy. We are waiting for a fix for the DR issue from the chaos group. Once we have that fix in place, we will likely be releasing the patch. In the meantime, we are going to be going around fixing whatever we can. After the patch is put out, we will begin V-Ray for Rhino development. During that development cycle, changes will likely be made to VfS also, and another patch or version will be released after V-Ray for Rhino. It all depends on what changes are made, and how well they mesh with our VfS plugin. We hope that this next patch will not take much longer, but unfortunately we can’t give any more exact of a release date than by the end of the month. That’s the plan anyway. You know what they say about the best made plans of mice and men though…
Also, I do not think the glossy effects option in the global switches menu works…I unchecked the option for a test render and anticipated all of my blurry reflections to not render as blurry but they still ended up rendering blurry.
DING! you found a new bug, thank you!
There are several other issues that arent coming to mind yet and will continue to post them to hopefully help the developers.
Please do!
