|
|
|
[
Permlink
| « Hide
]
Qarl Linden added a comment - 31/Jan/09 05:33 PM
Aminom - there is a known issue with oblongs failing to load. are any of the sculpts you see "sticking" oblong?
teleported to sculptomancy, and so far, I haven't seen this on 128x128 or 64x64's. Some did seem to load slower than others, but nothing like the problems seen at Dearheart.
I did note that the problem with 256x256 sculpts not loading (which were used extensively prior to May to get around the lossless bug and could only be uploaded losslessly using a third party client) "sticking" seems to have gotten worse. Any chance this will be fixed? Note that 256x256's are a bit less than twice 128's in file size, but often load quicker. Thanks for this report.
Your observations seem correct, that since 1.22 RC6 sculpted textures receive less priority in downloading to the viewer over other textures. This is an effect of a Partial fix we made in RC6 to the issue VWR-8503. We will continue to investigate the sculpt textures which seem to never download at all. Oblong-heavy build that will be broken in 1.22. 3 weeks of development time; almost everything you see is sculpted, and textured, from scratch. What about all the other sculpt designers who use oblongs as well?
Today at Qarl Linden's office hours, I was informed that this bug, which is new in the 1.22 RC, will not be fixed in the final 1.22 client. This is completely unacceptable; it BREAKS CONTENT, and that content will be broken for 3-4 months until a new client is released. We have taken great pains to learn to work with oblongs and have started incorporating them into our work. This is totally unacceptable. It is one thing for the new RC to have bugs; that is to be expected, but with the number of oblongs being produced, a fix must be made before it reaches the general public with the final release. It would be horrid to have to redo the sculpts. This is livelihood of which we speak. We try to move forward and incorporate new features as soon as possible with the expectation that Linden Labs will support us as we support them. This needs to become a priority.
I have spent weeks developing on a project that i will finish early March and almost all sculpts involved are oblongs. This would decimate a project that is costing all involved huge amounts of time and effort to make a reality. If the oblongs fail the project will become an impossibility as its realism would require more normal prims and standard sculpts than we have prims for. As Eleanora so rightly says we 'expect' support on features you promoted and gave us, and as Aminom says, a change in the viewer that you know would break content is unacceptable. We'd all rather stay with the existing client until you have actually fixed it. Bringing it out with a major flaw would be worse.
I was just discussing this with another trainee sculptor using an inworld creation tool. Having been passed their in progress sculpts i can see that inworld tools may also be using oblongs, making newbie sculptors work fail and losing us potential talent when they think they just can't do it
Further notes:
This bug is different than the bug that makes some oblong sculpts staying as spheres. That bug has a pending fix and can be worked around. The bug is experienced by sculpts loading halfway. They will either look "melted" or otherwise partially loaded. Partially loaded sculpts can be corrected sometimes by the following means: 1) relogging (so the sculpt is retrieved from cashe) 2) viewing the sculpt map as a texture (such as opening the edit tab of the object window) 3) camming out and in to force LOD to switch. This also effects some normal sculpts, such as 64x64. Subjectively, this bug seems similar to the lossless bug. Aminom - i've requested that our release team look at this issue. i hope to get an answer to you soon.
I am going to go ahead and chime in my support of this issue being looked into as someone else who is heavily invested in these sculpts. Thank you Aminom for the diligence and I am looking forward to seeing the progress made to rectify this serious issue.
Me too.. this needs to be fixed! Oblongs are very useful... please please
 should be fixed in the next RC. please let me know ASAP if you continue to have problems.
I don't know why or how, but this is completely fixed in RC9. everything loads blazingly fast now.
I'm sorry, but I can't confirm that it's completely fixed in RC 9. If I clear cache, and login in the same region, some of Aminoms trees don't load completely. Only if I relog without clearing cache, let them load fully for me.
@arton, can you supply a SLURL to the sculpts you are talking about?
@Harleen,
I'm sorry, but it was a private region and it is not mine. Cleared cache and logged in another three times now, and all sculpties load completely now. Maybe my problems was in conjunction with this issue? Only thing I know is, three times cleared cache and logged in, some sculpties didn't load fully. Watched them for about 15 minutes everytime. I would recommend to wait a while and see if some others have still problems with this issue. Arton - can you run a test for me on these troublesome sculpts? under the "Advanced" menu is an option "Render->Info Displays->Sculpt". selecting that will display internal data for each sculpt (it will look something like "T0C1V1 64x64", hanging above the prim like settext.)
can you give me the numbers for the sculpts you saw fail to load? The sculpts that failed were all "T0 CO V0 256x256".
But as I said, right now they all load completely, either I clear cache or not. yeah, i suspected. 256x256 sculpt maps are not supported. sometimes they load fully - sometimes you only get 128x128. (which is still to big, the max necessary size is 64x64.) and to be fully clear here - we've never supported 256x256.
sorry... I cleared cashe and relogged many times. From what I can tell, every officially unsupported 256x256 that I use loads properly.
Yes Qarl, I know. Unfortunatly, the bigger the sculpt map, the faster the loading. It, would be great if 64x64 would load faster than even 128x128. That's why I made my sculpts 64X64, because I hope one day they will load faster than the bigger ones.
And some time ago, 256X256 was the only size that load reliably. I think there is lot's of content out there wich uses that size. You know, for sure. oofa. so long as you guys understand that they're not supported - so if you have problems with them loading again - we won't fix them.
about them loading reliably - i don't believe that's true. the code which requests only 128x128 has never changed. The original description should now be fixed in RC9. Please now download the Release Candidate 1.22 RC9, as it includes a bug fix to the code, where sculpts were not always properly being prioritized as expected.
We believe the performance regression that began in RC6 is now solved in RC9. Thanks again for reporting this! Qarl,
English is not my native language and I keep my sentence most of the time to short and my explanations are not that clear as they should be. I;m sorry for that. I have no problem to eccept that 256x256 will be not supported and the Info Display>Sculpt come in real handy to see what size a sculpty use. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Major
Sculpts either load extremely slowly or fail to load altogether.
