Post by perfectblackout on Nov 6, 2018 18:18:46 GMT -5
Running LW 6.0.18 Build 193
Hardware:
Windows 10
Intel Core i7-6700HQ @ 2.60 GHz
16GB RAM
NVIDIA GeForce GTX 970M
120GB SSD
Lightwright has always been a little bit sluggish on almost every system I've ever run it on. My old Macbook ran LW5 and scrolling was always choppy and sluggish. My current laptop (specs above) ran LW5 with few issues. A little sluggish while scrolling up and down and a short freeze when updating a cell while VW data exchange was active. But it was tolerable and I could work with it. However when I recently updated to LW6 I was shocked at how slow and sluggish it ran.
On my laptop (specs above) which more than meets the minimum system requirements LW6 is just plain slow. Clicking on a cell causes a 1-2 second delay before the cell is selected. Scrolling is nonexistent. Scrolling down or up simply freezes the screen until I stop scrolling, then after a 1-2 second delay the screen jumps to wherever it decides I stopped the scroll. Which, since I don't actually SEE a scroll means that I have no way of telling how far I've moved. The worst part is that anytime I make an edit to a cell, say changing the purpose of a light, the whole program locks up and all the data disappears revealing the yellow to white gradient that acts as a background for the program's window for a few seconds. After which all of the data reappears with my edit made. This process is twice as slow when I'm making an edit with VW Data Exchange active, then the delay from hitting enter after making the edit to seeing the data reappear is closer to 5-6 seconds. In effect LW6 is completely useless to me in its current state. I'm reverting to using LW5 for the time being until LW6 is fixed.
I've searched this relatively new forum for posts (by the by putting a link to this forum on the main Lightwright site, maybe under the support section, would be immensely helpful. I didn't even know this forum existed until I got a popup in LW6 telling me about it) that might be related to this issue and only found two, neither of which provided a workable solution. One person had it fixed by an update last year and the other saw a response from John saying that he was working on a fix.
Is this a known issue for the current LW6 version? If so when can we expect an updated version that fixes the problem? If not is there anything that anyone could recommend I try to fix the issue?
I hope to hear back soon.
Thanks,
- A very frustrated LD
