I was checking out the vertices of a PLAIN object made with M1Utils and I noticed that if the size of the object does not exactly match the number of squares then the vertex positions seem to be reported incorrectly. However, if I use
MAKE OBJECT PLAIN 1,32,32,32,32 for example, things seem to line up just fine.
In this example by using the TAB key you will notice that a plain size of 20 using 32x32 squares doesn't match up in 3D space when you cycle through the vertices:
make object plain 1,20,20,32,32
move camera up .8
move camera -.5
set object wireframe 1,1
dim Vx(10000):dim Vy(10000):dim Vz(10000)
lock vertexdata for limb 1,0
Vcount=get vertexdata vertex count()
for c=0 to Vcount-1
Vx(c)=get vertexdata position x(c)
Vy(c)=get vertexdata position y(c)
Vz(c)=get vertexdata position z(c)
NEXT
unlock vertexdata
autocam off
make object sphere 2,.2
position object 2,Vx(0),Vy(0),Vz(0)
sync on:sync rate 25
do
set cursor 0,0
print "Total count: ";vcount
print "X: ";Vx(Tabbed)
print "Y: ";Vy(Tabbed)
print "Z: ";Vz(Tabbed)
print "Tabbed: ";Tabbed
if scancode()=15 then inc Tabbed:if Tabbed>Vcount-1 then Tabbed=0
while scancode()=15:endwhile:position object 2,Vx(Tabbed),Vy(Tabbed),Vz(Tabbed)
control camera using arrowkeys 0,.1,3
sync
LOOP
Is this an actual bug or am I not doing/thinking something correctly?