thelightingguy Posted January 17, 2019 Share Posted January 17, 2019 I have a question. I updated Vision to 2019 service pack 1 today and have noticed something odd that has never happened before. Vision seems to not respond unless I move the mouse on my computer. Has anyone ran into that before? I didn't use to do it. I am running on a 2018 15" MacBook Pro. Thanks Quote Link to comment
Vectorworks, Inc Employee bbudzon Posted January 17, 2019 Vectorworks, Inc Employee Share Posted January 17, 2019 @thelightingguy I'm not sure if you were working with our tech support already or not, but I did hear about a customer who was having this issue (it just may have been you! hahaah). I believe they worked around the issue by switching DMX Providers?? (I have no idea why this would ever fix it, but it did seem to work around the issue for the time being.) One piece of information that I didn't receive was that it seems you are able to reproduce this in Vision 2019 SP1 but not in Vision 2019 SP0? Is that true? If so, it drastically helps us narrow down where the problem may be. FWIW, as well, I would recommend updating to Vision 2019 SP2 as it fixed a performance issue with SP1 involving multiple selections. Quote Link to comment
Gaspar Potocnik Posted January 17, 2019 Share Posted January 17, 2019 I've had this same problem when using sACN, the workaround I found was either using Artnet or restarting the App n number of times until it was OK. JIRA has already been generated on my side a coupe of months ago... 1 Quote Link to comment
thelightingguy Posted January 17, 2019 Author Share Posted January 17, 2019 Thanks. I updated to SP1 today and this is the first time I have seen it. I didn't see the SP2 but I can try that and let you know if its still there. I am using sACN which I would like to continue to do from and ION console. The whole building runs on it so I wanted to try and keep that instead of Artnet. Quote Link to comment
Vectorworks, Inc Employee Edward Joseph Posted January 17, 2019 Vectorworks, Inc Employee Share Posted January 17, 2019 Hey @thelightingguy try turning off auto graphics switching. Occasionally, the macbook pros aren't sure which one to use. Go to System Preferences>Energy Saver and uncheck the box, then launch Vision. 1 Quote Link to comment
Brandon Posted April 5, 2019 Share Posted April 5, 2019 I am intermittently having the same issue. I seems restarting Vision a few times sometimes fixes it, leaving the preferences window open fixes it (but then won't let me select and change fixtures) and playing with the rendering quality preferences sometimes fixes it. What seems interesting to me is as soon as I launch Vision my gpu meter spikes to full throttle, even before I open a file in vision. When it is having the "must be moving mouse to render" problem, the gpu meter jumps to full if I stop moving the mouse, but drops to about half when the mouse is moving. 1 Quote Link to comment
Vectorworks, Inc Employee bbudzon Posted April 8, 2019 Vectorworks, Inc Employee Share Posted April 8, 2019 If VSync is enabled, I do not believe it should be pegging your GPU at 100%. If you select ROOT in the Scene Graph Dock and press the 'o' key, it will show an FPS meter. If this is a very large number in an empty scene, you likely have VSync disabled. I highly recommend running with VSync unless if you are testing/comparing performance of the rendering engine. Have you seen this issue in previous SP's of 2019 or previous releases of Vision such as Vision 2018? Quote Link to comment
Brandon Posted April 9, 2019 Share Posted April 9, 2019 So I just updated to SP3 and I still intermittently am experiencing the freezing if I am not moving the mouse. I doesn't seem to be pegging the gpu when no scene is loaded though. VSync is enabled. FPS without a scene loaded is right around 60, and my gpu meter goes up, but is sitting around 50%. I just started working with the Vision software so I was never on 18, but I was having the issue before updating to SP3. 1 Quote Link to comment
Vectorworks, Inc Employee bbudzon Posted April 10, 2019 Vectorworks, Inc Employee Share Posted April 10, 2019 Can you please post your system specs? Quote Link to comment
Brandon Posted April 10, 2019 Share Posted April 10, 2019 MacMini 2018 running OSX 10.14.4. 3.2Ghz i7. 16GB ram. Running a Radeon RX Vega 64 8GB externally over Thunderbolt 3 in a Sonnet eGFX Breakaway Box 650. 1 Quote Link to comment
Gaspar Potocnik Posted April 12, 2019 Share Posted April 12, 2019 Are you running Artnet or sACN? Mac or windows? Quote Link to comment
Vectorworks, Inc Employee bbudzon Posted April 12, 2019 Vectorworks, Inc Employee Share Posted April 12, 2019 On 4/10/2019 at 5:54 PM, Brandon said: MacMini 2018 running OSX 10.14.4. 3.2Ghz i7. 16GB ram. Running a Radeon RX Vega 64 8GB externally over Thunderbolt 3 in a Sonnet eGFX Breakaway Box 650. @Brandon We've done limited testing of external GPU's over Thunderbolt. I can't see any reason it wouldn't work if you aren't having issues with other OpenGL applications, but perhaps there is something wonky going on in the Vision 2019 code that is messing with the drivers. Do you have boot camp installed? If so, does the issue happen there as well? Would you be able to test Vision 2019 on a system that has a dedicated graphics card to verify the issue is specific to the external GPUs? Sorry for any inconveniences this has caused you! I've let the Vision team know about the problem so we can look into acquiring equipment for internal testing. Quote Link to comment
Brandon Posted April 12, 2019 Share Posted April 12, 2019 @Gaspar Potocnik I am running sACN and its a Mac. @bbudzon I don't have boot camp on this machine but can look at getting that installed to test it out. I don't have a system on hand right now with any kind of decent internal graphics card either, I'm working on a show that is next week and the file is pretty big. I seem to have things working smoothly for now, the issues I was having seemed to possibly be file related. After several tries sending to vision from vw, I eventually get a file that works just fine. The files with issues also seem to have some kind of various issues with objects randomly missing, a stick of truss in one, a light fixture in another, etc. Just going back and sending to vision again from the same vw file without any modifications eventually gets me a vision file with all objects showing up correctly, and that isn't having the rendering problems 1 Quote Link to comment
Vectorworks, Inc Employee bbudzon Posted April 12, 2019 Vectorworks, Inc Employee Share Posted April 12, 2019 @Brandon Any help you can provide will help us help you as well as the next customer that comes along so it's greatly appreciated! One thing I noticed was you kept using the phrase "send to vision". I just wanted to make sure you saw my post about MVR support in VW/Vision 2019 SP3. If you aren't exporting an MVR and opening that in Vision, give it a try! We weren't able to switch the "Send To Vision" command from ESC to MVR in a SP release, but it should switch to MVR most likely for 2020 😉 Quote Link to comment
Brandon Posted April 12, 2019 Share Posted April 12, 2019 @bbudzon I did give it a try, but it doesn't handle layering quite right. When exporting the MVR and choosing to export just whats visible in vw, it still exports all the layers in the drawing. 1 Quote Link to comment
Vectorworks, Inc Employee bbudzon Posted April 12, 2019 Vectorworks, Inc Employee Share Posted April 12, 2019 Yes, unfortunately that is a known issue on the VW side of SP3. We are working to resolve the problem in SP4. Layering issues aside, did MVR fix your rendering issues with being forced to move the mouse? That will definitely help us narrow the bug down in the code! Quote Link to comment
Gaspar Potocnik Posted April 15, 2019 Share Posted April 15, 2019 I've tried this out again, with a old .v3s file (previous to sp3) and a new .mvr file generated with SP3 and the problem persists, with sACN on a Mac, sometimes you get latency (or mouse move to render) and sometimes you don't. Artnet works fine. I guess this bug wasn't fixed... @Brandon can you try using artnet to see if you get the same results? Quote Link to comment
Vectorworks, Inc Employee bbudzon Posted April 15, 2019 Vectorworks, Inc Employee Share Posted April 15, 2019 @Gaspar Potocnik What DMX Provider were you using before Artnet that seemed to be break the renderings unless the mouse was moving? sACN! Sorry! You are on OSX, correct? Also, can you please post your system specs? Quote Link to comment
Gaspar Potocnik Posted April 15, 2019 Share Posted April 15, 2019 13 minutes ago, bbudzon said: You are on OSX, correct? Also, can you please post your system specs? This happens con any Mac I try it, 2016 MacBook Pro 15" Touch Bar, 2010 Mac Pro with Vega 64, custom Hackintosh. JIRA was submitted 11/16/18 though I had some emails with tech support about it even before. Quote Link to comment
Vectorworks, Inc Employee bbudzon Posted April 15, 2019 Vectorworks, Inc Employee Share Posted April 15, 2019 Just now, Gaspar Potocnik said: This happens con any Mac I try it, 2016 MacBook Pro 15" Touch Bar, 2010 Mac Pro with Vega 64, custom Hackintosh. JIRA was submitted 11/16/18 though I had some emails with tech support about it even before. I'll ping tech support and QA on this again and see if we can reproduce the issue on any equipment in house. That will make it much easier to debug the code! Quote Link to comment
Vectorworks, Inc Employee bbudzon Posted April 15, 2019 Vectorworks, Inc Employee Share Posted April 15, 2019 On 1/17/2019 at 4:13 PM, Gaspar Potocnik said: JIRA has already been generated on my side a coupe of months ago... @Gaspar Potocnik Can you please give me the ticket number? I'm having trouble locating it in JIRA 😞 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.