Cobalt Neutra

Trying to wrap my head around rigged avatars, using SLAV, with Max 2011. Am on the beta grid, in sandbox 4, using Second Life 3.0.0 (238864) However, upon attempting to import anything expored from max with a rig attached, the "calculate upload weights & fee" button vanishes the moment I click the "skin weight" button. Is this a bug, or a "feature"...?

To be fair to the Lindens, it is a sandbox region. You shouldn't expect to be able to leave things sitting there for hours on end without them being returned. Check your Lost & Found folder.

I did a JIRA. Feel free to add to it if need be. https://jira.secondlife.com/browse/CTS-686

Just downloaded the latest mesh beta client update. It instacrashes on login.

"Those SL creators are a hideously crafty bunch and it is hard to anticipate what deviltry they will conjure up to get around limits." But y'know - we shouldn't have to. We shouldn't have to look for some hack, that gets us around lousy implimentation. With the roll-out only weeks away, things are not looking good for the mesh revolution. After seeing how prim cost has risen on the beta grid, I'm actually finding myself more excited by the prospect of up-to-64 meter prims on the main grid, than I am by mesh objects being introduced there - because it looks like when mesh finally is implimented, it'll be so cripped by cost as to be worthless. Numbers that don't add up. Prim costs that skyrocket if you attach prims to each other. The current setup seems like some passive-agressive attempt to punish users for daring to use it. I'm almost starting to wonder if an executive decision hasn't been made to maintain the status quo at all cost.

" If you make the lowest very low, you have a good chance to bring the cost significantly down." I'd add to that thought, another - Considering that the lowest LOD isn't likely to ever be seen, as it's called primarily when the object is at such extreme range as to be little more than a pixel dot, it's safe to make your lowest LOD out of practically nothing.It doesn't have to even be the same shape as the object in question. The only limit is that you need at least one face for every texture area you want to use. If you have five textures, you have to have at least five faces.

Ok, so there is something more that needs fixing, than just telling the server to allow the larger size prims.Thankye.

Thank you! That works great. Yeah, i was a little leery of the dataserver nonesense, but the person I was trying to riddle this out with swore blind that was the only way it would work.

I thought these were the forums. It says "Forums > Content Creation > Mesh" on my screen.

Is the code that lets users create prims larger than ten meters so deeply tied to mesh, that it would be impossible to just let us have 64m prims on the main grid, right now? Why are we having to wait for that? I mean, ok - mesh isn't finished. There's still a lot of work to do on it, I get that. I'm not talking about mesh. I'm talking about the stopper that locks prims at ten meters. It doesn't seem like it would be that hard to change the setting from 10 to 64, and be done with it.

I'm trying to write a script that reads lines of text from a notecard into chat, and when it gets to the last line, loops back to the first line, so it ends up in a repeating loop until acted upon by an outside command. So far I've managed to get a script together that reads the text, but I cannot find any way to make it loop. key kQuery; integer iLine = 0; string thenote = "New Note"; default { state_entry() { } link_message(integer send, integer num, string message, key id) { if (message == "Sitting") { kQuery = llGetNotecardLine(thenote, iLine); } if (message == "Standing") { kQuery = llGetNotecardLine(thenote, 9999); iLine = 0; } } dataserver(key query_id, string data) { if (query_id == kQuery) { // this is a line of our notecard if (data == EOF) { llSay(0, "No more lines in notecard, read " + (string)iLine + " lines."); } else { // increment line count llSay(0, data); // delay time between responses llSleep(5.0); //request next line ++iLine; kQuery = llGetNotecardLine(thenote, iLine); } } } }

So.. is simplebot.dae also not going to be made available to the public until the 13th? I keep checking http://wiki.secondlife.com/wiki/Mesh_Walkthrough:_Rigged_Mesh_Upload to see if it's been unlocked yet, and the download link still dead-ends at: ACCESS DENIED It seems that you have tried to perform an operation which you are not permitted to perform. If you think this message is wrong, please consult your administrators about getting the necessary permissions. Even if folks can't try the import function until the 13th, it would be nice if we could get the simplebot.dae file, so we could see how an avatar mesh would need to be put together.

Thanks for posting the log, and the added info about prim usage calculations. I guess I'll have to wait and see if the magic compression calculation can make mesh models usable. 4k seems bizarrely low, though. if I can't import a mesh with the equal number of vertices as a 32 X 32 sculpt, for the same prim usage, then I'm not going to be too thrilled.

If 4k worth of .DAE file is going to equal one prim, then mesh isn't going to be very useful. I just saved a cube to collada format. 5k. Which would make it a 2-prim cube. So, if that's the case, then forget prim savings from using mesh. Mesh would actually use more prims than SL's native building tools. I seriosly hope 4k != 1 Prim. That's asinine.

For the beta testers: got a Q. There are going to be 4 sub models, one for each level of detail, and a collision mesh? Does the vertice weight of all four models count against prim usage, in one big lump? Or does it only use the Hi-res version of the model to calculate that, since really - only one model at a time will be rendered in-world. So like - one object: Hires layer: 1024 vertices Medium res layer: 512 vertices Lowres layer: 256 vertices Collision layer: 256 vertices Will SL calculate that vertice weight to be 2048? Or 1024?

I'm looking forward to getting my hands on Mesh. I really am. I've been a professional 3d Modeler outside SL for well over a decade, now. Being able to bring some of my 3ds experience into SL without having it strained through sculpties will be extremely sweet. I just hope that mesh won't be tied to the 2.X interface. Otherwise, it won't be widely adopted until some third-party client (Hello Phoenix, I'm looking at you) gives it to us, and that could take awhile.