Jump to content

bbudzon

Vectorworks, Inc Employee
  • Posts

    749
  • Joined

  • Last visited

Reputation

251 Spectacular

4 Followers

Personal Information

  • Location
    United States

Recent Profile Visitors

9,102 profile views
  1. Unfortunately, I'm unable to reproduce this issue. We'll have to try to get more people involved and see how wide spread the issue is / who all can reproduce it. There are some known issues with our noise algorithm in the rendering engine. It's just a little stronger than we desired. The intent is to reproduce the real world grain you would get on film if you used a high iso in a dark environment. Because of the complexity of this issue, I'm not sure there is an easy work around or fix. We're aware of the issue, however, and working towards some potential solutions. Glow in Shaded/Showcase does not actually cast light onto nearby surfaces. It merely glows. In RW, I think glow can actually trigger things like light bounce. And so, it can handle glow much better. This is largely due to the fact that it does not need to render frames quickly. Mid air gobo effects should work in Shaded and RW. This is different than the way Showcase handles gobos as Showcase requires DMX and uses a different backend. For example, Showcase is aware of gobo slots and gobo wheels. Shaded/RW is not aware of this and cannot do things like gobo splits.
  2. It's always hard to give exact recommendations or to say yes or no. But, I think that is a very nice PC and GPU for running realtime graphical rendering. 100 lights isn't too taxing on Vision. If you weren't aware, Vision also has a Performance <-> Quality slider that can help you get better performance if your file is running a little slow. I hope this all helps!!
  3. Thank you very much! If you find more in the future, feel free to add additional comments here. I'm watching the thread so I will get email notifications for it.
  4. I'm glad my test helped you get further in our understanding of what might be going wrong! Unfortunately, there is no way to change channel functionality in Vectorworks/Vision for Fixture Modes/litfiles short of using a different mode of the device or a different device entirely. We'll have to open tickets internally to investigate content issues with the fixtures/modes that are causing you trouble. If you could get me a list of fixtures+modes that are misbehaving for you, I can work on opening tickets for each one.
  5. I got around to testing this quickly and it seems that the Chauvet Colorado 2 Solo in Tour mode has working zoom for me when using DMX and Showcase. I've attached a video demonstrating it in working order. I've also attached the VWX I used for testing. A DMX Recording named "test" is saved into this VWX. You can recall this DMX Recording and play it back. You should get the same results I am seeing. forumTest.mp4 forumTest.vwx
  6. Hmm... if Device Type is not "Light" and is set to "Moving Light", then it should ignore all values in the OIP and always use DMX for control. If you're still only able to get control via the OIP, then there might be an problem in the code. I'm sorry! I'll try to look into this in more detail when I find some time and get back to you.
  7. Ahh, this might be a problem with the way conventionals are handled. We try to detect that the conventional has zoom, and in this case ignore the OIP and allow the zoom to be controlled via DMX. But, you might be stuck in a situation where zoom cannot be controlled via DMX and can only be controlled via the OIP. If that is the case, I think this would be a bug. You may be able to try changing the Device Type to "Moving Light" as that might "trick" the code into ignoring values from the OIP. This might get zoom working for you.
  8. There are some known issues with GDTF Fixture Mode and Showcase. I would suggest using the regular Fixture Mode for the time being. This statement seems to imply that some fixtures CAN zoom in or out when the fixture type isn't from GDTF? In my tests, zoom seems to work as expected. But, maybe I need to test specific fixtures. Which ones in particular work for you and which ones give you trouble?
  9. Lens glow will not work unless Showcase is running and the fixture is being controlled via DMX. We wanted to get lens glow working outside of Showcase, but ran out of time/resources. This is something we would like to address. There also are some bugs related to lens glow inside of Showcase that I'm actively working on. I hope to get these addressed for 2026 Update 2 or Update 3.
  10. Ahh, that is unfortunate. I thought this was working at one point, but again, because this stuff isn't officially supported and for debug purposes only, it does not get tested regularly. The only other idea I just thought of is that there must be programs out there that can convert a gltf to a glb. Perhaps, you could export a gltf out of VW and use some utility like this to get it into a glb format. Sorry I couldn't be of more help!!
  11. These menu commands are located under the Debug menu because they are not officially supported by VW. We used them internally for GDTF/MVR development, and management decided we would ship them under the Debug category in the event a developer needed the user to execute these commands to help us gather more information about a bug. If you try to use these menu commands, there may be issues. Especially if you try to use them outside of a debugging context with developer supervision. And as you are experiencing, you will also likely run into workflow related issues as these were never intended to be user friendly. They were as bare bones as we could make it for our developers and debugging purposes. All of that being said, I believe if you type something like "myfile.glb" into the file name field (even though gltf is selected as the "save as type"), it will save as a glb instead of a gltf. I'm not positive about this, but it's worth a shot 😋 More and more people are discovering these menu commands. And, more and more people are making requests to official support the gltf/glb formats for import/export. I'll take this post as your advocacy for us working on this further 😉 The more people that push for this, the more we will see it as a company, and the more likely we are to implement it. So, thank you very much for you post! I hope my suggestion works for you. Worst case, you may need to use some intermediary format to get from VW to a program like Blender, and you can do the glb export from there.
  12. The 8 light limit is a great thing to check. I would also turn Shadows off in the Showcase Preferences and in the Showcase RW Background's lit fog. This is just a temporary measure to try and figure out what is going on. But, this will eliminate the possibility of odd shadow bug blocking some lights but not others.
  13. I'm glad you were able to get a simple one-light setup in a new blank document working. At this point, it will likely just be a matter of tracking things down. I'm sure once you find the difference between your working file and your broken one, it will be pretty obvious what is going on. I hope at least!! If you continue running into issues, don't hesitate to reach back out.
  14. Ahh... I may need to look at the file more if this doesn't work out for you. But, I believe your problem is that your lights are not "On" in the Visualization Palette. In VW 2025, a light needs to be On in the Visualization Palette before starting Showcase in order for the light to be on in Showcase. We're aware that this was frustrating users, and as a result we've discussed this internally and talked about solutions. But for now, you need to have all of your lights On in the Visualization Palette.
  15. Hmm... I would think those camera settings if anything would be over bright. Light should be more evident not less... If you would like, you can post your VWX or DM it to me and I can try to find some time to take a look.
×
×
  • Create New...