Search

Search

Help

Page 7 of 41. Showing 401 results (0.011 seconds)

  1. Renders submitted through the command line fail or lock up

    Due to changes in render software architecture, a mechanism called JobObject which is used by the Qube! worker disrupts the internal code in common renderers such as 3dsmax and AfterEffects. The worker must be notified not to use the JobObject. To do this…
    Qube 6.6May 11, 2015
  2. Renders submitted through the command line fail or lock up

    Due to changes in render software architecture, a mechanism called JobObject which is used by the Qube! worker disrupts the internal code in common renderers such as 3dsmax and AfterEffects. The worker must be notified not to use the JobObject. To do this…
    Qube 6.7Jan 11, 2016
  3. Renders submitted through the command line fail or lock up

    Due to changes in render software architecture, a mechanism called JobObject which is used by the Qube! worker disrupts the internal code in common renderers such as 3dsmax and AfterEffects. The worker must be notified not to use the JobObject. To do this…
    Qube 6.8Oct 06, 2016
  4. Renders submitted through the command line fail or lock up

    Due to changes in render software architecture, a mechanism called JobObject which is used by the Qube! worker disrupts the internal code in common renderers such as 3dsmax and AfterEffects. The worker must be notified not to use the JobObject. To do this…
    Qube 6.9Jul 05, 2017
  5. Renders submitted through the command line fail or lock up

    Due to changes in render software architecture, a mechanism called JobObject which is used by the Qube! worker disrupts the internal code in common renderers such as 3dsmax and AfterEffects. The worker must be notified not to use the JobObject. To do this…
    Qube 6.10May 23, 2018
  6. Renders submitted through the command line fail or lock up

    Due to changes in render software architecture, a mechanism called JobObject which is used by the Qube! worker disrupts the internal code in common renderers such as 3dsmax and AfterEffects. The worker must be notified not to use the JobObject. To do this…
    Qube 7.0Nov 04, 2020
  7. Renders submitted through the command line fail or lock up

    Due to changes in render software architecture, a mechanism called JobObject which is used by the Qube! worker disrupts the internal code in common renderers such as 3dsmax and AfterEffects. The worker must be notified not to use the JobObject. To do this…
    Qube 6.4Nov 05, 2012
  8. Renders submitted through the command line fail or lock up

    Due to changes in render software architecture, a mechanism called JobObject which is used by the Qube! worker disrupts the internal code in common renderers such as 3dsmax and AfterEffects. The worker must be notified not to use the JobObject. To do this…
    Qube 6.5Nov 05, 2012
  9. What if I want to lock down certain hosts to specific groups that will only run jobs submitted to those groups?

    As we discussed, a host group is like an "alias" for a set of machines. You can assigned a host to more than one group, but jobs sent to the group will only run on those machines. A cluster is a priority scheme that will allow a job to run anywhere there…
    Qube 6.4Nov 05, 2012
  10. What if I want to lock down certain hosts to only run certain jobs?

    There are several ways to do this in Qube, but a best practice that we recommend is to use the worker's cluster and restrictions as outlined in How to use clustering for workers. Essentially, you set a worker's worker_cluster and worker_restrictions to th…
    Qube 6.5May 06, 2014