corel motion studio 3d directx requirements

Corel motion studio 3d directx requirements software#
Corel motion studio 3d directx requirements windows#

Despite 3 or 4 cycles of that with DirectX, this quartz thing keeps coming back. Usually, because the prior version has a config item in a file that the new version does not update, and the result is weird incompatibility. Applications, even ones that are quasi tools, like virus scanners, periodically have not. Tools, like disk burners, have worked properly.

Corel motion studio 3d directx requirements software#

I do it that way because - burnt fingers, much cursing over quite a few years of software upgrades - I noted that installing over the top of a prior version does not always fix a problem. To clarify - that meant getting the latest version from their website and manually installing it, after uninstalling the version then resident on the machine AND running a registry cleaner, all aimed at getting to clean platform for the new install. I mentioned previously re-installing Direct X, as MS suggested. So clearly the calls to the DirectX functions occasionally break internally in DirectX.

Corel motion studio 3d directx requirements windows#

For a while, I thought that VS was the cause, but windows has never pointed a finger at VS, just at quartz. But it happens when I click to execute something. I haven't noted any particular pattern to it - eg always when using/doing a specific function. To further clarify the issue, the failure occurs when I'm using VS to edit a project file. And hence my remarks on that item in the first post. Which I did for the first few times, but it became pretty clear that MS did not know what caused the issue and was taking the easy way out. Queries to the MS answers board have always come back with 're-install the DirectX runtime'. And I've not been able to find out just what the quartz.dll library does. I acknowledge that quartz is needed - it's just that when the failure occurs, that is the program cited by windows as the failed item. Is Corel even interested in investing in effort to stabilise the interface between VS and the windows runtime stuff, and improve the look and feel of it's software? Either directly eg in a service pack for X5 or X6, and particularly on X7 (forthcoming)? It would be nice to have some feedback. In the brave new world, Corel is supposed to be reviewing these forum posts regularly.

That loses everything one has done in a project file since the last save, which is bloody irritating, but it gets back into business quickly enough.Įxperience of repeat failures over several VS versions clearly suggests that the VS interaction with this windows runtime is unstable in some way. Simply re-installing Direct X doesn't solve the problem long-term, and short term, its far quicker to simply close VS and re-start it. The previous advisories I've had on this problem with MS related to Direct X - which I have the latest version/updates for installed. Clearly VS is interacting with windows, and specifically quartz.dll, somehow.