Never seen this before. I did the normal update, now I have to restart CorD from the Mac to launch VEP.
Is this intended with the new update?
189,681 users have contributed to 42,667 threads and 256,811 posts.
In the past 24 hours, we have 0 new thread(s), 5 new post(s) and 53 new user(s).
Never seen this before. I did the normal update, now I have to restart CorD from the Mac to launch VEP.
Is this intended with the new update?
(Once I do, a Console window opens with these commands:
C:\Windows\system32>tscon 2 /dest:console
C:\Windows\system32>"C:Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe -server"
Hi,
We added this as a workaround for broken Intel OpenGL drivers, causing crashes over remote desktop. The workaround opens up a local console and asks the user to reconnect remote desktop.
It might be that we can identify the GPU name, and only perform this workaround when the faulty adapters are in use.
The other option is to take this behavior away completely, and tell everybody using such chips to buy more professional graphics cards.
Best,
Paul
This makes sense, as I'd been having problems with MIR and note having the right chipset for OpenGL. I've added a card (but that is complaining about drivers still).
Thanks for responding. Maybe it's worthwhile to add a notification window there saying why?
Bumping an old thread...
It would really be nice if this could be fixed, because it's incredibly annoying. This morning, for about the third time this week, I went through the following rigamarole:
It would really be nice if