YOUR ACCOUNT

Login or Register to post new topics or replies
Sphinx.
Filter Optimizer

Posts: 1750
Filters: 39
Calling error("message") will stop execution, so how do you output several messages?

I had hoped print would do the job, but it seems that stdout is not directed to the message log, which is probably a good measure to avoid flooding the message log with samplecount * print("message"), smile:D

However I'm missing such a feature a lot when debugging a script: could you perhaps add some sort of custom print function that is allowed to output once per execution/rendering? I.e. much like error, only it will not stop execution
  Details E-Mail
GMM
Moderator
Filter Forge, Inc
Posts: 3491
stdout is directed to the log file located in the TEMP folder.
I agree that it's not very convenient but currently it's better than nothing smile:)
  Details E-Mail
Redcap
Redcap

Posts: 1290
Filters: 100
I have scoured the help documentation, have looked at others' example code hoping they used this, and still have no idea why my stdout function call gets an error or where the TEMP folder is; do you think you could show an example code when answering questions like this, so if newbies who take the intiative to find the answers themselves don't have to ask the same question twice because the answer is mystically mysterious in their eyes? smile:)

P.S. I really don't know how to use stdout or where the TEMP folder is, can you help?



If you are bored check out my unpractical math website
  Details E-Mail
GMM
Moderator
Filter Forge, Inc
Posts: 3491
Quote
Redcap wrote:
where the TEMP folder is


It's the user temporary folder. You can check or modify its location in Windows by selecting System Properties > Advanced > Environment variables: you need the location that the TEMP variable points to. (Alternatively, use the 'set' command from the command line).

The log file is called Filter Forge x86-SSE2.log or Filter Forge x86.log
  Details E-Mail
Sphinx.
Filter Optimizer

Posts: 1750
Filters: 39
I found my log file here:

C:\Documents and Settings\<your profile name>\Local Settings\Temp\Filter Forge x86.log

FF, you should consider adding an option for clearing that logfile when a rendering starts. It seems you just append to that logfile during the whole FF session

I'm looking at a 233 MB logfile right now smile:eek: - Yes I know I shouldn't put print calls inside get_sample .. but it is very helpful when debugging.

Beside from that "print" is not in the unsafe function category, meaning that it is possible to submit a filter that might fill up the disk with a huge logfile...
  Details E-Mail
Totte
Übernerd

Posts: 1460
Filters: 107
On Mac OS X, the log file is found here:
/private/tmp/Filter Forge universal.log
- I never expected the Spanish inquisition
  Details E-Mail

Join Our Community!

Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!

33,712 Registered Users
+19 new in 30 days!

153,534 Posts
+31 new in 30 days!

15,348 Topics
+72 new in year!

Create an Account

Online Users Last minute:

39 unregistered users.