stim list text showing up as random characters

[jarvis24]

Nice problem solving

Just wanted to confirm that DirectRT does in fact read stimulus references in a stim list as if each were literally transplanted within the cells of an input file. And, as by default, images require no prefix character, entering the stim dog will lead DirectRT to search for an image called "dog.bmp". If it can not find the image, it will display "dog.bmp" on the screen as a placeholder. If the word dog is to be presented as text then it would need to be entered as ~dog, or as a sound, !dog, etc.

And yes, I do believe that quotes are a problem for stimlist content as they can be mistaken as data / field delimiters when DirectRT is reading the file. We will try to resolve this in the next version.

See also:

http://www.empirisoft.com/directrt/h...ectrt_stim.htm

[Kira]

I have also encountered the same problem whereby I am pulling text from a stimlist and sometimes instead of the text I see ".bmp" on random trials. I have checked and all text in my stimlist is prefaced with a ~ so I am completely mystified as to why this is still happening! My stim all look like this "~A 4." If you have any ideas please help me out!

Thanks so much!

[BJG]

Hi,

I realise this thread is a little old now but thought I'd post my solution to the initial query in case anyone else is having the same issue. The solution was to resave all of the text files as UTF-8. I didn't know what this meant, but all it involved was opening up the text file in Notepad and clicking 'Save as'. Keep the file name the same but in the dropdown box next to 'Encoding' select UTF-8 (it was set on ANSI for me). Now all punctuation in the text is showing up fine (previously the apostrophes were showing up as rectangular symbols).
Hope this helps someone.

Bethanie

[jarvis24]

Thanks very much Bethany. I'll also look into why this is happening (so a fix like this wouldn't be necessary!). Regardless, it's great to see a temporary work-around posted. Thanks again. Btw, can you tell me exactly which version you had this issue with? I know you mentioned in an email it started with DirectRT v2010-- was that 2010.2 or 2010.3? -Blair