On Oct 11, 2011, at 6:11 AM, Evan wrote: > In CMD I do: Tundra.exe --headless --server --ogrecapturetopwindow > I run the client from Start Menu and connect to 127.0.0.1:2345 and I > get the black screen, no problem. > I then take my .txml file (at E:\RealXtend\OgreMeshTests\) and drag > and drop and go through the motions to add the object.
When working locally, I usually do this a bit diffently: 1) have a dir with my project, with the scene txml 2) open the server by specifying that txml, either: a) doubleclick the txml b) do Tundra --file d:\myproj\myscene.txml Then if need to connect to it in client mode too, start a client with --storage d:\myproj\ option. Nowadays the server can also communicate this storage conf to the client, but iirc it requires setting some additional param to the server. Ali gave the instructions once on irc, --help doesn't seem to doc that, we need to add it there and in some docs I figure. > When I click "Add Content" it just hangs and in the server window I > get a message in yellow "Warning: Server specified the client to use > the storage "System" as default, but it is not a replicated storage!" The procedure above sets d:\myproj\ as the default storage on the server. If you just do plain Tundra.exe without --file or --storage, it uses 'System' storage, which IIRC is the data folder in the program files or your windows appdata or somewhere, not usually the thing that you want anyway. With the way described here, drag&dropping meshes or txml snippets etc. adds the referenced assets (materials, textures) etc. to your project directory automatically. For just building a scene you don't need separate server and client, but can just run Tundra (as what I call) standalone .. if you omit --headless from the server run, it works like a viewer for building (but doesn't get avatars, client side chat ui etc. because those scripts are specified to give the ui in client mode only). Hopefully this clarified something, ~Toni -- http://groups.google.com/group/realxtend http://www.realxtend.org
