Welcome to Fractal Forums

Windows 7, last version of MB

I got very often this error

May be caused to try too much different maps, seems independent from render size (may happen  with 800X600 as easy than with 3200 x2200 ) ..once i got lights changes are no more applied

it is a know issues ? any workaround or suggestion

PS i know that is a dumb MS message that usually is not much useful to debug
i don't know if possible launch MB from command line in verbose mode to know more details

The only time I have ever seen the Lights/Maps/gradients become unresponsive is under this condition:

On an Intermediate size render (1024x512) used for setting Color/maps/lights etc, thinking I have it all set for Final Render. Changing the Size for a Full Scale Render (4000x2000) and then deciding to adjust Lights/Maps whatever again the controls have no affect, You have to return the size (1024x512) of the original Render to readjust lights.

I have never seen Lights go un responsive other than under those conditions.

You get this message when you try to calculate again, or when trying to change light pars or maps?

The message is very helpful, always post it if you can!  (Even the addresses can change when developing the program)

Can't say something about it yet...

i had often similar messages
When changing lights, more exactly the message pops out  when changing the object color map several times


Doesn't seems related to a peculiar map , but  too change too much object color maps (maybe too much too quickly ? )
Maybe the memory used for the first change is not fully released before a second command come and so on and on till the crash ?

P.S .

I am very interested to the lighs there is some documentation  ?(i.e.on the difference between the various coloring options, how map are used and similar )

again, again when changing map

2 changing map x position

oopps here numbers seems the same

Ok, thank you.
The address seems to have changed in my current version.
So it would be cool if you could test an updated version, teling me the new message if this bug still exists.
If you like to, send me an email address in a prvate message, then i send you the update.

sure ...check your PM

I think i already catched the issue, it is indeed not my fault but a bug in the pngimage unit when drawing a transparent png onto a bmp!
(but i will still send it to you for testing, because my transparent png doesn't created an error)

So if i remove the alpha channel or i convert to jpg everything should work ?

anyway i sended you my mail , i may even test on 2 OS (7 for the laptop, xp for a older desktop )

I try to send it to you again, because g..-mail does not accept executables in the zip file (rename the .bin to .exe).

Of course you could test it with different map graphic formats, bmp is also allowed in the current version.

ok checking now my mail

Hy Jesse the new binary you send me solved..more exactly being more verbose helped to find the culprit

For some reason seems that a few maps had something wrong with the header, even if other programs (gimp, xnview )
open and display them with no problem

Anyway solve was easy as open again in xnview the maps causing the error messages  and save them again

even more cool the fix worked in real time without requiring reloading MB3D.

It is  weird that gimp could open all them without problem, but is normal for xnview that somehow may open almost all graphic files even those without or with a wrong extension, or with problematic headers

Ok, but please send me one png file that does not work in m3d.
I have to use this, maybe somewhat old, png unit for some more time and it would be good if can fix this.

Thanks for helping!

Ooopss i didn't think to save them (i mean to copy before fixing them because the "fix" was just open the file in xnview and save again) BUT i made so much maps that is very probable that i would stumble again on some still giving errors.

and in case (again is very probable) i will remember to send you

FOUND 1 !
and found where was the problem the image is fine but its thumbnail was screwed up

And if MB3D can't show the thumb then refuse to use the image

OOPSS i can't put here as attachment is too big even if zipped i will send by mail..but again the culprit is the screwed up thumbnail, resave the image recreate the thumb and that fix

not sure if you can do something from your side

The problem with the file you send me is, that it is no png file, just a gimp xcf file that you renamed  :dink:
No program i tried could open it except gimp itself, that looks inside what filetype it actually is.

So, no real bug in m3d because it tells you that this file is corrupted, at least in my test.

ahh..weird !...may even happen once but strange i did with several files


i will check better in case happens again