Hi Antti, First off, thanks for your and your team's work on realXtend. It's greatly appreciated and without your hard work there would be no business concept at all for me and the vision I have on the architectural application for Virtual Worlds. For that I am insanely grateful.
Now, I'll chime in with a few pet peeves of mine, maybe some more will follow later on: -MATERIALS OF MESHES ARE NOT SAVED WHEN TAKEN TO INVENTORY AND RE- REZZED (Capitalized, super-important. Materials are also not saved when your object crosses a region border (i.e. reverts to blank) -Names are often not remembered in the REX tab. The applied model name shows as <unknown> when there obviously is a model applied -OGRE rendering of prims and (I think mainly) textures on prims being slow (this is really important, but you already knew that. I can understand not fixing this as it may just be unfeasible) -Not able to put stuff like 3d models, material scripts and some other things in other folders than where they are uploaded. This is extremely annoying when working with higher quantities of data that need to be organized -Add a big button somewhere that lets you switch between rex-mode and SL-mode instead of having it be some obscure feature nobody seems to know about -Options to scale the client for performance (instead of scaling the sim with draw distance and maybe LOD, though I haven't gotten that to work right either) -Think some more about general opensim compatibility. I realize that your architecture may be better, but for example when ti comes to authentication it is annoying now and will become increasingly annoying that REX login strings are different. For example, Second Inventory, a really important program if you want adoption from the current VW community, won't work with rex because it is not firstname +lastname+password-style. Obviously the SLinventory ppl can and should make it compatible with REX, but isn't it more feasible for REX to be more compatible with OS instead? On Mar 23, 12:54 pm, Antti Ilomäki <[email protected]> wrote: > We're currently considering our options. As you all probably know, > we're focusing on the new architecture, including an entirely new > viewer and improved authentication / storage services. > > Our internal resources are naturally limited and we are looking to the > community to join in and assist in the production. It has been heart > warming to see all the great conversation on our mailing lists, it > appears that many brilliant people are genuinely interested in what we > are doing. It is also very important to note that we are working for > you guys, one of the important measurements of success for us is how > many interested developers and users we have, so all the feedback and > contributions are vital for us. Thank you for everything you have done > so far. > > I realize that the present realXtend viewer is something relatively > few people are interested in working on for licensing issues. It's > also important to note that fixing certain issues is a lot of work; > one of the very reasons we chose to start building a new viewer was > that creating the features we really wanted was becoming excessively > difficult and time consuming on the current codebase. > > I have many things I would like to see fixed in the present viewer as > well and the NG architecture is still some time away. I would > appreciate your help in deciding what kind of fixes we should focus on > right now, so write down your ideas and let's discuss them in this > thread. Let's see what the community can come up with, find out the > crucial problems and see who, how and when they could be fixed. > Although the progress on the new viewer is quite promising, we don't > intend to just abandon the present one. Then again, this is an open > source project, so if you know people who could help us fix the issues > we find, it would greatly benefit us all. > > So let's hear your thoughts! > > Here's one to begin with: > - The default click & drag function for users with building rights > seems to cause more problems than it's worth. Moving objects could be > done exclusively in a slightly more complicated (push button to grab & > move for example) but far less accident-prone way. > > 2009/3/23 Jani Pirkola <[email protected]>: > > > Dear realXtend, Antti, > > > Modrex seems to advance fast and I am truly excited to see it starting to > > work! Thank you! > > > As Paul Fishwick noted in his new modrex blog, there are new issues that > > need work to be done at the viewer side. I hope it is not DIY, but you guys > > have some plans to make basic fixes. If so, do you have plans or schedules > > already for 0.5 release of the viewer? > > > Best regards, > > Jani --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/realxtend http://www.realxtend.org -~----------~----~----~----~------~----~------~--~---
