using OS 0.9.1 on Metro

HuHu Everyone.

I've been waiting for a while to use opensim 0.9.1 to support my Metro regions and I'm not seeing any official movement in that direction.  I thought I would just try it myself as I am going to make a server change anyway. 

Several comments mention that 0.8.3 has special stuff just for Metro and I know about some of it in the Region.ini files -- though I think 0.9.1 also implements that now.

What I really need is a list of the things I need to change in 0.9.1 in order to make it work here.  I know several users have it running and I'm hoping you will share your insights.

And thank you in advance.



  • Mareta Dagostino
    Mareta Dagostino
     Member edited April 2018
    Hi Emil,

    the only thing (from resident's perspective) in the Metro edition which will not work on 0.9.x is the "SYSTEMIP" feature in the Regions.ini file. In the original OpenSim a parameter with the same name exists, but it behaves diverse. So, if you have a static IPv4 address, simply insert that real IP instead of "SYSTEMIP". If your provider does not support a permanent IPv4 address, you can use a "dynDNS" service. They give you a permanent subdomain which is automatically connected to your actual IPv4. Then, you can insert that subdomain name instead of "SYSTEMIP".

    Of course, if you use the OSgrid example, you must replace the references to OSgrid with the equivalents of Metropolis. Also Metro has the new groups module and does not need the old "OpenSimSearch" module. But these differences are the same as in 0.8.x.

    Features of 0.9 which need grid support will not work as long as Metro grid runs on 0.8. Region-only features (like physics and scripting for example) work.

    Regards, Mareta
  • Emil_Jannings
    Thank you Mareta for this detailed reply.  I do have an "dynDNS" address and will use it. 

    When you mention the "OSgrid example" do you mean the entire package of OpenSim.exe and the various bin folders that I can download from Osgrid?  Or perhaps you just mean the Regions.ini file.

    I see the Groups module in 0.8.3 Metro addition.  

    I have just moved my Metro regions to a new server and will let that settle down before I try changing the opensim software.  

    Thanks again.

  • Mareta Dagostino
    Mareta Dagostino
    Hi Emil,

    I mean the configuration files: OpenSim.ini, GridCommon.ini, Regions.ini. Eventually (if used and the defaults do not fit) also osslEnable.ini and FlotsamCache.ini. If you load binaries from OSgrid these config files are prepared for OGgrid. You must compare them with the equivalent files from the Metro edition and fix the references to URLs and modules.

    The binaries you can take from the download (which is the most recent if you don't compile yourself) or the old 0.9.0 from .
    I would not recommend 0.9.0, the OpenSim devs have fixed a lot in the last months.

    Kind regards,
  • DeeLisdun

    I got the most up-to-date 0.9.1. sources and compiled them without issue on Windows 10 machine. Uploaded to OpenSuse server, copied the 5 .ini files mentioned above over... and it worked! Not only worked but some persistent stuck attachments on my avatar became unstuck.

    Also, previously, I'd get mono crashes. Bit early to say for sure, but at least so far - about 24 hours - it's been running stable. Possibly a little bit faster than osgrid version too, as it looks like they compiled that with the debug stuff on.

    My changes to  metro defaults are static IP and mySQL.

    So, based on my experience, I'd recommend giving your own compiling a try. I used Visual Studio 2017, some of the guides mention versions that won't work anymore.

    Good luck,
    Thanked by: Pius Noel
  • Emil_Jannings
     Member edited July 2018
    Yesterday I got the latest opensim package from osgrid (05.04.18 - 0.9.1).  I moved the config-include folder from my old metro installation to the new software and also moved my Regions.ini file.  In Regions.ini I replaced SYSTEMIP with my server IP and ran it.  It seemed to take forever on the first go but it ran and is faster and handles teleports really well.  I was having mono 4.8.0 crashes with 0.8.3 and so far 0.9.1 seems much more solid.
    Thanks to everyone who responded.

    p.s. you also will need to set the listener port in OpenSim.ini -- I use 9000 which is the default
  • Manfred Aabye
    Manfred Aabye

    OpenSim 0.9.1 musst du unter Linux Kompilieren dann läuft das besser.

    OpenSim 0.9.1 ist viel schneller als die 0.8.3 Version.

    You need to compile OpenSim 0.9.1 on Linux then it works better.
    OpenSim 0.9.1 is much faster than the 0.8.3 version.

  • Kxirya Weytana
    Kxirya Weytana
    Huhu zusammen,

    eine Sache, die vermutlich auch schon in der 0,8,3 geändert wurde, (oder früher?) ist recht ärgerlich:

    wenn ich per Script Menüs erzeuge, dann durfte bis dato der Nachrichtentext immer 1024 Zeichen lang sein. Seit geraumer Zeit aber meckern viele meiner Scripte, da die Meldungen eben länger sind:  "llDialog: Message longer than 512 bytes"

    Wer hat sich den diesen 'Blödsinn' ausgedacht und vor allem, worin liegt der Grund, etwas an sich funktionierendes zu 'beschneiden'. Wir sind doch hier nicht bei Veräpple, wo die Telefone immer teurer werden und zugleich immer weniger können XD XD :D :D


  • Sheera Khan
    Sheera Khan
     Member edited August 2018
    Huhu Kxyria,

    das wird wohl in ihren Bemühungen, die Scriptsprache möglichst kompatibel zum Original-LSL zu halten passiert sein, denn in SL darf der Message-Text auch nur 512 Bytes lang sein :-( Und dabei sind die Bytes noch nicht mal gleichbedeutend mit Zeichen: da heutige Systeme eher mit UTF-8 arbeiten, benötigen die deutschen Umlaute z.B. sogar 2 Bytes!


  • Kxirya Weytana
    Kxirya Weytana
     Member edited August 2018
    Dann könnte man vllt. in die nächste Version ein osDialog() einbauen, der dann vllt. auch den "Ignore" Button berücksichtigt? XD

    Hab gerade mit mehreren Leuten abr noch einen offensichtlichen Fehler gefunden:
    Wenn jemand die Gruppe wechselt oder keine Gruppe anlegt, wird in dessen Profil (wenn ich es anzeige) immer noch die alte Gruppe angezeigt. Bei ihm selber wird die neue Gruppe angezeigt, aber er behält die Rechte der alten Gruppe.

    Wir haben das mit 3 Spielern getestet und es ist reproduzierbar. Selbst Ein aus- und Einloggen aller Spieler hilft nichts.

    Schaut doch mal, wie das bei Euch ist.

    Nachtrag hierzu:
    Die Scriptfunktion "llSameGroup()" funktioniert, es scheint nur die Anzeige im Profil betroffen zu sein, sowie die damit verbundenen Rechte.

Sign In or Register to comment.


It looks like you're new here. If you want to get involved, click one of these buttons!


© Copyright 2019 - Metropolis Metaversum
All times are GMT