Please fix ALL (/sys /ui) startup errors

As I include all errors in my logger, I get log entries for all the errors in /sys and /ui
errors.toe (3.7 KB)

python >>> 
Using old export map format. Please include path column. CHOP /ui/dialogs/mainmenu/fps1/count1
Using old export map format. Please include path column. CHOP /ui/dialogs/mainmenu/fps1/count1
Invalid path for node "../../panesWork/panes/paneLayout/paneLayoutBottom/paneGadget/ui/navigationBar/contextPath/contextPath/item0" referenced by parameter "Button Comp" COMP /sys/TDResources/buttonPopMenu
Check script language!  Evaluating expression in Tscript. DAT /ui/dialogs/keyframer/graph/label_end/local/eval1
Invalid expression at entry (0,1): Bad path argument for expression (-1,-1) `par($KEYPATH+"/end")`. DAT /ui/dialogs/keyframer/graph/label_end/local/eval1
Check script language!  Evaluating expression in Tscript. DAT /ui/dialogs/keyframer/graph/label_start/local/eval1
Invalid expression at entry (0,1): Bad path argument for expression (-1,-1) `par($KEYPATH+"/start")`. DAT /ui/dialogs/keyframer/graph/label_start/local/eval1
Cook dependency loop detected. Check for exports, expressions or wiring that are creating this loop: 
 /sys/TDDialogs/CompEditor/extensions/ext1/ext1Basic
	/sys/TDDialogs/CompEditor/extensions/ext1/container1
	/sys/TDDialogs/CompEditor/extensions/ext1/advanced1
	/sys/TDDialogs/CompEditor/extensions/ext1/ext1 (Parameter: Height)
	/sys/TDDialogs/CompEditor/extensions/ext1/ext1Basic
	/sys/TDDialogs/CompEditor/extensions/ext1/manageExt1
	/sys/TDDialogs/CompEditor/extensions/ext1/extClassStatus1
	/sys/TDDialogs/CompEditor/extensions/ext1/extClassStatus1/bg (Parameter: Background Alpha)
 COMP /sys/TDDialogs/CompEditor/extensions/ext1/ext1Basic
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/label_rangeend
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/label_rangeend
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/label_rangeend
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/rangeend
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/rangeend
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/rangeend
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/rangestart
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/rangestart
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/rangestart
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/label_rangestart
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/label_rangestart
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/label_rangestart
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/rangestart
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/rangestart
(tscript) Bad data type for function or operation COMP /ui/dialogs/keyframer/graph/rangestart
python >>> 
Cook dependency loop detected. Check for exports, expressions or wiring that are creating this loop: 
 /sys/TDDialogs/CompEditor/extensions/ext1/ext1
	/sys/TDDialogs/CompEditor/extensions/ext1/ext1Basic
	/sys/TDDialogs/CompEditor/extensions/ext1/container1
	/sys/TDDialogs/CompEditor/extensions/ext1/advanced1
	/sys/TDDialogs/CompEditor/extensions/ext1/ext1 (Parameter: Height)
 COMP /sys/TDDialogs/CompEditor/extensions/ext1/ext1
python >>> 

Even if these are minor errors, they still clutter my logs and it would be great if you could fix those

1 Like

+1 ! there are also errors that stem from that general area of td that happen periodically when deleting stuff. It makes exposing errors globally less attractive because users of my software may be reporting things that are false positives, for lack of a better word.

I will try to report back with the error I see from time to time, next time it crops up.

Ahh here it is!

/ui/dialogs/panebar/launch (line 4 - set pathid = `oppathtoid("$path")`): Tscript Expression error: Bad path argument
/ui/panes/panebar/copy_of_pane1_0/local/macros/sethistory (line 4 - set jumppath = `oppathtoid($jumppath)`): Tscript Expression error: Bad path argument
/ui/dialogs/pane_timeline/launch (line 6 - set location = `timepath("$path")`): Tscript Expression error: Bad path argument

hunting down some tscript! Thanks for submitting this.

2 Likes

EDIT: found it - these errors come up when deleting a network that a pane is browsing… fixing it…

Hey,

is there a specific thing that happens in the ui when these errors come up? Somehow a new pane is being created but the path is missing…

cheers
Markus

Hmm, trying to think, it’s very intermittent for me so not able to recall it now, but if it happens again I will try to think about it from that perspective.

generally, I have an object, usually a clone of some other template object, and I delete it then 1% of the time it feels like this error comes up.

I’ll report back next time it happens with a clearer picture!

Thanks for motivating this, guys. I got rid of the warnings my stuff was producing.

2 Likes

Likewise the tscript errors have been removed…

2 Likes

Exciting! Thank you thank you, will be making heavy use of td’s reporting of errors n such, this will make things so much more elegant.

we have a bunch of new ones in experimental

source message absframe frame severity type
/sys/TDDialogs/CompEditor/extensions/ext1/addMenu/window (Parameter: Justify Horizontal) td.Error: Cannot use an extension during its initialization. 59 547 abort COMP
/sys/TDDialogs/CompEditor/extensions/ext1/addMenu/window (Parameter: Justify Vertical) td.Error: Cannot use an extension during its initialization. 59 547 abort COMP
/sys/TDDialogs/CompEditor/extensions/ext1/addMenu/window (Parameter: Offset) td.Error: Cannot use an extension during its initialization. 59 547 abort COMP
/sys/TDDialogs/CompEditor/extensions/ext1/addMenu/window (Parameter: Offset) td.Error: Cannot use an extension during its initialization. 59 547 abort COMP
/ui/dialogs/menu_op/family/select_Custom6 Invalid path for node “/ui/lib/TUIK2/colors/exp/Custom_off” referenced by parameter “DAT” 7364 51 warning DAT
/ui/dialogs/menu_op/family/select_Custom6 Invalid path for node “/ui/lib/TUIK2/colors/exp/Custom_off” referenced by parameter “DAT” 7364 51 warning DAT
/sys/local/user_shortcuts File not found (“C:/Users/tgallery.T-GALLERY/AppData/Local/Derivative/TouchDesigner099/TouchShortcuts.txt”) 7364 52 warning DAT
/sys/local/user_shortcuts File not found (“C:/Users/tgallery.T-GALLERY/AppData/Local/Derivative/TouchDesigner099/TouchShortcuts.txt”) 7364 52 warning DAT
/sys/local/user_shortcuts File not found (“C:/Users/tgallery.T-GALLERY/AppData/Local/Derivative/TouchDesigner099/TouchShortcuts.txt”) 7364 52 warning DAT

We’re back to this again in 25370… errors in a clean session in /ui/dialogs/keyframer/graph

1 Like

Thanks, the issue has been reopened

2 Likes

@drmbt This will be fixed in the next build.

2 Likes

in the latest build we have a cook loop in the compEditor and a few smaller warnings listed on file start. It would be great if those could be fixed

Could you elaborate what and where you are seeing this? I do not see anything in Console, textport, or errors dialog on starting 2022.31030

Attached the wrong file today, will update tmr

But basically it’s an error DAT in a fresh file. saved and reopened the toe and those errors where there

1 Like

NewProject.1.toe (5.6 KB)

I included a locked version in case it differs on your machines

@ben the user shortcuts error in there is not my domain

The comp editor stuff is a long time problem I’ve had. The layout works, but TD is internally unhappy about it. Will put it in the bug queue.