2
May
2026

Yannick "TAIS" Tholomier


A + for LightWave

Yannick Tholomier

LightWaveDigital: Can you start by telling us about yourself and your career?

Yannick Tholomier: My name is Yannick Tholomier. I am a VFX/3D supervisor, project manager, and director with around 30 years of experience in visual production. Before founding my own studio, I led 3D graphics departments for several production service companies. I have always maintained a strong technical interest in LightWave, plug-in development, automation, and workflow tools.

LD: How long have you used LightWave?

YT: I’ve been using LightWave since version 5.5 — but that wasn’t the beginning.

It all started with drawing — filling time with imagination.

The first computer I ever touched was a Thomson TO7-70, with its light pen and some truly awful games. That naturally led me to programming my own games in BASIC and experimenting with early graphics using the pen.

Things accelerated when I got noticed and was invited to demonstrate Deluxe Paint on an Amiga at a trade show — that’s when I got my hands on my first Amiga 500.

A summer internship introduced me to the Amiga 3000 and TVPaint, then the 4000… and eventually to PC, LightWave, a TBC, and the magical world of video. Photoshop didn’t exist — at least, not in my world.

LightWave became my path. I discovered DFX+ through a bundle, then Fusion. Suddenly, I could do everything.

I was hired by a post-production company, where I built a full LightWave pipeline — multiple workstations, a render farm — which led me to scripting in LScript to optimize and automate workflows for the whole team. It was a real pleasure, even as we maintained a relentless pace producing TV content.

Later, I built another department for a service provider, and eventually started my own studio, IJIN PROD, which I ran for 18 years. I was joined by a crew of loyal LightWave artists Gaël, Karim, Salif, Vbk, JeanPhi, Sylvain, Salomon, … We were like mercenaries, armed with our magical Swiss Army knife: LightWave. What a time it was. Everything had to be built, and we built it our way.

LD: What is the feature you use most often in LightWave for your work?

YT: I’ve used LightWave as the backbone of my pipeline for over 25 years.

The feature I’ve relied on the most — and simply couldn’t have worked without — is LScript.

It was essential because it allowed me to work around the software’s limitations, speed up slow processes, and essentially extend LightWave beyond its native capabilities. It opened up an entire ecosystem: discovering third-party tools, integrating them, modifying them, and adapting everything to fit the specific needs of the moment — whether that meant solving a production problem, automating a tedious process, or simply saving the day under pressure.

LScript was also my gateway into coding — much like the scripting language George was for Aura.

An entry point. A learning language. Simplified, yes, and limited — but accessible to artists (well… slightly technical artists at least). And that matters, because when I look at something like Python, for example, I find it complex: a language designed by programmers, for programmers. But LightWave is a creative tool for artists, often generalists, who may also need to code. Leaving coding only to programming experts is like cutting off one of LightWave’s tentacles.

LScript and Python side-by-side

LScript and Python side-by-side

What I’ve always needed is for LightWave — through the LScript Commander or the Python Commander — to properly expose everything that can be exposed:

the state of UI buttons, all property statuses, all events, all commands — everything that may have been overlooked.

(For example, it is no longer possible to set an RGB output path command in LightWave...)

If I had one final thing to say, it would be this: while new tools are always welcome in LightWave, what I really want is for what we already have to be finished and refined.

I’m far more eager to see the 300+ user-reported bugs listed on LW+ fixed, along with the hundreds of pending tweaks.

These are real requests from users who are constantly dealing with frustrations and slowdowns — and who, with the genuine intention of improving LightWave, take the time to share their feedback and ideas.

To be clear, LScript isn't being removed. There are many parts of LightWave itself that rely on LScript. There is, however, no further development work being done on LScript.

LD: Tell me about the LW-Database

YT: The LW-Database is primarily a structured catalogue of LightWave plug-ins, scripts, and related assets. It currently indexes roughly 3,500 plug-ins (32-bit and 64-bit) and around 500 additional assets, all organised with filtering, tagging, visual previews, and creator references whenever available. Beyond simple indexing, the database also functions as a preservation effort, recovering tools and resources that have disappeared from the web (including from the Wayback Machine).

LD: What inspired you to create it?

YT: When I first started using LightWave, a site called Flay.com played a major role in shaping my interest in the software. Every day it highlighted new tools that improved efficiency or opened new creative possibilities. It quickly became clear that the plug-in ecosystem—its developers, its community, and its culture of sharing—was an essential part of LightWave itself. After Flay disappeared, Ken Nign continued the effort with LWPluginDB, keeping third-party development visible. However, when this database was later integrated into the NewTek website, the active monitoring and community-driven visibility gradually declined, and many independent developers slowly disappeared, particularly during major transitions of the software. During the more recent revival of LightWave, it felt important to help reignite that ecosystem. While running my VFX studio, I constantly searched for tools that could save production time, which led me to develop a deep knowledge of the plug-in landscape. I eventually decided to consolidate my internal catalogue into a structured community resource, both to clarify a fragmented situation and to preserve as many tools as possible before they disappeared.

LD: What are your plans for it?

YT: The next phase focuses on integration, expansion, and long-term sustainability:

  • Direct integration of the catalogue inside LightWave through a plug-in access.
  • Indexing of tutorials, learning resources, and existing video material
  • Completion of descriptive thumbnails and visual documentation for remaining entries
  • Continued archival recovery of disappearing plug-ins and developer resources
  • To ensure long-term maintenance and monitoring, the project will gradually move toward a modest subscription model designed to cover hosting and operational costs. Access will be granted free of charge to active contributors, particularly those helping expand the database or actively participating in the LW+ Discord community.

LD: Is there a way users can support or help the future development for the LW-Database?

YT: The most valuable way to support the project is by contributing missing plug-ins, archived installers, documentation, or legacy assets that may still exist in personal collections. Many historical LightWave tools likely still exist on private storage, and sharing them plays an essential role in preserving the ecosystem. Of course, if users can't provide us with any of these things but who really value what we're doing and want to keep us alive, then any user can support us financially with a donation of any amount via our donate button on the site.

Their generosity really makes big difference and has our heartfelt thanks.

LD: Tell us about the Discord channel you made.

YT: LW+ is a Discord server dedicated to LightWave resources, plug-in development, and community collaboration. Originally created to support the LW-Database and the LWUI+ interface plug-in, it later evolved into a broader LightWave community hub structured more like a forum than a traditional chat server. It provides:

  • Contribution channels where users can submit plug-ins and archived resources for indexing
  • Daily LightWave news tracking and discussion highlights
  • Public bug and feature tracking lists
  • Ticket-based help sections for structured technical support
  • Technical discussion and benchmarking areas
  • Development-focused resource channels
  • A Japanese-language channel helping connect international LightWave communities...

All of this operates under the supervision of LWBot, a custom-developed bot designed to assist moderation, automate certain organisational tasks, and help archive important information shared within discussions.

LD: LW+ has loads of great threads, tips and links. Are there any you'd like to highlight for readers of this blog post to get started?

YT: In recent years, Discord has established itself as a strong alternative to traditional forums, offering real-time interaction, instant support, and features like voice chat and screen sharing. While it’s especially popular with newer generations, proper structure is essential to avoid chaos.

If I had to highlight current “hot topics” for new members, I would recommend checking the Showcase section, especially third-party developments. Many developers have adopted LW+ to share and track the progress of their tools.

AI-assisted programming tools have unlocked hidden potential in many LightWave artists, enabling more users to code and significantly boosting the productivity of experienced developers.

Chunderburger is developing a LightWave ↔ Blender bridge

Mattc is working on several tools and recently released The Scattering, an improved version of my script Grassit, which was also born on LW+

You can also find hidden gems scattered throughout the server, such as a revival of GENE3, a plugin for generating organic and tentacle-like forms—something long missed by experienced users.

LW+ has helped bring attention to talented developers like Emulyator, known for AI tools for LightWave and procedural animation systems that existed even before LightWave’s ProGeoNodes.

Today, Michael Frisk is probably among the most advanced in this field.

LW+ is a place of ongoing exploration—where technical knowledge, tools, and ideas are shared efficiently, clearly organized, and easy to find thanks to categories and tags.

LD: Any other information you would like to add?

YT: The take away from all of this is; this project was created by LightWave users, for LightWave users, and is kept alive by LightWave users. Come and be part of it.