search

tomvandeneede / p2pp

Palette2/3 Post Processing tool for Prusa Slicer
143 stars 39 forks source link

Enhancement Requests... #166

Open dondec123 opened 1 year ago

dondec123 commented 1 year ago

Hi Tom,

  1. When you knee deep in Splice Tuning woes, you even wonder if your P2PP Splice Table is taking effect (especially with lots of material combinations). REQUEST: could you please PRINT the transition entries read in from Gcode and used for the current print, in the P2PP popup window: for example:
    W -to- RT : 1 0 3 RT -to- W : 1 1 3

  2. In the P2PP GCODE Splice Tuning section, could you please allow for the use of "white space" (spaces, tabs) instead of a single _ underscore. This would make the table far easier to read and to edit.

  3. There's a bug which I slid past. I created a material called "BLT" (blue transparent), and put that in the splice table. But then (as I recall from memory) I had a material called "BL" (for black) listed after. P2PP seemed to get confused and may have miss matched it to BLT. I didn't save the warning messages for this, but this is a common text matching error... maybe just have a 2nd look at that code.

Thanks

  Don

PS. My current Splice Table (work in progress)... ;P2PP MATERIAL_DEFAULT_1_2_3

;P2PP MATERIAL_W_BL_1_2_3 ;P2PP MATERIAL_W_RT_1_0_3 ;P2PP MATERIAL_W_GT_1_0_3 ;P2PP MATERIAL_W_ORT_1_0_3 ;P2PP MATERIAL_W_YT_1_0_3 ;P2PP MATERIAL_W_WT_1_0_3 ;P2PP MATERIAL_W_BRA_3_1_3

;P2PP MATERIAL_BL_W_1_3_3 ;P2PP MATERIAL_BL_RT_1_0_3 ;P2PP MATERIAL_BL_GT_1_0_3 ;P2PP MATERIAL_BL_ORT_1_0_3 ;P2PP MATERIAL_BL_YT_1_0_3 ;P2PP MATERIAL_BL_WT_1_0_3 ;P2PP MATERIAL_BL_BRA_3_1_3

;P2PP MATERIAL_BLK_W_1_0_3 ;P2PP MATERIAL_BLK_BL_1_0_3 ;P2PP MATERIAL_BLK_RT_1_0_3 ;P2PP MATERIAL_BLK_GT_1_0_3 ;P2PP MATERIAL_BLK_ORT_1_0_3 ;P2PP MATERIAL_BLK_YT_1_0_3 ;P2PP MATERIAL_BLK_WT_1_0_3 ;P2PP MATERIAL_BLK_BRA_3_1_3

;P2PP MATERIAL_RT_W_1_0_6 ;P2PP MATERIAL_RT_BL_1_0_6 ;P2PP MATERIAL_RT_GT_1_0_6 ;P2PP MATERIAL_RT_ORT_1_0_6 ;P2PP MATERIAL_RT_YT_1_0_6 ;P2PP MATERIAL_RT_WT_1_0_6 ;P2PP MATERIAL_RT_BRA_3_1_6

;P2PP MATERIAL_GT_W_1_0_6 ;P2PP MATERIAL_GT_BL_1_0_6 ;P2PP MATERIAL_GT_RT_1_0_6 ;P2PP MATERIAL_GT_ORT_1_0_6 ;P2PP MATERIAL_GT_YT_1_0_6 ;P2PP MATERIAL_GT_WT_1_0_6 ;P2PP MATERIAL_GT_BRA_3_1_6

;P2PP MATERIAL_BRA_W_1_0_6 ;P2PP MATERIAL_BRA_BL_1_0_6 ;P2PP MATERIAL_BRA_RT_1_0_6 ;P2PP MATERIAL_BRA_GT_1_0_6 ;P2PP MATERIAL_BRA_YT_1_0_6 ;P2PP MATERIAL_BRA_WT_1_0_6 ;P2PP MATERIAL_BRA_ORT_1_0_6

;P2PP MATERIAL_ORT_W_1_0_6 ;P2PP MATERIAL_ORT_BL_1_0_6 ;P2PP MATERIAL_ORT_RT_1_0_6 ;P2PP MATERIAL_ORT_GT_1_0_6 ;P2PP MATERIAL_ORT_YT_1_0_6 ;P2PP MATERIAL_ORT_WT_1_0_6 ;P2PP MATERIAL_ORT_BRA_3_1_6

;P2PP MATERIAL_YT_W_1_0_6 ;P2PP MATERIAL_YT_BL_1_0_6 ;P2PP MATERIAL_YT_BLK_1_0_6 ;P2PP MATERIAL_YT_RT_1_0_6 ;P2PP MATERIAL_YT_ORT_1_0_6 ;P2PP MATERIAL_YT_WT_1_0_6 ;P2PP MATERIAL_YT_BRA_3_1_6

;P2PP MATERIAL_WT_W_1_0_6 ;P2PP MATERIAL_WT_BL_1_0_6 ;P2PP MATERIAL_WT_BLK_1_0_6 ;P2PP MATERIAL_WT_RT_1_0_6 ;P2PP MATERIAL_WT_ORT_1_0_6 ;P2PP MATERIAL_WT_YT_1_0_6 ;P2PP MATERIAL_WT_WT_1_0_6 ;P2PP MATERIAL_WT_BRA_3_1_6

tomvandeneede commented 1 year ago

can you pls send me the code that triggers 3. an uprocesed gcode file would allow for testing as I have no issues on thos side bit I may be doing things differently or in a different orderOp 27 jun. 2023 om 01:23 heeft dondec123 @.***> het volgende geschreven: Hi Tom,

When you knee deep in Splice Tuning woes, you even wonder if your P2PP Splice Table is taking effect (especially with lots of material combinations). REQUEST: could you please PRINT the transition entries read in from Gcode and used for the current print, in the P2PP popup window: for example: W -to- RT : 1 0 3 RT -to- W : 1 1 3

In the P2PP GCODE Splice Tuning section, could you please allow for the use of "white space" (spaces, tabs) instead of a single _ underscore. This would make the table far easier to read and to edit.

There's a bug which I slid past. I created a material called "BLT" (blue transparent), and put that in the splice table. But then (as I recall from memory) I had a material called "BL" (for black) listed after. P2PP seemed to get confused and may have miss matched it to BLT. I didn't save the warning messages for this, but this is a common text matching error... maybe just have a 2nd look at that code.

Thanks Don

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

dondec123 commented 1 year ago
 Hi Tom,  Sorry I didn’t save that project.  All I remember were the details mentioned, and P2PP complaining that there was no splice method defined for that similarly named Color… when in fact it wasn’t even used in the print. If there’s nothing obvious… just ignore this.  Maybe user error.  Perhaps  I’ll rediscover it at some point and forward laster.  Sorry can’t be more helpful here.     Don From: Tom Van den EedeSent: Tuesday, June 27, 2023 12:35 AMTo: tomvandeneede/p2ppCc: dondec123; AuthorSubject: Re: [tomvandeneede/p2pp] Enhancement Requests... (Issue #166) can you pls send me the code that triggers 3. an uprocesed gcode file would allow for testing as I have no issues on thos side bit I may be doing things differently or in a different orderOp 27 jun. 2023 om 01:23 heeft dondec123 ***@***.***> het volgende geschreven: Hi Tom, When you knee deep in Splice Tuning woes, you even wonder if your P2PP Splice Table is taking effect (especially with lots of material combinations). REQUEST: could you please PRINT the transition entries read in from Gcode and used for the current print, in the P2PP popup window: for example: W -to- RT : 1 0 3 RT -to- W : 1 1 3 In the P2PP GCODE Splice Tuning section, could you please allow for the use of "white space" (spaces, tabs) instead of a single _ underscore. This would make the table far easier to read and to edit. There's a bug which I slid past. I created a material called "BLT" (blue transparent), and put that in the splice table. But then (as I recall from memory) I had a material called "BL" (for black) listed after. P2PP seemed to get confused and may have miss matched it to BLT. I didn't save the warning messages for this, but this is a common text matching error... maybe just have a 2nd look at that code. Thanks Don —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***> 
tomvandeneede commented 1 year ago

Really a needle in a haystack to find what was happening…

9.0.4 should allow usage of spaces in the definition, will look into printing the table of splices in a later release

On 27 Jun 2023, at 06:52, dondec123 @.***> wrote:

Hi Tom, Sorry I didn’t save that project. All I remember were the details mentioned, and P2PP complaining that there was no splice method defined for that similarly named Color… when in fact it wasn’t even used in the print. If there’s nothing obvious… just ignore this. Maybe user error. Perhaps I’ll rediscover it at some point and forward laster. Sorry can’t be more helpful here. Don From: Tom Van den EedeSent: Tuesday, June 27, 2023 12:35 AMTo: tomvandeneede/p2ppCc: dondec123; AuthorSubject: Re: [tomvandeneede/p2pp] Enhancement Requests... (Issue #166) can you pls send me the code that triggers 3. an uprocesed gcode file would allow for testing as I have no issues on thos side bit I may be doing things differently or in a different orderOp 27 jun. 2023 om 01:23 heeft dondec123 ***@***.***> het volgende geschreven: Hi Tom, When you knee deep in Splice Tuning woes, you even wonder if your P2PP Splice Table is taking effect (especially with lots of material combinations). REQUEST: could you please PRINT the transition entries read in from Gcode and used for the current print, in the P2PP popup window: for example: W -to- RT : 1 0 3 RT -to- W : 1 1 3 In the P2PP GCODE Splice Tuning section, could you please allow for the use of "white space" (spaces, tabs) instead of a single _ underscore. This would make the table far easier to read and to edit. There's a bug which I slid past. I created a material called "BLT" (blue transparent), and put that in the splice table. But then (as I recall from memory) I had a material called "BL" (for black) listed after. P2PP seemed to get confused and may have miss matched it to BLT. I didn't save the warning messages for this, but this is a common text matching error... maybe just have a 2nd look at that code. Thanks Don —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub , or unsubscribe . You are receiving this because you commented.