This page is meant to help you troubleshoot your experiment.
It is a good idea to keep the Debug window on (ie. do not use DebugOff) until you are ready to collect data: the Debug window can provide you with very helpful feedback when troubleshooting your experiment
Below is a list of common issues. Click to unfold troubleshooting instructions. If you don’t find an answer to your question, check the forums.
- You have named one or several files with an uppercase extension, eg. image.PNG. Make sure to rename your files so they all have lowercase extensions (remember to update your scripts accordingly if needed).
- You are referring to a native-Ibex controller (eg. DashedController) in your script but you made a typo on its name, or you forgot to upload its script to Controllers/js_includes, or you made a typo when naming the script file.
- First, check for any mismatch between the name of the file and the name as you typed it in your script or in your table. You won’t see an error message in case of a mismatch, but you will see everloading messages.
- Make sure that your resource file is properly uploaded to your experiment or to your distant host. If your resources are hosted on a distant server, check for any typo in the host’s URL.
- If your resources are in a zip file, make sure that they are placed at the root of the zip file (not embedded in a subfolder) and that you have properly set the CORS configuration (if you initially named the file htaccess.txt, make sure to rename it .htaccess)
- If your resources are hosted on a distant server (whether directly or not as part of a zip file) make sure that the domain is secure (https).
- Check that your table does not contain extra empty rows: if it does, your Template command will generate extra trials using (invalid) empty resources.
- Most browsers block automatic playback of multimedia files in an effort to block unsolicited ad-content. Make sure that your participant interacts with your experiment through a keypress or a click before automatic playback is supposed to start. Initial welcome/instruction/consent pages are an effective and sensible solution.
- Different browsers support different audio/video formats and encoding. If your audio or video file won’t play, try converting it using another format or another codec. As a starting point, you can check the w3schools guide on HTML Media for pointers on multimedia browser support.