Maxwell Render | Official public forum

i often get this when trying to render the sea

The render engine reports the following errors:

1. Type: System.AccessViolationException
Source: Maxwell
Message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at CmaxwellRender.startRender(CmaxwellRender* )
at Maxwell.Scenes.nIPScene.RenderScene(nIPScene* )

also somtimes it is not possible to delete an sea extension from the extension tab in the scene manager.

running maxwell 3.1.1 and plugin 3.0.3

that error comes from fire,.. it does render when i export to maxwell.exe

just tried on a fresh scene and i get the same error, just after creating the sea only.

we also tried on two machines, so i doubt it has actually anything to do with corrupt memory

What is the resolution you are trying to use in the sea extension? I imagine you have a lot of memory on your machine, but still, high resolutions can take a ridiculous amount. If you were on the edge, it could possibly load in maxwell.exe, but not in Rhino, since there would be less memory required without Rhino's overhead.

By the way, access violation doesn't mean you have bad memory, it means some code attempted to access memory which wasn't allocated, which resided outside of its allocated area, or which had been illegally accessed by other code. I should generally think it would indicate a bug in the extension, but in my experience, .NET is not completely reliable in reporting errors correctly, in which case, it could be due to out of memory. With a very large allocation, it can be difficult to diagnose via Task Manager, since a failure to allocate will not show up as memory being in use; in other words, if you have 2GB free, and code requests a 3GB chunk, that would fail, but task manager would not show the free 2GB as having been taken.

thanks for the quick reply

still 31GB available

the thing is it did work, and i think it does not work anymore since i installed 3.1.1. could it be?
If i open a new scene click on maxwell sea, hit enter, assign default material and render to fire i get the error. (resolution 256)

hmm.. something fishy here.

i get the exact same error when i try to apply a subD extension to any object.(and with maxwell grass)

just wondering: should i try to revert or install 3.1.3?

That would at least be something to check -- the plugin loads .mxx files from the Maxwell 3 extensions folder, so the behavior will depend on which version of Maxwell you have installed.

Jeremy i am really clueless.

i reverted back to 3.0 installed 3.1.3 and everything in between again.

but i don't get it to work at all. reinstalled the plugIn too.


could this in anyway be a licensing issue?? because we added another seat license the other day.
(i know it is needed eg for sea mesh display.. and that works fine.. but still.. i am just guessing)

ok:

for some reason not clear to me installing 3.0.0 over 3.x did not replace the extensions correctly.

they still showed 30.05.14.


uninstalling 3.x and reinstalling 3.0 (i switched from 3.0 to 3.1.1)
did the job ant the extensions are working.


but they do not with anything greater than maxwell 3.0.0.

a bit frustrating

can you confirm?

I've checked into it now, and confirm the issue with 3.0.1.3, but not with 3.0.1 (that is the current official release, available in the portal). This is not just with Rhino, but with any plugin (I assume -- I can only check the ones that I write) that depends on the extensions in MAXWELL3_ROOT.

Thanks for checking.

I never installed 3.0.1, only now to check and eventually i had some issue with replacment of the extension files as mentioned before.

I will try reinstall when i am back in the office tomorrow.

JDHill wrote:I've checked into it now, and confirm the issue with 3.0.1.3, but not with 3.0.1 (that is the current official release, available in the portal). This is not just with Rhino, but with any plugin (I assume -- I can only check the ones that I write) that depends on the extensions in MAXWELL3_ROOT.

i can confirm 3.0.1 is working now after a clean uninstall.
however i am a bit baffled how such a bug can remain unnoticed for two .dot releases.
I understand that it is not directly related to the plugIn but reminds one to be careful.

Well, 3.0.1.3 and 3.0.1.1 were uploaded only four days and six days ago, respectively.

true say.

i think we need 3.0.1.4

polynurb wrote: also somtimes it is not possible to delete an sea extension from the extension tab in the scene manager.

for 3.0.1/3.0.3 i can repeat the following behaviour:

-make a new scene

-make two sea objects

-delete one of them

-save scene

-exit&reopen

-both sea objects are there again.