Re: [realXtend] Content not loading on Localhost
If you are headless and in windows it will pick null renderer instead of dx9. It prints the selected plugin to the console too, so you can be sure. We use same server OS and null renderer and it works fine. The machines we are using dont have graphics cards and you dont need a proper GPU. Just be sure latest directx 9 is installed (the msi installer should have suggested it if you dont). You still need directx installed even if null renderer is used, heck even if you dont load dx9 plugin at all. This is because we link to it in OgreRenderingModule for the dx blitting, its kind of unfortunate. If you want to build non-dx requiring Tundra, you can switch DIRECTX_ENABLED to 0 in the main CMakeLists.txt before building. Also if you are --headless meshes should not even be loaded to ogre at all. They get null factories assigned to them and they are just "ignored" after the asset download is completed. So I dont know how meshes could cause the crash. Null renderer also fakes ogres rendering plugin system in a way that (afaik... hmm) it never puts anything to the GPU, just reserves and frees memory blocks (not in the gpu) when asked. Best regards, Jonne Nauha Adminotech developer On Tue, Oct 11, 2011 at 5:07 PM, Toni Alatalo wrote: > On Oct 11, 2011, at 4:43 PM, Warren Sheaffer wrote: > > When installing Tundra on a Windows 2008 server with a very marginal > (on-board) graphics card we hang-up. I was wondering if the server needed a > graphics card when starting Tundra in "headless" mode. It appears that it > does due to issues we have with it hanging when attempting to load an Ogre > mesh. > > > You could test what happens with the NullRendering plugin. > > I suppose you are already running with --headless? > > The Ogre rendering plugin used can be configured in Ogre's plugins.cfg, > which by default apparently looks like this: > Plugin=RenderSystem_Direct3D9 > #Plugin=RenderSystem_Direct3D10 > #Plugin=RenderSystem_Direct3D11 > Plugin=RenderSystem_GL > Plugin=RenderSystem_NULL > > Perhaps commenting out others and leaving just NULL will make it use that. > The null plugin has basically just stubs for the Ogre things so doesn't do > (much) with gpu. I'm on mac now where don't have it built so can't test, I > think the Admino hosting system (used e.g. for the public > www.realxtend.org demo) uses the null renderer (Jonne has configured > that). > > Warren > > > ~Toni > > On Tue, Oct 11, 2011 at 1:34 AM, Jonne Nauha wrote: > >> This is how I usually work with Tundra. I usually use both server >> (headless) and client as I most of the time need them both to make stuff :) >> >> Open cmd prompt and go to your install location. >> >> Tundra.exe --server --headless --protocol udp --file >> E:/RealXtend/OgreMeshTests/yours.txml >> Tundra.exe --config viewer-browser.xml >> >> Host: localhost:2345 >> Name: something >> Check UPD >> >> As Toni said the storages should be trasferred to your client from the >> server. If not and you get "could not request asset" errors. Try running the >> client with added "--storage E:/RealXtend/OgreMeshTests". >> >> For the original problem if it hangs after you try to add your txml >> content it must be hanging when copying the assets under >> /data/assets (you could look if it copied anything there >> successfully). I dont recall the security model for XP but I make the >> default local storage /data/assets writable for all users to >> avoid this kind of thing from happening to everyone on vista/win7. It's a >> little bit of a problem always to write in the install dir, we should not do >> it. But if you install Tundra with the idea you are going to host stuff you >> should be a admin or know how to run stuff as admin so you wont get things >> like this. We should propably move the default asset storage to >> %appdata%/Tundra/assets imo and we propably will in some future release. In >> the meanwhile if windows is giving you a hard time you can try to install to >> eg root of C:\ as its the not governed by windows as program files might be. >> Again I dont really remember how XP works that well and the rex devs dont >> really regularly test things on XP. >> >> Keep us posted how it goes. >> >> Best regards, >> Jonne Nauha >> Adminotech developer >> >> >> >> On Tue, Oct 11, 2011 at 8:42 AM, Toni Alatalo wrote: >> >>> 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 m
Re: [realXtend] Content not loading on Localhost
On Oct 11, 2011, at 4:43 PM, Warren Sheaffer wrote: > When installing Tundra on a Windows 2008 server with a very marginal > (on-board) graphics card we hang-up. I was wondering if the server needed a > graphics card when starting Tundra in "headless" mode. It appears that it > does due to issues we have with it hanging when attempting to load an Ogre > mesh. You could test what happens with the NullRendering plugin. I suppose you are already running with --headless? The Ogre rendering plugin used can be configured in Ogre's plugins.cfg, which by default apparently looks like this: Plugin=RenderSystem_Direct3D9 #Plugin=RenderSystem_Direct3D10 #Plugin=RenderSystem_Direct3D11 Plugin=RenderSystem_GL Plugin=RenderSystem_NULL Perhaps commenting out others and leaving just NULL will make it use that. The null plugin has basically just stubs for the Ogre things so doesn't do (much) with gpu. I'm on mac now where don't have it built so can't test, I think the Admino hosting system (used e.g. for the public www.realxtend.org demo) uses the null renderer (Jonne has configured that). > Warren ~Toni > On Tue, Oct 11, 2011 at 1:34 AM, Jonne Nauha wrote: > This is how I usually work with Tundra. I usually use both server (headless) > and client as I most of the time need them both to make stuff :) > > Open cmd prompt and go to your install location. > > Tundra.exe --server --headless --protocol udp --file > E:/RealXtend/OgreMeshTests/yours.txml > Tundra.exe --config viewer-browser.xml > > Host: localhost:2345 > Name: something > Check UPD > > As Toni said the storages should be trasferred to your client from the > server. If not and you get "could not request asset" errors. Try running the > client with added "--storage E:/RealXtend/OgreMeshTests". > > For the original problem if it hangs after you try to add your txml content > it must be hanging when copying the assets under /data/assets > (you could look if it copied anything there successfully). I dont recall the > security model for XP but I make the default local storage > /data/assets writable for all users to avoid this kind of thing > from happening to everyone on vista/win7. It's a little bit of a problem > always to write in the install dir, we should not do it. But if you install > Tundra with the idea you are going to host stuff you should be a admin or > know how to run stuff as admin so you wont get things like this. We should > propably move the default asset storage to %appdata%/Tundra/assets imo and we > propably will in some future release. In the meanwhile if windows is giving > you a hard time you can try to install to eg root of C:\ as its the not > governed by windows as program files might be. Again I dont really remember > how XP works that well and the rex devs dont really regularly test things on > XP. > > Keep us posted how it goes. > > Best regards, > Jonne Nauha > Adminotech developer > > > > On Tue, Oct 11, 2011 at 8:42 AM, Toni Alatalo wrote: > 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 > specif
Re: [realXtend] Content not loading on Localhost
Hi Guys, When installing Tundra on a Windows 2008 server with a very marginal (on-board) graphics card we hang-up. I was wondering if the server needed a graphics card when starting Tundra in "headless" mode. It appears that it does due to issues we have with it hanging when attempting to load an Ogre mesh. We have a 32-bit install of Windows 2008 server, and are attempting to install Tundra 2.1.1 from the installer program (msi) download. It starts up fine until we get to the codes loading the Ogre mesh. We do not see this behavior on our workstations. Thanks in advance. Warren On Tue, Oct 11, 2011 at 1:34 AM, Jonne Nauha wrote: > This is how I usually work with Tundra. I usually use both server > (headless) and client as I most of the time need them both to make stuff :) > > Open cmd prompt and go to your install location. > > Tundra.exe --server --headless --protocol udp --file > E:/RealXtend/OgreMeshTests/yours.txml > Tundra.exe --config viewer-browser.xml > > Host: localhost:2345 > Name: something > Check UPD > > As Toni said the storages should be trasferred to your client from the > server. If not and you get "could not request asset" errors. Try running the > client with added "--storage E:/RealXtend/OgreMeshTests". > > For the original problem if it hangs after you try to add your txml content > it must be hanging when copying the assets under /data/assets > (you could look if it copied anything there successfully). I dont recall the > security model for XP but I make the default local storage > /data/assets writable for all users to avoid this kind of thing > from happening to everyone on vista/win7. It's a little bit of a problem > always to write in the install dir, we should not do it. But if you install > Tundra with the idea you are going to host stuff you should be a admin or > know how to run stuff as admin so you wont get things like this. We should > propably move the default asset storage to %appdata%/Tundra/assets imo and > we propably will in some future release. In the meanwhile if windows is > giving you a hard time you can try to install to eg root of C:\ as its the > not governed by windows as program files might be. Again I dont really > remember how XP works that well and the rex devs dont really regularly test > things on XP. > > Keep us posted how it goes. > > Best regards, > Jonne Nauha > Adminotech developer > > > > On Tue, Oct 11, 2011 at 8:42 AM, Toni Alatalo wrote: > >> 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 >> > > -- > http://groups.google.com/group/realxtend > http://www.realxtend.org > -- Warren Sheaffer 651-699-5006(h) 651-261-6669(c) -- http://groups.google.com/group/realxtend http://www.realxtend.org
Re: [realXtend] Content not loading on Localhost
On Oct 11, 2011, at 11:17 AM, Jonne Nauha wrote: > working directory). I can tell you that if my msi installers would not grant > full write to /data/assets for all users you would never be able > to drag and drop and copy assets in there without running as admin in > vista/win7, as said i dont know how XP really works in yep, i just meant that is good to do as instructed in this thread, use some other dir (e.g. d:\myproject\ ) for data. then AFAIK don't need admin rights. > Jonne Nauha ~Toni > On Tue, Oct 11, 2011 at 9:42 AM, Toni Alatalo wrote: > On Oct 11, 2011, at 9:34 AM, Jonne Nauha wrote: >> Tundra.exe --server --headless --protocol udp --file >> E:/RealXtend/OgreMeshTests/yours.txml >> Tundra.exe --config viewer-browser.xml >> As Toni said the storages should be trasferred to your client from the >> server. If not and you get "could not request asset" errors. Try > > ok so the storage config transmit from server to client just works, as you > don't need --storage for your viewer start? goodie, thanks for info! > >> It's a little bit of a problem always to write in the install dir, we should >> not do it. But if you install Tundra with the idea you are going to host >> stuff you should be a admin or know how to run stuff as admin so you wont >> get things like this. We should propably move the default > > i don't think running as admin is needed really, at least on linux never do > that when hosting servers :p (nor on windows for that matter) > >> a hard time you can try to install to eg root of C:\ as its the not governed >> by windows as program files might be. Again I dont really remember how XP >> works that well and the rex devs dont really regularly test things on XP. > > i actually always test at least releases with XP at home (on an ancient > celeron laptop with integrated intel gfx -- my measure for 'if it runs here, > it runs everwhere' .. and tundra does :) > >> Jonne Nauha > > ~Toni > >> On Tue, Oct 11, 2011 at 8:42 AM, Toni Alatalo wrote: >> 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 >> >> >> -- >> http://groups.google.com/group/realxtend >> http://www.realxtend.org > > > -- > http://groups.google.com/group/realxtend > http://www.realxtend.org > > > -- > http://groups.google.com/group/realxtend > http://www.realxtend.org -- http://groups.google.com/group/realxtend http://www.realxtend.org
Re: [realXtend] Content not loading on Localhost
You dont need to be admin on linux, of course if the deb has been made correctly (or I dont even think you need to think about this stuff even in a deb). If you work with a local dev build, not ofc you dont need to worry about it. For windows these kind of things unfortunately needs to be taken into consideration. We should never in the first place try to create/modify files in the install directory. This is problematic on windows as program files write access is limited for a normal user (hence saying you should run as admin). We had this same problem back in Naali, many people complained about the app crashing on starup (we wrote some stupid config files to the working directory). I can tell you that if my msi installers would not grant full write to /data/assets for all users you would never be able to drag and drop and copy assets in there without running as admin in vista/win7, as said i dont know how XP really works in that sense. I have done this write permissions since Tundra 1.x and will continue to do so until we move all writes from the install dir. This would not include cases when the user explicitly wants to do --storage there, that is his choice then and he needs to know the write access to the folder he is using. But as long as we default to /data/assets as the local storage things are more complicated as you can see from the reports we get now here. As said you should install to C:\ root or something to prevent these kind of issues from coming up, untill we fix it. I can just smell a windows write permission denied crash here (the bug that was reported my OP) very very strongly :) Cant really verify just gave my tips to try and go around it for now. Best regards, Jonne Nauha Adminotech developer On Tue, Oct 11, 2011 at 9:42 AM, Toni Alatalo wrote: > On Oct 11, 2011, at 9:34 AM, Jonne Nauha wrote: > > Tundra.exe --server --headless --protocol udp --file > E:/RealXtend/OgreMeshTests/yours.txml > Tundra.exe --config viewer-browser.xml > As Toni said the storages should be trasferred to your client from the > server. If not and you get "could not request asset" errors. Try > > > ok so the storage config transmit from server to client just works, as you > don't need --storage for your viewer start? goodie, thanks for info! > > It's a little bit of a problem always to write in the install dir, we > should not do it. But if you install Tundra with the idea you are going to > host stuff you should be a admin or know how to run stuff as admin so you > wont get things like this. We should propably move the default > > > i don't think running as admin is needed really, at least on linux never do > that when hosting servers :p (nor on windows for that matter) > > a hard time you can try to install to eg root of C:\ as its the not > governed by windows as program files might be. Again I dont really remember > how XP works that well and the rex devs dont really regularly test things on > XP. > > > i actually always test at least releases with XP at home (on an ancient > celeron laptop with integrated intel gfx -- my measure for 'if it runs here, > it runs everwhere' .. and tundra does :) > > Jonne Nauha > > > ~Toni > > On Tue, Oct 11, 2011 at 8:42 AM, Toni Alatalo wrote: > >> 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 separ
Re: [realXtend] Content not loading on Localhost
On Oct 11, 2011, at 9:34 AM, Jonne Nauha wrote: > Tundra.exe --server --headless --protocol udp --file > E:/RealXtend/OgreMeshTests/yours.txml > Tundra.exe --config viewer-browser.xml > As Toni said the storages should be trasferred to your client from the > server. If not and you get "could not request asset" errors. Try ok so the storage config transmit from server to client just works, as you don't need --storage for your viewer start? goodie, thanks for info! > It's a little bit of a problem always to write in the install dir, we should > not do it. But if you install Tundra with the idea you are going to host > stuff you should be a admin or know how to run stuff as admin so you wont get > things like this. We should propably move the default i don't think running as admin is needed really, at least on linux never do that when hosting servers :p (nor on windows for that matter) > a hard time you can try to install to eg root of C:\ as its the not governed > by windows as program files might be. Again I dont really remember how XP > works that well and the rex devs dont really regularly test things on XP. i actually always test at least releases with XP at home (on an ancient celeron laptop with integrated intel gfx -- my measure for 'if it runs here, it runs everwhere' .. and tundra does :) > Jonne Nauha ~Toni > On Tue, Oct 11, 2011 at 8:42 AM, Toni Alatalo wrote: > 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 > > > -- > http://groups.google.com/group/realxtend > http://www.realxtend.org -- http://groups.google.com/group/realxtend http://www.realxtend.org
Re: [realXtend] Content not loading on Localhost
This is how I usually work with Tundra. I usually use both server (headless) and client as I most of the time need them both to make stuff :) Open cmd prompt and go to your install location. Tundra.exe --server --headless --protocol udp --file E:/RealXtend/OgreMeshTests/yours.txml Tundra.exe --config viewer-browser.xml Host: localhost:2345 Name: something Check UPD As Toni said the storages should be trasferred to your client from the server. If not and you get "could not request asset" errors. Try running the client with added "--storage E:/RealXtend/OgreMeshTests". For the original problem if it hangs after you try to add your txml content it must be hanging when copying the assets under /data/assets (you could look if it copied anything there successfully). I dont recall the security model for XP but I make the default local storage /data/assets writable for all users to avoid this kind of thing from happening to everyone on vista/win7. It's a little bit of a problem always to write in the install dir, we should not do it. But if you install Tundra with the idea you are going to host stuff you should be a admin or know how to run stuff as admin so you wont get things like this. We should propably move the default asset storage to %appdata%/Tundra/assets imo and we propably will in some future release. In the meanwhile if windows is giving you a hard time you can try to install to eg root of C:\ as its the not governed by windows as program files might be. Again I dont really remember how XP works that well and the rex devs dont really regularly test things on XP. Keep us posted how it goes. Best regards, Jonne Nauha Adminotech developer On Tue, Oct 11, 2011 at 8:42 AM, Toni Alatalo wrote: > 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 > -- http://groups.google.com/group/realxtend http://www.realxtend.org
Re: [realXtend] Content not loading on Localhost
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
[realXtend] Content not loading on Localhost
So I have Tundra 2.1 installed on my Windows XPsp3 machine at C: \Program Files\realXtend\Tundra 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 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!" -- http://groups.google.com/group/realxtend http://www.realxtend.org
