The Demonstrator's office is in W109 and will be able to help you with Software Problems, you can also email them using animdemons@bournemouth.ac.uk
To report problems with either Hardware or Software please use Service Now. If there are physical issues with the Labs (such as doors not locking etc) these need to be reported to estates via estates portal
If you have issues with logging in you can go to the IT service desk in the Library or access the IT portal online.
The NCCA lab build is very complex and installing new software can be problematic. This is also compounded by the fact that we have both Windows and Linux builds.
For linux changing the build is relativly easy and we can sometimes just add new software (or you can even do it yourself locally).
Under Windows it is harder as we have no control over the packaging and installation of the software and it needs to be done centerally via IT services.
We have a "2 times a year" policy for software installs, once at the Christmass break and Once just after Easter. The software to be installed must be requested via Jon Macey. He will need to know the following.
Also note that licenses may be an issue. We have a limited software budget that is allocated at the begining of the year and we can't buy new licenses during the academic year. The core software installed should be sufficient for all projects required for the course.
All Renderfarm documentation is located in : /public/bin/ncca_RenderFarm/Tutorials/
Video tutorials:
Documentation:
you can setup houdini to run from the command line (i.e. hrender, hcustom, hython etc) by doing the following (this is the latest version but there are other version of houdini installed just change the point version).
cd /opt/hfs16.0.705/
source houdini_setup_bash
You should see a message saying "The Houdini 16.0.705 environment has been initialized." and be able to run hython for example.
You can also add the following to the .bashrc
# declare current Houdini version
export HVER=16.0.705
#initiate Houdini's secondary applications
cd /opt/hfs$HVER/; source houdini_setup_bash > /dev/null; cd;
This is usually due to being over quota. There are a number of reasons why this may be so.
The easiest way of seeing how much space you have used is by using the quota command in the shell.
quota -s
Disk quotas for user jmacey (uid ):
Filesystem space quota limit grace files quota limit grace
jh-na02:/vol/NCCA_Home
68216M 101376M 100G 538k 4295m 4295m
du -h --max-depth=1 ~
This may take some time but will show the sizes of all the directories and where you may need to remove files.
It is recomended that you use the /transfer directories to store (volatile) data for projects such as images and caches. This will be quicker as on the local hard drive, however they will not be backed up.
Most applications are installed in default locations and run via go Scripts (located in /public/bin/2017).
Sometimes we need to find out where and application lives to find other data and resources, the following is a list of usual locations for applications (you could also read the go scripts to find exact locations).
The majority of 3rd party apps are in the /opt directory
ls /opt/
3D-CoatV4-7 code hfs16.0.600 MATLAB pfx rawtherapee thepixelfarm
arduino-1.8.3 foundry hfs16.0.671 ncca pixar realflow TMP_QUBE
autodesk Golaem hfs16.0.705 NEW_PFX_QUBE_v6.9_wont_work Qt5.9.0 resolve var
Autodesk google katana Nuke10.5v4 QT_done Shotgun vrlclient.xml
ChaosGroup hfs16.0.557 Mari3.3v1 OFX QUBE_INSTALL solidangle yeti
other standard locations are /usr/bin /usr/local/bin /public/devel/bin
There are many libraries installed as part of the default build as well as a number of 3rd party development ones. To find which ones are installed we can use
ldconfig -p
You will notice there are many libraries installed so you may need to use grep to find the ones you want
ldconfig -p | grep -i egl
libva-egl.so.1 (libc6,x86-64) => /lib64/libva-egl.so.1
libnvidia-eglcore.so.375.66 (libc6,x86-64) => /usr/lib64/nvidia/libnvidia-eglcore.so.375.66
libgegl-0.2.so.0 (libc6,x86-64) => /lib64/libgegl-0.2.so.0
libQt5EglDeviceIntegration.so.5 (libc6,x86-64) => /lib64/libQt5EglDeviceIntegration.so.5
libEGL_nvidia.so.0 (libc6,x86-64) => /usr/lib64/nvidia/libEGL_nvidia.so.0
libEGL.so.1 (libc6,x86-64) => /usr/lib64/nvidia/libEGL.so.1
libEGL.so.1 (libc6,x86-64) => /lib64/libEGL.so.1
libEGL.so (libc6,x86-64) => /usr/lib64/nvidia/libEGL.so
libEGL.so (libc6,x86-64) => /lib64/libEGL.so
Libs may also be installed in locations such as /usr/lib64 /usr/lib /public/devel/lib
Resetting Maya can be a good first step in troubleshooting many issues that can occur, such as missing menus, failure to start, unexplained crash's that happen at the same point every-time or slow performance when moving objects in vertex mode.
When you remove your preferences, either by renaming or deleting the directory, Maya creates new preferences the next time you run the application. This refreshes tools and options to their default values, and often provides a quick fix for any new, unexpected tool behavior.
Before removing your preferences, check if you have saved any data in the affected directories, and create any backups that you require. (For example, if you have saved images in the \projects\default\renderData or \projects\default\images directories.)Workflow to remove all preferences
Maya recreates the default preferences directories in the same location. The interface is restored to the ‘factory default’ layout.