Cool VL Viewer forum

(I am using Cool VL Viewer v1.32.0.24, May 25 2024 10:08:48)

I have looked at Henri's scripts and don't see anything different from how I am using string.find

I have reduced my Lua script to just enough to show what is happening for me.



This is what I see in the chat window:



The message clearly has the string of interest in it.

If I specify a pattern of just "M", it works, but in my actual script, I will need a whole word.

Your usage of Lua string.find() is simply incorrect. You should use:

That's what I first tried and got the same result. I added the optional arguments to see if making it a "plain" find (instead of regex) per the Lua 5.4 reference (https://www.lua.org/manual/5.4/manual.h ... tring.find)

Verify that you did not use UTF-8 characters in your dialog message (since you do not give the LSL script sources here, it is hard to find what is the problem); for example, are the "a" or the " x" of "Max" actual ASCII characters or are they some fancy UTF-8 variation ?...

Since your code works for finding "M" and not when trying to find "Max", there might be an issue with how the latter is spelled in your LSL script... Oh, and also verify that your Lua script is saved as ASCII/ISO/ANSI (i.e. 8 bits characters only) and not as UTF-8 (or, worst, UTF-16) by the editor you are using to write/edit it !

I verified here that your Lua code does work with the following LSL script:

I checked that and as best I can tell it not UTF-8 or other fancy characters.

I made sure my Lua script is ANSI, but that did not help.

I tried printing the message using print(string.format("%q", message)) and did not see anything fancy.

I am now working on printing the message as a series of byte values.

(I am new to Lua, though not programming. Usually I program in C.)

The only thing I can think about is an issue in your LSL script (please, post the relevant part of your LSL script (the llDialog() call and whatever code initializing the variables used in that llDialog() call), or with your operating system's configured locale; the viewer only knows about English (no UI translators/contributors), and maybe you configured a different (UTF-8 only) locale for scripts (in the "Preferences" floater, "General" tab) ?...

Also, you can use the Lua console ("CTRL ALT L" to pop it up) to test your Lua scripting; in this case, try:
Which should print:
If you get different values, there is a character encoding issue... See Unicode and Lua.

For any further investigation by me, please also post the viewer log file (with a log obtained running your script with the "Lua" debug tag enabled, via "Advanced" -> "Consoles" -> "Debug tags"); I'm tired to spend time poking in the dark to try and solve your issue...

I am assuming it's an encoding issue and working on a function to convert the characters in the message to a list of codes.

From experimenting, it seems the problem is with the "a" and the "x", so that limits what codes I have to get.

Thanks for looking at this.