-
Notifications
You must be signed in to change notification settings - Fork 54
Note: If you have any questions, just double click and add them.
Excellent question! The previous version of Tooll was OpenGL, 3d-framework with which we had a lot of problems. So this time, we decided to try something new and go for Direct-X 11. Additionally C# and .NET is very nice for development. Eventually, we might port T2 to Mac and or even HTML5/JS but for the time being, it's limited to Windows.
Whenever tooll crashes, we wanna know. Please report a new issue and attach the crash-report.txt. If you can remember what you did before the crash, perfect, But if you can even reproduce the crash, it's quite likely that we fix it right away!
It's an mislead attempt to be funny. It's a reference to Werkkzeug combined with a hint of the German word toll.
Yes indeed. The central entry point is the "Default"-operator. It's a local(!) user-specific playground. Bigger projects are structured within their own Operators (e.g. "Square"). These project-Operators have their own namespace (e.g. "projects.square"). Any Operator-Type created inside an project name-space derives that namespace. By this, things stay halfway organized.
Read about this topic more under Materials, Lighting and Shading
Sadly, there are many potential reasons for this behavior. Make sure that:
- You installed the latest version of .net 4.5.
- You have a recent graphics card with latest drivers (we require a DirectX11 compatible graphics card)
- Your Windows is at least Win7
- Your Windows is 64bit
- You start tooll with admin rights.
- Try to remove the
./Temp/Cache/directory
- Sadly, there're a couple of known ways to crash Tooll. Please check this list first.
- Can you reproduce the problem? Great! Please report a bug.
Sadly, it's really hard to determine what went wrong. Often this happens through extreme memory consumption. You can send us the latest Log-File from the Logs/ folder so we might be able to identify the cause of that.