"why is it giving me that measage
Its obviously that 1.90 still needs alittle work"
No, it's obvious that you have a bug in your program. :-)
A memory access violation most often occurs when you pass a variable to a function in Blitz which does not contain a valid pointer to an entity, mesh, brush, texture or whatever object it is that function is designed to deal with.
For example, this program might throw up a memory access violation:
sphere = createsphere()
positionentity mysphere, 10, 10, 10
See how I have accidentally used the variable mysphere instead of sphere? Sphere contains the pointer to the sphere, but mysphere is a new variable and just contains the value 0.
This too might cause such an error:
sphere# = createsphere()
positionentity sphere#, 10, 10, 10
Here, I am using a floating point variable to store a pointer/handle to the sphere. That is a no-no. Floating point variables are not designed for holding pointers.
Often, if you turn on debug mode, then when you get that error, the program will stop and bring up the debug window with the line that cuased the error highlighted.
I have been using Blitz for years. It has been my experience that 99% of the time, a crash is caused by an error in your programming, and not a bug in Blitz.
Its obviously that 1.90 still needs alittle work"
No, it's obvious that you have a bug in your program. :-)
A memory access violation most often occurs when you pass a variable to a function in Blitz which does not contain a valid pointer to an entity, mesh, brush, texture or whatever object it is that function is designed to deal with.
For example, this program might throw up a memory access violation:
sphere = createsphere()
positionentity mysphere, 10, 10, 10
See how I have accidentally used the variable mysphere instead of sphere? Sphere contains the pointer to the sphere, but mysphere is a new variable and just contains the value 0.
This too might cause such an error:
sphere# = createsphere()
positionentity sphere#, 10, 10, 10
Here, I am using a floating point variable to store a pointer/handle to the sphere. That is a no-no. Floating point variables are not designed for holding pointers.
Often, if you turn on debug mode, then when you get that error, the program will stop and bring up the debug window with the line that cuased the error highlighted.
I have been using Blitz for years. It has been my experience that 99% of the time, a crash is caused by an error in your programming, and not a bug in Blitz.