[eric nixon]

This scene was crashing heavily, just popping out of existence around sl10-12, then I checked it and fixed a problem with two air-bubbes which were intersecting the sss geo. But now it still crashes every hour or two, but in the normal way with the dialogue box... There are definitely no intersections now, (I tried a boole command on each marble to make sure)... I keep restarting it because its a nice image, so far its reached sl23 after 3 restarts.

I'm stuck on 3.0.99.6 for XP compatibility, for the time being.



The setup here;

Marbles have a single-bsdf glass material, roughness 0 with 2 normal maps (global one is offset for randomization) a non-bump copy is applied to a poly-selection for the airbubbles.

Swirls have a single sss bsdf, and an additive diffuse layer (single-bsdf) which is textured.

Hdri lighting is tortuously sharp, hence the slow render... geo is clean, with some minor phong errors at the swirl tips. Marbles are about 2cm across.



P.S. Another image where an emitter with self-intersecting geo, which was embedded inside a transmissive, also crashed yesterday. I fixed the geo and it renders fine now.

[eric nixon]

After a few more restarts I gave up, it wouldnt get past sl23, just crashing almost straight away each time.

I tried again with softer lighting, I also made some minor changes; DOF, camera angle, sss nd reduced from 1.45 to 1.25, and its roughness reduced from 45 to 30, and its r90 increased from 33% to 50%. And now it doesn't crash, still some noisy pixels at sl25 (I painted them out), but no noise in preview.



Perhaps the swirl geo was too coarse for the sharp hdri I used before? There were some slight poly artifacts.

[nachob]

Hi Eric,
Doesn't the newest betas work with XP, I think they should because as you reported it didn't work there were some changes made to make it work again.

nachob

[eric nixon]

Really thats awesome, thnx for letting me know, I'll try again.

[eric nixon]

Ok, I installed the latest MW + plug, but same error as before, "the procedure entry point SetThreadGroupAffinity could not be located...."

Then C4D says "The mxcommon_64.dll library has failed to load...."

Should I try a clean install, or reboot? (cant reboot right now...)

[rusteberg]

nice marbles

[eric nixon]

Thnx rusteberg,

Nacho, I just tried MW 3.1.1 + latest c4d plug... no joy

[nachob]

HI Eric,

what error is it giving? the same "the procedure entry point SetThreadGroupAffinity could not be located...."? Is it happening in C4d loading the plugin or also rendering in maxwell?

thanks

nachob

[JDHill]

I'm not sure if it is supposed to be working or not, but really, would you have been surprised if, in 2005, if it had finally become too difficult to cripple the software enough to let it continue running on Win 3.x? XP had a good run, but...

[eric nixon]

Nacho, yes same error, just when loading c4d.

[nachob]

And does Maxwell work as expected, or does it also crashes?

nachob

[eric nixon]

I installed 3.1.1 again, in order to check that everything is working including rendering. Found no problems running maxwell studio.

[eric nixon]

I just noticed that 3.1.1 appears to work with the c4d plugin 3.0.995, (hide to gi tag works now). Maybe other issues will surface... though?

[nachob]

Hi Eric,

You should be able to use the beta plugin with the release 3.1.1 without problems, since the scenes saved with the beta plugin can be opened with the newer version of Maxwell. Its like opening v2 scenes in new maxwell, it can open them and render, the only limitation is that new features in 3.1.1 won't exist in the old plugin or fire inside the plugin. Said this, the plugin is a beta plugin so not tested in depth so some issues could happen.

nachob