phoenixFD demo ocean

[waaazoo]

Thank you Ivaylo, I will check this right now, but I thought that I tested each of these rendering modes.

I continued the investigation to my blue screen problem. To avoid any confusion :

StationA: i7 9330K, Quadro 4000, Win7 X64, 32GB
StationB: i920, Geforce 8400GS, Win7 X64, 16GB

As said earlier, I had several Blue screens on StationA, nearly each time I made a simulation. I tested several Nvidia drivers (same crashes). I tried simulation on StationB and it was fine. Then I decided to switch graphic boards between station A and B.
Test on StationA went well, test on StationB also (but with different driver 295.73 certified for Maya2013). Then I switched back the Graphic boards and installed driver 295.73 on StationA, and it was still crashing. Then I made a last test, same driver, same setup, but with viewport out of view (nothing to see in view), and StationA finished the 100frames without problem.
I'm wondering if there is not an graphic board overheat problem on StationA even if I never had such problems. Forgot also to say that all last tests made on StationA were in single monitor setup.

Any thoughts would be greatly appreciated.

[ivaylo.ivanov]

Can you try simulating without the mesh perview? This is in the Preview -> Mesh Preview section.

[ivaylo.ivanov]

You must also increase the wind speed of the ocean texture to something a lot bigger, like 1000. There is maybe a bug with the scene units, I must check this.

[waaazoo]

OK, will check the Texture also. Yes, I was wondering if the scene units were correct. To have something looking somewhat correct I need to scale the Boat 1.5 or 2.

Without mesh preview it worked for 100frames without crashing. What does that mean ? I'm moving several millions of polygons each day on this rig....

best regards,

olivier

[ivaylo.ivanov]

It's somewhat normal to scale the scene 2x, because bigger resolution produces better quality for the same settings. I'm not sure what can go wrong with the mesh preview, but at least we have a clue what is causing the problem. Will try to test it here with similar card.

[waaazoo]

Hi,

I launched a test over 500frames with the StationA (i7 3930K, Quadro4000....) with view out of anything but meshpreview enabled. It crashed at frame 116.
Will launch the same test with Geforce 8400GS to see what happens.

[waaazoo]

some more feedback:

Same test launched (500frames) with Geforce8400GS was completed. I really don't know what happens with the Quadro card.
Questions:
-Graphic board doesn't really seem to be used during simulation, am I wrong ?
-What kind of graphic boards do you use with Maya ?

Now I experienced another problem. I decided to make another test with bigger grid and over 1000frames (with the G8400GS | StationA ). It went well but was kind of stuck at frame 604. Frame 604 AUR file was written at 6PM and I decided to stop at 8:30PM as nothing happened any more (no crash, no error message). Before stopping I tried to pause the simulation and resume, but it didn't work.
It doesn't seem to be possible to save the scene, load again and resume a simulation that was partly calculated. Would be nice if we could do this. If it's already possible, please explain the process.

best regards,

Olivier

[Ivaylo Katev]

one important question - if you simulate with disabled mesh preview, and enable it afterwards, can you crash the system dragging forth and back the timeslider?

[waaazoo]

I will try this ASAP. Thanks

[ivaylo.ivanov]

We've noticed that if you try to use too much virtual memory, the simulation practically stops. This is happening often during the saving since it requires additional memory. Not sure what we can do about it. When working with memory intensive programs like Phoenix, it's best to use lower virtual memory like 4-5GB or you will have many kinds of memory issues. For example wrong settings of foam/splashes can generate huge amount of particles and kill your computer. Resimulation is also dangerous.

[waaazoo]

one important question - if you simulate with disabled mesh preview, and enable it afterwards, can you crash the system dragging forth and back the timeslider?

Hi,

No, I can't seem to crash the system while playing back and forth. Tried for 5/10 min... no crash.

[Ivaylo Katev]

well, just to exclude the possibility to be not related to the simulation , thanks for the test

[waaazoo]

Is there anything else I can test regarding the quadro card ?
Also, What kind of settings do you use for displacement (phoenix and vray rendersettings) ?

best regards,

Olivier

[waaazoo]

I made another test this night, with a simulation over 1000frames, less cells (to have it simulate faster) on the i73930K with Quadro4000 and disabled mesh preview, and less virtual memory (5GB). It crashed (blue screen) at frame 97.
I'm doing right now another test on a third setup (i920, 16GB, QuadroFX1700) on the same scene... let's see what happens.

[Ivaylo Katev]

apparently the mesh is not related. still not sure how the card is involved