-
Notifications
You must be signed in to change notification settings - Fork 267
help.FAQ
⚠ This page has moved. The current version is at help.tixl.app/using/FAQ/. This wiki copy is no longer maintained — edits made here will be lost.
Please contribute and edit this page. ♥
Installing Visual C++ Redistributable might help: vc_redist.x64 (from https://learn.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist?view=msvc-170)
To be honest, I am not really familiar with TD. From what I have seen both applications use a Directed Acyclic Graph (just like Houdini, Maya, Grasshopper and countless other node based programs). Information flows from left to right and both rely heavily on visualizing texture outputs. What might set TiXL apart is its extensive use of key frame animations and time manipulation possibilities. It is also very very good for live coding with Shaders and C#. Also, since TiXL has its origins in the Demoscene, it can export small size executables.
As far as I know TD has a huge community and tons of features and is probably much more stable, great documentation and support -- all the things you would expect from a mature commercial product.
The two might look similar on the surface which might make the transition between the two easy. But I would be surprised if the similarities run very deep.
We can totally understand this question. We work with Macs, too. And since the latest hardware push with the M1 silicon, Apple once again became an very promising platform.
At the moment however we are focusing on a single use case and moving fast. For this DirectX11 is the ideal API because it fits the sweet spot between performance, features and established development Tools like RenderDoc.
In the long run the picture looks different: TiXL is made with ImGui and .netcore. Both technologies are available for Linux and Mac. In theory porting the user interface layer should be possible in a weekend or so. A completely different story are all compute-, image- and rendering effects. Vulkan is a vastly more complex and verbose API than DirectX. So porting these would be a very big undertaking. Questions like backward compatibility to older TiXL projects or support for multiple rendering APIs are two more question that we need to address once the time has come to make the transition.
If you have a background in .net and Vulkan helping us on that front might be the perfect opportunity to contribute.
If you're using Linux, you can already use TiXL today: See Install on Linux
New Standalone Version available with significant updates and quality of life improvements...
Get the latest Standalone version here → https://github.com/still-scene/t3/releases/
At the moment, you still require:
We invested a lot of care and to design a software architecture and data format that maintains backwards compatibility when updating. So if you use the following guide lines updating with git should „just work“:
- Never modify Symbols in the
lib.*namespace without submitting a pull request. - Don’t work directly in the [Dashboard] operator -- create your own playground or project ops instead.
- Use a consistent namespace for all your Operators like
user.yourname.project. - Carefully separate your personal resource files. We suggest to create folders like
Resourced/user/yourname/projectTitle/for this.
If you are using git pulling the latest version from master should work without a hitch. There is a video tutorial demonstrating how it works.
If you are using a stand alone version, you would need to move...
- all files in .t3/
- Your resources
- And you custom ops to the new version.
In the Long run this method should be improved with more comfortable migration features.
See Exporting Videos
We're sad to hear that. But not all is lost. TiXL automatically saves backups every 3 minutes. Read more about backups
Possible reason for startup problems can be...
- A crash while saving lead to incomplete or empty files in
/Types/Operators. - The internal state of an operator got corrupted and saved.
The user-facing documentation has moved to help.tixl.app. Edits made to pages on this wiki will be lost — please edit the sources under .help/docs/ in the main repo instead.
- Welcome
- Installation
- Introduction
- Basic concepts
- How TiXL works
- Video tutorials
- Keyboard shortcuts
- Exporting videos
- Exporting executables
- Live performances
- Presets and snapshots
- FAQ
- Operator reference
These pages stay here — they're for people building TiXL from source.
- Installing the dev build
- Coding conventions
- Operator conventions
- Developing operators
- Writing code ops
- Working with git
- Integration tests
- Manual testing plan
- Using RenderDoc
- Debugging the Player
- Visual Studio Code setup
- Standalone builds
- Release issues
- Audio roadmap
- Ideas for operators
- Transform gizmos
- Context variables
- Changing file-path format
- Updating the Home template
- Proposed breaking changes for main
- TiXL vs Tooll3
- Contributing