irradiance map calculation problems

[jackieteh]

Hi to all respect, i have set up a irradiance map animation with multiframe incremental and leave it for overnight night calculation with autosave,
this morning when i back to office, i notice that my pc was re-start, i have no idea where is the irradiance map start when my pc re-start itself,
is there anyway to check that? or i have to re calculate everything again?

Urgent! please help

[svetlozar.draganov]

I am not sure if I understood you correctly - you are wondering up to which frame IM was calculated at the time of restart?
There is no way to determine up to which frame the IM was calculated but you could check the vray-log file and see which is the last calculated frame.

Just scroll down to the bottom of the file and find the last line that prints:

[2015/Jun/25|11:19:10]   Entering RenderAtTime(t=2400, fieldMask=3)

Then divide t=value by 160 (2400/160)=15 and this is the frame that the calculation is stopped.

Another way to check up to which frame IM is calculated is to open the saved IM cache with Irradiance Map viewer and depending on the IM samples you could estimate roughly the last calculated frame.

[jackieteh]

I am not sure if I understood you correctly - you are wondering up to which frame IM was calculated at the time of restart?
There is no way to determine up to which frame the IM was calculated but you could check the vray-log file and see which is the last calculated frame.

Just scroll down to the bottom of the file and find the last line that prints:

[2015/Jun/25|11:19:10]   Entering RenderAtTime(t=2400, fieldMask=3)

Then divide t=value by 160 (2400/160)=15 and this is the frame that the calculation is stopped.

Another way to check up to which frame IM is calculated is to open the saved IM cache with Irradiance Map viewer and depending on the IM samples you could estimate roughly the last calculated frame.

thank you for your explaination, this is actually what i want to know, but why divide (160)?

[tashko.zashev]

thank you for your explaination, this is actually what i want to know, but why divide (160)?

This is the time in Ticks and the conversion (2400/160)=15 will give you the exact time in frames (30fps). This is actually the way 3DS Max interpret the increments of time. 30 frames in a second (NTSC) are 160 ticks in each frame, for an example.

[jackieteh]

This is the time in Ticks and the conversion (2400/160)=15 will give you the exact time in frames (30fps). This is actually the way 3DS Max interpret the increments of time. 30 frames in a second (NTSC) are 160 ticks in each frame, for an example.

thank you for explaination, how to calculation in (PAL) 25frame?

[tashko.zashev]

If you're on PAL then Max has 192 ticks per frame.