|
Threads
View context
Lol, you know how this process works: First I'll visit the region for ideas, find inspiration photos, note the parts of each that I like, combine those disparate elements into a working plan, build, texture, then create furniture and accessories. But first I have to finish a chapter in my book that's due to my writers group :-)
like(0)
View context
So cool...thankyou! Steep learning curve for me, but you've made it really easy
now waiting for the grid i'm on to update so we can use it.
huge hugs!
liked(2)
now waiting for the grid i'm on to update so we can use it.
huge hugs!
View context
Hi Cyber.
Look up the asset in your robust assets table
select * from robust.assets where id="0977861a-9289-436a-9f48-0e82c16ed0d6";
This will give you the name of the asset, then just do an area search for it (WORLD, AREA SEARCH on Firstorm) then you can EDIT it and sort the script out (in theory)
show asset 0977861a-9289-436a-9f48-0e82c16ed0d6 on the robust console might work as well
Name: [AV]menu
Description: 2018-01-31 08:10:55 lsl2 script
Type: LSLText (type number = 10)
Content-type: application/vnd.ll.lsltext
Size: 19694 bytes
Temporary: no
Flags: Normal
0000: 2A-20-5B-41-56-5D-6D-65-6E-75-20-2D-20-41-6C-6C
0010: 6F-77-20-75-73-69-6E-67-20-70-72-6F-70-73-20-77
0020: 69-74-68-6F-75-74-20-75-73-69-6E-67-20-73-69-74
0030: 74-69-6E-67-20-73-63-72-69-70-74-73-2E-0A-20-2A
0040: 20-28-4F-70-65-6E-53-69-6D-20-76-65-72-73-69-6F
Name: [AV]menumed Console found (see the log4net config file for this executable)!
Description: 2018-01-31 08:10:55 lsl2 script
Type: LSLText (type number = 10)
Content-type: application/vnd.ll.lsltext
Size: 19694 bytes
Temporary: no
Flags: Normal
0000: 2A-20-5B-41-56-5D-6D-65-6E-75-20-2D-20-41-6C-6C
0010: 6F-77-20-75-73-69-6E-67-20-70-72-6F-70-73-20-77
0020: 69-74-68-6F-75-74-20-75-73-69-6E-67-20-73-69-74
0030: 74-69-6E-67-20-73-63-72-69-70-74-73-2E-0A-20-2A
0040: 20-28-4F-70-65-6E-53-69-6D-20-76-65-72-73-69-6F
like(2)
Look up the asset in your robust assets table
select * from robust.assets where id="0977861a-9289-436a-9f48-0e82c16ed0d6";
This will give you the name of the asset, then just do an area search for it (WORLD, AREA SEARCH on Firstorm) then you can EDIT it and sort the script out (in theory)
show asset 0977861a-9289-436a-9f48-0e82c16ed0d6 on the robust console might work as well
Name: [AV]menu
Description: 2018-01-31 08:10:55 lsl2 script
Type: LSLText (type number = 10)
Content-type: application/vnd.ll.lsltext
Size: 19694 bytes
Temporary: no
Flags: Normal
0000: 2A-20-5B-41-56-5D-6D-65-6E-75-20-2D-20-41-6C-6C
0010: 6F-77-20-75-73-69-6E-67-20-70-72-6F-70-73-20-77
0020: 69-74-68-6F-75-74-20-75-73-69-6E-67-20-73-69-74
0030: 74-69-6E-67-20-73-63-72-69-70-74-73-2E-0A-20-2A
0040: 20-28-4F-70-65-6E-53-69-6D-20-76-65-72-73-69-6F
Name: [AV]menumed Console found (see the log4net config file for this executable)!
Description: 2018-01-31 08:10:55 lsl2 script
Type: LSLText (type number = 10)
Content-type: application/vnd.ll.lsltext
Size: 19694 bytes
Temporary: no
Flags: Normal
0000: 2A-20-5B-41-56-5D-6D-65-6E-75-20-2D-20-41-6C-6C
0010: 6F-77-20-75-73-69-6E-67-20-70-72-6F-70-73-20-77
0020: 69-74-68-6F-75-74-20-75-73-69-6E-67-20-73-69-74
0030: 74-69-6E-67-20-73-63-72-69-70-74-73-2E-0A-20-2A
0040: 20-28-4F-70-65-6E-53-69-6D-20-76-65-72-73-69-6F
I did all that, the odd thing was it did not exist. I finally forced it out using mysql workbench. That was the only way. Thank you for your help. I did find it was [av]menu but deleting that file failed to knock it out. So after a tons of queries finding the object in robust.fsassets and in robus.assets, but it had no name and did not exist! It was weird. I finally just deleted the rows, then switched to Xengine from Yengine which seemed to release the script state and let the item go. weird, just weird.
liked(1)
yes and i restarted the grid about 10 times after i deleted it. It was only switching the script engines that finally eradicated it.
liked(1)
View context
I don't mean to offend you... nothing in life is really optional... we're just finishing up how things are going, not just in SL but also in OPenSim... LL isn't currently showing any signs that the rendering will be improved in relation to PBR... If you want to give double the performance for 5% of the result, well, then that's just how it is... But what I don't like is downplaying something.
like(0)
Honestly, I do agree with you RIGHT NOW, in fact, it caused a few issues. *BUT* I'm excited to see where this will go in the future.
like(0)
As long as you give the option to use the non-PBR viewer in the grid... nobody will stop you from experimenting with the PBR... I also hope that the whole thing will get better... but when I read that the next projects are already underway at LL... it could take a very long time. i guess
like(0)
Oh yes I agree. We ofcourse are backward compatible on our grid as far as we can but always looking to the future, we have features like speech to text and text to speech, in world streaming and much more :-)
liked(2)
View context
Why change something if it looked good before... hmmmm... destroy something that is good... so that you can do something in the hope that it might look good. ok so you think ....
like(0)
View context
Yes... just posted about it this morning (I held back yesterday because we only had release candidate out!)
like(0)
View context
There are 2 items in LBSA Plaza that are painted in PBR most all see them as grey. The ones with slightly older viewers.
like(0)