Hi I am new to blitz3D, I am have problems runing the games that come with the software I updated the program to v198 and the Docs to v188 why are they giveing to so many error. Just to say that all of them. What can I do to fix this?
some help please
Blitz3D Forums/Blitz3D Bug Reports/some help please You could post error messages for better understanding what is going on.. One issue I found when running some samples was that textures were non power of 2 and it made blitz not to load texture and therefore giving some error in debug mode.
Fix for that is to resize textures to power of 2 ie. 256*256, 512*512 etc.
Fix for that is to resize textures to power of 2 ie. 256*256, 512*512 etc.
here is one of the program call wing ring it say
Memory access violation
the debuger say
Pix=ReadPixelFast(x,y)
sorry about that new to this stuff. If you need more please ask I do not know this stuff.
Memory access violation
the debuger say
Pix=ReadPixelFast(x,y)
sorry about that new to this stuff. If you need more please ask I do not know this stuff.
Where are you getting these programs from? I've been through every sample and I just can't find one called "Wing Ring". All I can find is one called Wing Pilot and it works fine.
it's there in "media" folder.
C:\Blitz3D\Media\wing_ring
C:\Blitz3D\Media\wing_ring
Nope, it's not. Must be something they only distribute with new versions.
It looks like a small bug in the program.
There are some loops in the style For x = 0 to ImageWidth(logo).
This is one pixel too many. The upper limit should be ImageWidth(logo) - 1.
Likewise for ImageHeight().
The graphics card may 'pad' images, using a slightly larger block of memory, to suit the hardware. Depending on how this is done the 'off by one' error may be harmless, or it may crash with a Memory Access Violation.
There are some loops in the style For x = 0 to ImageWidth(logo).
This is one pixel too many. The upper limit should be ImageWidth(logo) - 1.
Likewise for ImageHeight().
The graphics card may 'pad' images, using a slightly larger block of memory, to suit the hardware. Depending on how this is done the 'off by one' error may be harmless, or it may crash with a Memory Access Violation.