About me
indice
Where the idea comes from
At the beginning, there was no “serious” project.
I simply wanted to have fun with friends when they came to visit me: a few outings, a bit of adventure, and the desire to do things properly.
For some time, I had already been preparing roadbooks “by hand” and printing them as PDFs. That was where the first need came from: an essential tripmaster, clear and accurate enough not to ruin your day because of a number that does not match.
Then came the second idea: if creating a roadbook took me hours, why not build a tool that could really help me? A simple, logical program, able to manage icons, junctions, road types… without unnecessary complications.
And meanwhile, in the back of my mind, there was always a “maybe later” thought: what if one day everything could be read digitally, in a reliable way?
That spark, in truth, had been there for a very long time. Since 1978, the year of the first Paris-Dakar, I had admired the system invented by Thierry Sabine: turning approximate directions into clear vignettes, with tracks, junctions, obstacles, and that human touch of hand-drawn sketches.
Later, when I started taking part in the 24 Ore del Frignano, I became truly fascinated. It was no longer a matter of “following a leader”: with the co-driver — just as important as the driver — you had to interpret the notes precisely.
“After 1200 meters, turn right, then another 600… after the isolated tree, go left downhill.”
And at night, because it is called 24 hours for a reason, everything became almost magical: paths described by a vignette and a few lines. A whole new world opening up.
Why these programs are freee
Because I am passionate about 4x4 and adventure.
I would have loved to find something similar already available — and maybe free. It would have saved me a year of work.
The project was born as something personal. I did not originally plan to distribute it. I simply wanted a tool that would help me create roadbooks in a more orderly and consistent way.
But when I saw that something good was coming out of it — at least according to my vision — and, above all, something complete, I thought it would be nice to share it.
If you like organizing events, whether 4x4, motorbike or even bicycle events, using a roadbook, I believe everyone should have access to modern tools to do it, without being limited to trial versions.
From the beginning, I never tried to compete with commercial programs.
On the contrary, I deliberately set some limitations: for example, an essential management of the main junctions, and a broken line instead of more complex and configurable graphic connections. Simple choices, but functional.
The roadbook structure also follows this philosophy:
- First column: only odometers, total and partial, and the note number.
- Second column: the central part, dedicated to graphic indications — junctions, directions, obstacles and landmarks.
- Third column: short text lines, the CAP, which is the direction to follow, and, in small size, the waypoint coordinates.
I tried to keep everything clear, readable and logical.
Simple does not mean poor: it means focusing on what is really needed when you are there, on a track, maybe at night.
Adventure before software
I am a perfectionist.
When I began travelling toward what, for me, was the “dream land” — Africa — one thing was very clear: either I really learned how to read maps and compasses, or I would depend on guides to face the trans-Saharan tracks. And I did not want to depend on others in my adventures.
So I studied cartography almost obsessively. To the point where I could “see” beyond the drawn lines, mentally reconstructing a three-dimensional shape with just one look at the contour lines.
Map compass, sighting compass, inclinometer, which I was already using during caving trips: simple tools, but tools that must be understood deeply.
I got lost, and I found my way again. I took a few risks on forbidden tracks. I had mechanical problems, fortunately solved on my own. All experiences that teach more than any manual.
And sometimes, the manuals themselves were the problem.
They often explained concepts while assuming a “know-how” that I did not yet have. Too many notions depended on previous knowledge that had never really been explained.
Perhaps this is also why I designed the programs to be friendly. With logic, order and simplicity.
With detailed instructions, concrete examples, and sections like “Tips”, designed for those starting from zero.
With time, everything becomes easier.
But when I decided to distribute these programs, I understood that they had to be accessible to everyone: even to those who have never done anything similar and simply want to try.
In the end, this is the LSU philosophy:
Logical, Simple, Useful.
A simple invitation
These programs come from experience, study, and many mistakes made in the field.
They are not perfect, but they are built with care and with a clear logic.
If you want to try them, do it with curiosity and a little patience.
They are not “magic” tools: they work well when the person using them really wants to understand how they work.
I am always available to help, clarify doubts or explain details that may seem not very intuitive — including note management, which is not always immediate at first use.
I believe in meritocracy and personal commitment.
If there is a willingness to understand, there will always be willingness to help on the other side.
They are not perfect, but they are built with care and with a clear logic.
If you want to try them, do it with curiosity and a little patience.
They are not “magic” tools: they work well when the person using them really wants to understand how they work.
I am always available to help, clarify doubts or explain details that may seem not very intuitive — including note management, which is not always immediate at first use.
I believe in meritocracy and personal commitment.
If there is a willingness to understand, there will always be willingness to help on the other side.