Search the Community
Showing results for tags 'Network'.
Found 3 results
If you want to run LNM on a remote computer: There is no need to share the scenery library or files of any simulator on the network. Neither do you have to copy the simulator scenery library nor do you have to install a second simulator on the client. You load the scenery library on the flying computer and then copy the scenery database to the remote/networked/client computer. Nothing else is to do on the remote computer. The copied file is read-to-use. Do not forget to exit Little Navmap before copying a database. Below is a copy of the related chapter in the manual. The linked chapters explain everything in detail. 5.2. How to run a network Setup See the two chapters below if you like to run Little Navmap in a networked setup using one computer for the flight simulator and one computer to run Little Navmap. Connecting to a Flight Simulator Running without Flight Simulator Installation How to prepare a network setup: Install/extract the whole Little Navmap archive on the flying and network computer. Copy Little Xpconnect to the X-Plane plugins directory if you use X-Plane. Use Little Navmap to generate the scenery database on the flying computer. Main menu -> Scenery Library -> Load Scenery Library ... Open the database directory using Scenery Library -> Show Database Files. Copy the database files to the network computer. Quit Little Navmap before copying. Flying in a network setup: Start the simulator Start Little Navconnect on the flying computer. Run Little Navmap on the network computer. Connect Little Navmap on the network computer to Little Navconnect on the flying computer. Main menu -> Tools -> Flight Simulator Connection ... See links above for detailed instructions.
Hi, has anyone got Voxatc 7.41 running over network? I tried that but with no success. All status-bars were green and the files have been sent to the server computer when i ran it the first time. When i have clicked the "enable" button inside the Voxpanel, nothing happend. And when i have clicked the "disable" button, the Voxserver crashed. The windows eventlog shows a side by side error id 33 in the .net environment. I tried that on different pc´s. The behaviour is similar at all. On one pc the voxserver crashed a few seconds after pressing the enable button with the same entry in the eventlog. For me it seems to be a general problem with the software. I tried to get support by Voxatc, but i got no answer. Has anyone got Voxatc running over a network or can someone try this. This will take 10 minutes and can be done also on one pc. Jürgen
I have a small private network at home connecting 2 PCs via a BT hub. I can see one of my PCs on the network schematic, but not the other. It appears that I have 3(?) names networks (don't ask me how this happened … lost in the mysteries of time). These are Ethernet, Ethernet2, and Ethernet3 all Private Network. Now my main PC connects to Ethernet2 and the other to Ethernet and I believe that this may be the fundamental reason why I can only "see" one PC on the schematics. It did seem that the old "Homegroup" facility was able to overcome this issue to a large degree. I can see a facility "Network Reset" does anyone have any experience with this as it seems a drastic action. I do use the applications (AS16, AH2) on one to pass data to the other so a rock solid network is important to me. I hope someone can help. Peter