This is my personal blog, but hope to also offer a lot of good information of wide interest. This website will contain some mature content, and also LGBT topics, relevant to my life. If you are a minor, or worse, an easily offended adult… kindly hit the back button. Thanks. 🙂
Some of the categories, that are more personal, such as “Changes” are not on the front page. You can find them in the “Categories” widget on the lower, right.
We will start by looking at your video ram available...
sudo glxinfo -B
This will output something like…..
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) HD Graphics (Whiskey Lake 2x6 GT1) (0x3ea1)
Video memory: 3072MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES profile version: 3.2
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics (Whiskey Lake 2x6 GT1)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 3.0 Mesa 19.0.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.0.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
You can see the line: Video memory: 3072MB
So you know that you have at least that much ram…
Usually it is a set fraction of your total system ram.
like 1/5 or 1/4
Next… look for your Xorg log
In Ubuntu 18.04 / Mint 19 /var/log/Xorg.0.logcd ~/your_firestorm_folder <--- change to wherever Firestorm is
cp /var/log/Xorg.0.log . <---- copies to your Firestorm folder
pico Xorg.0.log <---- Now we edit and falsify the log!! :)
Look for a line that looks like this…
5.234 Intel(0): Memory: 262144 kBytes
this can be any number really….
...change it to
5.234 Intel(0): Memory: 4194304 kBytes
This is a nice round number. 4gb.
Firestorm will then give you half / 2gb
* if that line does not exist.. Just paste the line above anywhere.. it should work.
control-X (to save and exit)
Now we will alter your Firestorm startup script.
This will need your password for sudo.
enter editor then make the first lines….
echo yourpassword | sudo -S cp ./Xorg.0.log /var/log/Xorg.0.log
(control-X save and exit)
When you start firestorm, this will copy your fake,
counterfeited, sneaky, lowdown log , over the system log..
and fool Firestorm into thinking you have a really sexy video card.
This is just a quick test. I indexed 600+ dance animations in OpenSim, and made them searchable on the web server. This one just returns a random search match, and sets your avatar dancing. Eventually we’ll have a really nice club board and you can have lists of your favorite dances.. A list of matches for “Disco” or whatever you are searching for.. And have it in a wiki type format where people can help describe the dances better, and add single word search tags like sexy, slow, hiphop, rock etc…
At this time. This only will work on Nani OpenSim. The standard one will not allow UUID’s to be used in place of animation names. A fairly easy patch may be available soon for other OpenSim versions.
For a lot of people who host OpenSim on a remote or cloud server, or run a grid with multiple region owners. It can be a pain to get OAR files (region archives) uploaded or downloaded from the server. Usually you need an external file manager or FTP server, and a lot of times you really don’t want to casually provide access to that.
I have come up with a scheme to use the Region Terrain upload/download tool, built into Firestorm and other viewers. If you upload an OAR file via the terrain upload tool, it will detect if it is an OAR file and load it onto the region.
To create and download an OAR backup of your region. We have added a chat command /#save oar That will save a temporary OAR file of your region. Then.. you can go to the Terrain Download tool, and it will allow you to download the OAR file you just saved!
The uploads and downloads, using this method are slow. But they are working, and should provide an easy way for your clients to be able to access their regions, if you wish.
There is also a /#load oar chat command that works exactly like the console command. You can quickly load an oar from an external http url, such as outworldz.com or Zadaroo.. a GoogleDrive, or dropbox.. etc.
This is tested/working on our sandbox region, and should be available soon, with everyone’s favorite, alternative OpenSim distro. STAY TUNED! More cool stuff on the way! 🙂