MantisBT - opensim
View Issue Details
0008705opensim[GRID] Asset Servicepublic2020-05-20 13:112020-07-09 18:17
resolvedno change required 
ServerUbuntu 18 mysql
Grid (Multiple Regions per Sim)
Mono / Linux64
0008705: Please see why the textures are not copied.
When converting to fsassets and integrating the old database as fallback, all assets except for the textures are taken over. The textures of the models in the inventory remain empty.
To fix this, I have to save the assets from the fallback and load them manually into the fsasset database.

Please see why the textures are not copied.
No tags attached.
Issue History
2020-05-20 13:11ManniNew Issue
2020-05-26 04:11mewtwo0641Note Added: 0036509
2020-05-26 04:18mewtwo0641Note Edited: 0036509bug_revision_view_page.php?bugnote_id=36509#r9062
2020-05-28 02:57ManniNote Added: 0036518
2020-05-28 05:10tampaNote Added: 0036519
2020-06-02 07:44Ferd FrederixNote Added: 0036524
2020-07-09 18:17tampaNote Added: 0036589
2020-07-09 18:17tampaStatusnew => resolved
2020-07-09 18:17tampaResolutionopen => no change required
2020-07-09 18:17tampaAssigned To => tampa

2020-05-26 04:11   
(edited on: 2020-05-26 04:18)
I have used FSAssets before but have not noticed missing textures (Though that could have very well been that it was falling back on what was already on the database).

For testing, have you tried starting with a blank database, and already configured for FSAssets, and uploading some meshes, individual textures, etc, and checking if they exist?

2020-05-28 02:57   
So I do it very simply:
I am creating a new empty database for fsassets.
I activate fsassets and the FallbackService in Robust.HG.ini.
The FallbackService gets the old things from the old database, but many textures are missing.
I already have this problem with the third grid.

Here is further information: [^]
2020-05-28 05:10   
I would advice to convert this stuff manually instead of using the fallback system, that way you can get rid of the old db as well, free up some space.
Ferd Frederix   
2020-06-02 07:44   
You need to move the data per the instructions. Here is my Help guide:

FSAssets will use the MySQL database to collect the original data. This will not automatically convert all the old assets to the new service. To convert all assets from the default service there is a Robust console command provided:

 import <conn> <table> [<start> <count>]

The import command expects a database connection string and the name of the legacy asset table to be passed as parameters. The following example shows how to start the import process for a MySQL database. Change the connection details to match your database schema, username and password, or use the DreamGrid default shown here, and copy and paste this into your Robust console:

import "Data Source=localhost;Port=3306;Database=robust;User ID=robustuser;Password=robustpassword;Old Guids=true;" assets

Depending on the size of your existing assets table, the import process will take some time to complete. The optional parameters, start and count allow you to specify the position and number of rows to convert.

A default, blank database will look like this:

R.O.B.U.S.T.# import "Data Source=localhost;Port=3306;Database=robust;User ID=robustuser;Password=robustpassword;Old Guids=true;" assets
Reading data
0 assets imported so far
100 assets imported so far
200 assets imported so far
Import done, 274 assets imported
2020-07-09 18:17   
The built-in conversion should work fine, tested on the default assets it wrote 292 assets, which is normal for current master. Please re-open if needed.