ThreadBoard ArchivesSite FeaturesActiveworlds SupportHistoric Archives |
SDK terrain error (Sdk)
SDK terrain error // SdkcotarrJun 6, 2006, 7:39pm
At some point I guess it is just time to sit back and laugh,
I used the SDK to make a call to aw_world_attributes_change(); Look what it did to the terrain, http://leaves.cotarr.net/temp/terrain-error1.jpg http://leaves.cotarr.net/temp/terrain-error2.jpg http://leaves.cotarr.net/temp/terrain-error3.jpg -cotarr shredJun 6, 2006, 7:53pm
cotarrJun 6, 2006, 8:25pm
more info,
I think this is a browser issue. If I leave the world and return, I can still see the effect, but if I delete cache and then return the effect is gone. It's not actually in the server database, it's in the cache. Each time i have reproduced this, the world log contains individual CHANGE ATTRIB entries, each is followed by large numbers of TERRAIN QUERRY. In the world, i can see the sky change color, but then the chat window floods with terrain texture errors with high texture numbers in range of terrain100 to terrain300 not found. [View Quote] >Cotarr managed to reproduce this for me while I was in rratoc. > [View Quote] dr. squailboontJun 6, 2006, 9:33pm
In 4.1, the terrain heights can now be much higher... Therefore, the
type has been changed from "short" to "int". You will also need to set AW_TERRAIN_VERSION_NEEDED. Example C code: http://www.pastecode.com/350 cotarrJun 6, 2006, 10:24pm
Actually, thank you, I was wondering the differences. That will be
useful when I update the build parts of my bot. The error above did not occur during terrain upload. I was changing the color of the sky, but the terrain changed unexpectedly, concurrent with the sky color change. Thanks for the upgrade info. -cotarr On 6 Jun 2006 19:33:57 -0400, "Dr. Squailboont" [View Quote] >In 4.1, the terrain heights can now be much higher... Therefore, the >type has been changed from "short" to "int". > >You will also need to set AW_TERRAIN_VERSION_NEEDED. > >Example C code: http://www.pastecode.com/350 cotarrJun 18, 2006, 8:03pm
This is now fixed in browser build 951.
I can no longer reproduce it with the SDK function calls. Thank you |