Using lock vertexdata to modify an object, followed by saving the object will cause the changes to be undone.
Try un-commenting the "save object" command:
sync on
make object triangle 1, 0, 0, 0, 0, 0, 0, 0, 0, 0
lock vertexdata for limb 1, 0, 0
set vertexdata position 0, -1, -1, 0
set vertexdata position 1, 0, 1, 0
set vertexdata position 2, 1, -1, 0
unlock vertexdata
position camera 0, 0, -5
rotate camera 0, 0, 0
if file exist("test.dbo") then delete file "test.dbo"
`save object "test.dbo", 1
do
sync
loop
Without the "save object" command you will see the triangle, but with the save object command you will see nothing.
The work-around is to use lock mode 2 when locking the vertexdata.
This is a bug because "save object" should not modify the existing object, regardless of its history.
I remember having similar problems using other commands such as "set object light" after editing vertexdata, but I haven't been able to reproduce them yet.
Windows XP - SP3
GeForce 7900 GS
Tested with U7.5 and U7.7RC7
[b]
