illumination map problem

[madwands]

Hi there!

I have a problem with illumination map. Can I force Fume to use one frame of illumination map saved on disk? and not calculating it each frame?

My case is a huge simulated "nebula like" cloud, with fxd cache up to 4Gb. Calculating illumination map takes a lot of time, and lighting don't change . I want to render a space flight. around the cloud. Copying the calculated illumination map is not a solve as I have 800 frames and ~10 such clouds in my scene would make 2TB of cache files

Thanks in advance!
Artur

[sitnisati]

Hello,

Yes - if you're rendering one fxd cache file over and over again with appropriate out of range type, then the IM should read the same fim cache as well.
Just make sure that .fxd and .fim are calculated at the exact same frame (or you can just change filename in Windows Explorer).

Regards,
Kresimir Tkalcec

[madwands]

Thank you for your reply. It makes sense, but it doesn't work as well

IM is being calculated over and over again (apart from the frame that fxd file is held on). Out of range type is proper as I have only one .fxd file (to save disk space) and it renders each frame. Names of the files are the same as fumeFX object. The same problem is both on default and post caches. I have no idea what else could I miss.

[sitnisati]

Hi,

Please find attached an example scene... I hope it will work for you.
Please notice that Multiple Scattering is calculated each time as it's not saved inside the IM.

Regards,
Kresimir Tkalcec

[madwands]

Thanks a lot for your help.

Unfortunatelly settings are same as mine, and my problem occurs in your file as well.

I simulated first frame, lovely small cloud, rendered it, cache file for frame 0 was saved. All cache files (fxd and fim are in the same folder with same name test_0000).

Now I moved to frame 1, and again illumination map was calculated and saved (same file size as frame 0). Frames 0 and 1 now renders quickly without recalculting, but frame 2 again calculates illumination map.

I work on on max 2013 and 2014 with latest updates and service packs, on both is the same. Win7 SP1. FumeFX 3.5.4

[sitnisati]

What are .fim cache names - does it always save to test_0000?
This scene works here and for one more client who had similar issue so not sure what might go wrong in your case.

Regards,
Kresimir Tkalcec

[madwands]

Names are with correct frame numbers, test_0000 both for fxd and fim, and in other frames fume uses test_0000.fxd but generates test_0001.fim test_0002.fim end so on...

In your test scene I changed nothing but the folder where to save cache files...

[sitnisati]

Hello,

Please try to re-download the FumeFX 3.5.4 version and install it as this bug was fixed in it.

Regards,
Kresimir Tkalcec

[madwands]

You just saved my deadline, it works now!
Shame on me, but I haven't thought to reinstall Fume earlier

Thanks!
Artur

[sitnisati]

I am glad to hear that everything is working okay now !
Feel free to post anything you might find buggy in the future.

Thank you.

Kresimir Tkalcec