On 7/18/2017 1:29 PM, Kenneth wrote:
> (Running Windows 7 Ultimate Edition, and using v3.7.1 beta 9, but the problem
> may not be specific to it.)
>
> Some unexpected behavior with #debug messages, regarding ending line breaks (vs.
> their absence). This seems to be different behavior from what I remember in
> v3.6xx.
>
> * A SINGLE #debug with NO line break at the end does not show up in 'messages.'
>
> * TWO #debugs without the ending line breaks: only the FIRST message shows up,
> not the second.
>
> * With multiple #debugs, and no ending line breaks at all: the final message is
> always missing
>
> * Any #debugs (with no ending line breaks) that follow one WITH a line break:
> the final message is always missing
>
> * If only the FINAL #debug has an ending line break, all messages show up
>
> * If ALL #debugs have ending line breaks, they all show up
>
> In a nutshell, it seems that the final #debug statement in a scene file MUST
> have an ending line break, or there will always be a missing message.
>
> Try commenting-out and/or re-arranging some of the following lines, to see the
> results. (Hopefully, the formatting will show up correctly.)

Win 7 Home Premium IIRC

I tried it in UberPov (Oops!)
What I found using your code. Was that after running it with the , "/n" 
at the end of the last #debug. I could put the newline at the end of any 
of the debug statements and all the lines would print. You can reset it 
back to missing the last line by not having a new line character. It had 
me going for a while.


-- 

Regards
     Stephen

Post a reply to this message