StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Your problem reeks of some kind of corruption: especially that you can write zeroes but not ones - that sounds like you're not writing to where you think you're writing to (either some kind of padding or data that for whatever reason is supposed to zero). Either that or you're simply not supposed to be modifying this data in this way after the voxels are initialised.</p> <p>Do you have all the possible debug checks and guards enabled? The C Runtime can help you out a lot if this is some kind of corruption</p> <p>If you are already running with all debug options enabled, be aware of the following values when debugging:</p> <pre> * 0xABABABAB : Used by Microsoft's HeapAlloc() to mark "no man's land" guard bytes after allocated heap memory * 0xABADCAFE : A startup to this value to initialize all free memory to catch errant pointers * 0xBAADF00D : Used by Microsoft's LocalAlloc(LMEM_FIXED) to mark uninitialised allocated heap memory * 0xBADCAB1E : Error Code returned to the Microsoft eVC debugger when connection is severed to the debugger * 0xBEEFCACE : Used by Microsoft .NET as a magic number in resource files * 0xCCCCCCCC : Used by Microsoft's C++ debugging runtime library to mark uninitialised stack memory * 0xCDCDCDCD : Used by Microsoft's C++ debugging runtime library to mark uninitialised heap memory * 0xDEADDEAD : A Microsoft Windows STOP Error code used when the user manually initiates the crash. * 0xFDFDFDFD : Used by Microsoft's C++ debugging heap to mark "no man's land" guard bytes before and after allocated heap memory * 0xFEEEFEEE : Used by Microsoft's HeapFree() to mark freed heap memory </pre> <p>If you see any of these values being used in place of valid data, something's gone wrong</p> <p>EDIT: Also, something difficult to ascertain from your question: Is there just voxel data or is there other supporting data - e.g. indices or colour/texture coords of some kind? If writing 1s enabling the children crashes, is it actually that drawing them causes some other data to be used/required? (that for some reason isn't available). Do you get the same crash if you first disable a child writing zero and then later <em>re</em>-enable it? Or do you only get crashes from enabling children that didn't exist at all previously?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload