1. I found a bug. What should I do?
  2. I make every effort to make my scripts bug free but it happens. Feel free to reach out to me through the Contact page and tell me about the bug. Please provide the steps necessary to recreate the bug. Without the steps, it becomes very time consuming for me to track the bug down.

  3. I have a feature request. Can you add it?
  4. Feature requests are great and you're more than welcome to tell me about it through my Contact page. I can't guarantee I can implement it as I make every effort to make my script as production ready as possible. I have a full time job and scripting is more of a hobby for me so I just might not have the time to add the new feature. If the script is uncompiled, you're more than welcome to add the functionality you want.

  5. I have a great idea for a script. Can you make it?
  6. Maybe. Several factors will determine if I can make your script.

    • Do I have the time? My full time job takes up a lot of time and energy so I just might not be available.
    • Is it even possible with the SDK.
    • Am I skilled enough to create this script. I'm not an expert with the LightWave SDK. I would describe myself as a casual scripter. So if your request deals with areas of the SDK that I'm not familiar with, that'll be an obstacle. I don't mind the challenge but with limited free time I just might not have the free time. That being said, you're more than welcome to ask.

  7. I bought your script. Can I get a refund?
  8. Sorry but all sales are final. I offer a limited version of the script for evaluation purposes or for those that don't want to buy the unlocked version. The only difference with the free/evaluation version is that your workflow will be restricted (number of possible items, number of layers in a file, etc) but the script has the same capabilities as a licensed one.

  9. I bought your script and provided the incorrect dongle id. What should I do?
  10. Send me the correct dongle id through my Contact page. Note: I reserve the right to deny sending you a new license if I suspect you're requesting new licenses to get around buying additional licenses.

  11. I'd like to get into scripting for LightWave. Do you have any recommendations on how to get started?
  12. Well, I hope you have a lot of patience. Scripting isn't hard but it will take awhile to learn. Especially LightWave's implementation of python as what you need is spread out across the python, the C and the Lscript SDK. I learned scripting by dissecting other people's scripts and that's why I keep many of my scripts uncompiled. I would recommend starting there. Lscript is the easier of the two scripting languages but I would recommend going straight to python as Lscript will eventually be deprecated. Below are links to good resources.

    • LScript
      • The LScript section of the NewTek forum is a good area to learn. I've learned a lot. It's not unusual for someone to ask for help and for another forum member to actually post the code.
      • Mike Green's lscript page is good if you're looking for lscript reference.
    • Python
      • The LScript section of the NewTek forum is a good area to learn for the same reasons stated above.
      • Ryan Roye has an Introduction to Python tutorial. I have not seen it but if it's like any of his other tutorials, I'm sure it is excellent.
      • Just Add Milk has examples of LightWave python code. It has excellent examples of how to build the ui panels in python.