-
Notifications
You must be signed in to change notification settings - Fork 200
dev.main branch faq
This page summarizes best practices and questions regarding the new operator structure branch.
- Install .net 8.0
- Install the latest version of Rider (at least 2023.3) or Visual Studio
- Rebuild solution
There are a bunch of warnings when building Editor:
Currently player has some errors caused by Windows forms not being available:
It would probably be important implement some kind of option to switch between users, so you can see all imported packages...
If an assertion is thrown during startup, the splash-screen is annoying. Is there a method around that?
-> Yes. I added the following change to SplashScreen.cs
:
#if RELEASE
// only force topmost in release builds, to not interfere with debugging
_splashForm.TopMost = true;
#endif
-
Normally, when a exception is thrown, it's possible to click on items in the stack trace to jump to according line of code: Currently this doesn't seem to work:
-
Also, normally you would see line-numbers next to the stack-trace items. Now you only see:
Symbol.CreateInstance() in T3.Core.Operator, Core.dll [2]
-
Maybe we need to include more debug information?
This issue was probably caused by some adjustments of the layout. Restoring it, made the stack-track items clickable again:
In 451da0e69d5
...
-
debug startups with a bunch of assertions because connection targets are no longer valid.
-
release crashes with "examples" not found
-
IDE crashes in
ProjectSetup.cs:CreateSymLinks()
because -
invalid directory:
C:\Users\pixtur\Documents\T3Projects\cynic
Interestingly creating the target parent folder Documents\T3Projects\
worked just fine.
I tried...
- changing it to relative path
var linkName2 = Path.GetRelativePath(".", linkName);
- Desktop instead of documents
C:\Users\pixtur\Desktop\T3Projects\cynic
- Creating the directory with unix-write mode, which is not supported:
Directory.CreateDirectory(targetDirectory, UnixFileMode.UserWrite);
- Adjusting the readonly-flag from code
- Unsetting the real-only attribute manually with File-Explorer property windows.
Wrong windows-cluster fuck rabbit-hole:
The Read-only and System attributes is only used by Windows Explorer to determine whether the folder is a special folder, such as a system folder that has its view customized by Windows (for example, My Documents, Favorites, Fonts, Downloaded Program Files), or a folder that you customized by using the Customize tab of the folder's Properties dialog box.
Also, the properties of the created directory look kind of funky:
From Core/Operator/Instance.cs:TryGetTargetSlot()
...
#if DEBUG
if (!gotTargetInstance)
{
Debug.Assert(connection.TargetParentOrChildId == Guid.Empty);
}
#endif
It's kind of annoying that rider does not correctly use Guid.ToString()
to display guids in a readable format:
Reference
Getting started
- Basic Concepts
- How Tooll Works
- Keyboard shortcuts
- Video tutorials
- Rendering Videos
- Exporting to Executable
- Creating new Operators
- Tooll for live performances
- Presets and Snapshots
- Optimizing Rendering Performance
- Using backups
- Realtime Rendering for Artists
Advanced features