I don’t have the answer to your question, but I’d be wary of including any special characters in your script code – even within a standard codeset.

For example, · displays as shift-jis characters in the JPN version of 3ds Max, and × causes the CHS version to throw an error when attempting to parse the script. I had to replace the latter with (bit.intAsChar 215).

Hey Richard,
Thanks for the reply. Can you tell me how those characters fared when included in the file as part of comment blocks?

Haven’t used them in comments – so I’m afraid I haven’t the foggiest. If the problem is with interpreting the actual script (as opposed to just reading in the script file), then I’d suppose comments should be fine.

As for your original question, go to…
Tools -> Open Global Options file
Search for ‘unicode’, you should get a section that originally looks like this:

# if set to -1, max will set the code page and character set
code.page=-1

# Internationalisation
# Japanese input code page 932 and ShiftJIS character set 128
# code.page=932
#character.set=128
# Unicode
# code.page=65001
# character.set=204

Change that to:

if set to -1, max will set the code page and character set

# code.page=-1

Internationalisation

Japanese input code page 932 and ShiftJIS character set 128

code.page=932

#character.set=128

Unicode

code.page=65001
character.set=204

Then re-start 3ds Max, and the editor should be using UTF8 / Unicode.

Your 'full block' looks like an outline of a full block here under the variable width font, but looks like a full block with the monospaced font of choice (Andale Mono)

That’s really useful info, and it works!

However, it looks like I can just add the following lines to the Users Preference file, which overrides the Global Preferences file.

code.page = 65001
character.set = 204

Thanks for the info,
Cheers,
Dave

yep, that’ll do, too Saw what you did with it in the other thread – cute