T0.8 Problem

[Xman]

bidirectional + hybrid and hdr
Work some time after, appear mistake, withdraw automatically.
Are you also similar?

[Xman]

I tested 15 times, only an 1 times can work,
But after 30 minutes, it is again can't work (with top similar problem)

[Kram1032]

you mean, this error mesage irregularely pops up and forces Indigo to close?

Could you translate the Error to English, please?
Maybe, that can help

[zsouthboy]

I've had this happen from time to time. It's a memory bounds problem I believe.

The slightest change to the scene can fix it. I don't know why.

Or, rather, to verify that this is what I'm talking about, go into your .ini file, and set supersamplefactor to 1 (or in the scene XML if you've defined it there)

I bet you won't see the error.

[Xman]

@ Kram1032
English meaning is :indigo.exe meets problem demand to close(probably this meaning, have no special meaning)

@ zsouthboy

Sorry! i can't Clearly understand you of meaning, do you more tell I how to demand modify?

Thx you-all

ini file,

------Output image dimensions------
"width" "600" --Note that the ratio of these should match the camera aspect ratio defined
"height" "450" -- in the scene xml file.

------Metropolis light transport settings------
"metropolis" "false" --if true, use MLT, if false, use pathtracer
"large_mutation_prob" "0.4" --Probability of using fresh random numbers.
"max_change" "0.01" --max mutation size, must be in range [min_change, 1)
"max_num_consec_rejections" "1000"

------General tracing parameters------
"max_depth" "10000" --max ray bounce depth.
"bidirectional" "true" --Use bidirectional path tracing / bidirectional MLT?

"hybrid" "true" --If enabled, direct lighting is computed with path tracing.
-- Indirect lighting is computed with MLT.

------Network rendering settings-----
"frame_upload_period" "30.0" --number of seconds between uploads of image to network master

------Miscellaneous settings-----
"halt_time" "-1" --time in seconds after which to halt the program. Halting is disabled if negative.
"logging" "true" --write to log.txt?
"display_period" "10.0" --number of seconds between display of the render in preview window.
"image_save_period" "20.0" --number of seconds between saves of the render to PNG, EXR and IGI.
"save_tonemapped_exr" "false" --Write .exr tonemapped render as well as normal PNG?
"save_untonemapped_exr" "false" --Write .exr untonemapped render as well as normal PNG?
"save_igi" "false" --Write Render to Indigo Image (.igi)?
"num_threads" "1" --Number of render threads to use. Set to number of cores for fast rendering.
"cache_trees" "true" --Cache kd-trees on disk?
"polarisation" "false" --broken, leave it off.
"super_sample_factor" "3" --a higher value takes more RAM but reduces aliasing along high contrast edges.
"bih_tri_threshold" "500000" --Any meshes with at least this number of triangles will use a Bounding Interval
--Hierarchy (BIH) acceleration structure instead of a kd-tree

[zsouthboy]

Code: Select all

"super_sample_factor" "3" --a higher value takes more RAM but reduces aliasing along high contrast edges.

Change from "3" to "1", and I bet the error either takes longer to appear, or goes away completely.

[Xman]

zsouthboy,
Change from"3" to"1", is already modify by me.
But the problem is an come again and again, 10 tests, all failure.

[CTZn]

Hello,

1/ how is memory usage in task manager ?
2/ try another hdri/without hdri, try to convert to exr.

Second image is turning good !

[Xman]

Hi CTZn,
In fact, I am to use exr, just only I say HDR habitually.

[CTZn]

Er... ok maybe try the reverse then, convert it to *.hdr... does it crash also without HDR lighting (either exr or hdr), using meshlights only ?

How about memory ? Disk space ?

Gah, I have no clue

[Kram1032]

I thought, HDRi just can be .exr or .float, for now...

[CTZn]

Anyway.

[Xman]

In many tests, I discover the problem is with EXR.

I am to use int0.8 + Maxigo-07_v02
I don't know the problem from int0.8 or Maxigo-07_02 or my problem.

If i not use EXR, so whole will be work very goodly.