MAV
It can't access the memory that "doesn't exist" AFAIK but it can try to access memory that it shouldn't access.
Imagine that a wrong object, instead of MAVing out makes it reach out of the array and in... memory occupied by Notepad. Just for an example. Can you GUESS what happens to poor Notepad and what glitches may ensue?! It's unpredictable.
That's not the worst possibility either. Sometimes, a program (probably not in this case) can contain a pointer that points to some specific variable or something, but of course, it actually points directly to memory. When whatever it was in that memory block is deleted, the pointer now points to memory only and should be immediately NULLed, but if the program attempts to do stuff with that pointer instead, unpredictable behaviour may result, as that memory can by now be filled by literally anything. It's far harder to catch (i.e. simple "Access Violation" detector cannot catch it) so it's more vicious to the programmers.
Imagine that a wrong object, instead of MAVing out makes it reach out of the array and in... memory occupied by Notepad. Just for an example. Can you GUESS what happens to poor Notepad and what glitches may ensue?! It's unpredictable.
That's not the worst possibility either. Sometimes, a program (probably not in this case) can contain a pointer that points to some specific variable or something, but of course, it actually points directly to memory. When whatever it was in that memory block is deleted, the pointer now points to memory only and should be immediately NULLed, but if the program attempts to do stuff with that pointer instead, unpredictable behaviour may result, as that memory can by now be filled by literally anything. It's far harder to catch (i.e. simple "Access Violation" detector cannot catch it) so it's more vicious to the programmers.
Rest in peace, Kym. I hardly knew ya.
Rest in peace, Marinus. A bright star, you were ahead of me on my own tracks of thought. I miss you.
Rest in peace, Marinus. A bright star, you were ahead of me on my own tracks of thought. I miss you.
It can't access non-existant memory? Then what does it do when we have a non-existant dialog, or a red arrow pointing to a non-existant area (Level 0) in Wonderland Adventures?Muzozavr wrote:It can't access the memory that "doesn't exist" AFAIK but it can try to access memory that it shouldn't access.
Imagine that a wrong object, instead of MAVing out makes it reach out of the array and in... memory occupied by Notepad. Just for an example. Can you GUESS what happens to poor Notepad and what glitches may ensue?! It's unpredictable.
I don't know much about coding (Only HTML), but I'm going to assume I do and answer my question.
I'm assuming that the whole thing is full of pointers - e.g., signs have a pointer to the correct animation, and the correct dialog, Stinkers have those pointers too, etc. - so each pointer needs to have a file for it (e.g. Red Arrow pointing to level 5 has a pointer to load it, so it needs to exist).
As a result, if the pointer can't find the file in the Data folder (or User Data for WA Editor, for levels), it starts searching for another file by the same name (Like I said, I know nothing about coding, I'm just making a theory), and it Violates the game's Memory Access area, making it give off the MAV and close.
But then, what about Array Index out of Bounds? It's actually something really annoying, I'm trying to make a level in my adventure bigger than 101 (for testing some stuff), except it gives me an Array Index Out Of Bounds error once I increase the size to more than 101.
Once again, I'll assume I know something about Blitz coding and I'll make another theory.
I'm gonna assume that each game programmed with Blitz (or any level editor) has a specific Array of data that states what the game's levels or areas are capable of being. In this case, WA Editor's Array has a maximum Index of 101 (Once again, making assumptions so don't take what I'm saying for fact). However, due to a small code that's out of bounds, the editor itself lets you try to extend the size - or index - to larger than normally allowed, so the Array ends up needing to get the game to close.
Am I right? (If I am I'll be so surprised)
deleted (quadruple-post)
Last edited by Qloof234 on Mon Jan 05, 2009 11:31 pm, edited 1 time in total.
When you can't find a file it's one thing, and when you can't find a memory address it's completely another. In your case you're kinda right.
And the array index is also related to memory. If you COULD go over the array, memory problems would ensue.
And the array index is also related to memory. If you COULD go over the array, memory problems would ensue.
Rest in peace, Kym. I hardly knew ya.
Rest in peace, Marinus. A bright star, you were ahead of me on my own tracks of thought. I miss you.
Rest in peace, Marinus. A bright star, you were ahead of me on my own tracks of thought. I miss you.
A MAV backwards,maybe... Dlcs That picture is pretty weird. At least we can't have it now, since it's 2009 now.duncan wrote:what???tyteen4a03 wrote:VAMmqdar wrote:That would give you a MAV!tyteen4a03 wrote:Delete MAVduncan wrote:MAV has got to go, does anyone have a ida on how to make MAV BLOW UP LIKE A KABOOM!!!!!!!!!!!!!!
