I put this together just now on top of something I made earlier yesterday, just in case it can make some sense of the scaling issue...
If not, just ignore it, but the original project will be on here soon for another reason anyway...
REM CODE BY MRVALENTINE *** AUGUST 16 2012
SYNC ON:SYNC RATE 60 `control the refresh rate
LOAD OBJECT ".\testmap\testmap.x", 1
LOAD OBJECT ".\testmap\testmap.dbo", 2
` I loaded two models as this is actually
` code adapted to one of my projects soon
` to be shared on the forum to diagnose an issue
POSITION OBJECT 1, 0,0,0
POSITION OBJECT 2, 0,0,2000
` position the objects apart for comparison
` not mandatory you could just load one object if you wish
` just position the camera a tad back so you can see it scale
SET NORMALIZATION ON
SET OBJECT TRANSPARENCY 1, 2
SET OBJECT TRANSPARENCY 2, 2
` again this code is from an example so use this if needed
xval=120
yval=120
zval=120
`set variables for the scaling
DO
SET CURSOR 30,70
PRINT "LIMBS"
SET CURSOR 30,80
PRINT "exist:";limb exist(1, 1)
` check for a limb and print its data
IF limb exist(1, 1)=1
SET CURSOR 30,90
PRINT "name$:";limb texture name(1,1)
ENDIF
` get some additional data for the limb
WHILE mouseclick()=1
` Begin a while loop, you could ue others but
` for the purpose of this example I used a while loop
` You could try an IF : ENDIF too
INC xval, 1
INC yval, 1
INC zval, 1
` Incremet the variables prior to applying the scaling
SCALE LIMB 1,1,xval,yval,zval
` pick the limb and apply scaling using the variables defined earlier
WAIT 100
` slow things down a bit, by a 10th of a second
ENDWHILE
` end the while loop, again you could probably use a function to do the above
SET CURSOR 30,30
PRINT xval
SET CURSOR 30,40
PRINT yval
SET CURSOR 30,50
PRINT zval
SET CURSOR 30,60
PRINT "FPS: " + STR$(screen fps())
` Print data relating to the changes and get the screen refresh rate
` This will allow us to also check that our variables are actually incrementing
` Diagnostics are good!
CONTROL CAMERA USING ARROWKEYS 0, 5.5, 5.5
` some basic camera movement
SYNC
` lets see whats happening between loops
LOOP
` close the loop
END
` Some good practice to put this here...
Comments and crits of my formatting welcome
Hope this helps somewhat...
That Mesh idea looks like a sinner too... Any code to support the idea? I would love to test...
