Jump to content

Printc


d4v3

Recommended Posts

I've just started my first big mod, and need to get some debug info printed to screen. I've been using 'Message', but got fed up of the 10 second wait.

 

I changed to PrintC, but don't get any messages.

 

I've typed tdt at the console, and used ScrLk to cycle through each debug screen, but can't get any of them to display PrintC messages.

 

I also tried PrintToConsole, which did output 9 messages... and then stopped.

 

What am I doing wrong?

Link to comment
Share on other sites

I've just started my first big mod, and need to get some debug info printed to screen. I've been using 'Message', but got fed up of the 10 second wait.

 

I changed to PrintC, but don't get any messages.

 

I've typed tdt at the console, and used ScrLk to cycle through each debug screen, but can't get any of them to display PrintC messages.

 

I also tried PrintToConsole, which did output 9 messages... and then stopped.

 

What am I doing wrong?

We can't say if you doesn't post the complete command you are trying. Maybe the line is just misspelled or isn't reached under the conditions given. PrintC doesn't print messages into the screen, only in the console, anyway.

 

Edit: In some cases is even a bad constructed command that terminates abnormally the script and so the PrintC isn't reached (the game continues as normal and the script can be even called again and again fail at some point).

Link to comment
Share on other sites

We can't say if you doesn't post the complete command you are trying.

 

I set up a test spell, with a test script, that said:

Printc "Test message"

in the spell start effect.

 

PrintC doesn't print messages into the screen, only in the console, anyway.

According to the wiki

When PrintToConsole is called while TDT is active, console messages will be visible during normal gameplay.

How do I make them visible during normal gameplay?

Link to comment
Share on other sites

We can't say if you doesn't post the complete command you are trying.

 

I set up a test spell, with a test script, that said:

Printc "Test message"

in the spell start effect.

 

PrintC doesn't print messages into the screen, only in the console, anyway.

According to the wiki

When PrintToConsole is called while TDT is active, console messages will be visible during normal gameplay.

How do I make them visible during normal gameplay?

PrintC is a debug tool, you must use message and formated message to achieve it in game. But seems I wasn't clear, often some function call or command can terminate a script abnormally and this isn't reported. For example a PrintC works just before certain command and another just after it isn't reached. As PrintC seldom is the guilt you must seek the culprit in others commands and conditions.

 

Edit: saw now what is being misunderstood, right printc shows in the console, what I said is it doesn't to be used as message to player, normal game mode.

 

Edit2: Indeed, a strong debug practice is using printc to identify that script failing for exactly not being shown.

Link to comment
Share on other sites

Thanks for your help - I've managed to solve this for my 'Test' spell - I assumed that because I was casting the spell, my messages should appear, but it appears that they only do if the spell is actually cast on a target.

 

Now I can go back to the original script, and put more messages in to see where it stops working, as you so correctly pointed out!

 

Thanks

d4v3

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...